The first time, I thought it was just a glitch.  After I finished an editing session in Adobe Premier, and tried to open Sonar, it hung.  I DID NOTICE that, when I open Premiere, it loads some of the DLLS and VSTs that Sonar uses.  To get Sonar to work again, I have to reboot (Windows 7 64bit).

could be premier changed the sample rate to 48. check that your audio device is set to 44 before opening sonar.

Thanks,  that is a possibility, but the audio files in the Sonar project I'm trying to open have never "seen" Adobe Premiere.  Are you saying that Premiere can change audio bit rate for audio devices in or attached to my system, or does it just change the bit rate of the files in a project that is open in Sonar?
 
TD

Adobe will not affect the SONAR projects, it does not even know they are there. Adobe just like SONAR does need to communicate with your audio interface.

Whatever your settings are in Premiere should not affect how Sonar works and vice verse.  Regardless of your bot rate in PP, Sonar would have know way of knowing.  What could be possible, and I have had this happen with Adobe programs before, is that when you exit Premiere it is still running in the background and locking up your audio device.  The next time that happens, open up your task manager (ctrl+alt+del) and check the processes and see if PP is still running.

Thanks to everyone who has replied.  As I thought about the issue, I don't believe that drivers get stuck with one or another bit rate, causing issues with a subsequent program.  This is based on years of experience running numerous programs on my PCs without experiencing anything like this.  But something dubdisciple said has triggered my memory regarding something that happened this past week; after experiencing a problem with Premiere, I could not reopen it.  It only allow one instance of itself to be open at any given time, so I bet it was still open in the background.  And, if it was, it probably tied up those drivers that Sonar uses, which (because Premiere loaded some of them) would explain everything.  The next time I have the originally described issue, I'll certainly check Windows Task Manager to see what processes are running.  My bet's on dubdisciple's explanation.
 
Again, thanks to everyone.
 
Ted David

I seem to remember an old(er) version of one of the Adobe apps, and it may have been Premiere, installed its own ASIO driver that caused problems with SONAR and other audio apps: worth checking that.

don't know about premier, but my default in vegas is 48, so when vegas loads, it sets my m-audio firewire 1814 to 48. when i exit vegas, if i forget to reset to 44, sonar opens but will not play (audio device error). i have to close sonar, reset to 44, then reopen sonar and all is good.
 
if the sonar default is 44, sonar can only work with 44. while vegas can reset my m-audio, sonar cannot.