scook

Rski
No worries anyway as what others said, besides when adjusting the latency on your sound card app...Sonar needs to restart before the latency changes take effect. .

Not necessarily. I adjust the buffers for my interface using the vendor supplied AudioBox client and SONAR picks up the change without restarting.

I kinda wish that was the case on my Focusrite Saffire Pro40 - the Mixer app actually locks all settings related to drivers/buffers/latency when ASIO is in use. I need to have any ASIO aware application closed in order to change settings. Not a big deal, but it's a minor annoyance on longer project sessions, when I'm tweaking latencies for softsynths and am going back and forth between different settings.

Focusrite Scarlett 18i6 here and it's never worked for me either. Also if I open the Scarlettmix panel with Sonar running and change my buffers Sonar gets all crashy on me so I just close Sonar before making such adjustment.
 
Can't remember if my Echo worked with the ASIO button. I think it did. Maybe it's a PCI thing.

stevec
In my case I have to click on the ASIO button twice - the first click never opens the ASIO panel, but the second click always does.   Strange, but true.   
 
 

hmm... With your Scarlett?

With both a delta 1010 and now the impact twin, I open the "asio audio interface" and the "preferences" in Sonar, change buffer size on the audio interface then click apply change in Sonar preferences. Works like a charm.

robert_e_bone
It's not that it '"didn't work".  Sonar provides that ASIO Control Panel button IN CASE the driver UI is written to take advantage of it.  Some are, and some are not.

 
Yes, it's up to the interface manufacturer to decide how they want to expose their applet.
 

It's not that Sonar is broken, or that the UI is broken.  It's just that different companies do it sometimes to respond to that button in Sonar, and some companies instead launch access to the UI for their audio interface by opening an icon that sits in the Windows System Tray.
 
I have only seen the above two methods, though there may be some that use neither, and instead require double-clicking on some desktop icon.

Here's another method -I like what TASCAM does with the US-366 and US-322 desktop interfaces - there's a button on the top of the box that opens the applet as well as the built-in DSP. I actually don't know if I can access it from within Sonar; pushing the button is so convenient I haven't tried anything else.

there's a button on the top of the box that opens the applet as well as the built-in DSP. I actually don't know if I can access it from within Sonar; pushing the button is so convenient I haven't tried anything else.

 
Funny, there's no button on the box that my interface came in. 

Beepster

stevec
In my case I have to click on the ASIO button twice - the first click never opens the ASIO panel, but the second click always does.   Strange, but true.   
 
 

hmm... With your Scarlett?

Yup.  The first click on the ASIO button does nothing, but when I click a second time (not double-click) the ASIO applet will open - just a slider with values displayed.   It's much quicker than opening the mix panel, and it never crashes.  
 
 

jeebustrain
I kinda wish that was the case on my Focusrite Saffire Pro40 - the Mixer app actually locks all settings related to drivers/buffers/latency when ASIO is in use. I need to have any ASIO aware application closed in order to change settings. Not a big deal, but it's a minor annoyance on longer project sessions, when I'm tweaking latencies for softsynths and am going back and forth between different settings.

I like that feature and I can see why it is implemented. Many apps that use ASIO will crash if you change the settings in mid flow. People would be logging calls to Focusrite otherwise asking why the Saffire is crashing the ASIO app, so this reduces their support calls.... Perfectly reasonable... I notice the ASIO apps tend to inherit what the Saffire has already set anyway.
 
BTW please make sure you are on the latest mix control software without the legacy firewire driver if your behaviour is different to mine.

stevec

Beepster

stevec
In my case I have to click on the ASIO button twice - the first click never opens the ASIO panel, but the second click always does.   Strange, but true.   
 
 

hmm... With your Scarlett?

Yup.  The first click on the ASIO button does nothing, but when I click a second time (not double-click) the ASIO applet will open - just a slider with values displayed.   It's much quicker than opening the mix panel, and it never crashes.  
 
 

Weird. Maybe it was another case of X2 acting like a jerk to me. Maybe I'll see if it works in X3. Not really a big deal anyway. Takes like 5 extra seconds the way I've been doing it.

For me, it behaved the same way in X2.  Regardless, it's certainly worth a try in X3!