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, 

Get the latest system program and drivers from here:
http://www.roland.com/sup...=downloads&p=UA-55

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. 
 

First off, does windows see the QUAD? If it doesn't, then Sonar will never see it.
2nd, Disable or uninstall your onboard sound chip.
3rd, make sure your type of drivers and your windows architecture match. If its 64bit, you need to install 64bit drivers, if the QUAD even has it.
 
Cj

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
 
 
 

Disabling or uninstalling a computer's on-board sound is not normally a required step, although some folks do this.
 
Many folks choose to run with the Windows Default Audio Device set to the on-board sound, and then the music applications, such as Sonar, are set to point to the audio interface.  This is how I choose to run, and it gives me the ability to play music through Windows at the same time I also have Sonar up and running, and I have no issues or conflict when I do this.  Rather, I have use for doing that.
 
There is nothing 'wrong' about disabling one's on-board sound, but it is certainly not normally required.
 
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.

While it is commonly recommended, it is often represented almost as a fact that it needs to be done, and that is just not the case.
 
If Sonar is not using the on-board sound as its audio device, for instance if Sonar is set to use a completely different device (like the ASIO drivers for an audio interface), then the conditions are not present for there to be a potential for 'conflict' between Sonar and Windows for the on-board sound device.
 
I DO agree that the original poster should check to make sure he has the correct version if his audio interface drivers, and that he has the appropriate 32/64 bit one that matches his OS configuration.
 
At the same time, if he simply was pointing to the WDM driver mode, getting that properly set to ASIO and getting the audio interface to be seen and selected in Sonar, then he should be able to have the option of leaving his on-board sound enabled and it then specified as the Windows Default Audio Device, such as what I do.
 
I find that a useful thing to do, and unless there is a problem with it determined, I don't think it should be represented that someone should always just go and disable or uninstall their on-board sound.
 
Bob Bone
 
 
 

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
 

marvinglenn
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, 

 Hi. I have had issues getting Sonar to 'see' this card as well...especially if Sonar stops working. I don't know if this will help you, as Sonar will usually 'see' QC when first starting. However, if as I mentioned, it stops working, then if I restart Sonar, it states there are no audio devices on my system, despite Windows seeing it. So what I do, is after Sonar stops working I have to wait until Sonar shuts down from Task Manager - oh and I have to unplug QC.
 
Once Sonar disappears from TM - driver hang I've been told - then I re-plug in QC and then right-click on my volume icon and select playback devices. I then click on QC properties and go to 'advanced' and do a test. So I usually hear the test example. I then restart Sonar and it will 9/10 see QC. On the rare occasion it doesn't, I just do the test again after closing Sonar and it's game on.
 
It's a bizarre work-around, but it gets me working again without needing to reboot...loggin off/on again does not work.