Hi Spidie - couldn't think of a more fitting fellow to be conversing with on this dark, dreary, blustery, rainy Halloween night unless you went by the title of "Count" !
OK ! When you go to load a SONG ( .CMS ) file from the card back into the keyboard's USER memory, DO NOT use the CARD mode by pressing the CARD button alone. That is strictly for playing Standard MIDI Files ( SMF ) that have a .MID file extension, and that is all the keyboard will show in that mode. Instead, to load a SONG file, you have to enter SONG SEQUENCER mode by pressing the SONG SEQUENCER button and then pressing AND HOLDING the FUNCTION button as you press the CARD button for LOAD/SAVE. Then use the UP/DOWN cursor buttons to select the "Seq Load" function, if it is not already selected. If you have more than one song on the card, use the jog wheel to select the desired song and the display will show you which memory slot it is going to load it into. If you have something else in that slot, make sure you have already saved it to the card before you overwrite it with the song you are currently loading. Press ENTER, then YES, and you should be all set. Let me know if you still have problems with this. The SAVE/LOAD functions on these keyboards seem to be a lot more convoluted than they need to be.
NOW . . . For your next question . . . I do not have an exact answer for you, but we will have to really dig into the meat of things with the sequencer so that, maybe, you can figure out on your on what happened to your drum track. I covered all this either on another forum or somewhere else on this forum, but I can no longer find it, so will have to redo it here. To understand what Casio is doing with its SONG SEQUENCER, we have to talk a bit first about the two types of MIDI files, as Casio has applied that same idea to its sequencer. When we talk about INTERNAL MIDI data, that is MIDI data while it is still INSIDE the keyboard, or sequencer, or sound module, we talk about it being divided up or assigned to TRACKS. While most PC DAW's now have an unlimited number of tracks, most hardware or keyboard sequencers are limited to 16 tracks. Some years ago, Roland's JV-1000 flagship ROMpler touted a 32 track sequencer, but it was actually just two 16 track sequencers in the same keyboard. BUT . . . now . . . when we talk about MIDI data when it is BETWEEN devices, that is when it is in the connecting cable(s), we refer to it being divided up or assigned to CHANNELS. Usually it goes on a one-for-one basis (Track 1 - to - Channel 1 - to - Track 1), but that is not required. With your hardware and DAW set ups, you can mix them up anyway you want, say . . . Track 2 - to - Channel 5 - to Track 7, or what ever you like. So, once again, TRACKS carry MIDI data WITHIN the devices, while CHANNELS carry MIDI data between devices, and that now brings us to the two different types of MIDI files. A TYPE-1 MIDI file has its data spread across 16 CHANNELS - one TRACK PER CHANNEL, while a TYPE-0 MIDI file has ALL 16 TRACKS ON A SINGLE CHANNEL. A TYPE-0 MIDI player is able to split the data back into individual tracks and play them. So . . . now . . . along comes Casio. The CTK/WK-6XXX units hype a 16 track plus system track sequencer, while the CTK/WK-7XXX units tout a 17 track sequencer. Why Casio makes the distinction, I have no idea - THEY'RE THE SAME SEQUENCER IN BOTH MODEL LINES, but a peek in the manual will reveal an even deeper mystery. The manual shows that there are 16 "A" TRACKS and 16 "B" TRACKS. The "A" tracks are reserved strictly for INTERNAL use - for when you play the keybed, or for the auto accompaniment, or when the SONG SEQUENCER plays a User Song, while the "B" TRACKS are connected to the USB MIDI port for use by an external sequencer, or by the internal MIDI file player. So, the keyboard treats its own MIDI file player as an external device. That's why the difference in the way it handles loads/saves of song (CMS) files vs MIDI (MID) files. The "B" tracks can also be accessed (played) from the keybed when they are selected in the SONG SEQUENCER for a single track recording. So how do we accommodate all these extra tracks ? The "B" tracks are handled as 16 discrete tracks, just as you would suspect, but the sequencer handles the SYSTEM TRACK (TRACK 17) as though it were a TYPE-0 MIDI file. The SYSTEM TRACK (TRACK 17) "CONTAINS" the 16 "A" TRACKS. That is why you have to do an EXTRACT in order to edit them. The EDITOR can only handle 16 discrete tracks, not a composite that contains all 16 tracks. When you do an EXTRACT, the "A" tracks are fanned out and copied into the discrete "B" tracks so the editor can handle them. Actually, the EXTRACT function only copies TRACKS 4 thru 7 and 9 thru 16, as those are the only tracks involved in a QUICK RECORD. This is really neat. Where Roland had to completely duplicate their hardware to handle 32 tracks, Casio did the same thing with only one piece of hardware and only 17 discrete tracks.
Basically these Casio units are just glorified General MIDI (GM) keyboards, and the GM standard requires that the drums be on TRACK 10. I had assumed that when you did your EXTRACT, that the drum data got switched to another track, so I created a song file and converted it to SMF (.MID) both before and after extraction and then ported them to Sonar, but to my surprise, the drums were on TRACK 10 in both files. So, if your drums ended up on the wrong track, it is not because of any "default" action of the EXTRACT process. You may want to check with your DAW to see if the drum track got switched (and change it back to TRACK 10), or if it just got lost completely.
One interesting note - the SMF I made before extraction had glitches that would cause Sonar, and Cubase, and Power Tracks, all to "stumble" in 5 or 6 places, so I tried several more files and got the same thing, but the files I converted to SMF AFTER extraction all ran fine without a single glitch. So apparently a direct SMF conversion of a raw CMS file without extraction contains some kind of control data that DAW's do not like.
That's all for this time.
Good luck !