Author |
Topic: Cant send large sysex file (Read 1287 times) |
|
Roarc3
New Member
MIDI-OX Rules!
Posts: 2
|
 |
Cant send large sysex file
« on: Apr 21st, 2003, 1:59pm » |
 Quote  Modify
|
Hi!
I have a Zoom rt323, and saved several song dumps as sysex after making 10-15 songs.
I then tried to send the sysex back to the 323, but after a week, I still can not get get the data back. After I got a memory card to save on, I have tried sending just one or two songs back and forth as sysex dumps, and this works.
But these files are not so big as the first ones, which causes the problems.
The filesize are 1,2 - 1,3 Mb, and after everything is sent, the Zoom display just shows "empty"
One of the sysexdumps starts with F0, and the F0 repeats several places in the file, but, there are no F7 at EOF.
Have used the check function which doesnt indicate errors in the file.
If I just can find out what to look for in the file, maybe I could split them in smaller dumps, or do you have any other suggestions?
|
|
 IP Logged |
|
|
|
Jamie OConnell
Administrator
 
Gender: 
Posts: 2027
|
|
Re: Cant send large sysex file
« Reply #1 on: Apr 21st, 2003, 7:01pm » |
Quote Modify
|
Quote:| I then tried to send the sysex back to the 323, but after a week, I still can not get get the data back. |
|
It shouldn't take that long. 
Seriously, though, it's not a good sign that the dumps don't end in F7. Any embedded F0's should follow an F7 also. If these are missing, I would suspect data corruption by the MIDI interface and/or device driver.
If you can reliably transmit a song at a time, that might be your only solution for now. You might need to get a different MIDI interface for a long term solution.
|
| « Last Edit: Apr 21st, 2003, 7:02pm by Jamie OConnell » |
IP Logged |
--Jamie
Music is its own reward.
|
|
|
Roarc3
New Member
MIDI-OX Rules!
Posts: 2
|
|
Re: Cant send large sysex file
« Reply #2 on: Apr 22nd, 2003, 6:00am » |
Quote Modify
|
Pity, since I'll lose much work..
I did not expect my interface, as I use Event Layla 20-bit for this. I've had no problems with it before, but I have not used sysex for many years, not since I owned a DX-7, or dumped to my Ensonic SQ2's.
I was hoping I could split the sysexfile manually, but I guess it could take some time, as all songs will be of differnt lengths.
Guess it won't help degrading to an older driver either, as the file already will be corrupted.
Roar
|
|
IP Logged |
|
|
|
Jamie OConnell
Administrator
Gender:
Posts: 2027
|
|
Re: Cant send large sysex file
« Reply #3 on: Apr 22nd, 2003, 1:38pm » |
Quote Modify
|
I don't know of any specific problems with the Layla interface (although i don't have one). I would expect that to be fairly reliable, actually.
You could get evidence of whether the interface is working correctly, by doing several manual dumps and then comparing them all in MIDI-OX SysEx View. Place each of two dumps in a separate window and then choose: SysEx | Compare Windows Any differences in the dumps will be displayed. If all the dumps are identical you can be assured your card and driver are working correctly. The remaining possibility is that the Zoom rt323 is faulty, or that the SysEx is not really in error. If the dumps are not identical, then either your card and interface have a problem (likely) or the Zoom is malfunctioning.
If the SysEx is not in error, there may be a problem in transmitting it back to the device. You may need to slow down transmission from MIDI-OX. When sending SysEx, it is strongly recommended that in SysEx View: SysEx | Configure..., "[x] Delay after F7" is checked. You can experiment with the delays. Try 60 milliseconds initially. If that works, you can try reducing it.
You can manually split any raw SysEx file between messages. Everything from F0 ... F7 is a single message. The following F0 begins a new message. You could split out and save any message to a new .SYX file.
|
|
IP Logged |
--Jamie
Music is its own reward.
|
|
|
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register
Reply
Notify of replies
Send Topic
Print