[Solved] Sonar Platinum dropped ASIO Drivers on my Roland Quad Capture

Hi,
 
I loaded Sonar Platinum and received a pop up message that says, There are no audio devices for the current driver model on your system. Please go to Edit | Preferences | Audio | Playback and Recording and choose a different driver model.  I don't know what happened as the Roland always worked with ASIO.
 
Does anyone know what I can do to get it to work again on ASIO?  I haven't recorded in a while, I thought about doing a system restore, I am on Windows 10, but I can't remember when I last used Sonar Platinum.  I finally had some quiet time and wanetd to record and now can't.  Thank you for your help!

have you tried...
 
1- cold reboot. shut your pc on/off again. a restart.
2- make sure you are using the very latest driver for your device.
3- make sure windows is up to date. if you have windows up to date, look at your last few "optional" updates
as a possible offender.
4- have you used the Roland on windows 10 yet ?

Hi,
 
Here is an update.  I did a search and found other users had this same issue and they were instructed to close Sonar and then go to the run prompt and enter %appdata%Cakwalk and then locate and delete the AUD or AUD.ini file.  Close the folder and then launch Sonar. I tried it but it didn't work. So I tried it again but this time restarted the PC and it worked.  Does anyone know what AUD.ini is?  I am curious as to why it stopped working and what it was that made this work?  I also read another article where someone went to regedit to remove files and do a clean install bt I am not that brave!  Thank you all for your help!

Thanks so much!  Does anyone know if a new version of Sonar Platinum is out?

Just had this happen with my Duo-Capture EX.  I was in the middle of copying some midi tracks into a new project and got a popup saying it's no longer available.
 
Actually I thought I had this solved.  Since the most recent win 8.1 update I've been having issues with USB ports shutting down.  I realized that having all the power options...that are accessible through the control panel...set so nothing will ever shut off,  does not affect usb ports through the device manager.  I went through all the usb ports in the device manager and turned off the power management options there.  Originally my computer keyboard started shutting off which alerted me to it.  Then both Sonar and FL Studio started loosing connection to the Duo Capture EX, then I started loosing the connection to my Roland A800Pro.  Turning everything off in the device manager, I thought, fixed it.
 
I did install the pre release recently, and this immediately started happening.  But it was running so rough on my system I rolled it back to the normal 05 version.  I figured by now the 06 update would be fine.  And it does seem to be running great.  I ran FL Studio for several hours last night and no issues.
 
I keep win 8.1 up to date monthly and also my keyboard and soundcard drivers.  I just updated to the latest Sonar Professional (2016.06) a couple of hours ago and it's back.  I don't remember this happening on .05...  At this point I'm just confused and tired of fighting it.
 
 
Reboot is the only thing that works for me until 30 min later when it's gone again. 

I've an old UA101, the predecessor to the capture range. Originally an Edirol interface rebadged "Cakewalk" when Roland owned Presonus and Cake, with drivers supplied by Roland.

Back when I used it, every once in a while it would lose connection with Windows in what sounds like exactly the same way as is happening here. Shutting down Windows, switching the interface off, rebooting then, once Windows had loaded the desktop, plugging the interface USB cable in and switching it on usually persuaded Windows to report it had found a 'new' audio device and load the drivers.

I eventually pinned the problem down to most likely being an intermittently failing USB socket on the interface. If the USB plug in the interface was wobbled a little bit in the right way the USB light on the 101 would blink and Windows report it had lost contact. Once contact was lost it often required the reboot procedure above to get things working again.

tlw

I eventually pinned the problem down to most likely being an intermittently failing USB socket on the interface. If the USB plug in the interface was wobbled a little bit in the right way the USB light on the 101 would blink and Windows report it had lost contact. Once contact was lost it often required the reboot procedure above to get things working again.

 
I have this problem on a few usb ports now. I'm suspecting my cat has has some fights with the usb cables when I've been out.
 

The first step to confirming it's a driver issue is this: when SONAR hangs shut down and reboot your Capture interface. If it still won't work, it's a driver issue. The only solution is a cold boot. Sorry, but that's what it take sometimes. The Capture interfaces are notoriously finicky in this regard.
 

I get this with my Quad Capture, a reboot always fixes it.

I kind of skimmed the last handful of posts in this thread - and DID read the first bunch thoroughly, and have a question.
 
For the folks who also experienced this issue, as well as the original poster of this thread, is it possible you had Windows also using the audio interface as the Windows Default Audio Device?  If yes, then I would suggest that might explain some of the issues - as the ASIO specifications are written to only allow a single application to have control of a set of ASIO drivers. 
 
So, if both Windows (playing of Windows sounds - mouse click, any of those dings/bells/whatever sounds that Windows plays - as well as Windows Media Player, playing a video on YouTube, etc.), AND Sonar are set to use the ASIO drivers of the audio interface, then there is a good chance of conflict.
 
I have been rock steady for years now, since I learned to split sounds off - I have Windows Default Audio Device set to use either a set of computer speakers, or the HDMI HD audio of the HDTV I use for my computer's display monitor, and it is ONLY Sonar that is set to use the ASIO drivers of my audio interface - and I NEVER have those weird conflicts like what some folks reported in this thread.
 
I recommend that you try testing setting the Windows Default Audio Device to something OTHER than the audio interface, and THEN see if Sonar works properly being the only application up and running pointing to the ASIO drivers of the audio interface.
 
(I do also have other music applications set to use the ASIO drivers of the interface, such as the stand-alone versions of Dimension Pro, Rapture, Rapture Pro, Kontakt, etc.), BUT I would only ever be running one of those programs in stand-alone mode at a time, and never also try to have Sonar up at the same time).
 
I hope the above makes sense - it is easy to test out, and if I didn't make enough sense, please let me know, and I will take another shot at explaining the above to make it clearer. :)
 
Bob Bone
 

I had this problem right after I installed "Razer Synapse" and "Razer Cortex".
Razer Synapse is an app for customizing my Razer gaming keyboard
Razer Cortex is a game boosting app.
Uninstalled both, restarted, and I have my Asio drivers back.
What's funny is I did this to myself a year ago, and forgot about it and reinstalled both recently. Took me a day to have a flashback and immediately solve the problem again.
 
 

Rare on my Studio Capture but a reboot ( occasionally TWO reboots) fixes it. For good luck  connect to the internet before turning on the Roland - then give it a few minutes to think after you turn it on. It is my understanding that the Roland checks for drivers/updates on startup when internet is available. 

Never had that problem with my Octa-Capture and Win 10 (early versions as I sold the Octa-Capture when I upgraded to MOTU).  

If the Quad capture is now class compliant in Win 10 it doesn't need new drivers for Win 10. Don't know about earlier OS's

Looks like the OP has gone leaving a thread title that creates an impression there's this big problem with Sonar when his problem has nothing to do with Sonar at all.

Then another poster says when they read the title of the threads they're too scared to update Sonar because of all the problems.