Hi,
 
I'm about done with a DAW rebuild but since the hardware changed (removed an M-Audio, an SBLive and added also new Synth) the I/O channel assignments are all futzed up when opening previous projects.  I assume it is possible, in theory, to get projects to open cleanly if I could somehow control the order in which Sonar sees/maps the I/O assignments.   Just as one simple example, previously the SBLive MIDI Input entry was last in the Inputs list, now the FF400 MIDI Input entry is first in the list.  So everything else down the I/O assignment list is all thrown off.  If I could "place" the FF400 MIDI entry at the end of the list where the SBLive used to reside then projects would probably open up cleanly.
 
Is there some method to address this quandary??  
 
Sonic

Uh...anyone?   Or maybe some suggested terminology to search on?

I believe the only solution is to un-install the drivers and re-install them in the order you want them to appear, now whether the 1st shall be last and the last shall be 1st I don't know, hopefully you remember how they were before you get too far along. 

I'm not certain (because I can't easily revert back at this point) but it seems like maybe the I/O assignment options are simply alphabetized.
 
?

Guys, any other thoughts?   I suspect there HAS to be some way to address this problem. Surely Sonar users can't be expected to manually alter the I/O assignments of every track, bus, etc. within all past projects just because the DAW config changed.....
 
Am I missing or overlooking something.....???

If you can provide more details:
Are you speaking only of midi  Inputs and Outputs?
Are you trying to recall midi I/O assignments for a Hardware synth/s and Sonar is assigning them incorrectly?
Do you have Vsti tracks that are not playing correctly?
Are your Control Surface midi I/O working out for you?    
What works and what does not work?
 

MIDI outputs can be reordered with the "move checked devices to top" button in Preferences. I am not aware of an easy way to reorder the inputs. Perhaps the TTSSeq.ini file can be edited.

frankjcc
If you can provide more details:
Are you speaking only of midi  Inputs and Outputs?
Are you trying to recall midi I/O assignments for a Hardware synth/s and Sonar is assigning them incorrectly?
Do you have Vsti tracks that are not playing correctly?
Are your Control Surface midi I/O working out for you?    
What works and what does not work?

 
It's not just MIDI.  Since I'm not really clear on all the proper terminology probably best to just attempt to describe with more detail, so here goes...
 
Original System:  
 Synths:  DFH Superior
 Cards:   RME FF400 (MIDI I/O not active in Sonar),
              M-Audio Delta66
              SBLive (only MIDI "active" in Sonar)
 
New System:
 Synths:  DFH Superior
               Superior2 Drummer
 Cards:   RME FF400 (MIDI "active" in Sonar),
              Realtek on-board audio (not "active" in Sonar)
 
All other software and plugins are identical between systems.
 
As you can see there is a considerable difference in the hardware "profiles" between the systems.  So picture what happens when I go to open an existing project on the new system. All the track inputs and outputs are all screwed up.  For many years I relied mostly on the FF400, which is the sole remaining common factor between the old and new system - so ideally I'd like to be able to open those past projects involving the FF400 and not have to mess with anything.
 
Sonic

Any way to at least change the device names?  That way maybe Sonar would alphabetize them such that the devices could be positioned in a desirable order?   Aud.ini file?? 
 
Sonic

I'm sorry I can not understand from your post what is happening with the projects that are screwed up despite the added info.  DFH, Superior, and any playable instrument that is software we call "soft synths" which differentiates them from hardware synths which requires midi and audio(or just audio but...), if this were the case I can see the problem with things not playing correctly, anyway the soft synths are also call vsti as we of coarse use the vst protocol in windows and sonar, the i is for instrument to also differentiate them from regular vst fx like reverbs, compressors etc.  no matter what hardware you change, or what order it's listed in, this certainly should not change the assignment of an "instrument track" or even the output of a midi track that is pointing to a soft synth, are you using instrument tracks?  
 
when you're on a midi track or an instrument track and you select the input, at the bottom it has manage presets, have you been in there and made sure there were no midi devices checked that you are not using to play instruments?  for me my mcu pro used to show up as inputs to some soft synths until I unchecked them in this location.
 
also have you tried to uninstal re-install the one you want at the top? mine are not alphabetized so this is still worth trying.
 
what i don't see you mention is if you have a dedicated midi controller or a keyboard with built in sounds that you are using, along with DFH, does the soft synths play correctly in the projects?  I know you say the I/O's are all messed up, and you mostly want the FF400 assignments to play correctly, but what's not clear is your configuration that describes what the I/O has to do with the sounds that are already in the project.
 
Off Topic, I have a lot of old projects that does not play correctly due to plugins not being recognized because the plugin id is different even though they are installed and playable.  I've upgraded many times and built brand new systems and I've have settled on not ever using on-board keyboard sounds, unless I turn them into audio tracks, things have gotten screwed up for me and I strongly advise a dedicated way of working that is as future proof as possible to avoid these types of problems.