Author |
Topic: sysex hangs at send/rec (Read 2315 times) |
|
imaginary_east
New Member
MIDI-OX Rules!
Posts: 3
|
 |
sysex hangs at send/rec
« on: Nov 18th, 2017, 10:47am » |
 Quote  Modify
|
midi ox with casio cz-1000
please help if you can, trying to use my cz-1000 for recording and i need to figure out dumping.
i setup all parameters and followed troubleshooting guide here:
http://www.midiox.com/index.htm?http://www.midiox.com/mfaq.htm
i have verified input from the cz-1000 in the input monitor. when i issue send/receive command in sysex window, command appears in the output monitor, and eventually shows the dump in the input monitor, but it never populates the sysex scratch pad.
i'm using this hex command in sysex:
F0 44 00 00 70 10 40 70 31
thanks in advance for any help you can give. 
|
|
 IP Logged |
|
|
|
imaginary_east
New Member
MIDI-OX Rules!
Posts: 3
|
|
Re: sysex hangs at send/rec
« Reply #1 on: Nov 18th, 2017, 12:13pm » |
Quote Modify
|
i'd like to add that if i start playing the keys, that seems to trigger a dump. it's around 264kb. but i can't confirm that the dump is meaningful data, it could be nonsense because i don't know how to test it. also, i tried to go the other way (send to cz) and the cz doesn't seem to do anything. it shows the output command in the output monitor and the correct file (the one i saved during the dump) is represented in the sysex bar.
|
|
IP Logged |
|
|
|
imaginary_east
New Member
MIDI-OX Rules!
Posts: 3
|
|
Re: sysex hangs at send/rec
« Reply #2 on: Nov 18th, 2017, 4:28pm » |
Quote Modify
|
ok. update to this:
i figured out that i can get a dump from the CZ if i hook up the midi using my MIO midi to usb interface rather than my behringer interface. however, i still can't get the cz to recieve a midi file from sysex. i want to load midi onto the cz, isn't this how?
|
|
IP Logged |
|
|
|
Breath
Administrator
Gender: 
Posts: 1031
|
|
Re: sysex hangs at send/rec
« Reply #3 on: Nov 19th, 2017, 8:12pm » |
Quote Modify
|
Hi
"i'm using this hex command in sysex:
F0 44 00 00 70 10 40 70 31 "
Sysex starts with F0, as you have done, and ends with F7, which is missing.
All sysex messages must have the start and end bytes.
The stuff in the middle is up to the synth maker.
So your sysex message, a request for data from the Casio I am guessing, is never completed and so the Casio will discard it.
If you send a note message while the synth is waiting for the rest of sysex the Casio should cope with it but....
Some synths don't like it and can do unpredictable things if you interrupt a sysex message with a different message .
The sysex spec predicts this possibility and the Casio should terminate and ignore the sysex and play the note, but some synths don't seem to bother.
There are some exceptions. Timing or clock messages can be inserted in the middle of sysex as they can't wait for the sysex to finish.
Some Midi interface drivers try to fix the stranded sysex message by adding a F7 at the end, but this is incorrect and can cause other problems.
So the first step is to fix the sysex and try again.
If you have all the correct Casio data in the middle, then the message should be F0 44 00 00 70 10 40 70 31 F7
All the best
Royce Craven
|
|
IP Logged |
|
|
|
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register
Reply
Notify of replies
Send Topic
Print