Alvein Casio no longer includes the old 5-pin DIN (round) MIDI connectors on their CTK/WK model keyboards. Look at the lower half of Page 3 of your manual for a diagram of the connectors on the back of your keyboard.
Look at Connector #31 (USB). That is now your MIDI connector, commonly known as 'USB-MIDI'.
If you don't have a MIDI controller, head over to the tutorial that explains a way to use the computer keyboard instead. So here's how to set it up: Check if there are any drivers available at the manufacturer's website of your MIDI controller. If so, download and install them first. If it said plug and play on the packaging, you shouldn't have to. MIDI (Musical Instrument Digital Interface) is a standard protocol for inter-connecting computers with musical instruments, stage lighting, and other time-oriented media. Strictly speaking, MIDI is unrelated to audio.
It is bi-directional, so it serves the purpose of both MIDI IN and OUT. It uses what is commonly referred to as a 'standard USB printer' cable that can be found at just about any retail outlet that sells computer equipment/supplies. See Page 32 of your manual for instructions on connecting it to a USB port on your computer. Casio keyboards are now what we call 'Fully Class Compliant' (Windows) and 'CORE MIDI Compliant' (Apple), meaning that they will automatically work with the standard USB-MIDI drivers that have been built into Windows since XP Service Pack 2 and the last several versions of MAC-OS and iOS (iPad/iPhone), so you will not need to install any special drivers. Just connect the cable, power up the computer, then power up the keyboard, once the computer is fully up and running - truly 'plug-n-play'. Then, in any of your software (FL Studio, etc) MIDI set up menus, you will be looking to select a MIDI device shown as 'CASIO-USB-MIDI' or something similar to that.
The 'Audio In' jack you refer to in your post is for connecting the audio outputs of a stereo unit or MP-3 player or CD player, etc for playback through your keyboard's sound system and speakers. It has nothing to do with MIDI.
If you do connect something to the Audio In jack coming from a device's 'Phones Out' jack, start with the connected device's volume at minimum and bring it up slowly, so as not to overdrive the keyboard's Audio In circuits and damage them. The CTK-2400 allows you to record (sample) sounds, but it will not record or sample anything from the Audio In jack. Audio recording (sampling) can only be done with the CTK-2400's own built-in microphone. See Page 35 of the manual for use of the Audio In jack and Pages 11 through 16 for sampling. Best of luck, and enjoy the new CTK-2400.
Also - welcome to the Casio Forums! Hi, I got my CTK-2400 a few days ago and have now downloaded a piano learning app 'Piano Marvel' which should work via MIDI. I connected the piano via USB to my WIN10 laptop and the app recognizes the piano correctly but it does not seem to recognize any keys that I hit.
I tried also another app 'Jalmus' and it also does not recognize any key strokes. Can anybody please give me a hint what I should do? Could this be a Win 10 problem?
Any settings in the piano? Any other app to check the keys? - Edit: Found the solution by myself.
Looks like this keyboard does not work with Win10. Indeed Win 10 is not mentioned among the compatible OS, the highest is Win 8.1 I had hoped that this wouls make it compatible with Win10, too, but no way. Casio does not even offer a newer driver in its downloads. Connected it to a Win7 laptop and now it works. Edited October 2, 2016 by Volker found solution. Volker The CTK-2400 is 'Class Compliant', meaning that its USB-MIDI connection should work with the drivers that have been built-in to Windows, since XP-SP2 (including Win-10). Win-10 is missing from the Minimum System Requirements in the CTK-2400's manual, because Win-10 was not on the market, or just coming on the market, when that manual was written.
There seem to be certain combinations of Win-10, and the hardware that it is running on, that just do not get on well with USB-MIDI, as well as some of the more popular music production software programs. This is particularly the case with newer hardware running USB-3.0 ports. / all?) USB-2.0/MIDI devices do not work well (or at all) when connected to a USB-3.0 computer port, even though USB-3.0 is supposed to be backward compatible.
The trick here is that, if your computer has a both USB 2.0 and 3.0 ports and a USB-MIDI device will not work on the 3.0 port(s), try switching it to one of the 2.0 ports. On a desktop (or tower) PC (even just old USB 2.0) the USB ports on the front are normally 'hub' connected to the system board, while those on the rear are directly connected to the system board. Some USB-MIDI devices do not like 'hubs', so try moving your keyboard connection from a front port to a rear port on those types of systems. What works, and what does not, is a bit of a toss-up, so your Win-7 laptop workaround may have to be your solution, for the foreseeable future, at least.
I am still using an old Win-XP/SP-2 laptop to communicate with my old (non-Class Compliant) WK-3800, because that is the only system I still have that is slow enough to work reliably with it and not cause a lot of communications buffer overflow problems. At any rate, if you would like to pursue your connection between the CTK-2400 and your Win-10 system, I would recommend downloading and installing a MIDI utility program called MIDI-OX, which is, supposedly, compatible with Win-10. If MIDI-OX 'sees' your key presses coming into your Win-10 system from the CTK-2400, then you know that your basic USB-MIDI connection is working. That would put your problem with your apps set ups or an apps/Win-10 compatibility problem.
You can download MIDI-OX for free from: Good luck! Regards, Ted.
Before you can start having fun with your MIDI controller, it needs to be configured in Live - this goes for MIDI keyboards and all sorts of other controllers sending MIDI data. If you bought a MIDI controller that is supposed to be plug and play.
Well, you still need to set it up in Live. Plug and play only means that you don't need to install any drivers for it. If you don't have a MIDI controller, head over to the that explains a way to use the computer keyboard instead. So here's how to set it up:.
Check if there are any drivers available at the manufacturer's website of your MIDI controller. If so, download and install them first.
If it said plug and play on the packaging, you shouldn't have to. Connect the controller to your computer. Most controllers use USB connections these days, so plug in the cable on both ends. Don't connect it through an unpowered USB hub (this might really mess up the MIDI data stream), but either a self-powered hub or directly to the USB port of your computer.
Some controllers need to be connected to a power source and turned on. Older controllers only use MIDI ports, some offer both options. If you want to send MIDI to and fro, make sure you connect MIDI input and output of your device to the MIDI output and input of either a MIDI interface or an audio interface with those connections available. Now open Live and go to the Live Preferences MIDI/Sync (Cmd +, on a Mac; Ctrl +, on Windows computers). Control Surfaces are available for the most commonly used MIDI controllers. If this is the case for your controller, choose the Control Surface for it as well its Input and Output. This will enable instant mapping.
If it's a keyboard, also turn on Track for its Input under MIDI Ports. If Input and Output are shown in reddish, Live cannot detect the device (unplugged, off, broken driver). Some controllers require a preset dump. If so, the 'Dump' button becomes enabled.
Make sure your controller is ready to receive the preset dump. If you're unsure how, check its manual for instructions. Then press 'Dump'. If there's no Control Surface available for your controller, ignore the upper part in the MIDI/Sync tab. You'll have to set it up under MIDI Ports instead. Don't despair though, it's not rocket science!.
To use your controller to play notes (i.e. Keyboard, drum pads), enable the Track button for the device's input. To use your controller to adjust device parameters, enable its input's Remote button. If it sends visual or physical feedback, the Remote button of its output needs to be turned on as well. Controllers without a Control Surface for which you've enabled the Remote button, need manual mappings to be used.
Turn on MIDI mapping by clicking on the MIDI button in the upper right hand corner of Live or choose Cmd + M (Mac) or Ctrl + M (Windows). Everything that's mappable will now be displayed in blue. Click on the parameter you want to control, then move the knob/fader or hit the key/pad on your device you want to control it with. Repeat the steps with whatever else you want to map. In the Browser (left) you will see the MIDI mappings you made. You can set the Min and Max for the parameter if available. Once finished, click on the MIDI button again.
You can also manually map controllers that do offer a Control Surface. Then simply set them up as if there was no Control Surface available and map the controls as desired. Quick tip: If there's no Control Surface for your controller officially available, there's still the chance there's an user created one.
Quite a few nifty users have written their own MIDI remote scripts (a.k.a. Control Surface) for various MIDI controllers.
Do a search for:.name of the MIDI controller. MIDI remote script. This might save you a lot of time doing manual mappings. Of course, if you know or are willing to learn it, you could write your own scripts. The following blog is dedicated to this subject: Happy MIDI controlling in Live!
And of course, if you have feedback or questions, leave me a comment below. There are plenty where this one came from. Nick at Ableton sent me the link to your page.
Very useful, and I located a midi script that shows up in Ableton for my controller. I am using a Behringer FCB 1010 and even with the midi script and an editor I can’t get the thing to workmuch. Switch 3 in bank 0 sends out a note message (c2) and that seems to work, but that’s just about it.
The main, actually only reason that I purchased the fcb1010 is that as a guitarist I want to control the guitar efx with my feet Switch 3 works but nothing else. I have tried it with Amplitube and other plug ins and it’s the same story. Any suggestions would be most welcome. All the best, Helio. Hi Madeleine, This is a great tutorial. However, after following the instructions I am still having the same problem I’ve been having after following every other MIDI hardware instruction list out there (there aren’t many). Here’s what I do: 1) Plug in my MPD26 via USB on Windows 2) Start Ableton Live 8 Lite 3) Open preferences: (i) MPD26 is an unsupported control surface, so I don’t mess with the top (ii) I turn on both Track and Output for the MPD26, and Output for Microsoft GS Wavetable Sync 4) I go to session view and drag “Backbeat Room” MIDI drumset from Impulse into the MIDI slot 5) “Backbeat Room” 2X4 grid of drum components now appears in the Device area (“Kick”, “Snare”, etc.
Each with their own decibal wheels). 6) I click on the MIDI button, click on “Kick,” and hit a pad on my MPD26 7) I can now see the map point in the mappings list. It says: Channel: 1 Note/Control: Note D2 Path: 2-Backbeat Room Backbeat Room Name: Kick Min/Max dB 8) I turn off the MIDI button, to try to play the sound. But when I play it, it plays the tone D2 instead of the drum sound. For some extra info, the MIDI instrument inputs set to Channel 1 from the MPD26. Also, on the screen of the MPD26 it says “NOTE” directly next to the channel indicator.
How do I get it to play the drum sounds instead of (what seems to be) the default tone for the pad? I am using an Alesis QX49 with Ableton Live Lite 8 and my keyboard does not seem to work. II plugged in my QX49 with the USB port and it automatically turned on. Then I open Ableton. I have already copied the MIDI Remote Script to the propper file: Users Peter AppData Roaming Ableton Live 8.04 or your version Preferences User Remote Scripts But once I go to Options, Preferences, MIDI sync, and select QX49 inthe Control Surface, nothing appears in Input (it onlya says NONE).
And in Output, the only option is Microsoft GS Wavetable Synth. And under that, on MIDI ports, it appears only one output option: Output: QX49 Output (Microsoft GS wavetable). The Computer MIDI keyboard works just fine, but the Alesis QX49 keyboard does not work at all.
Please, help! Live has recognised the script, but not really your keyboard (there should be an option for Input both in the Control Surface In as well as the MIDI ports). First of all, you should really update your Live Lite 8 version as it’s outdated and might be (part of) the problem. Updates are free and can be downloaded from your Ableton user account. Please also update the firmware of the Alesis and then install the latest version of the remote script afresh in the updated Live Lite from:. Hope this helps.
Dear Madeleine, I have a problem with connecting my Yamaha CBX-K3 midi keyboard and getting it to work in ableton live 9. I connect the yamaha midi out with a Tascam US-144 and that is the DAW i use in ableton. I tought it was just plug and play.
It does not show up in the list of the midi devices and i tried to download a driver but it asks for a com port and so on and still does not work Do you have any idea if the Yamaha CBX-K3 can work in ableton? Or is it just too old? Thank you, in advance.
![Driver Driver](/uploads/1/2/5/3/125378144/146390336.jpg)
Hello Madeleine, I’m having some serious issues with midi (live input) lag. I’m using Ableton live 9.2.1, 64 bit, on OSX yosemite. Using M-Audio keystation Mini 32 at my desktop.
Komplete Audio 6 as audio interface. There is a huge delay between pressing a key on the keyboard, and getting a sound from ableton. I don’t think it’s an audio card / driver issue: If I use Logic X, or the standalone applications eg NI Battery 4, Pianoteq 5, there’s no delay. Even with exactly the same buffer settings.
When having both Ableton and one of the other programs open, playing the keyboard will immediately generate audio from the other program, half a second later the audio from Ableton will sound. Impossible to do any live input this way. (I currently have to default to pressing a chord on the keyboard, then position it on the piano roll ) I don’t know if it’s related to Ableton live 9.2.1 only, since I started a new project, and made a different template for it. Any idea where I should start looking for a solution? Many thx, Joh PS: I haven’t tested it yet with non-usb midi keyboards yet (my desktop is a bit to far from them at the moment), but that still wouldn’t explain the fact the other programs are doing just fine. OK, will do that.
I already to manage to link the problem to the template I made for the project. Don’t know why, it does contain around 100 channels, but not too many plugins loaded, and the sampler plugins don’t have actual libraries running yet. The strange thing is that it happens to all midi plugins, even the the VERY lightweight ones like Pianoteq 5, so it seems directly related to the Ableton’s (live input) Midi handling.
Shouldn’t be happening, especially since CPU usage only is about 15%. I will let you know the outcome (if they have a solution). Hope so, since all the project songs “backbones” have already been constructed with the specific template (including a lot of master tempo tracks ) Anyhow, thx for the input.