Calling All Roland Sound Card Users (Quad and Octa)

Have you been experiencing issues recently where Sonar crashes and your ASIO device vanishes from your DAW ?  (No crash log sent to Sonar, no attempted recovery save, all work since last save lost.  Have to restart your computer to get ASIO device back)
 
Have you been getting frequent audio drop outs when using pro- channel ?
 
Have your projects started to take up to 8 minutes to load ?
 
It seems that others have been seeing these issues and I am wondering how wide spread.  My OCTAcapture was rock solid for years, however recently it has become very unreliable.  Not sure if this is a Windows 10 or Sonar issue ?
 
I do know that I have never had a crash using standalone VST instruments from Toontrack or NI, only seems to happen with Sonar. And my older version of reaper that I use to test with, seems to not have any issues.
 
Add on to this thread if you have seen this and any thing you have done to mitigate.
 
JR

Inserting Rapture Session also crashes the home computer

If you are crashing and losing the ASIO driver try these :
(Found this on a PT forum where people were having similar issues, so may be a Roland driver issue after all and not Sonar or Windows ???)
 
1) If you're using the ASIO driver in your DAW, then you should disable the device in Windows' audio properties (manage audio devices - select all Octa capture ins and outs to "disable") This way you don't have two different drivers trying to access the interface. Of course this means that you cannot watch a move or listen to MP3s on your DAW.  But as an experiment I am trying this and it does seems to be much more stable.  I have not had a problem with CA2A, but I added it to a project and opened and closed it a bunch of times.
 
2) Go into Windows' power profiles, click 'advanced settings' and turn off "USB Selective Suspend". This is a power saving feature that turns off power to the USB port if the device isn't doing anything.
Unfortunately audio interfaces tend not to play well with this.  (not sure if this is an issue or not, but when plugged in I disabled USB selective suspend)
 
On the Roland web page it says that Intel USB chip set is best, not sure if there is anything you can do about this, but this will be something I check if problem persists.
 
JR

I should add that I have upgraded Windows 10 pretty consistently, including the anniversary update.  And I have upgraded SPLAT to 2016.11.
 
Still playing with Sonar with all my Windows octa capture sound drivers disabled and solid as a rock...hmmmm
 
JR

My Studio-Captures have had this problem since late X2 updates!!! I have posted here many times for help and I hope that this thread has better results! I am comforted by auto_da_fe's post above and will try these immediately!!

I think it's a Windows 10 issue. I have an m-audio firewire 1814. over the last 10 days or so i have found myself with no audio device. I've disabled the hdaudio device. Seems that win10 deletes the 1814 driver, tries to force the nvidia hdaudio driver, but can't enable it. 

I would just be happy at this point if I could get the Windows 10 version Studio-Capture install package to keep backed up on my hard drive for those times when internet is not available! The only thing I have found is the driver itself but no installation on the Windows archive site.
The Roland company obviously sold the driver package to Windows because the driver is only available thru Windows Update!!!! I don't foresee any attempt to upgrade these drivers in the near future!! HOLY CRAP!!!

These things tend to be system related. 
Look at the replies and there's mixed success using the latest Windows , the latest Sonar and the latest driver from Roland. 
So myself I would follow best practices for setting up a computer for a DAW and especially try disabling all other audio drivers and devices. On board and HDMI.  
I don't have any on board audio and have no problem with using Media Player or watching a video. It all plays though my Scarlett or Tascam just fine. 
There have been a lot of threads with Roland interfaces issues. 
But there'a also a bunch about all other interfaces too. 
For $99 you can buy a Focusrite, Steinberg or Presonus interface and see if the issue goes away. 
For $150 you can buy a TAscam us2x2.. 
Those brands have "known" good ASIO drivers. 
If it doesn't send them back, If it does send them back and order your dream interface. 

I've had this problem recently with my Quad Capture, but it's only happened when loading projects with CA-2A in them. Given the other threads I've read about CA-2A causing crashes, I've removed it from the project (when I was able to load it using WDM drivers) and was then re-able to load with ASIO enabled.
 
Only started happening recently, and I've not updated Sonar since April (running 2016.03 at the moment).

I have worked about 5 hours straight with no drop outs, no crashes.  Things are very stable again.  ( I disabled Octacapture in Windows Sound)
 
I used CA-2A and inserted rapture session with no issues.  (did not have any before though)
 
I am pretty sure that at least for some of us, Octacapture drivers do not play well anymore with Windows sound.  I am also pretty sure that the big Win 10 annivesary update changed something and the OctaCapture drivers were affected for some of us on some systems.
 
At some point I will re-enable OctaCapture in Windows sound and see if issues return, but not for a while, i am really sick of restarting by PC.
 
Oh well...guess I am back to 8 years ago when my Firepod did the same thing....DAW only no Windows Sound.
 
