- T -

It is not an easy process, by any means, and more often than not, produces much less than desirable results. Those that have tried have reported widely varying degrees of success, or the lack thereof. You may want to review the following thread: http://www.casiomusicforums.com/index.php?/topic/4281-software-to-create-patterns-for-wk-7500/#comment-14450 This thread deals with the WK-7500, but what is discussed in it applies equally well to the CTK-7000/WK-7500 and CTK-7200/WK-7600. There are also other similar threads. Do a site search on "style conversion" or "rhythm conversion" or "Yamaha style to Casio rhythm conversion", etc. The conversion program described in the above thread was written by a private individual many years ago, when Yamaha style files were much simpler and smaller than they are today. They were all in the Yamaha SFF-1 format and all ended in a ".STY" file extension. More current files end in a myriad of different file extensions and many are in the new SFF-2 format, which must first be converted to SFF-1 by another program, but also contain articulation tones that Yamaha calls "Mega Voices", which will not convert at all. Many, but NOT ALL, that have file extensions other than ".STY" can be simply renamed to have an "STY" extension. So, for the most part, you will be limited to styles from the older Yamaha PSR models, which I think you will find are not on par with the newer rhythms of the new Casio CTK/WK models, but to each his own. Hopefully, one of those who have tried will pop in here and share their experiences with you.

The new CTK/WK-6XXX/7XXX models do, indeed, accept the older Z00 Rhythm files, either in their raw Z00 format, or in their CKF encapsulated format. They can be loaded into User Rhythm memory via the Data Manager 6.1 software or directly on the keyboard from an SD Memory Card. As they are loaded into the keyboard's User Rhythm memory, the keyboard's operating system automatically converts them to the new AC7 format, so that if they are ultimately exported back to a computer or SD Card, they come back as the new AC7 files. The Z00 Rhythm files are the only Z0X files that can be imported from the older models. None of the tone based files are compatible because of vast sound engine differences between the older and newer units. Of course, "ALL" files from the older models can not be imported because of the incompatibilities I have just mentioned. Unfortunately, Casio has never provided a means of converting (porting) Song files from one model line to another. Even though they have offered a software program for converting the CM2 Song files of the CTK/WK models that pre-dated the WK-3XXX units to Standard MIDI Files (SMF) with a .MID file extension, there has never been a means of converting CM2 Songs to Z02 Songs or CM2 or Z02 Songs to the CMS Song format (all three of which are Casio proprietary MIDI formats) of the new 6XXX/7XXX lines. This seems even more curious, when you consider the fact that the CURRENT lower priced (entry level) CTK/WK models (WK-2XX and equivalent CTK models) still use the old CM2 Song file format.

Beginning with the CTK-7000 and WK-7500, the two models are identical in every respect, other than the fact that the CTK-7000 is a 61 key model, while the WK-7500 is a 76 key unit. This similarity now carries over to the CTK-7200 and the WK-7600 - other than 61 keys versus 76 keys, they are identical, so it is just a matter of deciding whether you want/need 61 keys or 76 keys. The current typical price difference is about $100 USD more for the 76 key (WK-7600) model.

What few videos are available on the CTK/WK-6XXX sequencers are really basic - pretty much how to play somerhing and record it the first day you get the keyboard. They do not go into the depth of what can happen when you start merging tracks and things like that. Several years ago, Casio's Mike Martin did a fairly indepth video on using the CTK/WK-7XXX's Pattern Sequencer to create a custom Rhythm, but that is an entirely different animal from what you are dealing with. Right now, you are having problems with sustained notes, but when you start merging tracks with embedded effects and controls, things can turn into a real mess real quick. Your best course is to come up with a workaround for doing what you want without merging tracks to begin with, and this does not affect just the Casio sequencers. What you are running into are sequencer facts of life. Commercially available quality videos covering specific items on specific keyboard models are extremely rare as there is just not that much of a market for them. You might try doing a search on Amazon for books on in-depth sequencer practices. There were two or three back in the mid 90's. With a little luck, maybe there are still a couple of copies lying around somewhere.

