Asio driver not recognized when using Focusrite Scarlett 18i20 3d since upgrade to Sonar

[Marco Werkman]

Hi,

I am using Sonar for more than 20 years now and moved to the new cakewalk version. I am using a Focusrite Scarlett 18i20 3d gen for 1,5 years now. Unfortunately I cannot select ASIO as a driver in the new version. Instead it uses WASAPI which comes with a unworkable amount of latency. Obviously all drivers were installed properly because they work with the previous Sonar, but also in other DAW's.

Any ideas?

Gr Marco

[Bristol_Jonesey]

Have you downloaded the latest driver from the Focusrite website?

Just FYI, I am using a Focusrite Scarlett 18i20 3rd gen with the new Sonar and it works perfectly.

[Chaps]

Have you downloaded and installed any Steinberg software? The Steinberg ASIO driver they install can cause ASIO problems. I would check your registry and see what is in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ASIO .

[msmcleod]

The most common reason for this is due to having an aggregate ASIO driver installed (such as ASIO4ALL) alongside the manufacturer's ASIO driver.

When Sonar enumerates the available ASIO drivers, it opens each one to determine what bit-sizes / sample-rates are supported.  If you have an aggregate driver such as ASIO4ALL installed, this driver will open your real audio device and quite often won't "let go" of it when the driver is closed.  This causes the real ASIO driver to be unavailable because the device appears as being still in use.

Another reason is simply because the ASIO driver it's being used by another application. 

[Amberwolf]

5 hours ago, msmcleod said:

When Sonar enumerates the available ASIO drivers, it opens each one to determine what bit-sizes / sample-rates are supported.  If you have an aggregate driver such as ASIO4ALL installed, this driver will open your real audio device and quite often won't "let go" of it when the driver is closed.  This causes the real ASIO driver to be unavailable because the device appears as being still in use.

Is there a way to code Sonar so that it simply doesn't open drivers it "knows" are this type of driver, or others that it "knows" are incompatible for whatever reason?   

"it knows" meaning y'all having created a list of those, kept updated, preferably something in an ini file that can be hand-updated if necessary, so a user can either add a new one to it if they have a problematic unused driver on their system that must remain for some other program, or remove one from it if they actually need that driver for Sonar and it does work on their system normally. 

 

It would save y'all and a lot of users a whole lotta heartache and time.