when trying to use wasapi driver i get "audio driver error"

any help wouldbe appreiciated,i emailed cakewalk,but under technical support sonar wasnt listed

Cactus Music
You'll need to provide a lot more information. We have no clue how , why or when your trying this. 
 
You don't even state which version or Sonar, your OS version, your audio interface etc etc. 

I'm sorry ,I should have explained it better.
I'm using an  HP Spectre x360 Convertible laptop,I have sonar platinum(the manchester 21.12.0.36)
When I switch the audio driver to wasapi i get an audio driver error that says "the following either do not support the current audio format,or are in use by another application,then it wants me to choose disable or use anyways.I choose use anyways but there is no audio.
I dont have any applications open except google chrome
I own a focusrote 2i2 but I am trying to be able to minimize latency just using the laptops audio drivers for when I want to sit in my living room and make music,when I use the virtual keys to play soft synths there is latency that makes it difficult form to be creative.
I wouldreally appreciate any help

not totally sure, but won't you have to be on 2016.11 or latter to take advantage of the wasapi stuff?
 
http://www.cakewalk.com/S...Fixes-and-Enhancements
 
manchester is way back there

The Grim
not totally sure, but won't you have to be on 2016.11 or latter to take advantage of the wasapi stuff?
 
http://www.cakewalk.com/S...Fixes-and-Enhancements
 
manchester is way back there

Wasapi has always worked in Sonar - particularly well under win 10. It was wasapi exclusive mode that was introduced in 2016-11. Ironically it has been less successful than the old wasapi driver on some of my gear.
 
 
To the OP - did you try closing and restarting Sonar after changing the driver to wasapi?
 
 

chuckebaby
If worse comes to worse and WASAPI wont work, use MME.Its not great and has some latency but it will still play and editing can be done. I've used it in a pinch (on the road with laptop).

you may want to (should!) consider asio4all (a wdm wrapper that tricks the host into thinking it's asio) before giving up and using mme, mme is the worst option, see here http://steamcommunity.com...80/#developer_response
or here http://steamcommunity.com/app/380080/discussions/2/365172547941995969/ for example
 
you should avoid mme if at all possible (it's designed for consumer playback of audio/video)

scook
May want to review the driver bit depth and record bit depth settings. I believe this error is thrown when the driver bit depth is set too high. There is no reason to set the record bit depth higher than the driver bit depth.

i think this is true for recording audio via an interface, but when just using VST instruments (soft synths) then 24 is better (if possible)

does synth recording use the audio interface (like a loop-back kind of thing)?

thx

why isn't he using the focusrite asio drivers?

Is it not correct that not all on board sound chips support WASAPI? 
 
I have one old W7 64 bit laptop and when I tried to do the loopback test using WASAPI it would not work. It also wouldn't use WDM mode. They would load and run the audio test, but I couldn't get sound to record.  So I had to do my test on my W10 desktop.
Later I have been using WASAPI on a different W7 laptop for a few months without issue. I now switched to Asio4all and it works better. But that is a good point about Asio4all co-existing with a Focusrite driver. In the past this was a known issue, But I think ASIO4all has matured and they fix things with updates.  I could test that tomorrow at work where the laptop is. I could take my 6i6 and see what happens. 
 
Yes please don't even think about MME mode that is not an option. See below.