JR

@Sidroe
 
Do you lose the QC drivers after a SONAR crash (for any reason)?
 
Or do the drivers just bail on you in the middle of a project? (I.e. "There are no audio devices for the current driver model on your system.")
 
fwiw, I tend lose mine on a Sonar crash (mainly issues with speed comping / take lanes) but a PC restart has always got me back up and running in the past. The installer routine works well enough if you're connected but does nothing to improve robustness. And yes, been looking into replacing it for some time, giving USB 3.0 a little more time to see what turns up. 
 
 
 
 

I'm using the Roland Quad Capture.  In general, it works great.   I have had a few issues which could have possibly been blamed on the Quad Capture, but they just as easily could have been blamed on other things like Windows, errant plugins, or other installed software.   I find that when an issue arrives that may be related to the Quad Capture, I can just uninstall the driver, and re-install.  That seems to clear up most issues.  Also, it's been years, but make sure that you have the latest drivers and firmware from Roland.  Eventually, I'd like to move to the UAD Twin USB, but I do see posts about that card, on occasion as well.

Hey, Jackson! Been mixing today! To answer your question, YES!!!!! A crash so hard it would make your teeth rattle BUT it only kills the ASIO part of the driver. The rest of the drivers and other apps using anything but ASIO still work. Once Splat crashes, the ASIO driver is gone and restarting will not bring it back. I have to totally uninstall the drivers, clean the registry, go online and let Windows Update reinstall the drivers!!!
The problem is the ASIO driver is the only driver that allows the 2 Studio-Captures to be synced together and use all 32 ins and 20 outs. Needless to say, the latency is too high with the other drivers and you can only use 1 Studio-Capture.
I wouldn't mind it so bad if I had the driver installation package for Windows 10 on my hard drive but Roland no longer has that driver available for download. You have to use Windows Update to reinstall!!!  AAAARRRGGGGHHHH!!!
I even tried the hack for the older Windows 8.1 driver but it will not work either!!!

I have a QuadCapture here and everything is rock solid until I open projects with the following plugins:
 
CA-2A
BT-Analog Trackbox
Rapture Pro

I checked in Windows Log gonna post here my findings if there's some useful info for the devs.

CA-2A:
Faulting application name: SONAR.exe, version: 22.11.0.111, time stamp: 0x583dc663
Faulting module name: CA-2ALevelingAmplifier_64.dll, version: 2.0.1.97, time stamp: 0x5802558a
Exception code: 0xc0000409
Fault offset: 0x0000000000085e88
Faulting process id: 0x2178
Faulting application start time: 0x01d250caa3ad2212
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Cakewalk\x64\SONAR\SONAR.exe
Faulting module path: e:\vsts x64\CA2ALevelingAmplifier\CA-2ALevelingAmplifier_64.dll
Report Id: 0d9a99e9-2e89-47eb-9b89-6250c845f637
Faulting package full name:
Faulting package-relative application ID:

BT-Analog Trackbox:
Faulting application name: SONAR.exe, version: 22.8.0.31, time stamp: 0x57c83875
Faulting module name: BT Analog TrackBox.dll, version: 0.0.0.0, time stamp: 0x5227a642
Exception code: 0xc0000005
Fault offset: 0x000000000000329e
Faulting process id: 0x2450
Faulting application start time: 0x01d219f78a2ea74c
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Cakewalk\x64\SONAR\SONAR.exe
Faulting module path: c:\program files (x86)\steam\steamapps\common\cakewalk\x64\vstplugins\Nomad Factory\BT Analog TrackBox.dll
Report Id: 3a49c21b-008f-4b93-b1d8-4322afb6f167
Faulting package full name:
Faulting package-relative application ID:

Rapture Pro:
Faulting application name: SONAR.exe, version: 22.11.0.111, time stamp: 0x583dc663
Faulting module name: RapturePro_64.vst3, version: 2.0.4.25, time stamp: 0x569d3a4b
Exception code: 0xc0000409
Fault offset: 0x00000000001d52e4
Faulting process id: 0x28e8
Faulting application start time: 0x01d24e127e114410
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Cakewalk\x64\SONAR\SONAR.exe
Faulting module path: c:\program files\common files\vst3\Rapture Pro\RapturePro_64.vst3
Report Id: 7ffb6000-5922-4c9d-8796-00c0dc024345
Faulting package full name:
Faulting package-relative application ID:

I have odd crashes/dropouts/etc and own an Octa-capture....but I've never been sure if it was the OS, the interface or a combination of software....(Had the same stuff happen with both win7 and win10) or some mix of all of them....
 
But sometimes task manager will save me, other times I will have to reboot.  It'd be a shame if it was the fault of the Octa....I like using that interface....previously I used an m-audio delta 1010 for over a decade....and thought it was a decent interface, but I like the Octa a lot more.