Somebody mentioned using their Realtek on-board sound....
 
 
FWIW,
 
Realtek provides WDM/KS (WaveRT) drivers for its sound chips - so there's no need to install ASIO4ALL at all. ASIO4ALL is not going to provide you any benefit over the WaveRT driver, and Sonar will allow you to set a buffer size with WDM/KS devices.
 
IMO, the purpose of ASIO4ALL is as a last resort, if you must absolutely have an ASIO interface for an application that only supports ASIO.
 
Note:
 
Although Realtek does support WDM/KS, they usually limit their drivers to 16 bits only, and they may not support all the sample rates you'd like. They usually stick to the basics.
 

Paul P

dubdisciple
Lol. I admit..no one in their right mind should use a realtek card with sonar. I never claimed to be in my right mind!

I use the WASAPI driver with my Realtek Win7 laptop.  Not great, but it works. 

Wasapi mode works well here, too - and as far as running cubase is concerned it ships with its own generic asio driver that plays fine with onboard audio.

Got a response from one of TASCAM's engineers...it pretty much confirms what I experienced. TASCAM is looking into the possibility of detecting if ASIO4ALL is installed, and if it is, putting up a warning message.
 
>Unfortunately, Asio4All grabs the interface and locks the
>sample rate for itself, and does sample rate conversion.
>The release notes show that it is getting more aggressive
>in attaching to devices.
>http://tippach.business.t-online.de/asio4all/index.html
>
>Once Asio4All has the device, any other software won't be
>able to get the US-366 directly, only through that additional
>(and quality sucking) interface.
>
>Our drivers are supposed to give the lowest possible latency
>while guaranteeing bit-accurate transfer to/from the DAW
>software.

Anderton
Got a response from one of TASCAM's engineers...it pretty much confirms what I experienced. TASCAM is looking into the possibility of detecting if ASIO4ALL is installed, and if it is, putting up a warning message.
 
>Unfortunately, Asio4All grabs the interface and locks the
>sample rate for itself, and does sample rate conversion.
>The release notes show that it is getting more aggressive
>in attaching to devices.
>http://tippach.business.t-online.de/asio4all/index.html
>
>Once Asio4All has the device, any other software won't be
>able to get the US-366 directly, only through that additional
>(and quality sucking) interface.
>
>Our drivers are supposed to give the lowest possible latency
>while guaranteeing bit-accurate transfer to/from the DAW
>software.

 
"Quality sucking interface"? That's a mite harsh.
 
It's unfortunate if Asio4All is causing a conflict with Tascam's drivers. Perhaps Tascam (or their actual driver developer, Ploytec in Germany) might contact the developer of the FREE Asio4All wrapper, Michael Tippach (in Germany also), to try and come up with a solution.