I'd contact RME Support to report this. Hopefully they can check it out and see if the issue is on their end or not.

Side-question: Given RME has loopback, why would you need to run Audio Hijack in the first place? I've stopped trusting Rogue Amoeba years ago, using another product from them.
For pro audio I'd place way more trust in Audinate's Dante Via technology, if I needed other rerouting out of some reason.

Side-question aside, glitches, dropouts and stuttering does not have to be related to Audio Hijack. I've seen multiple people saying 48k has been used when encountering such issues. 48k might not be relevant in itself, but it's an observation to note.

Thanks for sharing. From your post, it was easy to assume you were using Audio Hijack, like the previous poster, rather than the Loopback app. I'm not sure how much code these RA apps share these days.

I'd like to know this as well

Double posting makes you look like a spamer

Why hasn't anyone brought this topic up yet?
That is your question.
answer : Because there is no difference.
The wave file sounds exactly the same regardless what computer is on.
The converter of an interface has no information about the computers operating system.

I hear a very big difference in audio quality! The question is not raised by Mac users because they don't know or have heard the Windows sound difference! Perhaps - the difference in ASIO - Wasapi-Core Audio but this difference is very significant! Maybe I have the wrong Babyface Pro FS drivers installed - I'm waiting for a recommendation on what to install? Perhaps this is not the topic - give a link to the topic Mac

The 407 driver is what I use too.
As it works, it's the right one.

I am a musician with absolute pitch - I can hear the difference in the sound of Mac and Window! It's not bad and it's not good - it's a different sound. Perhaps - you need to get used to it, adapt. To put it simply - in Windows the sound is more musical, in Mac - more accurate, analytical. But he is different. Need to get used to...
Today I installed driver 408 - I'm testing

Sorry, but I can't believe this. Windows and Apple are both operating systems that are capable to playback audio lossless.
But surely on both systems you can make mistakes that you do not hear lossless, and you should find out what is causing this.
Like the mentioned audio enhancements.

To completely exclude these Windows sound enhancements and the audio subsystem of Windows and the mixer, you should use the ASIO driver, which completely bypasses it.
macOS has no ASIO, so the application has no driver with direct access to the audio HW. But there are surely settings, which enable you to listen lossless.

If you had an ADI-2 DAC or ADI-2 Pro or ADI-2/4 Pro SE, then you could easily validate, whether your complete audio chain from the player (or DAW) up to the DAC is lossless.

You can download short test files in .wav format from RME, that are available for different sample rates.
This you simply play back, and then you can see in the display of the ADI-xxx whether audio has been received lossless.

Then you would see, whether one of the audio chains (Windows or Apple) has loss .. then you only need to find out what it caused. If the transfers are lossless, then you have no issue and no sound difference, also no cable / USB transport issue.

Some posts earlier the sound you heard on the Mac was "very poor", "like on a cheap MP-3", "terrible" and "horrible". All of a sudden it's not only "just different" but even "more accurate, analytical". Your RME interface first was "like a cheap sound card from Aliexpress", later "definitely better" than the internal audio output on the Mac.
Please don't get me wrong. It is not my intention to simply disagree (or even argue) for any childish reasons like "I like Mac better..." or similar. But I just can't take that as a base for a serious discussion. Beside that, I'm a professional musician as well.
Again: it should be all fine with the driver versions you have tested (4.07 and 4.08), at least from a technical view. If the sound is really that bad as you described before, there is something wrong for sure. To find out what it could be, please post exact informations about involved software, settings (sample rate, clocking etc), and others as illumina already suggested. Also I'm with ramses when he writes, a comparison should be done using the exact same chain of audio hardware.

Probably - the reason for the bad sound was in the 407 driver on my audio interface, maybe it was installed crookedly! Most likely - it required a lot of system permissions, maybe I missed this moment somewhere. Version 408 - granted all permissions to the driver during installation. I'm testing while

If you were using iTunes, turn off sound check and check other settings like download hi res, use atmos, etc.

Aua
What does absolute pitch have to do with the ability of educated, professional listening? Do you think that you can hear, frequency response, dynamic range, thd, phase alignment, etc. based on absolute pitch? My son has really absolute pitch (you can play him any cluster and tell him to sing an f-sharp on top for example) but he is just a terrible mixer, because his ears are not really trained for music production yet.... And the way you describe the quality of the sound of different computers seems very "rudimentary".

PS: I don't want to go in the rabbit whole of perfect pitch and I don't want to question your skills, since I don't know you. But there are sooo many people speaking out loud that they have perfect pitch. And if you test it, it's rather embarrassing. Most of them are having trouble even with relative pitch. They have to repeat intervals and think about their mnemonics

PS2: Where are you from? We are a professional studio with professional equipment and class a clients (mostly large orchestras). You can check out the sound quality from different computers and different converters and have a good cup of coffee?

