ROLAND QUAD CAPTURE UNSEEN BY SONAR X3

It seems i've tried everything.  Latest driver for Quad Capture is installed.  My other DAW recognizes Quad Capture consistently and functions properly.
Sonar X3e is consistenly blind to the Quad Capture interface.  I re-installed Sonar, still no go.  Any suggestions?
 
Thanks for your time and help.
 
Win 8.1, 64 bit, i7 3.9 GHz, 16 GB ram, 

http://forum.cakewalk.com/PLEASE-RECOMMEND-AN-AUDIO-INTERFACE-m2880540.aspx#2887792
 
So last time you posted you were having trouble with your Scarlett 8i6. You never really came back to say if you resolved your issue. 
Did you ever let Matt from focusrite help you out? 
did you every optimize your computer? 
 
Anyhow the currant issue, If Sonar is not seeing the Quad Capture, what is it seeing? Your on board card? If so disable it. 
 

OK - perhaps it is not being seen because you have a non-ASIO Driver Mode specified in Preferences, such as possibly using WDM drivers for the Windows on-board sound.
 
Fire up Sonar, hit 'ESC' to close the Quick Start dialog box, and then hit 'P' on your computer keyboard to bring up the Sonar Preferences dialog box.
 
Navigate to Preferences>Audio>Playback and Recording, and look at what is specified for Driver Mode.  
 
If it isn't set to ASIO, you will likely not be able to see your interface show up in Devices.  IF this is the case, you can't simply change the Driver Mode yet to ASIO.  First, you have to go back and remove the check boxes from any enabled Devices, so navigate to Preferences>Audio>Devices, and remove the checks from any enabled devices.  THEN, go back to Preferences>Audio>Playback and Recording, and you should now be able to change Driver Mode to ASIO.
 
Once Driver Mode is set to ASIO, if you go back again to Preferences>Audio>Devices, you should (hopefully) see your audio interface show up and be able to be selected.  (IF your ASIO drivers for the audio interface are installed in Windows).
 
I hope I have explained the above well enough to be followed.  Please let me know if I melted your brain, and I will take another stab at explaining it.
 
Bob Bone
 
 
 

Bob when trouble shooting this particular issue it is a common step to take. Especially if someone has a PCI sound card installed. They are notorious for hoging the audio engine. What CJ said about checking windows is good advice too.
Let's wait for the OP before spending to much effort here, Last time he posted he never came back.

Oh - and Cactus - I agree that if this original poster has abandoned posts in the past, that waiting to make sure they are engaged in the thread is DEFINITELY a good idea.
 
Thanks for the heads up that they had done that in the past :)
 
Bob Bone
 

There are some common USB issues...not sure if they apply here, but you never know.
 

• USB 3 vs. 2. Some 2.0 interfaces aren't happy with 3.0. Some are happier with 3.0. Who knows?
• USB port sleep being active, which you need to turn off in Device Manager.
• Forgetting to turn on the USB interface, and then Sonar uses the onboard sound card. Now it thinks the onboard sound card is what you want to use because that's what it sees.
• USB having a bad day, going into a bar, getting drunk, and passing out. Once it's passed out, it doesn't work any more until it becomes sober.

 
I did manage to solve a variety of "weird" USB problems by getting a USB 2.0 PCI card and using it exclusively for USB audio devices.
 

I should have been more specific in my earlier post.
 
I was referring to situations where the on-board sound isn't using a set of ASIO drivers, and Sonar or your other music production software are the only applications using ASIO driver mode.
 
When there are multiple ASIO drivers present that are loaded into Windows memory, they too will be seen by Sonar, when Sonar loads and Sonar is set to a Driver Mode of ASIO.  This CAN be problematic, as folks often find out when they have ASIO4ALL installed along with their more high-end 'real' ASIO drivers from an audio interface.
 
Sooooo, for computers where the Windows Default Audio Device is set to the on-board sound, AND that set of drivers is NOT ASIO, if Sonar is set to Driver Mode of ASIO and the audio interface drivers are installed, THEN the on-board sound can exist peacefully to be used by all non-Sonar applications, while Sonar will just as cheerfully use the ASIO drivers of the audio interface.
 
THAT is a better explanation (I hope), of what I meant to describe.
 
I seem to recall that Sonar tended to pick and automatically assign the ALPHABETICALLY first detected audio device when multiple ASIO drivers were 'seen' when Sonar started.  This was often problematic.
 
Folks plugging in their audio interface to different USB ports from one start up to the next also frequently cause themselves problems, as many times the installed drivers will not be 'seen' by Windows or Sonar.
 
MAYBE, the original poster will come back from hiatus to engage in their thread.
 
I will consider my above posts to be all I will put out there for this thread, until the OP comes back into the discussion, so until that happens I will bow out of this discussion.  Also, I feel for you on those other bizarre problems from having a second set of ASIO drivers present in the computer.  Glad you have that squared away enough to get your work done without going any more crazy then you currently may be.  :)
 
Bob Bone
 

BENT
Yep It's a common occurrence for me to.The easiest workaround for me is to uninstall and reinstall QC's drivers.A pain in the but I'm up and running again quickly.  

 
That shouldn't be necessary...there must be something else going on.