Windows 10 - Lose Sound When Exiting Sonar Professional

Hi Mark,
 
Check the list of processes to see that Sonar has actually stopped running.
If it's still running, that might explain the behavior you're experiencing.

Some USB MIDI drivers (Korg in particular) would not let go when closing Sonar.
Sonar would thus appear to close... but couldn't completely shut down.
This may not be your situation... but it can cause similar symptoms.   

OK, so here's the behaviour, as best as I can describe.
 

• Run Sonar, everything works fine, regardless of whether another sound application is running (browser with YouTube was my test case).
• Run browser with YouTube, everything works fine.
• Run browser with YouTube after closing Sonar, no sound.
  • In this scenario, Control Panel | Sound | Saffire Speakers - the config button is in active.
  • Disable Saffire Speakers then re-enable, YouTube works.  
• If I open both Sonar and YouTube at the same time, only Sonar produces sound.  However, if I then disable/re-enable the Saffire Speakes under Sound, both play fine.  I can even then open up new browser tabs and new browser sessions, and get sound from both.

It does seem to be how Sonar is holding the Saffire Speaker device.  I've run Process Explorer though, and I can't see any hanging threads when I close Sonar...

Thanks - my Windows settings are as yours, but I've no option under Audio | Playback and Recording for suspend audio engine when Sonar is not in focus.  I've got "share drivers with other programs", which is ticked.

Most windows programs do not use ASIO.
One thing not mentioned so far is sample rate. Windows and SONAR should be set to the same sample rate. The interface can only run at one sample rate at a time and may have trouble switching back to the Windows sample rate (assuming it is different than SONAR) after running SONAR.

The Saffire still has drivers other than ASIO or applications that expect a regular Windows driver will not work. Very few apps use ASIO.
 
Here is how to configure the default playback device in Windows:

• In the Windows Control Panel, open the Sound tool.
• In the playback tab, click on the default device.
• Click the properties button
• Click the advanced tab in the Properties dialog to set the default sample rate and bit depth.

 

abacab
 Everything must be at the same sample rate and bit depth.

Pretty sure bit depth does not matter but sample rate is a different matter.

Thanks for the responses, guys - I thought that the bit depth/sample rate might be the thing, but I've synchronised them and the issue is still there.  Have to use the Focusrite box, as I don't really want to be buying more speakers...
 
I'll keep plugging away at it.

Check the Default Playback Port (Control Panel>Sound>Playback tab)
Make sure the selected port is the one connected to your monitor speakers.
Play some Windows audio... and you should see the meter bouncing (next to the selected Default Playback Port).

Cross fingers, Mark. I had a similar problem that persisted for a few weeks and then magically went away. Now it's come back after a 2-month hiatus. Symptoms are similar, insofar as Windows audio is lost after closing SONAR. But dissimilar in that it sometimes goes the other way: no audio from SONAR after watching a YouTube video.
 
I am also a Focusrite/MixControl user over Firewire. I found that forcing the interface to reset itself would bring audio back, which I effected by changing the buffer size. This makes me suspect that the Focusrite driver or hardware may be at fault, or conceivably the Firewire driver or hardware.

I'll chime in on this one.
 
I too have a Focusrite Saffire interface running ASIO.  IMO, Windows 10 continuously and needlessly screws with the PLAYBACK DEVICES sample rate.  I need to stay at 48kHz, and Win10 likes 44.1kHz despite being selected in the menu to be 48kHz.
 
I guarantee that when your audio is lost, and there is no sound, you will find your PLAYBACK DEVICES set to 44100Hz.  Usually you can set it back to 48000Hz (or whatever rate you're using) and get the sound back without delay.  However, sometimes it completely borks, and your options will be unavailable.  It's locked up and the PC will require a restart.
 
This is one of the biggest annoyances I have with Windows 10 for audio-related stuff.
 
Additionally, Win10 likes to sneak in additional audio drivers on ya.  For example, I have my motherboard's audio DISABLED in the Device Manager.  Also, my monitor seems to have an audio driver despite NOT having speakers (Dell U3014).  If the link is lost between the PC and the monitor, for whatever reason, Win10 will re-enable this device and put my audio on that as the default device.  So ridiculous.
 
Windows 7 never screwed with the sample rate...ever...even when flipping back and forth between Windows sounds (e.g. Media Player, VLC, iTunes), Firefox sounds (e.g. YouTube), and other applications running ASIO (e.g. SoundForge).

fireberd
I have a Firewire interface (MOTU 896Mk3 Hybrid) and do not have any problems with the MOTU, PC audio or losing audio.  I have mine set to 44.1Khz.  I don't use 48Khz as I don't do any audio for video.  I have the Win 10 Fall Creators Upgrade installed (also worked OK before the Fall Creators Upgrade).

With 44.1kHz, then you're already good friends with Windows 10.  It won't try to change your ways because you're already where it wants you to be.