yeah, sorry about your frustrations, strangedays, but did you not see the link that was posted in your other thread?

post 19:  https://forum.rme-audio.de/viewtopic.php?id=34567

It would probably help your cause if you posted your issues in the right thread (the driver issue you're having with your new Mac you posted in your thread about the faded writing on your BBF Pro Fs) so maybe that's why you didn't see the link. I understand it's frustrating but as an outsider to your situation, I see RME giving you plenty of assistance and almost always, I see the culprit in most peoples issues being NOT RME related. In other words, some driver, device or other issue besides RME drivers.

I know in these times people/customer/society expect fast food speed for resolving every crisis or problem one is having but the reality is that technology moves very fast and with thousands of different suppliers across hardware and software developers, it's near impossible, no, it IS impossible to predict every incompatibility. If you think you'll move to another product and not have these kinds of problems, then you should probably do just that. I do hope, however, that you are able to resolve your driver problem and continue to enjoy your BBF.

Good luck and do whatever it takes to be happy and make music

Peace,

-Steve

Link works for me, logged in or not.

No offense taken on my part   I don't like when people are frustrated because I know how it feels when you're trying to solve an issue. So, no apologies necessary

Hope you get the answers you need soon.

-Steve

Maybe I am not the only one..... seems like others are having issues still https://forum.rme-audio.de/viewtopic.ph … 81&p=8

I did read this, it’s the first thing I tried after my previous experience.  I recently upgraded my Intel Mac to the M1 air. I tested with a Mac Mini M1 on the previous thread but held of due to issues. I thought since it had been several months this would not be an issue still.  Apart from this everything else works, only RME seems to have fallen behind in a reliable driver install.  I’m sure they blame Apple but it needs resolving and all my other software has been upgraded.

I tried a bunch of things, I did get it working, but I noticed I also lost it again and then got it back again and seems to be staying.

If this is the norm now I’m just a bit disappointed that it’s become unreliable, I’ll see how I go but I hope RME come up with a better solution than this.

I have a BBF Pro Fs on a not ancient (but not new!) windows 8 machine. Neither the BBF, Totalmix nor the drivers have given me any issues. Only initial configuration and navigating through the settings during first time install and power up was all I had to deal with. So, definitely not similar to your hardware or the current driver issue you're having.

From what I've seen in several instances lately with people needing a solution to their issue, the best and most quick outcome is when the user supplies all technical details of their OS, hardware setup and error report, if available. This makes sense to me, although I admit I sometimes have a hard time following exactly what RME requests during some of the troubleshooting threads I've read. I'm NOT even close to a computer expert and only know enough to speak somewhat intelligently with things IT related.

Maybe the best path forward is take a step by step approach to what support has suggested you try, take LOTS of notes and document every outcome along the way paying attention to every message box that pops up or any irregularity in your OS configuration and then submit that to RME. It seems like a lot of effort when something should be ready to go out of the box (in my case and many others it usually is) but as you know, there's a lot going on in computers/drivers these days and providing a solution that's compatible with every combination out there is impossible for such complex devices as RME interfaces. I'm certain you'd find that other interface forums also have their share of users having difficulty with drivers, OS settings, etc.

Wish I knew the answer for you. Hope you can get it resolved soon. Hang in there

-Steve

This is a problem with your product, today I restarted my laptop and it dropped the drivers again.

Its getting stupid now and you are just blaming Apple.  My only solution is to consider selling the device.   This Macbook Air is a week old and your device simply does not work properly with it.  I am sure other devices work fine, I have tested an Apogee interface and its fine so I know this is just BS.

A look around the forum will reveal that this isn't a common problem, and that these solutions do help. Why this isn't the case on your system remains to be determined. It may be an individual issue, not even a general Apple matter. We may not be able to unilaterally provide a fix here, sorry.

That's a very limited and one-sided view on what's going on.

You think when Apple announced this a working/useable DriverKit for developers was available? That was an announcement about what will happen in unspecified years ahead. And I don't like when simple statements of a few words are not just taken as information, but turned around into an attack weapon. Shooting the messenger will not help you.

We are working on these new drivers for a long time already. You seem to think it is just a simple porting done in a week? Not at all.

As long as Apple not completely blocks 'old' drivers they are valid and should just work. On this whole unreliable and both us and the customers driving crazy Allow and driver blocking issues (that started long ago) I will continue to blame Apple - because it is the simple truth. It is 100% in their domain, not ours.

And as we already have a customer who claims that the old kernel extension shows slightly better performance than the DriverKit one - wait how all this new stuff will work out. It's far too early to be enthusiastic.

Basically RME have admitted they can no longer properly support Apple computers.   I don't care about technical details.  If RME cannot get it working reliably then that is that, you are Windows only with a bit of Apple support.  Every OS update kills the RME install to some degree.  I love the hardware but you need to get someone looking at the software again otherwise I am sorry your reputation is gone in my view.

I appreciate that RME are saying this is Apples fault - and it may be, but that does not mean you can no longer properly support the hardware.  If Apple have cut you of supporting it properly, fair enough, but something needs to be said and done so those of us using it can move on.

Reminds me of the USB issues at Apple that came up of all sudden due to a change from Apple in their USB stack ~4y ago.

RME rightly said that only Apple could solve the problem. But angry Apple customers have raised massive allegations against RME here in the forum.

The only thing that ultimately helped was that the trade press took up the topic after about six months.
The moment Apple was publicly criticized and with high visibility, Apple finally addressed the issue and resolved the issue in their USB stack, which RME correctly assessed and communicated from the start.
Unfortunately, the whole thing dragged on for around nine months in total and what did RME have to listen to here ...

Criticism in the public should be made in an appropriate way. It's not the best way when it escalates to massive and exaggerated allegations. Even if you don't care about technical details, you should at least consider that the problems in this case might also be on Apples side, as before certain security related changes in the Apple OS all was running fine.

Have you already opened a ticket with Apple and what is Apple's reaction?

What was interesting about the USB problem was that a customer reported that there were no interfaces between Apple customer support and development. Should surprise me, but it would at least fit into the picture that certain problems at Apple are not recognized in time and have to be publicly escalated via the trade press to get a solution.

You are entitled to your own opinion, but not your own facts. As others have tried to point out, this statement is simply not correct.

You should. That's the thing about facts, they matter.

I decided to post my response after a bit longer - ive not tried the new beta drivers so would be interested.  I also agree with the above poster.   What has annoyed me a bit is I have used RME products for a long time, youll see me moan on here only trying to learn Totalmix, but hardware wise, I thought the products were solid.  Also ironically RME support posted above a false startement, there are others having issues and are very frustrated. 

I have managed to get the device working - not reliably however, to say RME drivers are still stable when they simply are not , certainly not on the Mac M1.  I find constantly that the RME starts up hard panned to the left sometimes, it still drops and a complete reset is needed of the system.  Let not forget the quality of the device where the button text is fading on the physical unit itself.  I am sending it of to repair soon so hope this resolves that.  I have an Apogee device that is far more reliable and I am considering selling the RME - its a painful choice given all the time I spent learning Totalmix.  As a long time RME user I am sad as the first Babyface pro (no FS) I had was great quality.  I have read the comments above that seems to defend RME but as a pretty competent user (I am also an IT engineer) I expect a device to just work, or at least not keep failing. Also I am simply comparing it to the Apogee One on and M1 Mac and is simply more reliable.  Sorry but its true, my tests have proved it.  Maybe it is Apples fault that the RME drivers don't work as they should, however I don't have the time to mess about with this when other products simply work as expected.

If RME are just going to bury their head into the sand, at least I know I can use alternative products now and get the reliability I need.  I'll give it a bit longer but eventually I will just sell it of and maybe try a slightly more high end alternative.

The beta driver for USB v4.01 from last month is here, did you see it?

https://forum.rme-audio.de/viewtopic.php?id=35155

Have you updated to Monterey (OS12)? Many of the Apple bugs around the KEXT consent list are fixed there, as far as we can tell.

Odd. - even though I only had an issue with the RME after updating and resetting to default did it trigger it to calm back down.

I’ll see how all the up to date drivers behave now I still think it’s dropping the device though.

I've started using an Apogee device for a while, I still work on the Babyface but with reliability in question I have 2 options now.

Who knows where the fault lies, I hope eventually it settles down.  Various plugins runnng through Rosetta are causing issues as well.  I can appreciate that Apple are moving too fast, it seems like the M2 is coming out and we are still transitioning (and the M2 looks like a step back on the Macbook Pro).

I regret leaving my Intel based computer on many things, not noise and battery life though.  Have to live with it now.

Please consider that this is primarily a user forum. Customer support is available by mail directly.

Links have been posted here, and I pointed specifically to this forum and the website. There is a sticky link right here that mentions the issue with drivers being "dropped" after reboot.

It's a statement of a fact. The cause of these issues is not RME-specific, it's an Apple matter. I can only state facts here. There are working solutions, and I would not want to recommend a beta driver as a "solution" for a production system, because beta.
It isn't helpful to unilaterally put the blame on the RME side and simply ignore the fact that the solutions we provide do work. Sometimes there are things about an individual system that get in the way. This doesn't turn it into a general RME issue, and one would have to look closely at the system to see what might be the cause.

And the Babyface etc. can be connected to USB 3 or USB-C with a simple cable. They do not need the bandwidth, though, USB 2 is plenty. Even for the Madiface USB.

I had the same with Logic x, stuttering even without processor spikes. Someone on gearspace suggested to change the buffer so I changed process buffer range to medium, lowered it and voila works great on 1024 and 512.

Sorry yall I did not read the comment about the 4.3 beta drivers going to try that first

So far no good for me. Still jitters/dropouts and the pops in audio is actually worse. I tried thunderbolt2(didn't work) went back to USB3.2 into CalDigit TS3, IDK going to try some different dongles but so far it's bleak

Took the time to register here because I felt the need to share that the admin's attitude has succeeded in turning me off RME products. Later.

The "admin" I assume you meant MC? He is Matthias Carstens, the co-founder of RME.

What attitude are you getting from him? I think he is very knowledgeable and helpful, if you meant being direct, I guess that's the cultural difference. I am sure he meant no offense, just efficient and straight to the point.

Solution - get another interface.  It’s not ideal I picked up an Apogee One (one if the newer ones) for cheap which is not as good sound wise as the RME but it’s portable.  It works fine, but uses Coreaudio.  I’ve now read a number of issues on some companies drivers and what’s frustrating is everyone’s blaming each other.  I partly blame Apple as well in this but as a customer of both RME I don’t care whose fault it iis - I just need it to work.

It’s frustrating.  I’ve tried a lot of alternative things, there is no consistency - I can run a basic audio only session with basic M1 native plugins and get CPU spikes - totally random.  And I’ve been using Apple for years and it was all fine on Intel.  If someone suggests adjusting buffer sizes again I’ll cry haha! 

I’ve still got the Babyface but if the situation isn’t resolved when I can afford to test some good alternatives I’ll have to switch if I can confirm for sure it’s the heart of the issues.

If you have nothing helpful to say don’t bother.  I’m sure RME will do fine without me - and your point is? 

Can do without that sort of attitude, we are trying to get the devices working if you don’t like it don’t read it.  I’ve not got the cash to get another device yet so I was holding out till I can afford it.

The OS world is a very strange one esp Apple,

Apples seem to be always pushing the boundary, that courses them to keep changing OS, in turn messes up drivers and trashes your work flow, Windows is a bit more forgiving and carries drivers through for a very long time.

one does wonder if Apple is on a sort of sabotage mission as they seem to dont give two hoots about messing up your work flow and production

On the other hand Apple want wait for every one to catch up they will just move on and leave a trail of destruction behind them

So what do you do.

For one do Apple owners really need to update every time a new OS comes out iis what we are doing for our project more important than taking an update risk

We can at least do research before we pull the trigger and up date to the latest and greatest,

What was working so stable with out a glitch no issues, now becomes redundant because we pulled the trigger and updated to the latest OS.

So what is more important, staying put with everything working good or updating and destroying all our work.