Foobar2000 No Asio Drivers Found

| Posted on by

AsioFoobar2000

  • Re: ASIO Driver not working no matter what I do Post by Richie Witch » Tue Mar 03, 2015 12:53 pm yur2die4 wrote: Also, in some cases windows will interfere with the sound and cause it to cut off and be inactive.
  • In opened Install component window select foooutasio.fb2k-component file. Click OK button into Preferences window. Restart foobar2000. Open Preferences ( key combination) Output ASIO. Into ASIO drivers list double click on foodsdasio driver to configure according to your DSD DAC device. Go to Preferences Output.

I have reported before that the driver installer executable rmeinstaller.exe does not work properly. I have used it on three different Windows 10 Pro 64 bit machines, all of which are updated to the latest version ( 1803 ). The installer hangs after the first screen. The task continues to run without any CPU activity and after waiting for approximately 60 seconds appears to continue and finish correctly. However after a reboot the icon for the control tool is not present. To get around this is was necessary to go to the
C:Users%username%AppDataLocalTemprme directory and run or rerun dpinst64.exe. Incidentally I also tried running as administrator but that made no difference.

Asio proxy for foobar2000Asio

Foobar Dsd Asio

Foobar asio driver

Foobar Asio4all

The problem is that the only people using the real 'realtek asio' driver is for running foobar2000 to get bit perfect audio hi-fi sound. Nobody knows how to use 'realtek asio' driver to run a DAW. So even if the OP manages to install the asio driver, nobody can help him if he has any problem with the DAW.

Asio Plugin

On the particular machine I was building today ( core -I7 but with a fairly old socket LGA 1366 motherboard) there was a further problem even then because the ASIO drivers were not working. In Audacity ( built with ASIO support ) no ASIO drivers were even detected. In Foobar 2000 the output could be set to Madiface ASIO but when play was pressed it said that the driver could not be loaded. I checked a number of things but eventually found that I had to disable the Realtek HD Audio ( Realtek ALC889 codec) by switching off the on board audio device in BIOS. Not the first time I have found that Realtek drivers break ASIO ( and not only the RME ASIO drivers).