1

Topic: Overview on current driver and firmware state macOS USB 3 interfaces

Here is the latest state and info, presented in its own thread.

We have been working on further improvements of performance and compatibility for the Apple Silicon world, especially in regard to USB 3 - UFX III, MADIface XT II, Digiface Dante, Digiface Ravenna and USB.IO.

RME now supports three (!) drivers or operating modes for macOS with Apple Silicon and USB 3:

- Apple's recommended DriverKit architecture

- Apple's former Kernel Extension driver (announced to be dead anytime but still working)

- Apple's own audio driver for Class Compliant mode

Due to a tighter OS integration, bigger buffers etc the latter is the last resort if the used computer model and macOS suffer from clicks and drop-outs - CC mode should work without such issues.

But in CC mode there was no Settings dialog and no TotalMix, which made it not very usable - fortunately this has changed. The latest DriverKit driver and firmware updates allow the UFX III, MADIface XT II, Digiface Dante, Digiface Ravenna and USB.IO to be used in Class Compliant audio mode while control of the hardware via Settings dialog and TotalMix is still there. The Settings dialog will show 'Apple CC' in the top right, instead of the DK driver version.

CC mode is not the final and best solution, though. It does not offer a choice of Safety Offset settings (they are fixed and higher than our Large setting, resulting in higher latency), there is no Diagnostics error counter, and no playback data visualization is available in DigiCheck NG. Still, if it is the only way a specific system works these points not count much.

With Digiface Dante and Digiface AVB we changed the way the convenience feature 'internal network port' was realized. Those interfaces now use a Class Compliant network port, so run on Apple's own, native system network driver (available since 10.11, on both Intel and Apple Silicon machines). Additional software (we used netifc) is no longer required. That keeps the system clean and clear, reducing possible culprits and making installation more easy.

In the last weeks we learned that in isochronous record mode (the only mode available with CC, our drivers default to Bulk mode for record), simultaneous and heavy usage of audio, TM FX level meters, MIDI and CC network can disturb audio transmission. The latest firmwares take care of this specific USB 3 issue, so we are ready to roll out the new versions next week on our website.

We also further improved the deinstallation in both Kernel (v 3.35) and DriverKit driver (v4.27) for the 'other' driver. This helps the user to remove the other driver, which unfortunately in the later OS no longer works by simply deleting something (it is either hidden or can not be deleted by simple user actions). Having both driver extensions, Kernel and DK in the system will cause havoc as they become active simultaneously. Therefore both drivers also show a clear warning in case the other driver extension is detected.

Current versions

DriverKit driver 4.27:
https://www.rme-audio.de/downloads/driv … ac_427.zip


Firmwares:
MADIface XT II: USB 3/2 323, DSP 61, CC 17

Digiface Dante: 68, CC 20

Digiface Ravenna: 55, CC 2

Fireface UFX III: USB 21 DSP 25 CC 47

USB.IO (DirectOut Modul): USB 10 CC 14

macOS Firmware Update Tool:
https://www.rme-audio.de/downloads/fut_madiface_mac.zip


Note on Digiface Dante and Digiface Ravenna: these units have no hardware switch to change between CC and normal mode, therefore did not support CC so far. Now they do, which also allows new applications, for example using them on Linux systems. This is possible as with these products Settings dialog and TotalMix are often not required - the whole configuration is done via Dante Controller or the webserver remote, from any remote computer.

The change to CC mode is performed through the Mac Firmware Update Tool, in an easy and quick way by selecting/deselecting the newly added CC mode option. When the firmware is on the latest state already, changing CC mode does not flash the whole firmware, but only changes the CC state. Note that CC is not part of the Windows FUT, and if flashed to CC mode the DF Dante and Ravenna is no longer recognized by the Windows driver. So to use them under Windows the CC mode needs to be disabled via the Mac FUT first. See screenshot below.

Regards
Matthias Carstens
RME

2

Re: Overview on current driver and firmware state macOS USB 3 interfaces

The Settings dialog in Apple CC mode with DK driver 4.27, Digiface Dante:

https://www.archiv.rme-audio.de/images/settings_dfdante_ccmode2.png


Firmware Update Tool with Digiface Dante, showing the CC mode option:

https://www.archiv.rme-audio.de/images/fut_dfdante_v9.png

Regards
Matthias Carstens
RME

Re: Overview on current driver and firmware state macOS USB 3 interfaces

