I'm glad to hear about these improvements, but I'm not sure what the application of WASAPI is. I thought someone might be able to clear it up for me.
 
Occassionally, with my laptop mostly, I've attempted to use WASAPI drivers, but they've never been compatible with any of my devices.  
 
Who uses these drivers, and under what conditions?  with what hardware?  I've noticed that two of my 2-channel usb interfaces (Alesis iohub, and Audient iD14 both work with asio AND mme drivers!?!  They can be seamlessly switched and mixed and matched with my laptop's crappy onboard soundcard.   I like that.  Class compliance has made huge progress in windows.
 
How does wasapi factor in?

http://www.cakewalk.com/Documentation?product=SONAR&language=3&help=NewFeatures.002.html
 
It's for using on board audio, an improvment over MME, but not if your using W7. I tested it last night and posted here. 
 
http://forum.cakewalk.com/Home-Studio-and-WASAPI-m3521297.aspx
 
 

BIG improvement when using a laptop with an internal (realTec/IDT/etc) sound card. 
 
Also seems to make a big difference with generic USB sound devices.  Still experimenting here with a RockSmith guitar interface.
 
Glen

A recent driver issue lead me to discover that wasapi has come a long way and isn't just for laptop soundcards. I have 2 x32 digital mixers. The wasapi driver under Windows 10 solved a couple of issues I was having when using the supplied asio driver with the playlist feature in Sonar. Wasapi was introduced as a part of windows core audio in windows Vista in 2007 and has received major upgrades with every release since, particularly windows 10. It is vastly superior to the very dated mme driver model, and now a viable alternative to ASIO in certain circumstances.
 
That said, if your device has a well written and properly functioning ASIO driver, you probably wouldn't be jumping ship just yet:)

thanks everyone.
I'll try it with my on board audio when on my laptop.
I'm guessing it doesn't work with most "professional" interfaces?

This is an oversimplification, but you can think of WASAPI as an alternative to ASIO as a way for SONAR to talk to your audio interface.
 
For me (using a Focusrite Saffire Pro 40) WASAPI works great. I can get lower latency with ASIO, but the 5ms I get with WASAPI is perfectly adequate for playing virtual instruments in real time. One reason I use WASAPI is that I can set SONAR's buffers independently from other audio applications.
 
Some have reported that they couldn't get WASAPI to work with their interfaces. Others report that it only works in its native sample rate of 48 KHz and flakes out with 44.1. That hasn't been my experience, though. I'm always at 44.1.
 
I'm guessing how well it works (or if it works at all) depends a lot on your hardware. At any rate, it's easy enough to give it a try and see for yourself. Or just stick with ASIO if it's working for you.
 
 

With my Tascam it only shows 8 inputs and 2 outputs. ASIO gives you 14 and 4 plus SPDIF. 
 

How many I/O's are show in in Windows? WASAPI presents the app with "endpoints" which can be multichannel or stereo or mono. It looks like your device exposes an 8 channel input endpoint to the application.
One of the weaknesses of WASAPI is that its difficult for the host app to know how many channels are supported by an endpoint so we have to try and find out iteratively.
 
And FWIW WASAPI isn't a driver model. Its a layer that talks to the WDM driver itself. So there is no such ting as a WASAPI driver.
Some drivers may not play well with WASAPI if the manufacturer hasn't tested them with WASAPI.

Many thanks for this. It works on Win7/64 Lenovo TP530 internal RealTek HD
Just had to disable mastering plugins etc to avoid the delay -> don't forget to do this... ;-)
ASIO4ALL seems to be unnecessary for me now.
Would be interested in a new statistics on drivers in a few weeks...
Keep it up!

bitflipper
This is an oversimplification, but you can think of WASAPI as an alternative to ASIO as a way for SONAR to talk to your audio interface.
 
For me (using a Focusrite Saffire Pro 40) WASAPI works great. I can get lower latency with ASIO, but the 5ms I get with WASAPI is perfectly adequate for playing virtual instruments in real time. One reason I use WASAPI is that I can set SONAR's buffers independently from other audio applications.
 
Some have reported that they couldn't get WASAPI to work with their interfaces. Others report that it only works in its native sample rate of 48 KHz and flakes out with 44.1. That hasn't been my experience, though. I'm always at 44.1.
 
I'm guessing how well it works (or if it works at all) depends a lot on your hardware. At any rate, it's easy enough to give it a try and see for yourself. Or just stick with ASIO if it's working for you.
 
 

Bit:
Very helpful, I too am using several of the focusrite interfaces, including a PF26 that I use for VI tracking. If WASAPI is reliable at low latency settings that's a plus from the feel during a session