Reserved

After entering my password in the terminal (as described in the readme), I get the following output:

Checking the auxiliary kernel collection...
Error Domain=KMErrorDomain Code=71 "Could not find: Executable for Kext com.softraid.driver.SoftRAID v6.3.1 in codeless kext bundle com.softraid.driver.SoftRAID at /private/var/db/KernelExtensionManagement/Staging/com.softraid.driver.SoftRAID.DtaJDJ/SoftRAID.kext not found
Incompatible architecture: Binary is for x86_64, but needed arch arm64e" UserInfo={NSLocalizedDescription=Could not find: Executable for Kext com.softraid.driver.SoftRAID v6.3.1 in codeless kext bundle com.softraid.driver.SoftRAID at /private/var/db/KernelExtensionManagement/Staging/com.softraid.driver.SoftRAID.DtaJDJ/SoftRAID.kext not found
Incompatible architecture: Binary is for x86_64, but needed arch arm64e}

but every thing seems to have worked, i.e. the installer application says that "The installation was successful" and I was prompted to allow access in the security and privacy tab of the mac settings app.  Should I be worried about this?

thanks!

Via Large option and the ability to better diagnose the issue - yes. But CC mode with TM FX and Settings is not available for these right now.

Similar.

Excellent Matthias, 
Should I check this with UFXII (revA).   (Noting that in MacOS 15.4beta, there have been a few instances of the USB interrupts relating to drive activity).

Yes of course, that makes sense

Hello, thank you for your hard work. I am using babyface pro. And I bought mac mini m4 pro and want to use it together, but after updating to fireface 4.20, the mixer window of totalmix does not open. It is recognized by fireface, but the mixer window of totalmix does not open, and the Mac does not recognize BF pro. Is there any solution? I set the security settings, but it does not work. And the firmware update does not work either. Why is this happening? Please tell me how to solve it. Please... Please... ㅜㅜ

Driver 4.20 has been released on our website.

4.20 is not a kernel based driver.  It uses a different method called “DriverKit”. If you haven’t installed any drivers yet start with 4.20.  (You only use one type of driver, not both.)

Before asking others for their RTL values and settings, counter question:
What are your values? And if you have issues, which ones?

What do you mean with "this" and with which "end in sight"?

No, there isn't an end in sight.

Apple insist on DK client apps being in user space, where they don't get sufficient priority, so another device can saturate the system scheduler causing buffer underruns (at least the driver reports them now). It's not RME's fault, but also RME have demonstrably been unable to work it out together with Apple. If I understand correctly, the most recent version of Sequoia also seems to have regressed for some users.

If you're not afraid to relax System Integrity Protection settings, use the Kernel Extension (kext) driver and cross your fingers Apple don't disable that mechanism altogether for a long while.

Yes but that's not enough, the computer has a lot going on inside, MAU (Microsoft auto updater) and CreativeCloud for example,
if you want to do a hard test, then try a clean install, copy your system to an external drive and format the internal drive.
Setup macOS and install only the RME driver and a slim DAW like Reaper. Nothing else. And nothing else connected.
Switch off internet and try recording and playback.
Now your computer is at most powerful mode, no interruptions from outside and no task inside.
If it works fine then ad your other software one by one and make audio tests all along.
May be you can identify some problem child ? Let us know...

I couldn't say. In this forum we haven't been able to establish a pattern to any of this, though what you've pointed out seems like a basic requirement for stable audio. You can try, and you should keep trying, until you reach some conclusion for yourself, and with your specific system and hardware configuration.

I use the kernel extension driver. I tried everything to get rid of audio glitches with the DriverKit driver, but the SSD in my TB dock somehow always manages to create buffer underruns, especially when QuickViewing large images (hardware decoder). I've accepted that the OS will nag me every few months about the driver.