MC wrote:

There is a new firmware for the XT II, DSP 61, which reliably sets Aux First mode when TotalMix is detected in CC mode.

We tested this. In CC mode with CC Routing set to Aux First, both input and output channels are ordered with MADIx last, and loopback is no longer misaligned. If you unplug the USB cable, set CC Routing to any other value, and replug the USB cable, it changes automatically to Aux First, as described in the readme.

Channels in USB3 mode have always been MADIx first; i.e. Aux last. We have a strong preference for having the same channel order in USB3 and CC mode, so we can use existing DigiCheck workspace files and Reaper project configurations (designed for USB3 mode) in CC mode. Will some CC Routing setting (Straight, Aux Mirror, Aux All 1/2?) eventually provide the same order as USB3 mode?

Little Mountain Music
MacBook Air M1, MacOS 15.6, MADIface XT II, 4 x OctaMic XTC, M-32 DA

4

Re: Overview on current driver and firmware state macOS USB 3 interfaces

For users of the Digiface Dante on Mac (and Linux...) we have exciting news: As the first of more devices to follow, the Digiface Dante has got further extended and improved Class Compliant support. These are the changes:

FUT v 3.52, Digiface Dante CC v20:
- device takes over CC sample rate
- channel count follows sample rate range
- all channels got names
- channel names are based on the channel count in Single, Double and Quad Speed mode and USB 2/3 mode

For users who want to try out the new features, here is the pre-release firmware update tool for macOS:

https://www.rme-audio.de/downloads/fut_madiface_mac.zip

Also check post 1 for further info!

Regards
Matthias Carstens
RME

5 (edited by blueshirt 2025-08-01 00:04:54)

Re: Overview on current driver and firmware state macOS USB 3 interfaces

Can we expect other interfaces like UFX-II to get the Class Compliance with Total Mix support as well in the future or is it not planned at all?
I'd be interested because the CPU usage seems a bit high with driverkit and it doesn't seem to be the case in class compliant mode.

6

Re: Overview on current driver and firmware state macOS USB 3 interfaces

The UFX II is USB 2, thus typically not affected from issues that can be worked around by using CC. Therefore it has no priority for such changes, and I can't tell if and when they might come to it.

Regards
Matthias Carstens
RME

Re: Overview on current driver and firmware state macOS USB 3 interfaces

Thank you for your answer MC, I just wanted to voice that this is something that some users might be interested in.

I'll probably make a dedicated post regarding my issue then (~20-25% CPU usage by de.rme-audio.dkusb in activity monitor to just play a music seems excessive).

8

Re: Overview on current driver and firmware state macOS USB 3 interfaces

25% for one core, I guess... the Mac's CPU load display is often misunderstood...

Regards
Matthias Carstens
RME

9 (edited by waedi 2025-08-02 09:36:37)

Re: Overview on current driver and firmware state macOS USB 3 interfaces

The driver takes 25 % means 25% from the actual CPU work not from the CPU capacity.

Start Photoshop and DaVinci Resolve (let it render a video) and LogicPro (without selecting the RME interface) and FinalCutPro this 25% will shrink down to nothing

This number seems excessive but is not, it is meaningless.

I did read that the CPU display shows the overall CPU workload, but 1 core is 100% and if your CPU has 4 core the CPU-display goes up to 400%.
I did not test this, it sounds weird.

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

10 (edited by blueshirt 2025-08-02 09:55:38)

Re: Overview on current driver and firmware state macOS USB 3 interfaces

I was having some audio dropout that I don't remember having (when closing some apps for instance), and I saw the process around 20% CPU so I thought this was the reason, but now that you mention that, I checked the graph and you're right it is actually only one core.
I was used to not seing anything on windows so I thought it was high but yeah it's not for 16 cores, it's the reporting that misrepresent that.

