macOS Sonoma compatibilty list

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

The following plugins are compatible to macOS Sonoma:

- Valhalla
- Cherry Audio
- U-he (nearly all, except old stuff)
- Universal Audio (nearly all, even Apollos except old FireWires)
- Cubase (inofficially)

Who else?

It looks like nothing has changed in macOS because everyone at Apple is working on the Vision Pro.
Last edited by wangeroge on Tue Sep 26, 2023 11:06 pm, edited 3 times in total.
If you plan on purchasing your first Universal Audio hardware, you can get a free additional plugin. Just send a PM.

Post

Keep an eye here for a searchable Sonoma database - https://www.production-expert.com/apple ... chart#home .

As of right now, almost nothing is officially confirmed as compatible, so worth steering well clear for a while. That said, my sense right now is that this might be one of the easier migrations for developers, with luck there's little if anything for developers to do. This response from u-he gives that impression:
Initial tests showed no problems with beta versions of macOS Sonoma. However, a final verdict about compatibility can only be given once macOS Sonoma is officially released.
And on the other other hand there's practically nothing in Sonoma I'm interested in specifically, so I'm not exactly upset that I might have to wait.
http://www.guyrowland.co.uk
http://www.sound-on-screen.com
W11, Ryzen 7900, 64gb RAM, RME Babyface, 1050ti, PT 2024 Ultimate, Cubase Pro 14
Macbook Air M2 OSX 10.15

Post

Ok, then let's make it official!

All current u-he plug-ins are compatible with Sonoma. 8)

There are two slightly dated exceptions that are currently moving into our development focus: Uhbik and TyrellN6. We hope to be able to at least post beta versions of these in a few weeks/months time.

Post

every single 3rd-party plugin i use (and there are many) has run in logic on every sonoma beta, and now, currently, on the RC. the biggest issue i've heard about is with plugin alliance plugins (which i don't use). they're apparently trying to get that resolved.

working for me: atlas, uh-e, dune3, equator 2, fabfilter, icarus2, izotope, massiveX, phase plant, pianoteq, spire, valhallaDSP, sublabXL, trackspacer, waves, vital... etc
_______________________
https://upstatebrooklyn.com

Post

Anyone interested might want to also check this out: https://www.production-expert.com/apple ... lity-chart

Most of it doesn't have confirmation, but the ones that identify problems are helpful.

Post

Oh, kind of weird. I updated Sonoma beta to what, exactly, then? Two days ago. Must be a kind of bug in "System Settings", I mean it should have taken a little more time than it did on the restart and that.

Post

Anecdotally: I was desperate with a show-stopping issue* under Ventura so one thing I did was install Sonoma beta. I never do this kind of thing but I have something unusual here. Been at least a week.
These things have worked consistently causing no issues. These are all latest versions.

Cubase Pro 12.0.7 (*: with the glaring exception of it in connection with VE Pro 7). All the rest as plugged into Cubase.
VSL: Synchron Player; Vienna Instruments Pro; MIR Pro 3D & MIRacle convolution reverb; Vienna Suite [FX Plugins] Pro Equalizer, Power Pan, Limiter. All VST3. The instruments in two projects. Older projects w. VS Pro.
BFD3.4.5 [VST2] in three projects.
Orchestral Tools SINE Player VST3.
Native Instruments: Replika XT VST3. Reaktor 6 FX VST3, one thing from Legacy is all I've used. Absynth 5 [VST2]!.
SDRR2 Tube VST3.
This despite the disclaimer there at the Apple page, iZotope Neutron 3 I've used several presets and futzed with them considerable in regions in Audio Parts; and Ozone Imager.

Obv not official, but I've logged in considerable hours with all of these things in one project; other proj. more limited duty.
Last edited by jancivil on Mon Sep 25, 2023 8:56 pm, edited 1 time in total.

Post

I had no particular interest in Sonoma at all. I experienced an odd one in VE Pro setting something up before it proved fatal to like my whole machine, where VSL Support told me initially they couldn't reproduce my issue but they were on Sonoma beta. That's a coincidence btw. My reason was purely because of the bizarre VE Pro problem, w. nothing to do with my crashes in it under Ventura.

Post

I never do this, but I'm upgrading to Sonoma tomorrow as soon as it comes out. I bought a monster M2 Studio Ultra and Ventura has been slightly unstable with audio, not as much with DAWs, but basic youtube videos have audio glitches in them. RME forums has a poster claiming he knows it's not RME and is due to some bugs in Ventura. Sonoma is primarily a bug fix upgrade according to some reports, and people are claiming the beta fixes these issues. So yeah, this one I'm diving in head first on.

Post

Well, the issue that had me reaching like that was entirely audio, & ultimately in the most dramatic fashion. It began with Cubase telling me the audio device was removed from the hardware - something like that, a strange sentence - when that would be impossible as it was the built-in audio. It did the same with an audio interface. At one point quite before it became fatal and irrevocably I bought a pair of headphones to check to see if my audio strangeness (mainly a lot_of audio cutting out at Youtube at that time) was a simple matter like a headphone jack. It wasn't.

A chief symptom of the later SNAFU is the cursor in an audio file inside Cubase wouldn't move. The disease spread at one point to online audio; Youtube wouldn't play - stuck cursor as well - nor would Amazon Prime video, web or app; same behavior now in QuickTime Player and "Music" fka iTunes.
It appeared today once but not twice, and I opened both my last Cubase work and the new one where this became serious numerous times since. I had come to blame VE Pro because a correlation experiencing the phenomena was very strong; ie., only twice after totally rebuilding the project where 'the device was removed' began was I able to work with it, and with each occurrence the next launch was instant death. Cubase projects with no VE Pro consistently worked.


So I was actually kind of hoping Sonoma would de facto be a fix of a bug.

Post

jancivil wrote: Tue Sep 26, 2023 6:21 am Well, the issue that had me reaching like that was entirely audio, .............
So I was actually kind of hoping Sonoma would de facto be a fix of a bug.
Well damn? that's not a good sign, seems Apple might be breaking some "priority" settings in their OS, and that's causing strange things in audio. It's not the same bug, but the idea that it would be much much worse for me in a browser VS a DAW made me think it might have something to do with that, and this "gaming" priority thing they're touting in Sonoma.
With macOS Sonoma, Apple has a new feature called Game Mode, which kicks in automatically when the user launches a game and gives it top CPU and GPU priority to maximize the game's performance. It also improves connectivity with wireless devices, so items such as controllers and AirPods have less latency.
That makes me think that it might be possible that Game Mode also benefits DAWs, video editors etc. but in the process Apple might be screwing some things up. :shrug:

Post

I've been testing Sonoma since the initial release candidate came out. So far, I've found no issues moving from Ventura. Doesn't seem to be anything new in Sonoma that would screw around with plugins or change the audio APIs. I kind of assumed that this would be the case when Rogue Amoeba had officially working betas of all their audio routing stuff with official Sonoma support, very early in the beta cycle. That hasn't happened the last few macOS releases.

Post

I was wondering if Game Mode has any benefit to the DAW way o' life.
I was looking at software updates around 10 Pacific time this morning, but apparently what I did already changed to the actual release, there is no update to be had here anyway.

Post

It doesn't really look like there are many really radical changes in Sonoma - it seems more about iOS/MacOs integration and interface consistency, so maybe updating wouldn't be that big a problem in terms of potentially breaking stuff?

Post

Looks like it is available now anyway

Post Reply

Return to “Instruments”