Yahoo Groups archive
Thread
2013-07-03 by John
I have tried everything to write a patch that I have created in Midi quest to the memory of my cz3000 . Do I need a cartridge to do this ? I don`t think so but following the manual hasn`t helped at all.
2013-07-08 by Daniel Forró
Cartridge shouldn't be necessary... Let me guess: - Protect Switch? - MIDI Channel? - Some other setting in MQ (handshake mode)? Daniel Forro
On 4 Jul, 2013, at 8:32 AM, John wrote: > I have tried everything to write a patch that I have created in Midi > quest to the memory of my cz3000 . > Do I need a cartridge to do this ? I don`t think so but following > the manual hasn`t helped at all.
2013-07-08 by Lee Borrell
I cannot say for sure - but this is one suggestion. From sending stuff to a CZ1000 - unless the manual states that a given memory area is storing the patch - the patch will be stored in the temporary buffer.This usually means having to go through the STORE procedure before the patch is written to a memory. However it should still sound from the keyboard even if not stored. I have stuff online about sending data to CZ - this is not for the 3000,but may apply. http://templarseries.atspace.com/cz.html Click the links under SYSXfiles. ________________________________
From: Daniel Forró <dan.for@...> To: CZsynth@yahoogroups.com Sent: Monday, 8 July 2013, 13:59 Subject: Re: [CZsynth] Can`t write patch to memory.cz3000 Cartridge shouldn't be necessary... Let me guess: - Protect Switch? - MIDI Channel? - Some other setting in MQ (handshake mode)? Daniel Forro On 4 Jul, 2013, at 8:32 AM, John wrote: > I have tried everything to write a patch that I have created in Midi > quest to the memory of my cz3000 . > Do I need a cartridge to do this ? I don`t think so but following > the manual hasn`t helped at all. [Non-text portions of this message have been removed]
2013-07-10 by steve_the_composer
I didn't throw my two cents worth in because I thought Daniel's diagnostic suggestions were spot on. To the best on my recollection, CZ patches are assigned specific locations when sent as sysex data. Of course, I could be wrong. In the strongest urging I can possibly give, I enthusiastically encourage people to read (or re-read) the Nov. 1985 Casio Midi Guide. It simplifies midi so even a child above 10 or 12 could understand it--including sysex communication. A pdf can be found here under Files > CZ - Docs. It was uploaded as "Casio CZ Sysex," although it contains much more than the CZ Sysex details http://launch.groups.yahoo.com/group/CZsynth/files/CZ%20-%20Docs/ If you look at pdf page 20 (paper page 19), there is an explanation of the preset data sysex command. The sysex header uses d1d2 in the seventh position (counting the initial F0) to indicate where the patch data goes. The Sound Area is 60 (in hex). Steve --- In CZsynth@yahoogroups.com, Lee Borrell <templarser@...> wrote:
> > I cannot say for sure - but this is one suggestion. From sending stuff to a CZ1000 - unless the manual states that a given memory area is storing the patch - the patch will be stored in the temporary buffer.This usually means having to go through the STORE procedure before the patch is written to a memory. However it should still sound from the keyboard even if not stored. > I have stuff online about sending data to CZ - this is not for the 3000,but may apply. > > http://templarseries.atspace.com/cz.html > > Click the links under SYSXfiles. > > > > > ________________________________ > From: Daniel Forró <dan.for@...> > To: CZsynth@yahoogroups.com > Sent: Monday, 8 July 2013, 13:59 > Subject: Re: [CZsynth] Can`t write patch to memory.cz3000 > > > >  > Cartridge shouldn't be necessary... > > Let me guess: > > - Protect Switch? > - MIDI Channel? > - Some other setting in MQ (handshake mode)? > > Daniel Forro > > On 4 Jul, 2013, at 8:32 AM, John wrote: > > > I have tried everything to write a patch that I have created in Midi > > quest to the memory of my cz3000 . > > Do I need a cartridge to do this ? I don`t think so but following > > the manual hasn`t helped at all. > > > > > [Non-text portions of this message have been removed] >