I suppose these audio dropout are caused by a limitation of driverkit then right? (I don't notice this problem on windows)
The RME process loses its priority for a short moment to another one, for instance freeing the memory from closing an app, which for an app consuming a lot of memory, is enough to create the dropout?

Re: Overview on current driver and firmware state macOS USB 3 interfaces

20% when using USB 3 on my Mac M1 with FF UFX+.
8 % when using thunderbolt.
So I'm preferring thunderbolt
Same with older MBP intel.
But no dropouts so far with USB 3.

UFX+, FireFace 802 FS, Digiface USB
12 Mic, M1610 pro, Micstasy
MacBookPro M1
Logic Pro X

Re: Overview on current driver and firmware state macOS USB 3 interfaces

Relatively new UFX III user here. Had dropout problems for months usng DriverKit and Kernel drivers. Switched to CC a couple of weeks ago and it's been smooth since. Really appreciate all the work put in by RME to make this work

UFX III
Macbook Pro M1

Re: Overview on current driver and firmware state macOS USB 3 interfaces

Will the Digiface AVB get CC mode as well?

14

Re: Overview on current driver and firmware state macOS USB 3 interfaces

Sorry, no.

Regards
Matthias Carstens
RME

15 (edited by spluta 2025-09-17 18:39:07)

Re: Overview on current driver and firmware state macOS USB 3 interfaces

I run 4 studios using RME hardware. We have a UFX+ in two of the studies. Since just this fall the UFX+'s have been having constant dropouts. This never happened before.

Question 1: Will the UFX+ be getting CC mode with TotalMix?

I ask this because when I switch the UFX+'s to CC mode, there are no dropouts. Never. The crazy thing is, when I switch back to USB3 mode from CC mode, then the device will be fine for a while...and then it won't and there will be constant dropouts. I'm never sure when this happens, but it will be noticeable better for a while.

Switching to USB2 mode does not solve the problem.

Question2: Any insight on this? Our studios are used by 70 students, so I would love to just switch to CC mode. However, TotalMix is a large part of our curriculum. One thing that may be happening is a student with an old driver may be connecting to the device and putting it in a different state? Sounds superstitious even saying that though.

16 (edited by hselters 2025-09-18 12:19:36)

Re: Overview on current driver and firmware state macOS USB 3 interfaces

+1, CC for UFX+ would be practical.

We never got it to work reliably with USB 3 in our multi user environment, probably due to the required cable length and the wide variety of different laptop and adapter configurations being used.

USB 2 is working for us at the moment, as we don't need the MADI channels in that room. It usually stays on the USB 2.0 setting besides maybe two hiccups in the past years, so I would expect the same about CC mode, as it is probably not a setting which is part of the Total Mix Workspace.

Re: Overview on current driver and firmware state macOS USB 3 interfaces

I’ve run into similar dropout issues, both with the UCX II and UFX III. If I remember correctly, RME’s response was that it’s an Apple-side problem. Hopefully whoever’s responsible can sort it out soon. I need the lower latency and the other features not available in CC-mode.

18

Re: Overview on current driver and firmware state macOS USB 3 interfaces

With UFX III all features are available in CC mode. And Apple has improved latency in CC mode as well (lsmaller safety buffers).

UFX+ will not get the new USB3 CC mode, as this is not a simple copy / paste but re-development of several (!) firmwares within the unit. Not to mention that it might not fit into the existing hardware resources anyway (untested).

Regards
Matthias Carstens
RME

19 (edited by Ninbura 2025-10-20 07:35:24)

Re: Overview on current driver and firmware state macOS USB 3 interfaces

MC wrote:

FUT v 3.52, Digiface Dante CC v20:
...
- channel count follows sample rate range
...

This change in-particular is quite welcome. Previously macOS could randomly select a channel count other than 128 at 48 kHz, despite manually selecting 128 in the past. Took me a bit to realize what was going on there, much of my routing would occasionally stop working in Rogue Amoeba Loopback after re-docking.

Shouldn't be an issue anymore smile

MADI FX | Digiface Dante | Fireface UFX+

Re: Overview on current driver and firmware state macOS USB 3 interfaces

stephan_martin wrote:

I’ve run into similar dropout issues, both with the UCX II and UFX III. If I remember correctly, RME’s response was that it’s an Apple-side problem. Hopefully whoever’s responsible can sort it out soon. I need the lower latency and the other features not available in CC-mode.

Is this so? I have been having issues with my Digiface Dante and Mac M1 Pro, where occasionally I get a drop out of audio, and the Fireface USB utility is showing errors at the bottom.
I will try the CC mode, but I am giving up around 2ms of input latency to use the CC mode. Part of going RME was the reputation of super stable drivers and low latency... That being said, how could it be Apple-side problem if I have not had those issues with other interfaces?

21

Re: Overview on current driver and firmware state macOS USB 3 interfaces

Because most probably your other interfaces did not have 128 channels I/O nor used USB3.

Regards
Matthias Carstens
RME