Casio CZ/ VZ/ FZ - Pro Series

Howdy,

 I think ALL DIY CZ users shuld do the dartridge/auto power off mod to their units. It's simple. The only trade off if you have to decide if you want the auto power off,or on, permanently. That gives yuo 32 certridge sounds instead of 16. i would be happy to mod for non DIY people. A small fee would be mandatory for my time. I'll try to find the aticle in EM and list the process if I hear any interest in it.
Rig

--- In CZsynth@yahoogroups.com, "Jeremy Campbell" <captainjc@...> wrote:
>
> Man, I feel dumb, the problem was that I didn't have the proper 800ma ac adapter for it. Solved a bunch of weird issues I was having once I got it. Appreciate the help guys.
> 
> Jeremy
> 
> --- In CZsynth@yahoogroups.com, "Jeremy Campbell" <captainjc@> wrote:
> >
> > Thanks for the replies guys. So yeah, seems like an issue with the sets of 101 patches. I will try the patch test and troubleshoot that issue. Worse comes to worse, maybe I can use midiox on my virtual pc to save out the sets as individual sounds. Seems a bit labor intensive so hopefully I can figure it out.
> > 
> > I just noticed that Sysex Librarian has the ability to set the length of the pause between messages, so maybe that has something to do with it.
> > 
> > In the mean time, if anyone knows where I can get single patch sysex files, would love to check that out.
> > 
> > Thanks,
> > Jeremy 
> > 
> > --- In CZsynth@yahoogroups.com, "Fulfil Objective" <kasploosh@> wrote:
> > >
> > > Jeremy,
> > > 
> > > The Narfman patches are made specifically for the CZ-1. They have more information than the CZ-101 can handle. There are extra bytes in each patch for features that are unknown in the CZ-101, such as velocity. Also I think the patch headers are different than what a CZ-101 expects.
> > > 
> > > To sum up, these are not going to work in a CZ-101 without editing. So make sure you look for CZ-101/1000 patches, there are a bazillion of them.
> > > 
> > > As Steve mentions, the sysex files are hex data, so use a hex editor if you want to poke around in the insides of them. Don't use a text editor or it could save it wrongly. Some text editors can edit hex, like programmer's editors. But hex editors are fun, so why not use them?
> > > 
> > > Also keep in mind that some sysex files are SETS of patches, and some are individual patches. You will be able to tell by the file length.
> > > 
> > > 264 bytes = single CZ-101 patch
> > > 4224 bytes = 16 CZ-101 patches (264 * 16)
> > > 
> > > 296 bytes = single CZ-1 patch (it's longer!)
> > > 22016 bytes = 64 CZ-1 patches, plus operation memory.
> > > 
> > > Re-reading your message, I think you might have two different problems. Number one is that CZ-1 patches will probably not work in a CZ-101 without complicated editing.
> > > 
> > > Number two is that multi-patch sysex sets are not working. For that problem, I suggest trying again with something you KNOW is made for the CZ-101. It could be that you are trying to use CZ-1 data, or CZ-3000/5000 data.
> > > 
> > > I have had good luck sending sysex files to my CZ-101 using MIDIOX, so that could be another thing to try.
> > > 
> > > 
> > > 
> > > 
> > > --- In CZsynth@yahoogroups.com, "Jeremy Campbell" <captainjc@> wrote:
> > > >
> > > > I've been trying to use some of the sounds in the files section. I can load some individual sysex files just fine, but other just make the 101 switch off. It seems to have to do with how many sysex messages are sent. 
> > > > 
> > > > The 4 patches in FrankOsCZsounds.zip load up just fine (thanks!)
> > > > 
> > > > but when I try to load any of Narf's 471 Single Patches for the CZ1, no dice. 
> > > > 
> > > > The difference I've noticed is that with the former, it only sends 1 message. With the latter 2. 
> > > > 
> > > > Needless to say the some of the sysex files send 16 or more messages and none of those work. 
> > > > 
> > > > Anyone got any ideas? I can copy the text of these messages out of Sysex Librarian, but saving them as a text file with .syx extension doesn't work. What am I missing here. 
> > > > 
> > > > Thanks,
> > > > Jeremy
> > > >
> > >
> >
>