macOS Sonoma compatibilty list

[machinesworking]

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

It's OK you don't have to move goalposts, it's fine being wrong about simple things. Here's a thread right her on KVR about exactly what I was talking about. An OS level bug in Ventura that affects audio people directly. You don't have to prove anything to anyone.

If you're interested and not just wanting a debate, the blogpost is an enlightening read.

viewtopic.php?t=602383

[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

It's OK you don't have to move goalposts, it's fine being wrong about simple things. Here's a thread right her on KVR about exactly what I was talking about. An OS level bug in Ventura that affects audio people directly. You don't have to prove anything to anyone.

If you're interested and not just wanting a debate, the blogpost is an enlightening read.

viewtopic.php?t=602383

how am i 'moving goalposts'?? anyway, i still stand by my posts. but please feel free to try again (and i will let you get in the last word, as that seems important.)

[chagzuki]

Can anyone confirm that R4 and Phoenixverb work in Sonoma?

[jancivil]

anyway, i still stand by my posts. but please feel free to try again (and i will let you get in the last word, as that seems important.)

Well, the thing I noticed was saying machinesworking's issue was "singular".
Your use of the word is in error, unless you could know that the individual is the single person using the operating system to have problems with audio in the world.
Do as you like but standing by that will be bad form.

Anyway, Ventura I have to suppose added something* at version 13.6 which stopped the show cold here.

From the BlueCat blog mentioned:
While [it] sounds like a good idea to have at last some real-time features at the OS Ievel to properly prioritize audio processing, their implementation is definitely not ideal and is limited to Core Audio applications and Audio Units, leaving other plugin formats out in the cold! Moreover, it is a bit perplexing to see *Apple adding layers of complexity to their operating system while grappling with scheduler issues for Apple Silicon processors…

I could only conclude that Cubase and the plugin Vienna Ensemble Pro.vst3 could not play in the Mac OS13.6 sandbox here. Cubase is def. not Core Audio (is ASIO and wrapped) and VST3 is def. not Audio Units. {VEP worked until I'd connect it as plugin to Cubase 12} Since the regular release of OS14 Sonoma I was at least able to proceed with the project that was dead in the water because Cubase believed something that wasn't even possibly true, and I had no audio.

If someone told me I had "a singular issue", ie., basically to shut up I'd perhaps have been less gentle than what I saw here. It's at best a remote possibility it will have been only me, and as I reported it in these pages I saw other issues with audio behavior reported as well.

[machinesworking]

anyway, i still stand by my posts. but please feel free to try again (and i will let you get in the last word, as that seems important.)

Well, the thing I noticed was saying machinesworking's issue was "singular".
Your use of the word is in error, unless you could know that the individual is the single person using the operating system to have problems with audio in the world.
Do as you like but standing by that will be bad form.

Anyway, Ventura I have to suppose added something* at version 13.6 which stopped the show cold here.

From the BlueCat blog mentioned:
While [it] sounds like a good idea to have at last some real-time features at the OS Ievel to properly prioritize audio processing, their implementation is definitely not ideal and is limited to Core Audio applications and Audio Units, leaving other plugin formats out in the cold! Moreover, it is a bit perplexing to see *Apple adding layers of complexity to their operating system while grappling with scheduler issues for Apple Silicon processors…

I could only conclude that Cubase and the plugin Vienna Ensemble Pro.vst3 could not play in the Mac OS13.6 sandbox here. Cubase is def. not Core Audio (is ASIO and wrapped) and VST3 is def. not Audio Units. {VEP worked until I'd connect it as plugin to Cubase 12} Since the regular release of OS14 Sonoma I was at least able to proceed with the project that was dead in the water because Cubase believed something that wasn't even possibly true, and I had no audio.

If someone told me I had "a singular issue", ie., basically to shut up I'd perhaps have been less gentle than what I saw here. It's at best a remote possibility it will have been only me, and as I reported it in these pages I saw other issues with audio behavior reported as well.

I gave up responding to him, but yeah, this is one of the few times I've seen an OS level error that affected audio people directly this hard, and it's probably the biggest one. The other two times I can think of were when AU first came out and Apple tweaked the code to work with Logic, breaking it for any other host, and an aggressive power down mobile chip that Intel put out Apple used in their macbook pros, causing glitches in sample libraries when first played. Anyway, it's being sorted and IMO Sonoma is one of the few OS updates I will instal on the first day, considering how relevant multi core issues are to audio people.

[fisherKing]

Well, the thing I noticed was saying machinesworking's issue was "singular".
Your use of the word is in error, unless you could know that the individual is the single person using the operating system to have problems with audio in the world.
Do as you like but standing by that will be bad form.

i said this: "it's worth remembering that our singular experiences don't speak for everyone... unless, of course, everyone is experiencing those issues."

i simply (i thought) implied that individuals describing their experience (and certainly other individuals might have similar experiences) doesn't speak for everyone. as far as i can see, it doesn't. meanwhile, will move on to the next thread, as machinesworking and i are getting nowhere; so it goes.

[chagzuki]

I was having plugin instability problems in Logic (and Ventura) to the point where it was impossible to get anything done, so I had to try updating to Sonoma. Initial impressions are that those issues are gone, and I can confirm that the old Exponential Audio plugins continue to work as AUs and VSTs. No issues so far with other plugins. Sonible seem to work, though despite still being activated they seem to want to take me through the initial welcome guide as if they're newly installed.

The OS does feel a bit more responsive, though for some reason Logic's scrolling and zooming seem a bit blurry, as though the refresh rate is lowered. Odd.

[sQeetz]

I always just update right away when an update is available. Never had any issues... guess I'm just lucky

[nordickvr]

...
Sonible seem to work, though despite still being activated they seem to want to take me through the initial welcome guide as if they're newly installed.
...

Contacted them and they replied that the next update will fix it.

[machinesworking]

I always just update right away when an update is available. Never had any issues... guess I'm just lucky

How many plugins do you own? To me the most common issue with Mac OS updates is some plugin or another gets broken.

Yes, developers are probably doing things Apple didn't approve of to get their plugin working and some update exposes it, but it doesn't change the fact that updates seem to break plugins more than anything else here. It's always a good idea to upgrade your AU/VSTs before upgrading the OS.

Currently the only plugin that has some issues for me is the MPC VSTi, (spikes in some DAWs), and considering they haven't touched it in forever, and it's still not VSTi3 compatible, I'm not surprised.

[sQeetz]

I always just update right away when an update is available. Never had any issues... guess I'm just lucky

How many plugins do you own? To me the most common issue with Mac OS updates is some plugin or another gets broken.

About 300 third party plugins... I keep them updated all the time, though....

[sqigls]

I just upgraded from Ventura to Sonoma. I've been on Ventura (from Monterey) for about 2 weeks.
Here's a list of the instruments i have tested briefly.
By "tested" i mean I've loaded the instrument, opened the GUI, triggered it with MIDI notes and sound has emanated from it's codey wodey core. Except for the MIDI type plugins such as Playbeat, Chord Potion etc, which don't make sounds. They loaded none the less.
The only plugin which doesn't work in either Cubase or Live, didn't work on Monterey or Ventura either - is miniSyn-X.

I'll eventually test the effects too, but it's probably safe to say if all these VST2 and VST3 instruments are working then we might make an ass out of "U" and "umption".
All good so far. I'm running Cubase and Live
2021 Macbook Pro, 16GBG RAM

Sonoma Instruments.jpg

[syntonica]

The only plugin which doesn't work in either Cubase or Live, didn't work on Monterey or Ventura either - is miniSyn-X.

I've always found the Xils demos to be on the dodgy side on Mac and their support didn't exactly fill me with confidence. I'm not surprised to hear of issues cropping up. It's probably been a good 5 years since I reported a GUI issue inn Oxium and it was still there last I checked.

[sqigls]

miniSyn-X has crashed every DAW i've used on MacOS since Mojave, both the vst2 and 3
I emailed support, i guess they'll get around to it. one year
LeMasque still loads in Sonoma

[machinesworking]

About 300 third party plugins... I keep them updated all the time, though....

Same, but some like the mentioned MPC have not gotten the updates they need yet for Sonoma.