Richard I suspect that your problems with items 1 and 2 may be, to a certain extent, related, but to begin with Item 1 by itself: are you turning Auto Accompaniment ON AND pressing the Synchro button before making your first chord ? If not, Auto Accompaniment will not start properly, or at all. As for Item 2, and the possible tie-in from Item 1: When you have Auto Accompaniment in FULL RANGE mode, Auto Accompaniment "parses" the entire width of the keyboard for key presses by both hands to control the Auto Accompaniment, so in that mode, certainly, what you play with your right hand will affect the Auto Accompaniment. That is the whole purpose of FULL RANGE mode, but most players who make extensive use of FULL RANGE will tell you that you need to develop a "knack" in your playing style, so as not to confuse the Auto Accompaniment when playing complex full two-handed classical or jazz chords, particularly with grace notes. Basically you need to learn what you can get away with and avoid what you can not. You need to study the "Fingering Guide" on Page A-1 of the manual for the permissible chord styles. If you use FULL RANGE mode and stray from this chart, you are bound to get into trouble with Auto Accompaniment, sooner or later. For now, I would recommend using one of the FINGERED modes, in partucular, FINGERED 1, and let the Auto Accompaniment set the split point, but make your own legitimate triads and four note chords. That is, do not use the "Easy" or "Casio Chords". If you do this, and still have the symptoms you describe, then you may have a problem with your keyboard, if not, then the problem is most likely what I describe above. Your Item 3 is mostly a matter of semantics. The second paragraph in the left hand column of Page 38 in the manual states "You can edit built-in rhythms to create your own original rhythms . . . .". The key words here are edit and create. In "Casio-speak", you "edit" something that is already there in order to "create" your own "new thing". Many new owners are put off by this topic, when they realize that they have to start with something that is already there, rather than starting with a completely blank slate, and with the Pattern Sequencers in the CTK/WK-7XXX models, even that CAN be done. Mike Martin made a video several years ago about how to do it, but Casio avoids a confrontation on this with their finely engineered "selection" of words. As for you, you can just modify existing rhythms to your heart's content, and you don't always have to start with a factory pre-set. You can start with a User Rhythm that you already modified yesterday, or last week, or last month. So, go to it ! Enjoy . . . . and best of luck ! Sent from my HP laptop.

Johnathon I do not know if you ever found an answer to this, so . . . . . The .ckf files for the older 76 key WK-3000, 3300, 3500, 3800, etc and their 61 key CTK counterparts were distribution files which could contain a single rhythm, a single tone, a single tone with wave, a single drawbar organ tone, etc or any number or mixture of the same. They were sort of a Casio proprietary "zip" file. It was the IDES Data Management Software's job to extract the different file types and install them into the target keyboard's appropriate User Memory areas. Because of the vast differences between the older models' sound engines and those of the newer CTK/WK-6XXX/7XXX models, none of the older tone related files will work in the newer models, but because of the similarities in their Rhyrhm engines, the older Rhythm files will work in the newer models. In particluar, the old .ckf Rhythm files extracted to .Z00 files and the newer models will import either the .ckf file or the .Z00 file, and conversion to the new .AC7 Rhythm format is performed by the target keyboard's operating system as the file is loaded into that keyboard's User Rhythm memory. This conversion occurs whether the file is loaded from a PC by the Data Management Software or directly from an SD Card. That is to say, the "conversion" is done by the keyboard, not the Data Management Software. If, at some later point in time, those files are copied back to an SD Card or brought back up to a PC's hard drive with the Data Management Software, they come back in the new .AC7 format. So, if you wanted to convert a set of old Rhythm files for someone, you need only install them (either .ckf or .Z00) into one of the newer model's User Rhythm memory, and then bring them back to the PC in the new .AC7 format. That is to say, the keyboard is the "converter". I think you would probably find that the new PX models do the same.

Sorry ! I posted a reply in the wrong (this) thread. Please disregard ! See: for the correct thread.

