Hi, I'm experiencing similar problems on an M1Pro macbook with Sanoma 14.0 and a Digiface Dante. Once about every 10 minutes I get an audio dropout (sometimes two in one minute and sometimes it takes 20 minutes before the next, but on average that's it). I tried both the kernel and the driverkit drivers, swapped cables etc. I have two usb-c to usb3-b cables, both showing the same issue. However, when I connect to an USB2.0 hub, the device switches to USB2 mode and the problems disappear. Also, when I connect my Babyface Pro or FireFace 800 (yes, I still have that), they don't show this problem. Can it be a usb3 issue? I don't remember this to happen in my previous macOS version (Monterey) but it could be that it happened there once or twice too, sometimes it is hard to debug dropouts in a Dante environment. This time though I'm sure it's the driver and not Dante, as it happens with loopback inputs too (effectively bypassing Dante). Help would be appreciated, although for now I can live with using a USB2 hub ;-)

I am having an issue where I cannot get audio into Logic Pro using the V4.09 drivers and a BabyFace Pro. I can select the input, but no sound comes through. Input works in Ableton and Bitwig. When I switch to the older kernel extension driver, I can again hear audio from the BabyFace Pro inputs. Anyone else having this issue?

Is Logic Pro allowed to use the 'microphone' in macOS system settings (under privacy and security)?

USB drivers have been updated to v 4.10 as DriverKit and 3.31 as Kernel Extension. The new DriverKit driver reliably removes the Kernel Extension, so it is very easy to swap between these drivers and check which works better for you. That said CoreAudio works better in audio multiclient mode with the Kernel Extension, and if you set the Safety Offset to the new option 'Large' it behaves exactly like Apple's CC driver, at least in our tests.

Kernel Extension driver 3.31 also includes a slight performance improvement, so it is worth a try.

Driver download links in this thread:
https://forum.rme-audio.de/viewtopic.php?id=38691

We do our best, but we can't make wonders happen. When a system is so crooked up that a Kernel Extension driver does not only not help, but operates worse than DriverKit, that system seems to be ready for excorcism...

Seriously, contact someone with knowledge who has direct access to your computer, like our suport stuff or local guys. The forum can't help.

That makes sense. When my iphone is around is sometimes pops up as an alternative for audio!

I'm having performance issues and drop outs with the driverkit version (Babyface Pro) I tried installing the kernal extension instead but the babyface pro isn't detected at all when using that, so I had to switch back to driverkit, any reason why?

I don't know what RME call "reliable uninstallation" but after upgrading to Sonoma the Kext driver was disabled, and then when I tried the DK driver instead, along with the Kext, it managed to mess up my Sonnet hub and not install the DK driver.

p.s. and the interface wouldn't work till I unplugged it from power and plugged it back in. Reinstalling the drivers made it stop responding again on the next restart.

p.p.s and again it fails the basic test where if I have a bunch of large images, attempting to quick-view them while anything is playing out of the interface causes drop-outs.

I'm not sure I have much patience left for the tiptoeing it takes to make these drivers work. Surely I'm not alone?

It won't remove it, and there is also no conflict. The newer TM FX will also work for an older FW driver.

Why is it impossible to install a driverkit driver without first installing an kernel driver? i reverted back to using kernel drivers because i do not want to go through the whole procedure every time i restore my mac (which seems to happen from time to time due to troubleshooting because the new macs have become so unreliable).

no, it can't. i mean you can run the dk installer without running the kext installer first, but then the ff802 (in my case) is not recognized. no audio.

This!
The original Fireface 802 (not the FS version) is exactly one of these interfaces which need a firmware update first.
At the moment for some RME / Apple users the changing process from kext to dk can be a bit tricky. When you have an already updated interface (or for people who buy a new one), it works directly with the dk driver.
Plenty of information on the RME website:
https://rme-audio.de/driverkit-info.html
In short:
for UFX / UCX / UC / 802 and Babyface it’s
- install kext driver
- install and run FUT (for this the kext driver is needed)
- install dk (if you want)
With newer interfaces (and their firmware) this is not necessary.

my 802 has the current firmware. i cannot install the dk installer without first running the kext installer anyway. that's just the way it is. i am thinking about crossgrading to an apollo or something like that just because the drivers have become such a pain in the rear.

what do you mean by definitely not true? i am experiencing these problems and of course it is true.

what computer are you using?

the driver installation works insofar as the installer does not crash. but there is no sound from the interface after a reboot.

logic works and the microphone symbol is of course allowed. i have allowed audio access in all dialogues that come up.

system is the latest sonoma, but it did not work with any of the previous systems including ventura etc. the mac is a mac studio m1 max. the fireface 802 has the latest firmware.

This is interesting an good to know. Obviously it is not a general problem, but one with my rig. I'm just out of options what else it could be. Is there a special trick how you get the dialogues for driver's access to the system? I remember that one had to click yes multiple times (three if i am not mistaken), but i think these windows did not appear the latest times I installed the dk driver.

I use a Mac Studio with an M2 processor.
Sonoma operating system installed.
I can use my Fireface 800 soundcard very stable, but I'm having an interesting problem. I just can't get an input signal from Ableton, neither microphone nor line. There is no problem using Logic X. Does anyone have any information or suggestions?

Is there any update on this?
I am on an MacBook M2 and want to do all the proper updates (firmware + driver kit updates). is there already a consensus on what the best practice is? e.g. only update kernel driver or also update firmware?

A word of caution -

- MBP M3
- Sonoma 14.4
- RME UFX+ Hooked up via Thunderbolt
- Kernel Extension Driver (driver_tb_mac_125.zip)
- Latest Firmware

Everything has been going swimmingly with this setup, until tonight, when I was listening to a podcast in chrome on youtube and adjusting the EQ on the output in totalmix.

I wasn't doing anything crazy - No wild Q or Gain settings on any of the 3 bands - I think I was actually switching between filter types when it happened.

All of the sudden there was a high pitched SQUEEEEEEEEEEEEEEEEEEEEEEEEE for about 2 seconds in my monitors, which are turned all the way up. The main output volume to my monitors totalmix was turned way, way down.

I'll tell you what. That SQUEEEEEEEEEEEEEEEEEEEEEEEEE was so loud that it blasted the red clipping lights on on both monitors and almost flipped me over in my chair. I have tinnitus and severe hyperacusis so it was basically like getting a point blank shotgun to both ears.

Then it stopped and everything returned to normal. No crashes, no nothing.

Suffice it to say, Very ... Not ... Cool ... And I doubt I'll ever mess with the EQ in totalmix again just out of caution. I have very little hearing left and I'm trying to keep it what I've still got. This incident will likely cause a "setback" that could last indefinitely and run that meter down that much more

Anyway. Not saying this is an RME / driver / totalmix problem. Could be Sonoma being a buggy POS. I've had the UFX+ for years and it's been rock solid. Never had anything like this happen with ANY RME Interface in fact, in 20 years and with many of them, and it just so happens i switched from an intel macbook last weekend to this M3 Sonoma macbook.

Be careful out there with that Totalmix EQ under these conditions. That is all.