macOS Sonoma compatibilty list

[Cyoon]

Sonible seems to have issues, black GUI for a few seconds and registration codes not accepted anymore, they are working on a fix.

[jancivil]

Before I had this one radical problem the only times I ever used a new OS was because new computer.

AFAICT Cubase for instance might be more efficient as per CPU but its performance doesn't reflect it. Everything today is using so much RAM.
Bench tests, meh. getting a DAW to perform in real time is not so easily boiled down like that.

[syntonica]

Unfortunately, unless you can automate your workflow and time the program performing that workflow, the best you can do is to create a project using both internal and external plugins and note the CPU load within the DAW, both before and after the OS update. Not exactly scientific, but better than a poke in the eye with a sharp stick. Most likely, any difference will be marginal at best.

I haven't looked into it yet, but if you can set the new gaming mode manually, that will be the best option for speed and efficiency gains. Anything to keep those mds_workers at bay!

[sqigls]

gaming mode? does that mean we can assign which cores are utilised by apps?
like only using performance cores with Cubase or something like that?
it's all a bit rocket surgery for me. All i know is, if it aint broke don't fix it. Which is why i stayed on Monterey so long.

[syntonica]

gaming mode? does that mean we can assign which cores are utilised by apps?
like only using performance cores with Cubase or something like that?
it's all a bit rocket surgery for me. All i know is, if it aint broke don't fix it. Which is why i stayed on Monterey so long.

Okay, I looked it up. It's enabled by a setting in the specific game you're playing. Which is annoying. If available to DAWs, they'll have to update to provide the setting. Making it useless to us for now.

[machinesworking]

right, but i'm suggesting that your singular experience is just that. so again, i stand by my comments.

OK, you're being that guy in the thread on whether there are issues in an OS who does the whole, "well I'm not having that issue" BS. You can stand by being a pedant all you want, but you're not helping anyone, you're muddying the waters attempting to suggest it's not the OS, Application, or driver that is in conflict. If you aren't attempting to suggest that, why are you commenting? what are you contributing?

Literally, you're attempting to obfuscate actual data in favor of what?

[fisherKing]

right, but i'm suggesting that your singular experience is just that. so again, i stand by my comments.

OK, you're being that guy in the thread on whether there are issues in an OS who does the whole, "well I'm not having that issue" BS. You can stand by being a pedant all you want, but you're not helping anyone, you're muddying the waters attempting to suggest it's not the OS, Application, or driver that is in conflict. If you aren't attempting to suggest that, why are you commenting? what are you contributing?

Literally, you're attempting to obfuscate actual data in favor of what?

what? why are we still discussing this? if you have issues that aren't universal... get help. go to a mac forum. or call apple.

if you're having issues that all, or many, are having... apple needs to address those issues.

literally, you're attempting to obfuscate actual data in favor of what?

[noiseboyuk]

Sheesh.

Pretty simple - if you have issues or there's something new in the OS you think you'd get value from, update. If neither apply, don't bother, it's hassle for no reward.

A much bigger issue comes if you do this for several versions of macOS in a row, as then you might start to experience compatibility issues keeping latest and old apps running on the same system. But skipping one unnecessary update is obviously fine for a lot of people.

[Jac459]

Sheesh.

Pretty simple - if you have issues or there's something new in the OS you think you'd get value from, update. If neither apply, don't bother, it's hassle for no reward.

A much bigger issue comes if you do this for several versions of macOS in a row, as then you might start to experience compatibility issues keeping latest and old apps running on the same system. But skipping one unnecessary update is obviously fine for a lot of people.

Agreed but please monitor the security updates if you're version don't get, update .
Don't be a seating duck.

[machinesworking]

Sheesh.

Pretty simple - if you have issues or there's something new in the OS you think you'd get value from, update. If neither apply, don't bother, it's hassle for no reward.

A much bigger issue comes if you do this for several versions of macOS in a row, as then you might start to experience compatibility issues keeping latest and old apps running on the same system. But skipping one unnecessary update is obviously fine for a lot of people.

Agreed but please monitor the security updates if you're version don't get, update .
Don't be a seating duck.

Mostly, it's smart to wait a little bit, unless of course there's a major vulnerability that the update addresses. I jumped in because specific OS level issues popped up with Ventura, which came with the mac studio I bought. This would be the first time I've updated the OS the day the new version came out.

Like I've pointed out, there are also DAW and plugin specific concerns for various setups, this isn't uncommon with Mac OS updates, regardless of the peanut gallery attempting to do the time honored men arguing on the internet routine.

[fisherKing]

Like I've pointed out, there are also DAW and plugin specific concerns for various setups, this isn't uncommon with Mac OS updates, regardless of the peanut gallery attempting to do the time honored men arguing on the internet routine.

point updates are not guaranteed fixes for everything; some bugs get squashed, some new ones appear. OS development is never a straight line forward; hence, the endless betas, and point updates.

in other news, i guess we both come from the peanut gallery, so... see you there

[Cyoon]

that's the shit, thank you
i wouldn't ever doubt RME drivers, but there you go.
what machine are you running? for the record

Great. The problem is not the RME drivers per se but the extra hoops you have to jump through on Mx chips to get them installed. In the last 2 MacOs versions this involved going into Recovery mode to select ‘Reduced Security’ but if Apple ever close off that workaround then the hardware will no longer work

My fireface 400 with PCIe Firewire card is still working

[Cyoon]

Sonible seems to have issues, black GUI for a few seconds and registration codes not accepted anymore, they are working on a fix.

My bad actually, working now.

[dumbledog]

Anyone give Elektron Overbridge a shot? That seems to break often enough with OS releases.

[rACatkvr]

that's the shit, thank you
i wouldn't ever doubt RME drivers, but there you go.
what machine are you running? for the record

Great. The problem is not the RME drivers per se but the extra hoops you have to jump through on Mx chips to get them installed. In the last 2 MacOs versions this involved going into Recovery mode to select ‘Reduced Security’ but if Apple ever close off that workaround then the hardware will no longer work

My fireface 400 with PCIe Firewire card is still working

Actually RME have drivers that will continue to work post Apple closing the above workaround.