To adjust the overall Accompaniment Volume of the CTK-7000/7200 or WK-7500/7600: Page 133 of the manual starts you out on the very last display page you need to do this, but it does not tell you how to get to that page to begin with. So: Press the FUNCTION button to bring up Page-1 of the -Function- menu. Press the RIGHT ARROW ( > ) button to go to Page-2 of the -Function- menu. Use the UP/DOWN ARROW buttons to select the first item on the list ( Volume ). (It will probably already be selected.) Press the ENTER button once to go to the next display page. Use the UP/DOWN ARROW buttons to select the first item on this list ( AccompVol ). (It will probably already be selected.) Use the DATA WHEEL or the + / - buttons to set the desired level. Press the EXIT button twice to return to the home display screen. Once you have the Accompaniment Volume adjusted to your taste, you can save that keyboard set up as a Registration (See Pages 66 and 67) for quick recall. The WK-7600 will save up to 96 Registrations (16 Banks of 6 Registrations each). Your other option is to use the MIXER Section, as described on Pages 36 to 43, to adjust the levels of the individual Parts of a Pre-set Rhythm and then save it as a User Rhythm. The WK-7600 will save up to 100 User Rhythms. You can edit Pre-set Tones yourself and save the results as User Tones (up to 100), or import User Tones created by others, as ".TN7" User Tone Files, but to my knowledge, no one, including Casio, has made User Tones commercially available. There is a small selection of member contributed User Tones available in the Downloads section of this forum: http://www.casiomusicforums.com/index.php?/files/category/39-ctk-wk/ However, User Tones are nothing more than a set of Parameters for shaping the Wave Samples that the WK-7600 has onboard. For instance, the WK-7600 has several piano wave sample sets, and you can use the Tone Editor to create piano tones to your heart's content, but if you wanted to create a dobro or didjeridu tone, you would not be able to do that, as the WK-7600 has neither a dobro nor a didjeridu wave sample, and it has no means of importing wave samples. Keyboards that can import wave samples typically run twice the price of the WK-7600 and more.

Debbie Since the accompaniment was not transposed, then the keyboard could not have been globally transposed, and that is why it did not show as being transposed. Only your selected tone was transposed. This could have been caused by a pitchbend wheel that was stuck out of its normal zero position, particularly having it out of its zero position when the keyboard is powered up, or a pitch bend wheel that has become defective. It could also be caused by selecting a User Tone that has been transposed, or having a registration active that had selected a transposed User Tone, or a Mixer Coarse or Fine Tune setting that was transposing the tone. Some of these things can be done by playing MIDI files, from outside sources, that have control messages embedded in them. These will normally be cleared by a factory reset. If you do not have any transposed User Tones, or have not been playing any MIDI files other than your own, and the factory reset did not immediately resolve the problem, then the pitchbend wheel is my prime suspect. Try moving it to its upper limit and letting it snap back to its zero position. Play a tone to see if its pitch is normal. Now repeat with moving the wheel to its lower limit. Then, gently try to move the wheel from side to side at its zero position as you play a tone to see if its tuning becomes erratic. A defective wheel will need to be replaced by a service center, but in the meantime, you can try setting its bend range to 00 with the Function menu. See "Bend Range" under "Function Menu Settings" in the right hand column of Page 131 of the manual. Good luck !

The conversion I was referencing was using the Data Manager software to convert Casio proprietary audio files, that had been recorded to the SD Card, by the keyboard, to standard Windows WAV files, and transferring them to a computer's hard drive for distribution to other devices. This process has absolutely nothing to do with CMS files, as CMS files are MIDI files, not audio files. This is the only conversion process that the Data Manager software performs - Casio proprietary audio files to standard Windows WAV (audio) files. Basically, it is just a conversion from one audio format to another (more widely useable) audio format. Songs stored in the keyboard's internal Song Sequencer memory can be converted to Standard MIDI Files (SMF) when they are saved from the keyboard's internal memory to the SD Card, but that conversion is done by the keyboard itself, not the Data Management software. When a Song is saved to the SD Card, there will be an option to save it as a CMS file, or as a Standard MIDI File (SMF). See the appropriate section in the manual for saving data to the SD Card. The full "conversion" process I described previously amounted to loading a CMS (MIDI) file into the Song Sequecer, and playing it back, as the keyboard's Audio Recorder recorded it to a Casio audio file, on the SD Card, then using the Data Manager software to convert the Casio audio file to a Windows WAV (audio) file and transfering that to a computer, but there is no "direct" ("single step"/"menu option") conversion of CMS files to audio (WAV) files, rather, it is a somewhat involved process with several steps. Obviously, this procedure will only work on the CTK/WK-7XXX models, as the CTK/WK-6XXX models do not have audio recording capabilities.

