Topic: RME madiface USB with another USB driver.

So I have a madiface USB with my burl B80, and I want to add another USB driver to send out to my dangerous Source monitor. Can this be done?  Basically just another driver that allows me an additional USB out besides the Madiface USB.

Thanks

2

Re: RME madiface USB with another USB driver.

Your description is not easy to understand. I'll try: You can add any device of the MADIface USB series (see driver readme) to work with the same driver, in parallel to the MADIface USB. The second device needs to be in sync, as explained in the manual.

Regards
Matthias Carstens
RME

Re: RME madiface USB with another USB driver.

Let me ask this instead -

From the madiface usb manual.

"The BNC output is built according to AES10-1991. The output's impedance is 75 Ohm. The out-
put voltage will be 600 mVpp when terminated with 75 Ohm."

Does this mean I can take an AES signal from the BNC output?  If so, I'm assuming only one stereo pair? I would need a BNC to AES cable?
Thanks

4

Re: RME madiface USB with another USB driver.

AES-10 is MADI. AES-3 is what you want...

Regards
Matthias Carstens
RME

5 (edited by aselix68 2025-08-25 18:46:53)

Re: RME madiface USB with another USB driver.

Following up on this

I need to convert the Madi face BNC output to AES-3.  It seems this box would work -

Neutrik NADITBNC-M - BNC to XLR AES/EBU Converter - but will it recognize AES-10?

And if it does, how does it show up in the software as available outputs? 

Thanks

Re: RME madiface USB with another USB driver.

That converter is for AES3id (unbalanced AES on BNC) to AES/EBU, it would not work for your needs.

You'll need a MADI to AES/EBU format converter. RME used to make an ADI-642 that can do this, but that item is discontinued.

Take a look at the Appsys Flexiverter, you can build a MADI <> AES/EBU converter from their modular system.
https://appsys.ch/products/flexiverters

Regards,
Jeff Petersen
Synthax Inc.

Re: RME madiface USB with another USB driver.

OK, thanks.  I just need two AES channels so spending a lot of money doesn't make sense.  There's not a basic MADI to AES format converter somewhere, for less $$$?

Thanks

Re: RME madiface USB with another USB driver.

Just use analog...

Regards
Daniel Fuchs
RME

Re: RME madiface USB with another USB driver.

I have a Dangerous Source monitor box which needs to be fed AES from the Madiface output in my setup, hence the need for the format conversion.  Disappointing that all the options are rather expensive...

Re: RME madiface USB with another USB driver.

aselix68 wrote:

I have a Dangerous Source monitor box which needs to be fed AES from the Madiface output in my setup, hence the need for the format conversion.  Disappointing that all the options are rather expensive...


Indeed the Madiface does not fit to your demand.

Better change the interface

UCXll has AES output.

M1-Tahoe, Madiface Pro, Digiface USB, Babyface silver and blue

Re: RME madiface USB with another USB driver.

Another option might be to use ASIOforall.  Would that allow the RME driver and the dangerous USB driver to work together on the same computer?

Re: RME madiface USB with another USB driver.

From what I did read, the ASIO4all does combine different ASIO driver into one aggregate device.

There is nothing in the way to try out, it is for free and you can delete it at any time.
Nothing to lose.

M1-Tahoe, Madiface Pro, Digiface USB, Babyface silver and blue

Re: RME madiface USB with another USB driver.

Or, you could try some of those:
https://vb-audio.com/Voicemeeter/index.htm
Or Banana, Potato

FF UCX II, Digiface USB, Babyface Pro FS

Re: RME madiface USB with another USB driver.

waedi wrote:

From what I did read, the ASIO4all does combine different ASIO driver into one aggregate device.

There is nothing in the way to try out, it is for free and you can delete it at any time.
Nothing to lose.

You only get an unsupported setup.
Then the real (RME) ASIO driver does not have direct access to the recording interface anymore.
With ASIO4ALL you add another ASIO layer on top of the existing.
This is also against the concept of having a robust least latency connection.
I didn't try, but I would expect that also the DAW doesn't get values anymore for latency compensation.

In macOS the aggregation of interfaces is part of apples audio concept, thus supported.
This is not the case for ASIO4ALL under Windows.

BR Ramses - HDSPe MADI FX, M-1620 Pro D, 12Mic, UFX III, ADI-2 Pro FS R BE, Nuendo 14, Win10 IoT Ent