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?

You can save sysex with the file as long as its placed in a track not in the sysex bank. If its in the bank it can be save separately and loaded at any time. 

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

that link does not really resolve my issue though. I am not looking for bank names, I am looking for the actual banks of data I have in the SYX bank when I open the midi file.
 
Trying to understand how putting the SYSX on a track will save the SYSX banks in a MID file.
 
Is there no way to load multiple banks in the SYSX and save them to a MID file? Do I need to have autosend enabled?

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.
 

The sysex bank is a Sonar exclusive to help with managing sysex, It is not part of the MIDI spec any more then staff view is. You should be able to insert sysex in a track using the event list. What you will be limited to is a sysex message up to 255 bytes long. If its larger than that load it from a sysex file into the bank manager. 

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. :)

John
The sysex bank is a Sonar exclusive to help with managing sysex, It is not part of the MIDI spec any more then staff view is. You should be able to insert sysex in a track using the event list. What you will be limited to is a sysex message up to 255 bytes long. If its larger than that load it from a sysex file into the bank manager.

sysex itself IS a part of the midi spec, specifically designed for send large amounts of data, and can be an unlimited number of bytes... the CONTENT of the sysex is down to the individual manufacturers...
here's a couple of useful links:
http://www.blitter.com/~russtopia/MIDI/~jglatt/tech/midispec/sysex.htm
http://www.2writers.com/eddie/tutsysex.htm
and the spec itself:
http://www.midi.org/techspecs/midispec.php
how sonar has implemented this is another/different question - it could be as John described (uses a special sysex bank, has to be in a track, limited to 256 bytes)
hth
 

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.
 

thx Paul  I always end up digging deeper than I originally wanted to. :)
 
SysxSendPacketSize=n
System Exclusive bytes are transmitted in packets, with a 1/18-second default delay between each packet. Setting this value to a smaller number will help slower synthesizers avoid overflowing their internal buffers. This line sets the number of bytes between each Sysx transmit delay.
n = 1024 Default value (in bytes) - Larger than 255 as default.