For the 2nd day in a row I get this warning. This has never happened to me before yesterday. It only happens in 1 project. No settings have been changed.
 
Yesterday I was able to close out and reopen Sonar and it worked fine again. Today that is not working either.
 
When closing Sonar it asks to save changes. No changes were made by me.
 
Anyone else have this issue?
 
Steve
 

It could be a USB connection issue. I am using a powered hub which normally works fine. After flipping switches ON & OFF and reloading Sonar several times the project now works... for now.
 
Steve

soens
For the 2nd day in a row I get this warning. This has never happened to me before yesterday. It only happens in 1 project. No settings have been changed.
 
Yesterday I was able to close out and reopen Sonar and it worked fine again. Today that is not working either.
 
When closing Sonar it asks to save changes. No changes were made by me.
 
Anyone else have this issue?
 
Steve
 

I have had this issue. Are you using ASIO drivers? What is your card. Sometimes toggling, or closing and opening it like Obama is doing with the government works. ALso running the wav profiler.

Wave profiler doesn't scan for ASIO settings. That's why Sonar provides access to th ASIO applet that an ASIO driver installs where as WDM and MME are scanned internally as Windows see them too. That's also another reason why Windows can't use ASIO drivers.

If you have your sound card set to play Windows sounds and set Sonar to use ASIO drivers and sharing the same sound card, Windows will grab the sound card first for its own use. Also Windows sounds are all 16 bit, 44.1khz so will lock Sonar into that bit size and sample rate

In my case other projects worked fine. It was only this project and it's related sequentially numbered projects that gave this warning. So something goofy going on with them. Most strange, though I believe it to be a USB glitch as noted above.
 
Works fine today.
 
Steve

@mudgel - I used to have Windows set to use my Presonus AudioBox 1818VSL audio interface, with its ASIO drivers, as the default audio device for playback and recording in Windows, and that worked fine - with the caveat that all Windows sounds would attempt to grab the interface, which would cause issues between Windows/Sonar in ASIO mode.  
 
For that reason, when I was running in that fashion, I always turned off all Windows Sounds, to avoid that problem.
 
I currently have the Windows default audio device set to my on-board sound chip, and this routes all standard audio in Windows to a set of computer speakers I have, while Sonar is set to use ASIO driver mode and the audio interface.  With both being separate, I can be tracking in Sonar while also playing audio in Windows (YouTube, WMP, other audio applications).  Even processing this way, I still have all Windows sounds turned off, so that if gigging with my computer, it doesn't send audio through the band PA of things like Windows starting.
 
I also need to point out that when I had the Windows default audio device set to my audio interface, I also changed all of the Advanced Properties sample rates and bit depths for Windows Playback/Recording to match what I set the audio interface to.  For me, that means I changed those values to 48/24 for EACH set of inputs/outputs for the audio interface (I have 8 ins and 8 outs, specified as 1/2, 3/4, 5/6, and 7/8, so I changed the values for each of those).
 
Bob Bone
 

I have narrowed the trouble down to the ASIO drivers. I cannot even open the MOTU Audio Console to check the settings.
 
Will have to troubleshoot it later.

Well... after several days of trouble free usage I once again have this problem with X2a 64bit. It simply refuses to see the MOTU sometimes.
 
The solution for me is to turn the USB hub power on & off until it works again.
 
X1d Exp 32 & 64bit does not have this problem so it must be tied to the way X2a sees USB. Tell me why it would see USB differently than X1, tell me.
 
Steve
 

Could it be Windows disconnecting the interface, due to settings in Power Management?
 
Control Panel\Hardware and Sound\Power Options\Edit Plan Settings, then click on Change Advanced Power Settings, then:
 
Expand 'USB Settings'
Expand 'USB Selective Suspend Setting'
Set it to 'Disabled'
 
The above will tell Windows NOT to act on its default behavior of disconnecting idle USB-connected devices.
 
Also, IF you have sleep/hibernate active, this can cause problems for devices and/or Sonar waking back up properly.  I recommend you either turn sleep/hibernate behavior off, make it manual, or set the time to something long enough to where if you go fix a cup of coffee and/or accidentally pay attention to the spouse you won't go into sleep mode.
 
If you do go into the Power Management settings, I happen to also:
 
1.  Use the High-Performance power plan
2.  Alter the USB Selective Suspend setting (as noted above)
3.  Expand the Processor Power Management option, expand the Minimum Processor State option, and set that to 100%, so that my CPU never winds down.
4.  I never allow Windows to turn off the hard disk.  (this might get set when you choose High Performance power plan, can't recall)
5.  I also never let Windows automatically sleep and/or hibernate.  (I do have shortcuts I set up to manually allow me to Lock, Sleep, Restart, and Shutdown, and if you want the shortcut 'innards' to build those for yourself, just post back to that effect, and I will post that info.  I use those all the time and under Windows 8 I find them quicker than using the default methods in Windows 8).
 
Bob Bone