SYSX does not save correctly with MID files

I am not able to save any MID files with SYSX in them. I had multiple SYSX banks, save the file and when I reopened the MID file, all of the banks were gone. I tried both type 0 and type 1 mid files.
 
Is this a known issue?
 
If not, what is the trick for SPLAT to save SYSX?

http://www.cakewalk.com/D...&help=SYSX.14.html

here is what I am doing:
1. Load SYSX bank 1 with file
2. Do the same for bank 2
3. do the same for bank 3
4, File/save as MID file
 
Why should I not expect that the SYSX banks would persist in the MID file? Not looking for the names, just the SYSX banks.
 
When I open the above midi file, only one bank is present in the SYSX view.
 

thanks for the info John. I have confirmed that if I save it as a CWP, the banks persist. Also, if I save the MID file with the banks on Auto send, the banks seem to persist in the midi file too.
 
The Mid file I have originally has a 16k byte SYSX bank. I am curious to see how they created that if the bank limit is 255 bytes.
 
Gonna dig into it a bit more for clarification. Thanks for your time again. :)

I am not a strict midi guy. My main instrument is a guitar. I have recently acquired a load of equipment that has their presets changed by midi and SYX files. The vehicle for my last update was the midi file with the 16k length SYX bank. That is my motivation here btw. :) Trying to figure out how the 255 byte info above came about.
 
More info - With each SYSX bank set to auto send, I am able to save multiple banks in the MID file that have 16k bytes in length each. Opening the MID file and going into the SYSX view, I see all of the banks as expected. The first bank is set to auto send and the remaining banks are not. When I reenable the auto send on the remaining banks and save to another filename, the SYSX bank doubles the banks when opened. I can't quite get my head around that behavior yet. I find it very curious though.
 
here is my recipe
1. Load this file into a SYSX bank:
http://www.voodoolab.com/public/gcp/11RXP_GCP113_syx.zip
2. Set bank to auto send
3. Repeat 1&2 3x - Say I have Multiple units that need updating with different tweaks for each unit
3. Save as midi file MID1.mid
4. Open Midi File
5. Ensure all banks are set to auto send again - In my scenario, only the first bank in the midi file is auto send. The other banks have that option turned off.
6. Turn on auto send for remaining banks
7. Save as another file name MID2.mid
Opening the MID2.mid , in my scenario has additional banks added that were not there when I saved the MID2.MID
 
I don't think that should be behaving that way.
 

Can anyone repro with my recipe?

I guess not...

Guitarmech111
I am not a strict midi guy. My main instrument is a guitar. I have recently acquired a load of equipment that has their presets changed by midi and SYX files. The vehicle for my last update was the midi file with the 16k length SYX bank. That is my motivation here btw. :) Trying to figure out how the 255 byte info above came about.
 
More info - With each SYSX bank set to auto send, I am able to save multiple banks in the MID file that have 16k bytes in length each. Opening the MID file and going into the SYSX view, I see all of the banks as expected. The first bank is set to auto send and the remaining banks are not. When I reenable the auto send on the remaining banks and save to another filename, the SYSX bank doubles the banks when opened. I can't quite get my head around that behavior yet. I find it very curious though.
 
here is my recipe
1. Load this file into a SYSX bank:
http://www.voodoolab.com/public/gcp/11RXP_GCP113_syx.zip
2. Set bank to auto send
3. Repeat 1&2 3x - Say I have Multiple units that need updating with different tweaks for each unit
3. Save as midi file MID1.mid
4. Open Midi File
5. Ensure all banks are set to auto send again - In my scenario, only the first bank in the midi file is auto send. The other banks have that option turned off.
6. Turn on auto send for remaining banks
7. Save as another file name MID2.mid
Opening the MID2.mid , in my scenario has additional banks added that were not there when I saved the MID2.MID
 
I don't think that should be behaving that way.
 

I wasn't talking about sysex but how Sonar has a sysex bank manager. The manager is not part of the MIDI spec.

A little background info.
 
There are two main applications for sys ex. One is to save an entire bank of data, like all the patches for a synthesizer. This can be a significant amount of data. When going through a hardware MIDI interface, the slow baud rate means transfers can take a long time. Generally, you send this data out to a synthesizer (or whatever) before playing back a project to "set the stage" so when the synth receives MIDI data, it interprets the data correctly.
 
The other kind is short "bursts" of sysex to change some parameter that doesn't correlate to standard MIDI messages. These typically fit within the 255 byte limitation, so they're short enough to be inserted in tracks and sent in real time.