Can anyone repro with my recipe?

no one?

I guess not...

Gonna have to open a bug with support. Can't get home in time to contact them during their limited phone time.

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.

The file format of .mid is not a Sonar format -- it's a conventional standard, so Sonar may not be able to support all the features and data relationships of a Sonar project when it is saved as a .mid file.
 
Without trying your recipe, I'll just hypothesize:
About the file format of .mid:
  Maybe it does not support the idea of a sysex bank as Sonar does, i.e. as a data element not in any track.
  It does support sysex events in tracks.
 
So how should Sonar save .mid files when the project has sysex banks?
My guesses (WAGs to be sure):

• Projects with auto send banks could maybe save those sysex messages in a .mid track. Playing a .mid file would then send those sysex messages before sending notes.
• Banks not set to auto send don't have any convention for storing in .mid so they get dropped. They should not be saved in any .mid track, because then they would be sent whenever the file is played.

How should Sonar load .mid files with sysex events on tracks?
More WAGs:

• A sysex event at the very beginning of a .mid track could be loaded into a Sonar sysex bank and marked auto send.
• Subsequent sysex events from the .mid might be loaded as events into Sonar's tracks (check this?)
•    and they could also be loaded as Sonar sysex banks not marked auto send (as reported by Conley)

 
Saving a project loaded from such a .mid file should produce a nominally identical .mid file. However, setting the auto send flag on those banks that also appear in Sonar tracks may cause the sysex events to get doubled in the .mid tracks when the file is saved ... if my guesses are correct.

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. 

My gripe is this - IF SONAR has a built in midi SYSEX utility and is unique to SONAR, SONAR should save it at it's general state that it was saved on and it does not. It changes the banks from the desired saved state amd sugments the file. My resipe clearly demonstrates this issue on my machine and I am pretty sure others shold be able to repro.
 
I am using it for the bank utility which does not really apply to a track, but the devices.