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)

In the case where no audio recording is involved, avoid using synth recording (assuming it uses the Record Bit Depth, I am not sure it does) and use bounce or freeze instead. Those functions use the Render Bit Depth setting. The default Render Bit Depth setting is 32bit.

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

Probably not. Synth recording was released just prior to patch points and Aux tracks. I suspect is uses some of the routing logic made for that feature.

thx

pwalpwal

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)

 
Not sure that's a great idea
 

letyourlightshine
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

he is using a Focusrite 212 on the same PC (laptop). if he installs ASIO4ALL on that same PC along side the Focusrite 212 driver...
Guess what's going to happen ?

why isn't he using the focusrite asio drivers?

just to add, i have asio4all AND OTHER ASIO DRIVERS installed on the same machine without issue
 
to recommend MME is just LAST RESORT
 
oops, 'scuse the caps
 

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. 
 

i suspect that the "co-existing" issue may be host related
/fwiw