Beepster
"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.

 Word.
 
Like I say tho, the underlying issue *i believe* is the way programs bind and hog bitrates according to the drivers written.
I would suggest that Sonar have an equal responsibility too especially as I have just tested that PT works fine but Sonar doesnt (NOT A PLUG FOR PT!!!!) I also have read that Sonar are way more up to speed with conforming to the latest MS coding...

Either its a shame for me.

Beep, in an ideal world in the creative platform a bit more of an open source attitude between platforms of OS versions and drivers and Software would leave us Customers in a better place, unfortunately the corporate world wont allow it (But I shall dream of such a place this very evening, could turn into a an Ap[le shop nightmare of sci fi horror very quickly which I WONT subscribe to)

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

 Yes, naturally.

markyzno

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.

I did not roll back to Win 7, but to an earlier Win 10 build. Will give the build nr tomorrow.
All the best.

Zargg71

markyzno

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.

I did not roll back to Win 7, but to an earlier Win 10 build. Will give the build nr tomorrow.
All the best.

Lets swap build numbers when you can! cheers fella.

Ya... I love Sonar but it seems quite a bit crankier about such things in general. That's why I'm slowly poking at Reaper. Not to replace Sonar but to have a less finicky platform to fallback on for certain things when Sonar decides to give me a hard time.
 
For your issue though... should be working, man. That whole thing about your MOTU software screwing around is a huge red flag.
 
Maybe an uninstall/reinstall of the MOTU drivers is in order? You're doing pro level stuff though so really I'd be calling support for both MOTU and Cake. Mucking about wildly would make me very nervous.
 
This does not seem to be a simple issue.

Beepster
Ya... I love Sonar but it seems quite a bit crankier about such things in general. That's why I'm slowly poking at Reaper. Not to replace Sonar but to have a less finicky platform to fallback on for certain things when Sonar decides to give me a hard time.
 
For your issue though... should be working, man. That whole thing about your MOTU software screwing around is a huge red flag.
 
Maybe an uninstall/reinstall of the MOTU drivers is in order? You're doing pro level stuff though so really I'd be calling support for both MOTU and Cake. Mucking about wildly would make me very nervous.
 
This does not seem to be a simple issue.

Indeed. But calling support when I am a Problem manager in IT ...well Support isnt working for me as I dont want to waste time. The power of this forum and managing my own ticket is a better solution for me.
 
Your red flag is correct, as is WIN10 updates...as is only Sonar does this and PT does'nt.
 
Simple KT (everyone here as a trouble shooter should look at Kepner Tregoe Methodology for Problem Analysis btw, thats another thread)

Maybe dupe the thread down in the Computers subforum to see if Jim or the other lads are kicking about. I hear ya about more eyes up here and more chance of similar configs but the thread will roll off quicker and the tech doods don't visit as much.
 
Totally sounds like complex system related stuff and that sub definitely excels at such things... albeit a little more slow moving. Between the two you may get the answer and solve it for others experiencing similar issues.
 
All that is to say... IR2dum2halp.
 
;-)
 
Edit: Oh and toss MOTU in the title or something. That'll draw MOTU user eyeballs to refine things a bit.

Beepster
Maybe dupe the thread down in the Computers subforum to see if Jim or the other lads are kicking about. I hear ya about more eyes up here and more chance of similar configs but the thread will roll off quicker and the tech doods don't visit as much.
 
Totally sounds like complex system related stuff and that sub definitely excels at such things... albeit a little more slow moving. Between the two you may get the answer and solve it for others experiencing similar issues.
 
All that is to say... IR2dum2halp.
 
;-)
 
Edit: Oh and toss MOTU in the title or something. That'll draw MOTU user eyeballs to refine things a bit.

But its been tested on MOTU AND M-Audio, same results.
 
The only thing that is constant here is no driver updates since Win7 which harks back to my point of continuity of code.

Beep,changed title thread in the hope of a Root Cause analysis for future problem seekers. x

I assume this was an existing system that worked with Win7 and now doesn't work with Win10.  Have you changed any of the USB ports that your devices are using?  Sometimes that error pops up when the device isn't put back in the same port.