When I connect my midi cables to my PC and use Fruity Loops or Mixcraft and I play notes on the Roland Juno D keyboard, some of the notes stick and dont stop playing once released and others are played double i.e they make a sound when pressed and again when i release. Please Help on how to resolve this!!

I don't have any of that gear, but check that an option like "note on/off" is turned on in the MIDI setup menu on the Juno-D. Also check in Logic that it's midi is setup right. Logic could also be receiving sustain pedal MIDI info from the Juno. Anyway, that's all I got.

The name for the notes that don't stop playing is "Dreaded MIDI Drone". It is caused by multiple note on commands and lost "mating" note off commands.

Also read "c." on page 80 regarding buffer length and "choppy" sounds.

If you have the version 1 cable you need to download a driver. The details are at this link:http://www.cme-pro.com/en/news-detail.php?news_id=105

Oh, oh... that is often called the "Dreaded MIDI Drone".

There ccan be more than one causes, however two of those are this:

1. The receiving device either does or does not respond to the note off command or only responds to the note on command with zero velocity, which is also now interpreted as note off. Check the MIDI implementation chart to determine this.

2. Two MIDI commands have merged without using a MIDI merger which makes sure ONLY complete MIDI commands are sent. If the commands are mixed, dreaded MIDI drone is assured.

Simple way is MIDI out from Juno to MIDI in on MPC, then (depending on how you want to work), connect MIDI out from MPC to the in on the Juno. If you do this you MUST turn local control off on the Juno or else you'll get double triggers (internal + msg in from MPC). Now to record sequences on MPC , set MIDI to as track in setup window (on the 2500, this is accessed by pressing MODE then pad 9, then press button under the corresponding tab [on LCD]) then set your MIDI channel by port, meaning if your MIDI cable is physically connected to out A, in your LCD in bottom right corner it will show as follows: 1A. This indicates you are transmitting on MIDI channel 1; port A. Remember, MIDI IS NOT AUDIO!!!!! Since the Juno is a synth and not a workstation, all transport controls are handled by the MPC, that's pretty much it... Hope this helps a little, enjoy!

P.S. Go to mpc-forum.com its THE sh**! They also have links for their e-book I have one for the 2500 and its awesome!!!

You haven't said whether or not you are using a demo ,version of FL. If you purchased they have Lifetime Free Updates here:http://flstudio.image-line.com/documents/lifetimefreeupdates.html If you didn't purchase, try downloading the newest demo version here:http://flstudio.image-line.com/documents/download.html Some features of demo programs become disabled after a certain time period. I don't know if midi device recognition is one of them for this program. Try hooking your keyboard up first, making sure that you have the correct drivers for the keyboard, your USB adapter etc. Then start FL and see if the program lists your keyboard in the midi device list.

Fruity Loops version 4 requires Windows up to version XP.

If you happen to have Vista on your PC, you should probably retrofit to XP as there are MANY compatibility problems with Vista and a lot of the special purpose software.

First thing is to COMPARE the PC requirements against what Fruity Loops says it requires.

Theres a good article at recordingreview.com. If you join which is free you have access to a lot of great information. You can download Midiox to troubleshoot your midi connections etc. Make sure that your transmit channel on your keyboard matches up with the receive channel in your program. Hope this helps.

Unfortunately your model of Casio only has midi in and not midi out. You will be able to use it as an external sound module but not to input notes into Fruity Loops. In other words midi out of your computer to midi in of the Casio with the proper settings will play your Fruity Loops sequences through the Casio.

You are suffering from midi latency. There is a good article about this at www.thewhippinpost.co.uk/latency.htm There is also some good advice there.