To connect the two WK keyboards together, it would have to be done through a computer or through a "USB-MIDI host" device: http://www.kentonuk.com/products/items/utilities/usb-host.shtml http://www.lab4music.it/index.php?lang=EN There is no simple "adapter" that has the necessary processor intelligence to provide the required USB-MIDI protocol control to do this. The "Host" devices are really nothing more than very highly specialized computers.

sslyutov The CDP-130 can TRANSMIT on any one of the 16 MIDI channels - but only on one of those channels at a time. It can RECEIVE on all 16 channels simultaneously - making it 16 part multitimbral - even though it only has a 10 tone voice bank. As to your second comment above, some of the lower priced (entry level) Yamaha Arrangers operate the same way. The preset tones are fairly or completely fixed, with no way of altering them from the keyboard's front panel, but some parameters are alterable via MIDI. So, some of the more advanced of those users have devised ways of embedding those parameter "edits" into one or two bar "noteless" MIDI files and then play the file they need to set up the tones the way they want immediately before they start playing. In other words, they are using one or two bar "noteless" MIDI files as sort of "external" registrations. With this scheme, a couple of them have been able to turn a few of the mundane, lack-luster, run-of-the-mill pre-set "synth" (sine, saw, square, etc) tones into more lively tones that sound surprisingly like some of the popular vintage boards out of the past, but from the way they describe it, it takes quite a bit of experimentation and effort.

Woxof I apologize for not picking up on what you were describing in your initial post, and your final statement in your second post is correct. The instruments (tones/voices) that you select with the buttons on the keyboard's front panel only select what you play from the keys, and have no effect on what is played by a MIDI file. To do that, you need to use the MIXER feature. Description of and instructions for using the MIXER start on Page 39 of the PX-410 manual. In particular, what you are trying to do, select an instrument (tone) on a particular MIDI channel to be played by a MIDI file, will be found at the top of the left hand column on Page 41. Keep in mind that if a Program Change signal for a different tone comes along after you make your MIXER selection, the Program Change will override your MIXER selection. A better method would be to make the change in the MIDI file itself with Reaper. Your PX-410 should have come with an appendix that lists the Program Change codes for its various instruments (tones) that you can embed into the MIDI files with Reaper, but as I am not familiar with Reaper, I can not help you with that.

If you are having the same issue with both the MIC IN and AUDIO IN, there is most likely a problem with the CTK-7300IN's audio circuits, but just to be sure, do a check of your 3.5mm stereo cable - Connect your 3.5mm stereo cable from your phone to the MIC IN on your PC. If you can not hear what your phone is playing through the PC, you may have a bad cable, but if you can hear what the phone is playing through the PC, that is a good indication that there is a problem with the keyboard's audio circuits, and you should contact the retailer you purchased it from and arrange for a return.

cellachris Glad you got it working . . . BUT . . . If you did not save your file while it was playing correctly, it may fall back to your original problem the next time you load it. If it does, just repeat what you did to get it working, verify that it is working correctly, and then save it before you close it.

CELLACHRIS See this excerpt from the Ableton Live Knowledge Base for using "Clip View" for assigning Bank Select and Program Changes to your MIDI clips. I would say to start with the clip you already have and assign it a "Bank" number of 0. I am not sure what should go into the "Sub" entry field. If you can not leave it blank, assign it a number of 0, as well, but then as I stated above, you are going to have to experiment with the Program Change numbers to see what they actually select on the CDP-130. The CDP-130's ten tones may simply be listed as tones 01 through 10, but I suspect that they actually use the General MIDI tones numbers from the GM Tone List I provided the link to previously, except that the number you enter in Ableton's Clip View in the "Pgm" field will be one less than the Program Change Number shown on the list. Take one of the CDP-130's tones, look up its name one the Tone List, subtract one from the Program number shown on the list, enter that into the List View Program number, play the clip and let us know what you get. If the numbers from the Tone List do not work, just try entering numbers 1 through 10 and see what you get. If none of the Program numbers you try work, increase the Ableton Clip View Bank number from 0 to 1 and try again. Good luck: https://help.ableton.com/hc/en-us/articles/209070489-Can-I-send-MIDI-Program-Change-messages-from-Live-to-my-MIDI-device-

