A couple of notes: As far as I know there is no need to send anything other than the data that makes up sound files when sending TO the CZ - as before - if they are a whole block of sounds then the sysx should contain the patch locations- I have only ever sent ONE patch at a time and without alteration it will nominally end up in the edit buffer,which means the patch will sound on the keyboard but not be stored unless the store process is enacted on the CZ. To get sounds FROM the CZ - BOTH IN and OUT midi cables need to be in - I use 2 instances of MIDI-ox - one to send the command SYSx (through the output device) and one primed to receive (through the input device) on "receive manual dump". When the code is transmitted from the OUTPUT window - the command prompts the CZ to give up a patch to the INPUT window manual dump- which patch it is depends on what was sent from the command. If you are just sending patches then you only need the output line,in which case the defeating handshaking mechanism should work. ________________________________ From: dedlandar <dedlandar@...> To: CZsynth@yahoogroups.com Sent: Saturday, 10 August 2013, 2:56 Subject: [CZsynth] Re: Can't get sysex to work with a CZ-5000 This reply didn't seem to go out the first time, sorry it's so late. First of all, thanks for all the replies. It's nice to see how active this group is. The protect switch is off, and the keyboard is in MIDI mode on default settings. The patches I'm trying came from the "CZ starter kit" you can find on eBay, or patches I've downloaded from this and the other CZ Yahoo group. I'm trying several different ones. Previously I was using a $4.00 MIDI>USB cable from Amazon, which I later discovered does not support Sysex. I haven't seen any reports of the Hosa USM-422 I'm using now failing to transmit Sysex data. I suppose a defective cable could be possible, but I would think a defective cable should turn up more defects than just Sysex ability... I'd like to receive and back up my own patches first, but I'm also attempting to send SYX patches which will overwrite mine. (I don't mind as long as I can get this working) The procedure I'm using is this- Receiving In MIDI-OX, I select USB Audio Device (the only option) as MIDI IN, and for MIDI OUT, my options are USB Audio Device, USB Audio Device [2], MIDI Mapper, and Microsoft GS Wavetable SW Synth. I usually select USB Audio Device [2], though I get the same result with all of them. after tapping a few keys to see the key on/off messages in the monitor window, I open "View > Sysex" and in the command window I paste F0 44 00 00 70 10 20 70 31, which according to the tutorial I mentioned in the first post is the command to request the patch from internal memory 1. (A1) I've read about F7 being the proper byte to end a command with, and that the CZs ignore that byte? So I select "Command Window > Send/Receive sysex" the green light on the MIDI>USB cable flashes once, and a message pops up- "[Wait for completion] 0 Bytes Received" and just stays at 0. I've tried adding the F7 byte and still nothing happens. Using Bome's SendSX, I will load F0 44 00 00 70 10 20 70 31 into the MIDI Out field, hit send and it says "Sys Ex was sent successfully". Nothing happens. I've also tried omitting the last two bytes as per fulfil_objective's suggestion, and still nothing happens. Sending Using MIDI-OX, I will load a sysex patch in the command window and select "send". The green light on the cable flashes once, and nothing happens. Using Bome's SendSX, I will load a sysex patch into the MIDI Out field, and says "Sending line X of 8" (or "Sending line X of 128" depending on the patch) sending each line, the green light on the cable flashing each time. A message tells me the patch was successfully sent, and nothing happens. The display on the CZ never changes and there are no new sounds. Am I doing something wrong here? [Non-text portions of this message have been removed]
Message
Re: [CZsynth] Re: Can't get sysex to work with a CZ-5000
2013-08-12 by Lee Borrell
Attachments
- No local attachments were found for this message.