Hello, I am on Mac OS Ventura 13.3.1(a) , everything was working ok, then I lent my babyface PRO to a friend during the afternoon and when I went to use it in the evening, the Totalmix stopped working properly (the meters wouldn't display any signal although there was audio being sent to the monitors). I re-booted the laptop a couple of times, checked AUDIO-MIDI Setup and finally decided to re-install the latest driver compatible with M1 (which is my laptop).

Now whenever I try to open the Firaface USB Settings or the TotalMix they open and close instantly. There is audio coming out of the babyface but without access to the Totalmix it will be impossible for me to work properly. I am unable to do the routing I need.

I also tried to run the Flash Update, but the same happens - it opens and closes instantly.

I rebooted the laptop in recovery mode to allow for reduced security and rebooted the laptop once more to reinstall the drivers again.

I reinstalled the drivers multiple times, and in different versions, but nothing worked.

Tomorrow I will go to a friend to try to run the flash update from his laptop and verify if it is working correctly on his machine and try again on mine.

If nothing works I will have to backup my things and downgrade my MacOS System and try to install again.

If someone has any suggestions on how to troubleshoot this, I deeply appreciate. THank yoU!

That was it. thank you so much!

Hi
Driver v3.222b is not for your macOS, it's clearly declared for macOS 10.12-10.15 only.
For your system and the UCX you have three possibilities:
1) the driver v4.07 or 4.08 (Apple driver kit version) which requires a firmware update first. And to do this, the installation of a kernel extension driver is needed anyway.
2) the driver v.3.28B(2) (kernel extension) which requires the recovery boot and security settings first. You can find the guide on the RME site.
https://www.rme-audio.de/rme-macos.html
3) you connect the interface over FireWire > Thunderbolt (Apple adapters) and install the driver v3.41 which also requires the recovery boot first.

Subject: Outlook: Future support of legacy rme products on apple silicone Macs?

Hi all,

I don‘t want to start a new thread and the topic seems to be the right one.
My Mac Pro 2012 is getting too old, my MacBook Air 2013 stopped working, so instead of buying a Mac and a MacBook I recently purchased a MacBook Pro m2 as my new main machine for both home and on the road.

In the last years I was using a fireface 400 with should still work fine with this apple silicone machine (latest drivers still support fireface 400, but haven’t tried yet)
I am thinking about buying a used fireface 800 or something like that for stationary studio use (and having more XLR inputs) in the future and keep the fireface 400 for portable use.
Is there a time limit when rme legacy products might not be supported anymore with apple silicone Mac’s?

(I‘ve been using rme pci cards and FireWire interfaces for decades now and i‘ve always been loving them. Sound clarity, stability und usability of total mix and digicheck are things I don‘t wanna miss in the future also.)

Thanks everybody.

Hey, i only registered here to thank the RME Team, that they finally have fixed the issues with my FF UC via 4.08 driverkit update.

This year marks the 10th year i own FF UC. After i changed to a newer from Mbpro 2017 and recently the M1, all the time i had problems with glitches in Chrome only watching YT videos, playing simple audio, or had to switch audio output in Ableton just to render a session (otherwise would abort). This was driving me crazy for such a long time. Now everything seems to work flawlessly and i don´t have to reset my whole machine and will save a lot time. thank you!!!

ATM I´m still working on 13.0, unfortunately after standby or re-plugging without restart, it loses ability to change main volume via macOS/ doesn´t affect UC anymore. Only when i restart Totalmix it works again.

Not sure, but there was / is a certain point when i´ve installed various software, where some configuration has interfered with previous UC drivers which led to dropouts.

I´m still happy to have switched to driverkit 4.x, since i don´t have dropouts anymore, which also affected overall performance, mbpro stuck, long loading times, etc. Before that, i got used to listen to sound on my airpods or just the mbPro Audio output and only used the UCs Hardware out for my external gear. So, this is a big relief.

It's not been resolved. How could it? No new driver-updates recently as far as I know (I am using Ventura 13.4, Driver 4.08, FW43 - UCX II). It still stutters like crazy when RAM pressure is high. Unusable. The only workaround for me is to keep RAM pressure low, which is not really a workaround.

Regards
Terje

Does anyone know if Firewire UCX will work on macOS Sonoma?

Thanks

Honestly, MAC and RME has always been a horror, but now with the latest OS we are on another level, you have to go in and boot and remove security and it still not working, even worse it's rebooting my mac, when i followed all the steps on your website....
When you pay 900e for a soundcard and it's not click and PLAY there is something wrong with your gear. HIRE SOFTWARE DEVELOPERS MAKE IT WORK!!!!
You shoudn't have to be a computer nerd to make something work, i think you should stop selling your gear as compatible with MAC/APPLE. period....
seriously....

…always been a horror…?
Definitely not for me and for several other users. All fine with my different RME units on different Mac computers since many years.