I think this could be an issue with sample rate change on win 10 not working properly.
I`m seeing alote of treads about win 10 and usb problems while trying to solve my problem.
I hope its not that big cause if we have to wait for Microsoft God help us all.
Peace

I had this problem a lot while using Steven Slate Drums 4. At slower tempos, it would work, but once I bumped them up to 180+, I'd get motor-boating and then complete loss of sound. I usually had to reboot to get the sound to return.
 

Just FYI, I've been working in X3 all evening and haven't had the problem.  Haven't even had to press the audio reset button.  Seems like its a problem w/ Platinum?

Sorry to hear of your woes Chuck. I had issues with the audio engine in the last update too and have rolled back to an earlier stable version as I have upcoming shows. Slightly disturbingly, a simple rollback didnt rectify the issue.  I had to reload a disc image I took before updating to return my system to normal operations. 

Interesting. I've only just posted elsewhere about something similar. I also believe it relates to win10 and sample rates. I will stick with the current sonar version and await the next update to see if anything changes. You reminded me Bruce I need to buy another drive for disc imaging backup.........

MacFurse
Interesting. I've only just posted elsewhere about something similar. I also believe it relates to win10 and sample rates. I will stick with the current sonar version and await the next update to see if anything changes. You reminded me Bruce I need to buy another drive for disc imaging backup.........

Money well spent Dave:)
 
DAW is offline and I have not updated windows recently. Sonar is the only thing that has changed so I believe the issue for me is there. I'm thinking I'll sit out a couple of updates. Always seems to work wonders, particularly after big changes.

Interesting thread, guys.
 
just last night I had the same issue 3 times that Sonar "lost connection to its audio engine", meaning the song kept playing but Sonar entered the non-responsives state. playback was fine but could no longer be stopped neither from keyboard nor control surface. i know i had been pushing the system hard, running low ASIO buffers and doing "nasty" things like adding plugs while playback ... still, been guilty of that before, but have not seen that behaviour
 
The other odd thing is that Sonar occasionally does not like the combination of certain plug-ins e.g. FF MB and WAVES AR Plates (on different buses). Independent of ASIO buffer size it will crackle. Often closing the project and reopening fixes it (no changes to buffers or plug settings) ... weird
 
 

I've had this issue as well with both Windows 10 and Windows 7. In my case it occurred when dragging in audio from my desktop through the browser. When just importing through the drop down menu it worked fine. This is on two different PCs with different soundcards (both USB) and Platinum on one machine and Professional on another. 
 
Edited to say that the Win 10 PC is Anniversary Update, skipped Creators Update for now. Audio devices were Focusrite Scarlet 18i20 2nd Gen on Win 10 and Steinberg UR22 MKII on Win 7.
 
 

"Slightly disturbingly, a simple rollback didnt rectify the issue.  I had to reload a disc image I took before updating to return my system to normal operations. "
 
Tenfoot that could easily point to something in the OS not Sonar.
Peace

maltastudio
"Slightly disturbingly, a simple rollback didnt rectify the issue.  I had to reload a disc image I took before updating to return my system to normal operations. "
 
Tenfoot that could easily point to something in the OS not Sonar.
Peace

If you rolled back and also rebuilt the aud.ini file in Sonar, then it would most likely narrow this down to either the audio drivers or the OS, and rule out Sonar.