Hi All,
 
So, I have been on a bit of a hiatus (work related) and havent had a chance to fully play with Sonar and WIN 10 since my recent upgrade a good few months back.
 
Now I am firmly back in the creative zone and attempting to create I am back with a very basic error in Sonar Plat and Sonar X3 with the dreaded load a project and no playback due to the age old error in the title of this thread.
 
I am an aged and very experienced Sonar user so have been through all the basics.
 
so, what happens.
 
1. Open or create a new Sonar Project
2. Hit record or play.
3. "Unable to open record device etc etc"
4. Check Bitrate settings - Tick (if not in control panel, align them)
5. Reboot
6. Double check settings
7. See step 3.
8. Get really annoyed and apply Kepner Tregoe.
 
So, applying KT on this tells me that this never happened before on win7 or Win 8 with my MOTU Audio Express. Other apps work fine such as standalone NI gear like Traktor and Maschine or standalone Apps like Reaktor. This also happens on my Delta 1010.
If I change bitrates in W10 then a few reboots will eventually get rid of pops and crackles but I cannot get sound from Sonar.
 
I can assure you my settings are fine.
 
Very hard to troubleshoot. One thing I noticed was that if I loaded an old project Sonar will play but after a reboot back to step 3.
 
For me its clearly a sample rate issue between Win10 and Sonar and Drivers but trying to get some stability here is making me reach out to the forum.

I know there have been changes and work in WIN 10 and indeed Sonar in adapting to WIN10 but something here isn't right in my unchanged workflow.
 
So, with my change management head on, the only thing that has changed is Win10 and possibly installing PLAT also (side by side)
 
Come on then detectives! Discuss!
 
(this is very frustrating for me as I have two films coming up and rebooting my PC and unable to playback in Sonar is indeed, a massive hindrance)

Hi. Did you do a clean install, or an upgrade to Win 10?
I have seen posts, where an upgrade to Win 10 messed things up, but a clean install did not.
Are you running the 1010 in compatibility mode? You do not happen to have NI Replika 1.22 on your projects?
That is all I could think of for now.
Best of luck.

Hi Zargg71.

Now, Upon further thinking when I upgraded to WIN 10 the first thing I did was test Sonar. Green tick.
Since then I have been forced Win10 updates as have we all unless Enterprise.

KT is pulling me towards a forced WIN10 update.
 
Are the updates pushing Bakers code out of sync with communicating with sound drivers?

Hiya, Mark. I was wondering where you got to. :-)
 
This is likely not helpful but I get this message whenever I try to force Sonar to use a different driver mode on an existing project. Admittedly I have no idea what I'm doing when it comes to that stuff but if I, for example, take a project I recorded in ASIO and try to play it back in WDM it throws the error.
 
I have not investigate it beyond that and just stick to ASIO. This came up while I was mucking around with Voicemeeter recently. I need to explore it more.
 
My point? Maybe a driver thing (like outdated/incompatible/wrong driver setting) and... helloooooo.
 
Cheers.

I am utterly convinced its a binding of Bitrate between Windows and Sonar, a fight.
 
So, I did disable Cortana and Flash and other such nasties that would bind to my Sound Card (although thiswas never problem before) but, to no avail.
 
My 10/10 is disabled
onboard sound chip, naturally disabled.
Just routing through the audio express (drivers up to date)
Standalone Apps fine. Sonar not.
Tested with or without NIC - same crud
Tested exclusive mode with or without - same poop
 
One thing I have noticed is that now I cannot open my MOTU audio console without uninstalling it and reinstalling it, then it opens but when I reboot I cant open it. This again leads me to think its a binding of drivers issue yet my 10/10 has the same issue but can open the console if I enable it.
 
Nothing worse than an onion layered problem.
 
 
 

Due to an issue with my Tascam FW 1884 I rolled back Win 10 (but I cannot find out to which version), and all is well here. So I would try to do that if I were you. 
Ps. Just found out how to check Win version. But cannot do this until tomorrow, as my studio is being set up from scratch again. Will report back.
All the best.

Beepster
Hiya, Mark. I was wondering where you got to. :-)
 
This is likely not helpful but I get this message whenever I try to force Sonar to use a different driver mode on an existing project. Admittedly I have no idea what I'm doing when it comes to that stuff but if I, for example, take a project I recorded in ASIO and try to play it back in WDM it throws the error.
 
I have not investigate it beyond that and just stick to ASIO. This came up while I was mucking around with Voicemeeter recently. I need to explore it more.
 
My point? Maybe a driver thing (like outdated/incompatible/wrong driver setting) and... helloooooo.
 
Cheers.

I dont use WDM.
 
I am Mr Asio.
 
See my further point about bindings and drivers.
 
Hello Beep btw, good to be back although I have checked the Forum everyday :) XxX

"One thing I have noticed is that now I cannot open my MOTU audio console without uninstalling it and reinstalling it, then it opens but when I reboot I cant open it. This again leads me to think its a binding of drivers issue yet my 10/10 has the same issue but can open the console if I enable it"
 
I'd poke around the intertubeys and see if maybe there have been reports of problems with your MOTU driver and Win10. Maybe there is another point version that works better... or you can yell up MOTU's arse to help you and/or fix it.
 
They should have their shiz together at this point though. Win10 has been out long enough.
 
Cheers.

Zargg71
Due to an issue with my Tascam FW 1884 I rolled back Win 10 (but I cannot find out to which version), and all is well here. So I would try to do that if I were you. 
Ps. Just found out how to check Win version. But cannot do this until tomorrow, as my studio is being set up from scratch again. Will report back.
All the best.

Hi Zargg71
 
Rolling back to Win7 is not an option for me and nor should it be for anyone as that papers over the cracks. My studio HAS to be up to the most modern of OS. The mere thought of going back to win 8.1 is ghastly and the thought of going back to Win7 is even worse as its core is Vista.
 
But will appreciate your feedback.

Did you try moving the AUD.INI file somewhere Sonar can't see it and letting it recreate it?
 
Dan