Jump to content

Recommended Posts

Posted

As if I had a vote - But this thread should be a sticky--or some edited version of one. Noels  explanation for us " laymen " is gold.

 

Thanks.

  • Like 1
Posted

There is really no reason to install asio4all for an audio device that has a manufacturer provided asio driver. At best it will perform worse than the native driver. At worst it will cause pain because it grabs ownership of the underlying wdm driver and will cause grief if you use the native driver.

Posted (edited)

I generally agree - but my Q802USB has no ASIO driver, and the WASAPI does a decent job, but i've found the ASIO4ALL goes lower latency than the WASAPI and so i use it only to record. when using my main IO (UMC1820) then i use the native ASIO driver. ? the biggest win (for me) was deleting all the bogus drivers installed by applications (some of which were simply rebranded ASIO4ALL) and only having the native WASAPI, my Behringer ASIO, and the ASIO4ALL (rarely used). 

Edited by fossile
Posted

 

1 hour ago, sjoens said:

Why would my Behringer interface not like WASAPI at all? After running the wave configurator it say it's not compatible.

Shared or Exclusive?

Posted

I for one am glad that Cakewalk can allow background programs like networking to run as I use the Waves SoundGrid system which relies on offloading plug-in processing to a network attached audio device and server which is connected over a 1 gig Ethernet connection.

Posted
On 1/29/2023 at 4:05 AM, sjoens said:

Apparently both. The only audio that shows up with either one is the onboard Realtek.

My MOTU is decidedly unhappy if I try to use WASAPI (exclusive).  I'm surprised Shared also barfs for you.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...