Topic: Jeez What's going on with the Babyface Mac Drivers?
So today, I went to use my Babyface (original), like I always do, and nothing worked as expected.
The BF was not in the device list in Sound Preferences or Audio MIDI Setup.
Fireface USB Settings would not launch.
TotalMix appeared to be open but would not show any windows.
So I searched around the web and found some stuff about Class Compliant Mode and figured out how to turn it on and off.
But toggling it on/off did nothing for my issues, iirc.
I was confused between the leds behaviour for CC and Norm modes.
At some point I did get FF USB Settings to open and I did see the BF in the device lists, but I think it was when I was in CC mode, which isn't supposed to happen.
(Note: I've fixed the problem since then and don't totally recall all the details of my troubleshooting efforts.
It may have been that when I was in Norm mode, that I was able to launch the Settings app and select the BF in the devices list.
But still no windows in TotalMix and still not the way the BF usually behaved.)
Then I tried dl'ing the Driver and the Flash Update again from RME's web site.
The latest driver available was 3.25.
So I installed that again, and authorized the Mac to run it in System Prefs.
But I was already running that same driver, and when I restarted the Mac there was no change.
And the Flash Update app would not run at all.
Very weird, I thought.
Then I started reading some other threads on this forum and somebody had posted a link to Driver 3.26.
I dl'd that one, installed it, authorized it, and restarted my iMac, and now everything is fine.
So why the f... is that driver not in the list of drivers now on the main page where we go to dl RME drivers?
As a matter of fact, I can't find any mention of that driver anywhere on RME's site or on the web.
I wasted several hours today troubleshooting this CRAP.
There was a small security update Apple had us install the other day that didn't even require a restart.
I don't think it even changed the OS version number.
I'm on Mac OS 11.6 now.
Maybe that was the culprit that started the issue, and then RME came out quickly with a new driver?
Normally that would be laudible.
But that driver is ng to anybody unless we can find it.
Jeez.
I hope this helps the next poor fool who tries to figure this out.
Joey Goldstein
http://www.joeygoldstein.com
http://www.cdbaby.com/Artist/JoeyGoldstein