Someone must have deleted his posts (after mine #29) so the remaining made no sense anymore - I deleted those three as well.

Sorry I missed most of this discussion up to now. My MacBook Pro 2017 is running on Ventura (highest supported) and my new Mac mini came with Sequoia pre-installed. Is the driver kit supporting both computers, or will the firmware update for my FireFace UFX (yes, the original) allow me to work with the new Mac mini while breaking things for the MacBook?

Thank you for the improved DriverKit driver v4.21. Large Safety Offset has not eliminated USB3 audio dropouts between our MacBook M1 Pro and MADIface XT or XT II. The driver is obviously aware of the problems, as it now provides 5 diagnostic counters that increase on every dropout. We presume that solutions are beyond RME's control, having seen many reports of unresolved dropouts between M1 Pro/Max and various USB audio interfaces.

Do we know if more recent Apple processors (e.g. M3, M4) exhibit similar USB3 audio problems?

Tried CC mode with a MacBook M1 Pro connected directly to the MADIface XT II. Two problems were evident in Audio MIDI Setup:

1. Input and output channels have no names, only numbers (1-100 in, 1-102 out for double speed), and are ordered differently (MADI last) than in USB3 mode (MADI first), causing misalignment with channels in TotalMix and DigiCheck.

2. The MIDI device name ('USB MIDI Device') was different than in USB3 mode ('MADIface XT (#SERIAL#)'), affecting aux device port settings. This problem fixed itself when I updated from MacOS 15.3.2 to MacOS 15.4 just now.

The bigger problem is that TotalMix won't stay connected, so we lose control of the XT II. As soon as we power on aux devices (4 OctaMic XTCs chained to port MADI 1), TotalMix shows "disconnected" in the window title bar and all RME applications (TotalMix, DigiCheck, Fireface USB Settings) and Audio MIDI Setup go into kernel hangs with a spinning beach ball. Neither force-quitting apps or restarting the XT II return things to normal. So far, only a MacOS reboot has made CC mode usable again.

We've had to stop offering recording services after every live recording during the last year was corrupted by USB3 audio dropouts.

Do we know if more recent Apple processors (e.g. M3, M4) exhibit similar USB3 audio problems?

The disconnect issue seems to be specific to some M1 MacBooks and Mac Studios. That said, are you not running any kind of redundant backup during your live recordings?

We don't run backups or unnecessary applications during live recording, only TotalMix, DigiCheck, Fireface USB Settings (now that it keeps count of USB3 errors causing dropouts) and Apple Music (to play music during breaks).

We use an OWC thunderbolt 4 dock in our studio and a direct USB connection during at live events. TotalMix won't stay connected in CC mode with either setup. It's not clear what triggers the disconnect, but all RME applications deadlock thereafter. Sometimes Totalmix stays connected with aux devices active and disconnects after launching DigiCheck or Apple Music.

See above, the disconnects are a known phenomenon of M1 USB issues.

Not running an independent redundant backup recording on a second device for paid live gigs and ending up having to "stop offering recording service" is careless at best.
I'm not referring to the MacBook running some kind of data backup, but to a second computer or hard drive recorder doing a second recording from whatever available outputs your setup may have, or even just a stereo backup from the main output.
Grab a second-hand Fostex D-160 and install an SSD with adapters. 16 bit, 44/48k, better than nothing. Totally outdated technology, but for this specific purpose, that's just right.

Recordings fail. I've had a laptop that wasn't even online start an update moments before a concert while it was already running and recording. Never really trusted that computer again. Had a backup with a cheap Windows tablet recording to an SD card, saved the day. My current recording laptop runs Windows 8, no such problems.

We were able to reproduce the issue (USB3 CC mode with simultaneous MIDI usage) and are working on a fix. This was unexpected and not found before in testing, very sorry. Once this works CC mode should be a good alternative for you (as you already stated and as expected, clicks/dropouts should be gone).

any experiences with macOS 15.4 and rme dk 4.21?

Yes, DriverKit 4.20 works on both – Ventura (on your 2017 MBP) and Sequoia (on the Mac mini). Just make sure you update firmware on your UFX or MADIface XT II. That’s key for getting Class Compliant mode with full Settings dialog and TotalMix support.

Older Macs might behave differently – stability can vary. On my side Sequoia + 4.21 + UFX III = rock solid.