Topic: Foobar + ASIO + Madiface

Hi. I had my Foobar working well with Madiface driver, but when I updated the Madiface driver to the latest, something seems to have gone wrong.

It seems that the driver is no longer able to recognize the Sample Rate as it used to.

I am using Windows 10, with latest updates applied.

My ADI-2 DAC FS has the latest (very recent) firmware applied.

I installed Foobar 1.6.10 64-bit.

I have the Foobar ASIO output component 2.2: https://www.foobar2000.org/components/view/foo_out_asio

In foobar, I have some doubts about which settings to use. In Settings, Playback, Output, I select the device called:

> Default: Analog (1+2) (RME ADI-2 DAC)

Choosing this, all music plays well, but the DAC always shows the sample rate selected in the Madiface driver settings, even when incorrect.

There are other options of output components:

> Default: Analog (1+2) (RME ADI-2 DAC) Exclusive

Choosing this, music plays, but only if in the Madiface driver I select the correct sample rate, and restart Foobar, and re-select the output driver. Otherwise, I get the error "Unrecoverable playback error: Endpoint creation failed")

> ASIO4ALL v2

This gives error "Unrecoverable playback error: Sample rate of 352800 Hz not supported by this device". For other tracks, it plays through the laptop speakers instead of through the DAC.



Please help, how can I get back the former behaviour where tracks would be played in Foobar, the Madiface driver settings would automatically adjust the sample rate, and the DAC would show the correct sample rate on screen?

Thanks in advance!

2 (edited by ramses 2023-07-03 13:08:19)

Re: Foobar + ASIO + Madiface

One comment: ASIO4ALL is no valid ASIO driver, unsupported setup. Only use the RME ASIO driver.

BR Ramses - UFX III, 12Mic, XTC, ADI-2 Pro FS R BE, RayDAT, X10SRi-F, E5-1680v4, Win10Pro22H2, Cub14

Re: Foobar + ASIO + Madiface

Ok. How exactly do I "use the RME ASIO driver"? This is not obvious to me in the midst of all options...

4 (edited by ramses 2023-07-03 13:58:24)

Re: Foobar + ASIO + Madiface

pgorod wrote:

Ok. How exactly do I "use the RME ASIO driver"? This is not obvious to me in the midst of all options...

An ASIO driver bypasses the Windows Sound system and accesses the audio hardware directly, highest quality, lowest latency.

An ASIO driver you can load in applications like DAW and some music player that support ASIO.

For all other Windows Application and for Windows OS itself - which do not support ASIO - you need to create WDM compatible devices. This is being performed in the RME driver settings, see little icon in the lower right part of the taskbar (Windows notification area).

Only create WDM devices which are needed for windows, like for e.g. your active monitors or headphones.
In the WDM submenue in the driver there is a 2nd TAB "speaker".
Select the port, where your active monitors are connected to, as speaker device.
Then you can recognize the active monitors easier by looking for the speaker device.
Open Windows sound settings and make the speaker device to your windows default sound device.

Then Windows and all of its application (Browser, ...) that do not support ASIO are able to play audio through the speaker device which you configured as your systems default audio device.

This is all explained in the manual.

Additional information here in this sticky posting: https://forum.rme-audio.de/viewtopic.php?id=34394

BR Ramses - UFX III, 12Mic, XTC, ADI-2 Pro FS R BE, RayDAT, X10SRi-F, E5-1680v4, Win10Pro22H2, Cub14

Re: Foobar + ASIO + Madiface

Thanks for the detailed answer, I appreciate it and I am trying to learn.

But I am afraid I got lost at this point:

This is being performed in the RME driver settings, see little icon in the lower right part of the taskbar (Windows notification area).

Only create WDM devices which are needed for windows, like for e.g. your active monitors or headphones.
In the WDM submenue in the driver there is a 2nd TAB "speaker".

My RME driver icon takes me to these screens only:

