I wanted to crash the thread to see if the UFX III and latest driver kit versions are alleviating the glitches people were reporting on M4 (and silicon Macs in general)?

It’s easy to find complaints on the internet, but I’m guessing a lot more people are perfectly happy (with RME) than what the internet may lead you to believe.

Kind regards,
Phil

I noticed that for a split second the input and output latencies at 192 Khz goes from 0.80 input , 0.82 output , 1.62 total (assuming the readings are correct) to 1.12 sometimes under 1 ms !

I thought i could achieve that but no . I tried different cables or maybe by freeing some resources .
That's what MC is saying then i guess (btw thanks for taking the time to reply )
It tries to go to 32 but than it uses safety offsets and goes to 64 .

Definetely gonna try the RTL utility .

Thanks again everyone

Tip: RTL Utility can show all these buffers in detail, and also verify their 'size' - at least from the audio interface side. If Logic and others add small playback buffers it can't reveal these, of course.

So if it's an Ableton issue (which i seriously doubt )

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.

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

Installed the latest driver 4.27 (not cc)

I have a little issue . I can't lower the buffer size to 32 in any mode 48-192khz.
I tested it in ableton latest 12.2 .
Did i do something wrong , or am i missing something?
Just bought a mac after years of windows use, so i am sure it's a user(me) error .
Any help would be much appreciated

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!

Thank you for this info.  Would you know if it allows compatibility with the latest Mac OS?

I think there are reports that macOS Tahoe no longer supports Firewire. It still works in Sequoia (as per posts in this forum).

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

On the RME website driver install page I see macfire 2.62.  I do not see Macfire 2.42.
Thanks again!

MacOS Sequoia works also.
Read this thread : https://forum.rme-audio.de/viewtopic.ph … 16#p224916

Most owners of a FF800 did exchange the PSU in the time.
In your case I do recommend to let it repair.

Excellent! Thank you for your help!

Most owners of a FF800 did exchange the PSU in the time.
In your case I do recommend to let it repair.

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.

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.

This sounds like defect internal power supply.
Was it replaced in the past ?