Does the macOS RME USB 4.06 driver apply to the FireFace 400 connected via Apple Firewire to Thunderbolt to USB-C port? I see Fireface 400 is not listed in the readme, so I assume not.

Their position is to hide behind local forum regulars who answer on any post about Apple Silicon issues: "It works perfectly on my maschine. RME is famous with their reliable drivers. Software is perfect. Period. Case closed". Also they have few people that post regularly: "Finally, latest driver {number} is fixed all issues". It doesn't fixed anything, but hey, it looks like it fixed, and you now figuring out, maybe it's your fault???

I guess it's very difficult to tell because it doesn't seem to be a general problem. There are users which don't have any issues with RME USB interfaces on M1/2 Macs, others sadly have. Since there are hundreds of different combinations of Apple computers and RME interfaces and involved software, driver, system and firmware versions, buffer sizes, sample rates ... it's not easy to find the reason.

Great joke! Telling this about most unified hardware/software system in existence (Apple). Good thing Windows PC exist only in single combination...And here we go again, lying about "some having issues, some don't". RME officials and their buddy forum regulars are taking RME customers as a fools, clearly.

It's not easy to find a reason...FOR TWO YEARS! TWO!

For me it's absolutely clear that RME gave up. They CAN'T fix Apple drivers, and they don't have guts to publicly tell this.

Me personally already put my Babyface on sale.

Hi, does this only occur with me, or could this be a small bug in the Driverkit 4.08? It does not bother me, I just noticed it.

Everything is fine with the audio. The interface also shows 48kHz, seems to be just an optical error. Otherwise, so far no problems with the Driverkit on MacOS 12.6.6 with the M1Pro chip. 
But I haven't been able to max out my Macbook with my latest projects so far. So I can't say anything about the audio problems with increased RAM usage.

15 years of RME units, it is the first time that I cannot use the Hardware.

can we have a feedback from RME about de drop outs of audio ?

Please tell us if it can be fixed or not.  Just an answer !

Yes, Audio-MIDI-Setup also showed 48kHz. TM version 1.83.
I was able to solve the problem by restarting the Mac completely. I think it got "stuck" at some point after waking up from sleep mode.
Apparently it is just a visual flaw in the Totalmix window, but it has happened a few times since I switched to the Driverkit.

IMAO, there's nothing to wait. I am selling Babyface. And not because of Apple issue, because RME can't face this problem and communicate clearly with us, customers. This is not how you do business selling products at that price point!

For starters, you should clearly put a bold notification at your product pages: "NOT WORKING WITH APPLE SILICON". Because when I buy a product at that price, I expect it to work without any issues. Not to wait years for drivers and then got an answer that it must be something wrong with my 3k$ laptop.

Below is a link (edit: fix typo) to a thread on AudioScienceReview where several posters have issues with audio stuttering/dropout when using an external USB DAC (from various manufacturers) on M1 silicon. For M2 this seems, for now, not to be an issue. In post #266 a poster reports good experience with beta 2 of macOS Sonoma using M1 silicon where he earlier had audio issues.

https://www.audiosciencereview.com/foru … pro.42001/

Is RME here ?

Please MC, answer to us.

If you think it's an pure apple issue, tell us.

Need to now if I sell my 2 UCX II in that case as apple seems not aware of the issue

It seems to be very well aware, just doesn't care so much. The problem is not limited to RME devices, it's rather widespread, especially when memory usage is high, as discussed here: https://www.audiosciencereview.com/foru … pro.42001/

The problem is there are no memory slots in any of the Apple silicon Macs, and unified memory is rather expensive

I personally am not a Mac user, either, but it makes me sick reading some users here slandering RME for what is not their fault. I even finally registered on the forum after lurking for a couple of years

Some posts above I wrote about my test: even high RAM usage had no impact to the sound output on my Babyface pro on a M1 Mac. The other thing is: I had so many apps open, exported even a video out of FCP and there was still enough memory (or swapping was so smooth I didn’t take notice?). So what the h… are people doing with their computers? Ok, maybe they have large DAW projects with tons of plugins? But no, there are users reporting audio issues with very simple applications, listening music or such.
And in my opinion - sorry Ramses, not against you - in 2023 you certainly don’t write some shell scripts to solve something like audio or RAM issues, having such expensive professional gear in front of you. It should work without that! Again: I don’t experienced such issues myself but can understand users losing their patience…