https://gist.github.com/pgorod/afcc4adc … 9f5dac0c17
(I couldn't upload images here, so I posted them there as a public Gist)

About the final screenshot, from Foobar, I see that the ASIO4ALL executable file I find in my system is from 2012 (!) so I assume it has nothing to do with the current drivers I installed, it's just an old left-over from me tinkering with some other software.

But I think I should be seeing a "ASIO Madiface USB" device there too, shouldn't I? How can I fix that?

Re: Foobar + ASIO + Madiface

Ok... I think I got this. Quite stupid behaviour actually.

I was finding it strange to see the missing "ASIO Madiface USB" output device showing in Foobar. So I decided to install the RME driver again, reboot, and voilá! there it is, and everything is back to normal.

So I simply had to run the procedure two times instead of one. Something must have been incomplete in the first one. And yes, I had rebooted the PC in my first attempt also. I could see the windows driver was installed the first time, I checked the new version number, but for some reason Foobar wasn't seeing it, and after a reinstallation it is.

Sigh...

Thanks for your kind (and knowledgeable!) help, @ramses!

PS - in the manual called madiface_usb_e.pdf I can see the screens you were desribing with the "speaker" options, and device creation etc. For some reason this does not show for me? Is it maybe because mine is not the PRO model? Anyway, I don't think I need that now...

7 (edited by ramses 2023-07-03 17:27:04)

Re: Foobar + ASIO + Madiface

pgorod wrote:

Thanks for the detailed answer, I appreciate it and I am trying to learn.

But I am afraid I got lost at this point:

This is being performed in the RME driver settings, see little icon in the lower right part of the taskbar (Windows notification area).
Only create WDM devices which are needed for windows, like for e.g. your active monitors or headphones.
In the WDM submenue in the driver there is a 2nd TAB "speaker".

Sorry my mistake, forgot that you are not using a recording interface with TotalMix FX, but ADI-2 DAC.

> About the final screenshot, from Foobar, I see that the ASIO4ALL executable file I find in my system is
> from 2012 (!) so I assume it has nothing to do with the current drivers I installed, it's just an old
> left-over from me tinkering with some other software.

Again, ASIO4ALL is not an official (RME) ASIO driver for your device.

It is something being used to create workarounds, like, e.g., in cases where people want to use a USB mic with a recording interface. But this is not a real ASIO driver .. it packs all kind of audio drivers together under one hood and then talks on top of everything ASIO to the application.
But by this, you would add another audio driver layer over the original audio drivers (be it ASIO, WASAPI, or whatever).
This is no normal setup anymore and unsupported and not very useful / beneficial.
Because then you do not have direct access through the ASIO driver of your HW vendor (RME) anymore if you use the RME ASIO driver.

> But I think I should be seeing a "ASIO Madiface USB" device there too, shouldn't I? How can I fix that?

Either you didn't install the ASIO driver or it might be hidden, or you forgot to reboot after installation.

Another option is to install no ASIO driver at all and to use only Windows drivers.

Some people have in some cases less problems with streaming applications and sample rate changes if I remember right.

But if you want to perform a firmware update of your device, then you will need the ASIO driver.
Then you need to install it at least temporary again for flashing.

BR Ramses - UFX III, 12Mic, XTC, ADI-2 Pro FS R BE, RayDAT, X10SRi-F, E5-1680v4, Win10Pro22H2, Cub14

Re: Foobar + ASIO + Madiface

pgorod wrote:

Ok... I think I got this. Quite stupid behaviour actually.

I was finding it strange to see the missing "ASIO Madiface USB" output device showing in Foobar. So I decided to install the RME driver again, reboot, and voilá! there it is, and everything is back to normal.

So I simply had to run the procedure two times instead of one. Something must have been incomplete in the first one. And yes, I had rebooted the PC in my first attempt also. I could see the windows driver was installed the first time, I checked the new version number, but for some reason Foobar wasn't seeing it, and after a reinstallation it is.

I had similar problem after driver update. There was change in last driver version with different path names for driver and just simple reboot was not enough for correct installation.
I had to physically disconnect ADI/UCX, shutdown, wait, power on on pc, after boot physically connect the device and it started to work correctly. It means COLD reboot is important because of the latest change. There is a thread about it here.

ADI-2 DAC, Digiface USB, Fireface UCXII, ARC USB, Neumann MA1 aligned monitors