I have the same problem. MacStudio M1 Max with Monterey and Fireface 802. Rosetta works better as well.

Basically RME cannot be bothered to sort out the drivers in the new macs. It's been ongoing support headaches since M1.  I've noticed they don't seem to acknowledge it.   They have had plenty of time to get this right.

The driver is 4.02.

Logic runs fine natively with the other interface. I do have a few plugins that require rosetta, that does not seem to cause any problems even with native ARM Logic. I tested some logic sessions with stock plugins only with the same 'stuttering/looping' with the UC. I also made A/B comparison tests with several logic sessions testing both interfaces one after the other on the same session.

I don't think it is related to cpu usage in the conventional way because in that case playback would just stop (or playing distorted audio sometimes). In my case it keeps repeating a very small part of the session, like a mini-loop. I have a screenrecording i could send to you if that would help to understand the behaviour. And it keeps playing back that small loop until i stop it. It is very different to a normal cpu-overload. It seems to be triggered more easily on bigger sessions.

In my case with a cpu overload logic would just stop playback. I never had that kind of freeze in DC with a cpu overload, the bars would just fall down smooth normally.

Yes. There is software for monitoring, but i don't think it qualifies for a driver. It still works without it.

I have the same problem with Babyface pro fs with driver version 3.28 , which is the latest version. I cannot use the interface without putting Logic into Rosetta mode! There is no problem when i connect another interface or connect to the internal interface of the macbook pro (14" with M1 Pro & 16gb memory) Request the concerned people at RME to please solve the issue!

Thanks

Hi, The problem happens only when I use Logic Pro X with my BF Pro FS in Native mode. If I switch to another interface or the Mac's internal interface the problem stops completely. When logic is used in rosetta mode the session opens fine with my RME interface. This points to a driver issue which is causing the playback to stutter like mentioned by many in the above comments when Logic is running in native mode. I have tried with Logic's internal plugins or with plugins that run natively but the problem persists on the RME interface. No issues when used with another interface!

Have you updated your system ?

From Monterey to Ventura ( Just in case, Logic TNT versions no longer run under Ventura ! )
From Logic 10.7.3 to 10.7.6
From RME driver 3.28 to 4.06

Is there other software running like OBS or AudioHijack ?

Also try : Switch off Bluetooth

Do we have any solutions for this yet?

Your Babyface Pro is 'driverless' as well, just use it in CC mode. No TotalMix then, of course.  It would sure be interesting to see if Logic then behaves well...

I think that, when you get the suggestion to try CC mode from the founder of RME, perhaps you should at least consider taking his advice ;-)

Update:

It runs smoother with the following Logic Pro X audio settings:

Processing threads: Automatic (Recommended), before it was 10 (8 high performance cores)

Processing Buffer: Small, before it was Large

Multithreading: Playback & Live Tracks. before it was only Playback

Changing the multithreading setting has produced the most noticeable difference!

Further information about the multithreading function: (maybe helpful for the problem solution)

You can use multithreading to affect how Logic distributes the DSP load when a software instrument track stack is selected for live input or when multiple audio tracks are enabled for recording.

The Playback setting reproduces the behavior of earlier versions of Logic. When a track stack is selected for live input, or when multiple audio tracks are recorded, all of the DSP required for the input is processed by one processing thread-and thus by one available core on the computer.

The Playback and Live Tracks setting distributes the load across multiple threads when a track stack is selected that contains multiple software instrument channel strips, or when more than one audio track is being recorded. If the computer has enough cores and there are no other DSP demands on the computer, each live channel strip can be processed by a different core.

With the Playback and Live Tracks option, the system may be a bit more stressed. So if you don't have live tracks with high demands, track playback may be a better choice.