### device
Babyface Pro
Firmware v206
Driver: V4.16

### set up
connected via 1. USB cable. 2. with a hub
M3 Macbook Air
OS: 15.1

### issue experienced
FireFace USB Setting works and shows the Properties for Babyface Pro
TotalMix fails to show mixer or matrix window
CC Mode works so we can rule out the USB cable.

I hope the next driver fixes the issue.

Hi mr. Carstens,

You seem to be very confident stating that there are no issues.

Well, unfortunately I have a lot of issues. Hiccup's and stuttering when starting playback from selected regions within a cycle loop. Jumping back to beginning of the cycle although I start from a region on a different point in the cycle.

Ok...question: you say "enable microphone for Totalmix". Now I can see that I enabled it for Logic but there is no option for enabling this for Totalmix in Privacy and Security settings. How would I make Totalmix visible in this menu?
Thank you in advance.

MacBook Pro M1 Pro / 16 GB /1 TB
Logic Pro 11.0.1
Sonoma 14.7
UCX II connected directly to Mac usb-c port/Kernel driver v.3.33 / Firmware v106 (Latest Driverkit was even worse)

Thanks for your response Waedi,

I have always been doing starting playback from activated region somewhere in a cycle region without hiccups before Sonoma. So I don't agree with your statement that this is normal behavior.

Upgrading to Sequoia not yet due to unsupported plugins.

I will try your tip with AMS setup and aggregate device though.

Thanks again, Huub

So I tried 4.16 with the latest MacOS Sequoia and while everything appeared to go smoothly and Fireface USB indicated 4.16, The UFX III did appear in AudioMIDI as an audio device and TotalMix would not display. Went back to 3.33 and everything is working again.

Well except that with Sequoia, I can't change buffer sizes in either Logic 11 or Cubase 14 once a VI is loaded. The DAW audio engine is dead unless I close the DAW and restart. If I change the buffer before loading any VI's it works but once a VI is loaded, alll,bets are off.

And, yes, the FW is up to date on the UFX III

Sample rate change works fine if I use the Apollo as the audio interface

Nope - same issue. Once I instantiate a VI, changing the buffer kills the audio. Sometimes removing the VI(s) will restore it but sometimes it requires restarting the DAW

so, just looking around to see what's cooking with sequoia. still on sonoma and have no issues. seems like a bad time to update. better to wait for a new driver version from RME that is 100% shaking hands w/sequoia. I'm running a UFX+ and the driver kit driver. i forget what version but it works.

SUCCESS! Did I mess this little tidbit in the install instructions? (I think I read them like 3 times). And I can now change buffer size at least in Logic (haven't tried Cubase yet). So far no sign of the random clicks/pops I was getting with an earlier version of DK under Sonoma. Time will tell on that.

Thanks!!

I just read the install instruction in the 4.16 README again - no mention of the setting @waedi told me about. I looked in the download and support sections of the website and didn't see any other Sequoia instructions.

The DK driver seems to be working fine for me now. The kext driver works, but changing the buffer size in a DAW when one or more VI's are instantiated locks up the audio system (Cubase & Logic).

I made the changes in Recovery Mode to install kext's but I did NOT disable SIP via the Terminal command

This was the exact issue I was having previously with my M2 Ultra Mac Studio and a UFX III using an earlier version of the DK driver with Sonoma. I updated to Sequoia before trying DK 4.16 (you can read my problems with that combo before @waedi suggested the magic fix above).

The one thing I can suggest is to use the RME provided USB cable and connect to one of the USB ports directly on the MacBook, not through a hub or dock, although that seems far more critical with the USB3 UFX III other than USB2 like your 802.

I can say 4.16 and Sequoia 15.1 now appears rock solid so far with no random glitches like I got with Sonoma and earlier DK drivers (it was pre-4.12 but I don't recall the exact version I had trouble with).

In fairness, ny Mac Studio rig is very complex with a Caldigit Element TB hub, multiple USB4 SSD's, a Apple Pro Display XDR with USB devices and a USB hub connected to its USB ports, etc. It may well have been some downstream interaction I never discovered. And using USB3 (I am using the MADI buses in the UFX II to connect an Eventide H9000 so dropping back to USB2 was never an option) certainly increased the odds of having issues.

Kext driver 3.31 or 3.33 were completely trouble free on the Studio with Sonoma however. 3.33 does have some issue with changing buffer sizes in Logic & Cubase with Sequoia 15.1 for me, which is why I was trying to get the DK driver to work.

BTW, I still have my Apollo X8 connected as well and use it via ADAT to the UFX as a hardware FX unit so I can use UAD plugins on live, record-armed VI tracks with minimal latency. Using the plugins in the DAW with the Apollo or UAD Satellite have too much latency to use live. So I use the X8 on the ADAT ports exactly like my H9000 on the MADI ports as external HW FX.

I think a big part of the problem in what you (understandably) are requesting is the impracticality of testing all the combinations & permutations of gear. And what we learn from forums like this are largely anecdotal. I'm a bit concerned that there will be another round of learning curve (and associated driver tweaks) with the new TB5/USB ports on the new M4 Pro/Max/Ultra Macs. If anything will slow me up from upgrading to an M4 Ultra Studio next year (other than cost), the RME drivers will be it. That's not intended as a  slam of RME but just the reality of constant evolution of the USB protocol and HW.

Hi Guys

I've recently bought a Digiface Dante and I'm having issued getting this running on one of my mac's.

I've got a Mac mini M1 running Sonoma 14.1.1, I've managed to allow Kernals etc download latest drivers 3.33, Fireface USB Setting and Total mix both pop up and work fine.

I've got a MacBook Air M1 which ive tried a few different OS now, but currently on Sonoma 14.7.1, I've tried a load of different installs and clears, including a full restore of OS. I've tried the 3.33 divers and also the latest driver kit drivers. Everytime the applications install and appear in the applications folder. But they fail to open and just bounce in the dock a couple of times then disappear.

The latest install of the driver kit drivers gave this error in terminal.
Error Domain=KMErrorDomain Code=31 "Error occurred while building a collection:
Cannot build collection without binaries as only 1 codeless kexts provided" User Info={NSLocalizedDescription=Error occurred while building a collection: Cannot build collection without binaries as only 1 codeless kexts provided}

I'm 3 days in trying to battle with this at the moment and loosing the will, so any help would be very much appreciated.

Thanks, Jake

installed Sequoia a few days ago. works fine. didn't have to do anything w/drivers. just installed the MacS update via software update in system settings. no problems w/my RME UFX+. seamless update.

sure, Macbook Pro M1 Max connected to a Caldigit TS3 Plus. The UFX+ is connected to the TS3+ via USB. it's the Driver Kit driver. I forget which version it is but i think it's most recent one available from RME. I'm not connected to the studio right now but will check later to confirm driver details.

when i view the extension in finder and show details it's says it's v 1.0.42 and it was installed on september 4th 2024

but i'll double check details when i'm docked in the studio later.

edit: sorry for delay.. forgot about this. **firmware v55, Driver 4.16**

This has already been discussed in many different threads.
Just use the search function...

ex here:
https://forum.rme-audio.de/viewtopic.php?id=40022
or here:
https://forum.rme-audio.de/viewtopic.php?id=40440

Seems you overlooked, that MC provided 2 links?
Did you read the first one (clocking/sample rate issues)?

With all due respect, it would certainly be more constructive to share the details of your environment and system configuration. Or what things you can rule out.
Rather than sitting back and expecting someone to randomly find the needle in the haystack