Hi all, my main interface is a TC StudioKonnekt48.  I also have a Yamaha THR10 amp which can also be used as an interface via usb.  For my main recording I use the 48 but when noodling with my guitar and mic doing scratch song ideas I'd like to use the THR.  Can you set up different interface profiles with Sonar or do I have to just launch the program and manually change the I/O driver each time?  No biggie, just be nice to be able to load up a pre configured profile.... 

I have not tried this, but I think if you were to set up another Windows user account, those settings might be associated with the Windows user, and would then give you an automated change of devices when launching Sonar.
 
It should just take you a few minutes to try out the above - hope it works.
 
I think some folks may do this kind of thing by maintaining multiple copies of the Sonar aud.ini file, which is stored in the hidden application data folder (might be in program data folder, which is also hidden).  They do a rename exercise to switch between different versions of this file.  I do not know all of what is maintained in that file, and personally, I would likely opt for setting up a different user account in Windows instead (if it works).
 
Hope either of the above get you where you wanted to go.
 
Bob Bone
 

Thanks Bob.  It's probably faster and easier to just go to preferences and select the proper driver. 

Same thing for me.  I have a TCK 48 but have been using a Tascam lately.  It is a pain to switch drivers, but is a first world pain.
 
@

If you give your inputs/outputs "friendly names" at least it remembers which to use after a switch.

There is an old thread about adding command line parameters to Sonar 5.
I am not at my studio PC right now. Anyone know if this has ever been done. I do not see it in the docs.
There should be command line options for specifying alternate aud.ini and cakewalk.ini files.
If this were available you could simply have multiple sonar icons each with its unique command line specifying a unique hardware setup.
This would be trivial to add to code since you are essentially replacing strings.
Bakers, please consider adding this in X4.
 
Michael

microapp
There is an old thread about adding command line parameters to Sonar 5.
I am not at my studio PC right now. Anyone know if this has ever been done. I do not see it in the docs.
There should be command line options for specifying alternate aud.ini and cakewalk.ini files.
If this were available you could simply have multiple sonar icons each with its unique command line specifying a unique hardware setup.
This would be trivial to add to code since you are essentially replacing strings.
Bakers, please consider adding this in X4.
 
Michael

You could possibly do that as a series of .bat scripts. To rename which .ini you want to use, then launch sonar.
 
I was thinking of a similar thing to the query in the OP earlier, to be able to switch between my PCI sound card and my USB device. Might see if I can get it through this over the weekend.

I was thinking about writing a little menu program which listed multiple custom aud.ini files.
You pick one and it overwrites the real aud.ini file then launches sonar. I guess it should include a means to copy and rename the current aud.ini. It should probably include the same for cakewalk.ini. 
 
To keep things simple and accessible I would make a sonar_cfg.txt file which would contain a cfg name followed by an aud.ini filename and  cakewalk.ini filename. When the program is run, it would read the sonar_cfg.txt file and put the entries in a menu. You click on the desired config and sonar launches with the new cfg's. Naturally you could edit the sonar_cfg.txt file with notepad.
 
THe sonar_cfg.txt file would look like this
 
[My config 1]
aud_tascam.ini
cake_tascam.ini
[My config 2]
aud_emu.ini
cake_emu.ini
 
The menu in the program would look like this
My config 1
My config 2
 
Would something like this be of any use to anyone.  I have been thinking of a way to pay it forward for all the help I have gotten from the forum.
I have done similar programs many times so it would be a cut and paste thing.
 
Michael
 

It would probably be a good idea to save the current .ini files when the config program runs and restore them when it exits.