Alen I do not know where you are getting an LSB of 0. Per the General MIDI Spec - for Bank Select codes the first number listed (CC #0) is the MSB and the second number listed (CC #32) is the LSB: These are the control numbers that Roland originally used in their "GS" spec. The fact that the CDP-130 uses them indicates that it not only conforms to the GM-1 spec but also, in this respect at least, it conforms to the Roland "GS" spec. I have a feeling that this is nothing more than a design carryover from other Casio models to make them compatible with "GS" spec Standard MIDI Files. https://en.wikipedia.org/wiki/General_MIDI Do a search on "bank select". As for experimentation, and I think Jokeyman will attest to this as well, I started with this MIDI business in 1987, and in all the intervening years, I have never had any keyboard (Synth, ROMpler Workstation, Arranger Workstation, Sampler Workstation) of any price from any manufacturer that did not require a lot of experimentation, on my part, any time I wanted to go beyond simple "playing". Since this is the "norm" I have grown used to, I do not find it surprising or daunting when I run into it now. My comment about the CDP-130 being a single tone bank machine was made to confirm that fact to others who have been or may be taking part in this discussion. As for now, I am going to go see if I can dig up a trial copy of Ableton to see if we can help cellachris get it to send the right tone select codes to the CDP-130.

The MIDI Implementation Chart in the back of the CDP-130 manual indicates the following: The CDP-130 uses the 0-127 tone mapping scheme. The CDP-130 transmits and receives Bank Select codes, but with the following notation: It transmits an MSB of 0 and an LSB of 32 It receives only an MSB of 0. Any LSB codes received are ignored. This indicates a single bank tone set, but as AlenK has already stated, it may still be necessary to send the Bank Select MSB of 0 ahead of the tone select Program Change even though there is only one tone bank. I would just set up Ableton to send an MSB of 0 and an LSB of 32 on each track and let the CDP-130 use what it needs and ignore the rest. As I have seen Jokeyman write about many, many times here on this forum, this is going to require some experimentation with Ableton and the CDP-130. To begin with is determining whether it is possible to record the tone select codes from the CDP-130 with Ableton. Most likely, the CDP-130 sends the Bank Select and Program Change codes when the tone is selected. That means the Ableton track has to be already armed and recording when the selection is made on the CDP-130. This could result in a lot of awkward empty bars at the beginning of each track. These empty bars could be edited out manually with Ableton after recording, but it may be easier to just ignore trying to record the tone select data during recording and just embed them into the track manually with Ableton after recording. After that, experimentation will be required to determine what specific Program Change codes Ableton needs to send to select the correct tones on the CDP-130. As with any experimentation, a good set of accurate notes will be an absolute must for reliable future recording efforts.

"J" The MSB/LSB Voice Bank Select codes and Program Change codes are given on the Tone List (Appendix) that came with your specific model. If you did not get one, or have misplaced it, you can download a copy from the Casio Support website that offers the manuals for download. In reference to you original Item 2: If you want to use an iPad as a MIDI source for your keyboard, you need to make certain to get a DAW/sequencer app that outputs MIDI to external devices. Not all of them do. Many use MIDI strictly internally, surprizingly, chief among those that do is the iPad's marque sequencer app GarageBand, so that pretty much makes it useless for serious music production. Also, the same applies to iPad DAW/sequencer apps as to PC software for selecting proper tones on the keyboard - they need to be capable of sending MSB/LSB Bank Select and Program Change codes.

Thanks Simone and Arcturus. That is what I was looking for. Hopefully, it will be of use to others here, as well. As for myself, I think I will hold off and just stick with my trusty old WK-3800 workhorse for a bit yet. I wonder if the 560's coming from the factory with 1.14 already installed have the same issues, or if there is just something wrong with the 1.14 download package ? ? ? It would be nice if someone who got a 1.14 560 out of the box would jump in here and let us know. BTW Simone, you did mention an item in your reply that has been troubling me, and is the main reason I have not already gone for the 560 - the fact that it is not really a workstation. I had to give up my CTK-7000 and WK-7500 about a year ago to help cover the cost of repairs to my rural electrical entrance due to severe lightning damage. I thought I would come back in with the 560, but I was so reliant on the workstation capabilities of those models that I am afraid I would miss them dearly - to the point of being disappointed in the 560. So, I may just come back in with a 7200 and 7600, or their next iterations. Decisions, decisions, decisions ! ! !

A couple of the replies above mention audio, but I do not understand why that is, as the issue is MIDI. Other than that, I would say the problem is that Ableton is simply not sending the correct MSB/LSB Bank Select and Program Change codes to the CDP-130 for selecting the proper tones on it. I would think that with only 10 tones there would only be one tone bank and MSB/LSB Bank Select codes should not be necessary, but if the CDP-130 does not use GM Bank 0 then Ableton would need to send the proper Bank Select codes preceding the Program Change code. My assumption regarding the manual's mention of GM1 adherence means that the CDP-130's 10 tones are, by design, located in the GM1 default Bank 0, making MSB/LSB Bank Select codes unnecessary, and then the individual tones use their corresponding GM1 Program Change codes. So, the Grand Piano voice would be Bank 0 - Program Change 0 or 1, depending on whether the CDP-130 uses the 0-127 or 1-128 tone mapping scheme. The Harpsichord would be Bank 0 - Program Change 6 or 7, while the Strings would be Bank 0 - Program Change - 48 or 49, and so forth, so Ableton should really only need to be set up to send the proper Program Change codes on the proper channels to select the correct tones - with the following caveat - Standard MIDI Files would only work properly as long as they only used tones that are available on the CDP-130. If we were dealing with Cakewalk's Sonar, I could explain how to embed the Program Change codes into the file, but I am not at all familiar with Ableton. A list of the GM1 Sound Set can be found here: https://www.midi.org/specifications/item/gm-level-1-sound-set This list uses the 1-128 tone mapping scheme, but that does not necessarily mean that the CDP-130 does. If it uses the 0-127 tone mapping scheme, then all Program Change numbers (PC#) in the list would need to be decremented by 1.

Per the MIDI Settings section on Page EN-12 of the CDP-130 manual, it can only transmit on one MIDI channel at a time, but the user is able to select any one of the 16 MIDI channels to transmit on. Per the Specifications on Page EN-14, the CDP-130 is 16 Part Multi-timbral (Receiving), but that multi-timbrality is of very limited use, due to its voice bank of only ten tones, since it lacks the 128 tone GM voice set of most of the other models (CTK/WK/XW/etc).

Robin Adding sustain after the fact with a DAW will not necessarily resolve your issue. Any staccato signal on the same note of the same track occurring during an intended sustained note will still truncate the sustained note. In other words, you would be doing manually with the DAW, the same thing the keyboard's sequencer is already doing inadvertently. The only way to avoid this, is to keep the tracks separate to begin with. With 16 tracks available to you, is it really necessary to merge those two tracks?

Simone Sorry to hear that the update did not help you. You state that, not only did the update fail to fix existing problems, but it caused new problems, but you do not say what the new problems are. If you don't mind, and have the time, could you please list what problems were NOT corrected and what NEW problems were created, for those of us who have been considering a 560M, but may now be having second thoughts. We would not need an in-depth analysis that would take a lot of your time - just simple statements. If you could do that, it would help us decide whether purchasing one anyway is worth the risk. BTW . . . This is not to single out and beat up on Casio. Yamaha's upper end PSR's and Tyros Arrangers have some deficiencies that are slow in being addressed, and other than an AX-1500G Guitar Effects Processor, that I dearly love, I have never been a Korg user, but I seem to remember a similar history with some of their keyboard offerings. This seems to be a frightening trend for those of us not affluent enough to suffer a sizeable loss in disposing of a disappointing purchase in order to pursue something more promising.

J Glad you got the adapter problem sorted. As a rule of thumb on that: If Windows or your music software do not "see" the adapter, then the problem is usually between the USB side of the adapter and the computer and is usually a driver or compatibility issue. If Windows and your music software "see" the adapter, but the keyboard does not seem to be transmitting/receiving data, then the problem is usually between the 5-pin-DIN side of the adapter and the keyboard, and is usually an IN/OUT turnover issue or a MIDI set up problem with the keyboard or the music software or both. As for your audio problems - by any chance have you tried the ASIO4ALL universal drivers? They are about the only ones I have had success with for the Cakewalk products (Music Creator, Sonar, etc) with XP, VISTA, and WIN-7. Some sound-card/OS/DAW combinations do not get on well with them, but they may be worth a try..