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.

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.

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.

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.

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.

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.

I do need a rock solid solution for live recording including a redundant backup.

Now I have UFXII 2xOctamicII XTC and 12Mic with Df AVD

Several ways to set up recording 40 Channel DS with redundant recordings (intel Macs / DAW)

I had the idea to switch to UFXIII for easier setup

Which setup is the most reliable?
Does Windows (Here are several HP Notebooks from Professional Lines) perform better? Or even UFX+?

I can live with a solid 40 Chanel DuRec Recording

TotalMix and the RME hardware rightly have a reputation for being solid.

...and continue reading here if talking about USB 3:

https://forum.rme-audio.de/viewtopic.ph … 07#p237507

Great, hopefully this works with Fireface UFX II in Mac's Sequoia OS?

After searching, I did not find an explicit answer—maybe this is such common knowledge that this is now taken for granted?

I’m currently using Sonoma, and for other reasons, need to upgrade to Sequoia, but not at the expense of my (rock-solid) working RME environment. I have:

macOS: Sonoma 14.7.5
Total Mix: ver 1.97
RME Driver: v4.17
FireFace UFX II firmware: v26
Logic Pro 11.1.2
MIDI: MOTU Express 128 (Bus Powered)

I’ve downloaded driver version 427, and FUT release date of 2025-06-10 (File dated 25/6/6). But I won't pull the trigger until I can confirm these are the two revs of software I need to run in Sequoia--or should I download something else?

I understand I need to flash the firmware before installing the driver, thank you.

Also, could anyone please share how stable people are finding RME in the Sequoia enviro?

Thank you very much!

Here Totalmix 1.99
USB driver 4.27
firmware on every interface always the newest
Sequoia 15.5
LogicPro 11.2

All runs fine rock-solid

The FUT you can anyway put on .

When driver 4.17 is working then 4.27 will work too regarding the firmware.

Some interfaces had to get a new firmware for the driver upgrade from 3 kext to 4 DK
In your case you are fine you can update everything.

Reading the readme text of the FUT and Driver is always recommended.

I just did a look on the FUT page your unit is up-to-date, no worry

Hello everyone, I'm preparing to send in my FF 800 to syntax for repair because three of the front channels stopped working. I'm running the M2 with Ventura 13.7.4, with the firmware hack applied in the extensions.  With this new firmware upgrade 4.20, could I use the latest OS?

Also,Since I'm getting work done on it, is there a mod that will convert it to thunder bolt?

Thanks!

I did check that while recording but still no dice when I put it on 'front' and 'front + rear'.  Channels 7 thru 9 xlr imputs on the front
are not working. They all went out one by one during the same session. Channel 10 still works, and for some reason the signal bleeds into channel 9. 

Also, the red "clip" light on channel 7 is on and will not go off.

4.20 is not a firmware it is the driverKit driver for Mac for USB interfaces.
The FF800 is a pure firewire interface and needs the firewire driver.

Use macfire 2.42

Thank you for this info.  Would you know if it allows compatibility with the latest Mac OS?  Right now I'm on Ventura, and apparently that's as far as the ff 800 can go in terms of OS.

No, the power supply was never changed.

Excellent! Thank you for your help!

yes sorry I was looking at the old legacy product page this is not actual.
The Download page has better results :
MacOS 11 and up Intel and M-Macs  https://rme-audio.de/downloads/driver_fw_mac_341.zip

No problem. Thanks again!

On Mac the audio buffer is part of the DAW and it is up to Ableton what sizes they offer to choose.

In LogicPro I also can go down to 32, not further.
Cubase Pro too, I think Ableton will not be an exception here.

Just tested with dk driver 4.27, too. Ableton 12.1.1 is installed here atm:

Short:
It is definitely an DAW-related thing.

Long:
- You have to switch from "CoreAudio" to "No Audio" and then back again to "CoreAudio" after sample rate changes in Ableton.
   It seems to be necessary (maybe a little bug?) to refresh its state.
- Ableton allows 32 Samples at 32kHz-96kHz
- Ableton allows 64 Samples at 176,4kHz-192kHz (while 32 Samples are selectable, but it switches automatically back to 64 Samples)

In contradiction to Logic:
- Logic "allows" 32 Samples at all sample rates (32kHz-192kHz), but:
   -> if you select 176,4kHz-192kHz here, and hit Apply, suddenly the Latency values raise to the same values as Ableton with 64 samples
   -> as we know, the DAWs just read these values from the driver - so i think, Logic maybe shows 32 Samples, but in fact it uses 64.