Maldi Posted August 18, 2015 Share Posted August 18, 2015 The problem is I can't transfer rhythms and tones through "Data Manager v2 " because everytime I try, an error called "Midi Timeout" stops me, but the cable works perfectly through the program "One Man Band". I try in "Windows XP", too. Can you please help me? Quote Link to comment Share on other sites More sharing options...
Jokeyman123 Posted August 18, 2015 Share Posted August 18, 2015 Check the next tab called "directory" to see where you are storing your tones and rhythms. Look at the windows "path" to see where on your computer the "musicdat" folder is located-where data manager installed that folder, then make sure your rhythms and tones you want to transfer are in that folder. if that is all good, then check to see which other midi drivers are installed and running when you are using data manager. Sometimes more than one midi driver running in the background will cause this problem. You might need to uninstall another midi driver that is conflicting with the Casio midi driver. It could also be that the driver for your Casio is working a little slowly-the amount of data you are trying to transfer is too much for the memory allocated for midi transfer-called "buffer" memory. Windows establishes this memory allocation automatically and if it fills too rapidly, this is called a 'buffer overflow". Not really a Casio defect, more of a Windows problem as Windows historically has had trouble with midi driver conflicts in my humble experience. Try transferring just a few tones or rhythms at once and see if this works. If this works, but larger numbers of tones or rhythms are not transferring, this could be the problem. Sometimes simply trying to transfer your files again could clear the problem. Windows is supposed to stop one "process" (a midi driver in this case) when another "process" is called up to be active. It doesn't always do this and aside from uninstalling/reinstalling multiple midi drivers, there isn't usually an easy solution in XP. Or in Windows 7 or 8 either. Rebooting the computer might also help. Quote Link to comment Share on other sites More sharing options...
Maldi Posted August 18, 2015 Author Share Posted August 18, 2015 Sorry, but it's not working. I connected the cable in the keyboard, while the keyboard was closed. I plug the USB cable in PC, then I opened the keyboard and the same thing happens. Should I install any driver out of the one which is already installed? Quote Link to comment Share on other sites More sharing options...
Jokeyman123 Posted August 19, 2015 Share Posted August 19, 2015 Maldi-you might want to read this other post with some information from Tnicosno, happyrat (and me) about trying to solve this problem. http://www.casiomusicforums.com/index.php?/topic/7105-wk-3000-midi-driver/ I see from your helpful screenshots looks like you are using the right version of IDES (is it version 2.0?) I also see the driver required for this type of USB to MIDI cable is showing up which is right also. I use the same cables on the XW-P1, th PX350 and my older PX575-the PX575 is similar to your CTK-691. Notice after reading the wk-3000 post, you aren't alone with these driver issues. The WK-3000 and my PX-575 are very close to the CTK-691 in function and design. You may want to try installing the Casio XP driver designed for the later Casio CTKs and PXs here: http://support.casio.com/en/support/download.php?cid=008&pid=73 After reviewing all the info I could find and checking my own equipment, I needed to install this Casio driver in addition to the driver for the USB cable which (should) automatically install from the Windows XP driver database. From your screenshots I can see this USB cable driver is already working and installed but I do not see the Casio driver info. So although this above posted driver does not list the CTK-691 specifically, I am "guessing" this driver may work with your keyboard, and I can find no specific Casio driver for the CTK-691. This may be because as Happyrat posted, Casio never created one because it wasn't supposed to need one. Keep in mind if this solves your problem, as Tnicoson describes-you may still have problems with large files transferring back and forth due to buffer memory limitations. Windows doesn't allocate much memory for transferring MIDI data from computer to music instruments although the Service Pack III built-in drivers seem to at least work. One other thought-Microsoft updated MIDI and USB driver support as part of Service Pack III-support before that upgrade was very poor and often did not work with musical instruments or worked poorly. Make sure you have SP III installed on your Windows machine. I had no end of trouble connecting keyboards to XP with the older Service Pack 1 or 2. Post back whenever you can, let me know how this works out. I and others check in pretty regularly here. Quote Link to comment Share on other sites More sharing options...
Brad Saucier Posted August 19, 2015 Share Posted August 19, 2015 I am going to say it's the midi cable pictured. I bought that same low priced, no name cable as well. I had to return it. It would not work correctly. Some things worked with it, others didn't. I returned it and bought an Emu Xtab 1x1. It has worked perfectly. Quote Link to comment Share on other sites More sharing options...
- T - Posted August 19, 2015 Share Posted August 19, 2015 Brad I think on most of the lower priced USB-MIDI adapters, the manufacturers do not implement data flow control (cost savings), so this results in the buffer overflow condition, described by jokeyman, and results in the "MIDI Timeout" message on file transfers, yet work fine for simple streaming of MIDI song data. MIDI song data is transmitted at a much slower rate than file transfer and bulk dump data. I think those manufacturers just do not envision the user doing something as sophisticated as file transfers or sysex/bulk dumps, so they just provide for the simplest use. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.