Of course I also would try several things when having (heavy) issues with my computer/audio system.
What I tried to say is: when I buy an expensive computer from a company like Apple and a professional grade audio interface, as a normal customer I expect that it generally works. Especially when this gear is selled as 'easy to use' (Apple). Of course it's normal to have a bug here and there.
My sentence in the previous post was misleading: I did not meant to say about liking scripts or not, or even to find such thing generally unnecessary or outdated (and I'm thankful to experts like you, doing such work in the background for normal users). But when I should write a script to optimize RAM usage or similar on a Mac in 2023, as a normal customer, there is something wrong imo. When I go intentionally to some system limits (having really large DAW projects, hi res audio, tons of plugins and so on) of course I'm also willed to optimize my system in a more 'expert' like style.

So back to the main theme:
On one side, there are users reporting issues with USB audio interfaces in simple applications.
On the other side - as I already wrote -, it's not that easy to force a newer Mac to get to RAM usage limits. And in my case I was not able to bring one of my Macs to a point getting issues like described from other users (2012 Macbook pro i7 with 16GB RAM and 2020 Mac mini M1, also with 16GB).
In short: I don't think the reported issues are related to RAM usage. And this was your question, right?

Last thing: "you really can talk..": not that fair, I have already emphasized that I appreciate not to have any problems with my RME devices and that I understand the frustration of the affected users. On the way to find solutions for the existing issues it's also important to report about working systems. Maybe it's related only to specific Macs, or specific combinations of devices or software versions. So every information is a little piece of the puzzle. I think it's ok to not simply sit at home and be happy about my working system but spending some time in this forum here and sharing my thoughts, no?

Other applications, unlike audio, have no requirements for near-realtime processing..

How is it when you use lower sample rates?

No worries, it switches automatically to the internal clock when no clock signal is detected on the selected digital input. That’s another RME advantage

All I can say is that I'm glad I'm still running Big Sur on my Intel MBP and using Thunderbolt with my UFX+.  I feel for those users running more recent versions of macOS, Apple Silicon machines and using USB....the situation must be a real pain in the a$$ for those experiencing issues.

I came here to check what's up as by bandmate is thinking about upgrading to M2 mac to solve some issues. I have to say there's a lot of opinions here that do not reflect my experiences, mainly Apple Silicon and RME not being compatible.

I've complained my share and I totally get that it's annoying that basic shit does not work in 2023. Also it does not help that RME does not excel at communicating and troubleshooting, also it does not help that they eagerly although usually in somewhat condescending manner reply to people who have trivial user error issues and for experienced users with compability issues it's usually silence or apple's fault.

However, my experience is that Macbook RME compability broke in 2018 with T2 chipped Macbook pro's, and although according to the generally accepted truth it got fixed a year later all my issues we're finally only solved with a new M1 mbp. I had some issues with first published version of driverkit driver but before and after that (and some updates) I have not had a single problem with this machine and RME hardware (df avb, babyface pro fs, adi-2 dac, UFX, latest sofware, no betas), I'm using the machine for both studio work and live.

This was not really aimed for anyone who has issues, I hope there's a solution sooner or later be it new driver or switch to another brand. I know I would have switched so many times if there was something better!

Macbook Pro 2021 M1 Max Ventura 13.4.1 (22F82)

After I've upgraded to the latest DriverKit driver v4.08 my Babyface Pro FS glitches and clicks regularly. Unusable.

Switched to Class Compliant mode - works fine, but I want the TotalMix to work properly.

And I don't understand how to downgrade the driver, because I upgraded Babyface Pro FS firmware to v205.

Today I've switched back from CC to PC mode, and it glitches like before.

What I have found later today is that on my other m1 MacBook with previous version of driver Babyface with new firmware works fine, without issues. I have listened music and YouTube for about an hour.
Config here is:

macOS: 13.4.1 (22F82)
TotalMix FX Version 1.83 macOS (1)
Babyface Pro FS Firmware: v205
Driver: v3.28B

So the question is how to rollback to that version of driver on my main MacBook...
A full reinstall of macOS is not the best option at this point for me.

My DAW is Final Cut Pro and I tried to open my project and play. And it's fine.
On my main MacBook even Apple Music has issues with latest drivers.