There was another thread that recently seemed to off topic when ASIO4ALL was mentioned.
 
Started this thread here to continue discussing the pros/cons of using either one with Sonar.
 
Original discussion is here:
Projects Corrupting
http://forum.cakewalk.com/FindPost/3581648

i have used asio4all for many years across multiple different windows systems with different devices with great success. i haven't tried the new wasapi option, because i work along the "if it ain't broke don't fix it" way of thinking
 
two main points:
asio4all needs configuring to work well
don't use asio4all if your device has its own asio drivers, asio4all is a workaround for those that don't (or are **** like alesis)
 
one comment: asio4all seems to be a bit of scapegoat for sonar issues in these forums, at least that's my perception - try it yourself, you might just be surprised how well it can work
 
/fwiw/ymmv/etc

Hi. I have found that on my laptop, WASAPI Exclusive mode is the best for this PC, and works better that ASIO4ALL did.
It might be down to the updates to WASAPI drivers that came some time ago.
All the best.

some more info: i currently use asio4all with an alesis photon x25 (external usb) and the onboard realtek on an i5 w10 laptop; i also use an edirol ua-1000 but that has its own asio driver; i haven't found time to perform any benchmarks

I recently found another rogue ASIO driver on my system.  A gift from Steinberg, apparently! 
 
"Generic Lower Latency ASIO Driver 64bit Will Be Installed"
https://www.steinberg.net/forums/viewtopic.php?f=250&t=107480
 
I had been testing WASAPI, so I had my regular external interface (with ASIO) shut off, and was using the integrated audio on my PC.
 
In the meantime, and totally unrelated to the audio test, I installed the trial version of Cubase 9 Elements.  Apparently it stuck this generic ASIO thingy on here by default.
 
I didn't pay much attention to that until I recently went to hookup my external audio interface again, using the dedicated ASIO driver.
 
Sonar refused to allow me to configure my real ASIO driver again until I did two things:
 
1. Uninstall the Steinberg driver.
2. Delete the "aud.ini" file from Sonar, and let it rebuild my audio settings. 
 
Wow!!!
 
The bottom line is that you really should clean house if you plan to install a real ASIO driver for your audio interface!!!

Just to add, my laptop is running ASIO4ALL just great with Platinum and the on-board Realtek audio chip. 
 
And the WASAPI performed very well with Platinum 2017.01 on my Windows 10 DAW.  But I'm back to my real interface now with ASIO. 

The Laptop I'm using WASAPI on is Windows 7.  I guess on a slow day I could try installing ASIO4all and see if it works. Id be curious to try the loopback test. 
 
That's interesting about the Stienberg driver. I have Wave Lab7 and Cubase 7LE on my DAW and I don't believe that has ever happened. I guess I could take a look, but I've certainly never had issues with drivers and I swap out between the Tascam and the Scarlett from time to time.
 I do have a Stienberg ASIO driver on my live recording laptop as I was in a band and we bought a Yamaha mixer with stereo USB. It worked great along side my Tascam us1641 in WDM mode I had 16 channels available and recorded a couple of shows without issue. 

I use WASAPI on my laptop when I am not using my interface.  Nothing to install or configure, just select the driver mode in Sonar and it just works.

And the winner is--------Asio4all! 
 
OK,   I installed ASIO4all to this laptop I use at work and have been running Home Studio under WASAPI exclusive for a few months. 
So here you go, Asio4all wins the loopback test. It is very close to right on which boils down to you could use it for overdubing. 
I think the reason it works is it activates the offset controls and reports the latency properly. In all other modes there is no offset adjustment available. I am going to give it a run and see how it goes over the next few weeks. I noted what Sonar was reporting in each mode for latency. Most where all 10 ms which was what the buffer showed. Only Asio4all showed the RTL which was 30 ms. So there you go all you nay-sayers ( me sort of included) 
 

pwalpwal
i have used asio4all for many years across multiple different windows systems with different devices with great success. i haven't tried the new wasapi option, because i work along the "if it ain't broke don't fix it" way of thinking
 
two main points:
asio4all needs configuring to work well
don't use asio4all if your device has its own asio drivers, asio4all is a workaround for those that don't (or are **** like alesis)
 
one comment: asio4all seems to be a bit of scapegoat for sonar issues in these forums, at least that's my perception - try it yourself, you might just be surprised how well it can work /fwiw/ymmv/etc

are you a "Loyal" Sonar ASIO4ALL user ?