Does anyone know how to stop Sonar from randomly changing midi input designations after powering down and then back up?  
For example:  I set keyboard A's input to midi ch 1, keyboard B to channel 2... and on and on for live performances.  Save the song then move on to the next song and do the same.  Then when the performance is done and i shut everything down all those input selections will be lost or moved around to where i have to set them all back up again the next night.  This is beyond frustrating.
I have two midi interfaces that i use; MOTU midi express XT and MOTU Midi express 128.  When i look at the "Midi Devices" under options, they are both listed but sometimes the XT is at the top and sometimes it's at the bottom.  I don't know if that would make any difference to how my channels are set up input-wise but it seems odd that they would randomly switch positions in the device listing.
Has anyone ever run across a problem similar to this and how did you fix it?
 
Thanks

USB midi ports are like a moving target where good old 5 pin DIN Midi ports come sit and stay forever. I learned this with multiple control surfaces until finally getting a 8x8 midi box with 1 usb back to the host. Now My 4 bcf2000s stay where I left them even two years ago. They have 5 pin DINs as well as optional usb.
 
In a nutshell, I don't think Cakewalk can control this or they would have. AFAIK, Windows is rearranging things.
Someone will come along and tell me I'm wrong if I am.

bitman
In a nutshell, I don't think Cakewalk can control this or they would have. AFAIK, Windows is rearranging things.
Someone will come along and tell me I'm wrong if I am.

Sorry, but you are a kind of wrong The only case when a program can loose the track of USB devices is where there are 2 or more exactly equivalent devices which are re-connected to different USB ports. Logically, nothing can detect which device is moved where since they usually do not have unique (per exemplar) ID.
 
Unfortunately, Sonar is not the best MIDI devices detection software.
 
The only set of options a user has is to use Windows Device Manager, enable "show hidden" and clean up all old MIDI ports (every time USB is connected to different port, "new" device is created). And remove "TTSSEQ.INI" in %APPDATA%\Cakewalk\<version>.
 
There was a claim one of recent BandLab updates was supposed to fix some floating bug.
 

azslow3

bitman
In a nutshell, I don't think Cakewalk can control this or they would have. AFAIK, Windows is rearranging things.
Someone will come along and tell me I'm wrong if I am.

The only case when a program can loose the track of USB devices is where there are 2 or more exactly equivalent devices which are re-connected to different USB ports. 

So do you think this would occur if i have two 'nearly' identical units attached via USB?  The Midi Express XT and the Midi Express 128?  I seem to recall they both use the same drivers.
 
There is no "re-connecting" going on.  My rig stays untouched as far as the wiring is concerned but that's an interesting concept as far as the device manager goes.  Over the years i have disconnected and re-connected my midi devices many many times.  DO you think that the best way to proceed would be to just delete ALL midi devices and let windows 're-discover' them all?