Anderton

boblentil
Thanks for the feedback.  The sound card and latency settings appear to work fine in Ableton Live, which is why I thought this might be a SONAR issue. 

 
Are you using the 32-bit version of Ableton Live?

Yes.

I also should have asked if you're using the 64-bit version of SONAR...if so that might very well explain the difference if the product's 64-bit driver isn't as developed as one for 32-bit systems.

Ah haaa! :)

Anderton
I also should have asked if you're using the 64-bit version of SONAR...if so that might very well explain the difference if the product's 64-bit driver isn't as developed as one for 32-bit systems.

That was indeed the issue.  I switched to the 32-bit version of SONAR, and that solved the problem.  Thanks.

My understanding is that Sonar has no control over ASIO settings. Notice in the screen shot the adjustment for the buffers are grayed out in Sonar's Preferences. The ASIO panel is where changes must be made. However, the handshake may not work depending on how that panel works with various DAWs.  
 
If it doesn't send the data to Sonar than Sonar can't update itself. This could be due to the need to adjust the hardware manually. Some interfaces use the software ASIO panel to reflect how the hardware is set. Not to actually set it. I think this is what Beepster is referring to when he talks about needing to cycle on the hardware in some units.
 
I know that it all depends on the architecture of the hardware and how well drivers are written for it as to the ease of using software to adjust its settings.
 
 
I would try a WDM driver for this unit and see if that clears up the problem. 
 

When Ableton introduced a 64-bit-compatible version, they nonetheless recommended installing it only if essential because at least at that time, many of the tools people used with Ableton Live were still 32-bit. 

@John... I picked up Karl Rose's SWA X2/X3 vids when they were on special a while back and in the device setup section he talks about how the buffer slider and I think some of the other settings in preferences are for the other driver modes (WDM and the other one that is eluding me at the moment)... not ASIO. To me I just took that as the reason why I've never had much luck with those settings from within Sonar. The weird thing though is that I figured the ASIO Panel button would open the ScarlettMix software and I know that has work occasionally but mostly it hasn't.
 
Doesn't matter anyway because I have my foolproof method now and I prefer it anyway. I just figure the ScarlettMix software is ignoring Sonar for some reason and things get all wonky anyway when I change the interface settings with Sonar open anyway.
 
The OP was obviously having a 32/64 bit conflict though which seems to be solved so my post is not particularly helpful.
 
Meh.
 
Cheers.

Beepster
@John... I picked up Karl Rose's SWA X2/X3 vids when they were on special a while back and in the device setup section he talks about how the buffer slider and I think some of the other settings in preferences are for the other driver modes (WDM and the other one that is eluding me at the moment)... not ASIO. To me I just took that as the reason why I've never had much luck with those settings from within Sonar. The weird thing though is that I figured the ASIO Panel button would open the ScarlettMix software and I know that has work occasionally but mostly it hasn't.
 
Doesn't matter anyway because I have my foolproof method now and I prefer it anyway. I just figure the ScarlettMix software is ignoring Sonar for some reason and things get all wonky anyway when I change the interface settings with Sonar open anyway.
 
The OP was obviously having a 32/64 bit conflict though which seems to be solved so my post is not particularly helpful.
 
Meh.
 
Cheers.

All posts are helpful that try to stay on topic. Mine was more for why things seem the way they are. I don't think a 32 bit driver will load in a 64 bit OS. So that can't be the reason.  

I'll try to stay on topic here. 
 
I use the FA-66 with the 64 bit Win 7 drivers.  In 8.5 I used its ASIO drivers with 2.4ms effective latency.
Since the X-series (I'm on X3e) the wave profiler doesn't recognize my ASIO drivers and now I'm using WDM with effective latency at 9.0ms.  I still do occasionally notice the difference.
 
I've brought this up before,  but any ideas?  Thanks.

The wave profiler does not analyze ASIO drivers.  It didn't do it in 8.5.3 either, unless my brain just cut out on me.
 
Bob Bone