51 Reply by gigi (edited by gigi 2025-04-30 20:15:17)

  • gigi
  • ADAT user
  • Offline
  • Registered: 2010-02-27
  • Posts: 31

Re: macOS DriverKit driver 4.20 now available

Hi there,

I’m setting up a new Mac Studio M4 and have just installed Driver Kit 4.21. My interface is an RME UC with firmware version 49. After the installation, the driver reports a successful installation, but the system doesn’t recognize the card, even though the driver has found the UC.

From the information I found on the RME website (https://rme-audio.de/Downloadbereich.html), it seems I need to manually authorize the driver in the Systemeinstellungen / ‘Sicherheit und Datenschutz’. However, the system settings look completely different on Sequoia 15.4.1. I’ve searched everywhere but couldn’t find any options to authorize the driver as instructed on the website. I’m probably overlooking something basic, but I’m at a loss.

Any feedback would be greatly appreciated. Thanks!
Gigi
-------
EDIT: To reply myself, I’ve found the solution. The activation of the driver on Sequoia can be found in “Allgemein / Anmeldeobjekte & Erweiterungen / Treibererwetierungen” (sorry, my system is German). Now, macOS and Totalmix recognize the card.
Cheers!

By the way, I completely skipped installing the Kernel Extension driver because the UC already had the latest firmware v49. I was unsure if that would be okay, but everything seems to be working fine. Thanks RME!

52 Reply by MC

  • MC
  • MC
  • Administrator
  • Offline
  • From: Germany/Thailand
  • Registered: 2007-04-06
  • Posts: 26,132

Re: macOS DriverKit driver 4.20 now available

carich wrote:

Tried CC mode with MADIface XT II firmware upgraded to CC v16 and DriverKit driver 4.22.

Although it seems more robust, we are still seeing TotalMix go spontaneously into the "disconnected" state and deadlock, requiring a MacOS reboot to recover.

Please try the new firmware USB 323 CC 17. This one should fix the audio MIDI issues (and subsequent hangs) that you encountered, for both normal driver mode and CC DK driver mode.

https://www.rme-audio.de/downloads/fut_ … ac_337.zip

We also have a slightly updated driver with a fix for noise  effects on audio stop, although unrelated to your reports:

https://www.rme-audio.de/downloads/driv … ac_426.zip

Regards
Matthias Carstens
RME

MC's Website

  • Registered: 2009-03-04
  • Posts: 13

Re: macOS DriverKit driver 4.20 now available

Hello Matthias,
I have a UFXIII +1620pro connected with madi coax. I'm on a M4pro mini. Driverkit 4.21
I experienced severe spikes and audio drop problems whenever I touched a tabpage in a webbrowser or other task.
I now switched (in audio/midi setup AND in my daw) to Aggregate device instead of appointing the UFXIII directly. It seems that the drops are far less frequent - whenever I try another task now, it spikes but thus far no audio drops.
Can maybe someone who experienced the same problem try this too and see if it works for them?

I'm just guessing wildly here: since I migrated my system from a previous mac computer, could it indicate that by choosing the aggregate device route, the system works on the old kernel driver? (I had HDSPe Raydats before)
If so -> I'm a bit scared to download the new 4.26 since this works for now.
Thanks for your input.

best regards,

Koen.

54 Reply by MC

  • MC
  • MC
  • Administrator
  • Offline
  • From: Germany/Thailand
  • Registered: 2007-04-06
  • Posts: 26,132

Re: macOS DriverKit driver 4.20 now available

Use latest driver and firmware (links in post #52). Set the UFX III into CC mode. Aggregate Device adds a buffer which helps to keep audio rolling, but using CC does so too, and typically even better.

How can you be afraid of driver updates when you can go back anytime? And how can the UFX III via USB work on a PCIe driver?

Regards
Matthias Carstens
RME

MC's Website

  • From: California, USA
  • Registered: 2019-02-21
  • Posts: 35

Re: macOS DriverKit driver 4.20 now available

Upgraded MADIface XT II firmware to CC v17 and USB v323. Upgraded driver to DK v4.26.

Some MIDI responses over USB are now being corrupted. See the log at http://littlemountainmusic.org/download/rme_midi.txt, which shows corrupted MIDI traffic (e.g. response packets without a 0x7F terminator) between MIDI Remote and the XT II with 4 Octamic XTCs chained to it. Obviously, apps (MIDI Remote or TotalMix) receiving these behave badly.

In CC mode, we have not yet seen TotalMix deadlock with MIDI traffic, but we have seen TotalMix become unresponsive (all meters freeze) without showing "disconnected" in the window title. We could quit TotalMix normally (since it wasn't deadlocked), but it was still unresponsive after being relaunched. Hard to interpret given potential underlying MIDI corruption.

In CC mode there is still a channel alignment problem. Playback to channel 7 (e.g. from a DAW) appears in Totalmix at channel MADI 1. Playback to channel 1 appears in TotalMix at channel AN 1.

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

carich's Website

  • From: California, USA
  • Registered: 2019-02-21
  • Posts: 35

Re: macOS DriverKit driver 4.20 now available

In the MIDI log at http://littlemountainmusic.org/download/rme_midi.txt the Octamic XTC with Device ID 02 (second in the chain) responds twice to each 0x11 command requesting level data. It's the same device whose responses to 0x10 commands requesting all parameters are corrupted. We don't think that Octamic XTC is damaged or had any of its settings changed.

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

carich's Website

57 Reply by MC

  • MC
  • MC
  • Administrator
  • Offline
  • From: Germany/Thailand
  • Registered: 2007-04-06
  • Posts: 26,132

Re: macOS DriverKit driver 4.20 now available

Thanks, we're at it.

Regarding the channel alignment - that is not an error. The first channels are not MADIx, but Analog, then AES (offset 4 channels on inputs) and Phones (offset 6 channels on playback/hardware output). So indeed we need to add naming to avoid confusion in CC mode - as soon as the more serious issues are fixed.

Regards
Matthias Carstens
RME

MC's Website

  • From: California, USA
  • Registered: 2019-02-21
  • Posts: 35

Re: macOS DriverKit driver 4.20 now available

So MADIx channels are last in CC mode, but first in USB mode? DigiCheck workspace files refer to input channels by number, so all metering setups designed for USB mode stop working (or at least monitoring the intended channels) when you switch to CC mode. We can live without channel names in Audio MIDI Setup, but skewing the channel numbering when switching mode seems traumatic. Is it necessary?

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

carich's Website

  • From: California, USA
  • Registered: 2019-02-21
  • Posts: 35

Re: macOS DriverKit driver 4.20 now available

carich wrote:

In the MIDI log at http://littlemountainmusic.org/download/rme_midi.txt the Octamic XTC with Device ID 02 (second in the chain) responds twice to each 0x11 command requesting level data. It's the same device whose responses to 0x10 commands requesting all parameters are corrupted. We don't think that Octamic XTC is damaged or had any of its settings changed.

We discovered that the third Octamic XTC in our chain of four had its MIDI Device ID setting changed from 03 to 02, which explains the duplicate responses and corruption seen in http://littlemountainmusic.org/download/rme_midi.txt. Having corrected that, we'll test CC mode again.

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

carich's Website

  • From: California, USA
  • Registered: 2019-02-21
  • Posts: 35

Re: macOS DriverKit driver 4.20 now available

DAW project files also refer to channels by number, so our Reaper recording and mixing setups designed for USB mode stop working (or at least require routing matrix changes) when you switch to CC mode. Again, skewing channel numbers when switching mode seems traumatic.

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

carich's Website

  • From: California, USA
  • Registered: 2019-02-21
  • Posts: 35

Re: macOS DriverKit driver 4.20 now available

Thoroughly tested our MADIface XT II (firmware USB 323, DSP 60, CC 17) and DriverKit driver 4.26 with four OctaMic XTCs chained to port MADI 1. In the last two days, we have not seen any deadlocks and TotalMix has not disconnected or frozen. All MIDI traffic looks normal.

MC wrote:

Regarding the channel alignment - that is not an error.

We can't believe channel alignment is working as designed. In CC mode, we're confident that MADIx input channels are first and MADIx output channels are last in Audio MIDI Setup. On the input side, ever-present MIC 1/2 signals appear after MADI channels in all apps (=> MADIx first), including DigiCheck and Reaper. On the playback/output side, signals played back from apps to channels 1/2 are present at AN 1/2 (=> MADIx last). Activating loopback on output AN 1/2 incorrectly routes the signal back to input MADI 1/2.

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

carich's Website