latest sonoma update (14.3.1) causing issues in Logic

[fisherking]

Yes, unfortunately I wish it were just a plugin. Went through all the steps with apple (deleted all plugins, reset plist, etc.). Even did a fresh logic install (no plug-ins/no migration) on a brand new machine. I can replicate the issue anytime anywhere. I can even do it at the Apple store on their demo machines using their demo project. If you gave me 2 minutes with your machine I could show you, too. It's a sonoma bug--but fortunately only comes up with certain workflows and doesn't seem to affect audio--most importantly. Apple is "working on it" (slowly).

sorry to hear that, really. with my workflow, everything is fine, and i'm working now and it's going great. perhaps, as a compromise for the moment, change up your workflow a bit. but more importantly, hope it gets sorted soon 👍

 

[gank41]

Yes, unfortunately I wish it were just a plugin. Went through all the steps with apple (deleted all plugins, reset plist, etc.). Even did a fresh logic install (no plug-ins/no migration) on a brand new machine. I can replicate the issue anytime anywhere. I can even do it at the Apple store on their demo machines using their demo project. If you gave me 2 minutes with your machine I could show you, too. It's a sonoma bug--but fortunately only comes up with certain workflows and doesn't seem to affect audio--most importantly. Apple is "working on it" (slowly).

I actually reinstalled macOS just recently, too, and held off on installing any plugins and still had these issues. I guess we wait…
¯\_(ツ)_/¯

 

[Itconnects]

Yes, unfortunately I wish it were just a plugin. Went through all the steps with apple (deleted all plugins, reset plist, etc.). Even did a fresh logic install (no plug-ins/no migration) on a brand new machine. I can replicate the issue anytime anywhere. I can even do it at the Apple store on their demo machines using their demo project. If you gave me 2 minutes with your machine I could show you, too. It's a sonoma bug--but fortunately only comes up with certain workflows and doesn't seem to affect audio--most importantly. Apple is "working on it" (slowly).

Any updates with this on the latest version of Sonoma?

 

[3SQ Machine]

Any updates with this on the latest version of Sonoma?

Thanks for resurrecting this -- updated my M3 Max with one of the recent Sonoma updates, which minimized the issue. Also just upgraded to Sequoia--still OK. Oddly, my M1 Pro running Ventura is STILL "better" as the same project does not tax the CPU/GPU nearly as much (which makes no sense given the performance difference b/w M1 Pro v. M3 Max). But, the choppiness issue in the early versions of Sonoma is greatly reduced.

Apple Engineering never got back to me with a "fix" (or back to me at all) despite multiple calls/e-mails. I even uploaded to them (at their request) a "test" project with the steps illustrated on how to reproduce it. Crickets.

Anyway, TLDR; it's probably safe to upgrade. But I still plan to keep my M1 Pro running Ventura at least until the security updates stop coming.

 

[Itconnects]

Yes, unfortunately I wish it were just a plugin. Went through all the steps with apple (deleted all plugins, reset plist, etc.). Even did a fresh logic install (no plug-ins/no migration) on a brand new machine. I can replicate the issue anytime anywhere. I can even do it at the Apple store on their demo machines using their demo project. If you gave me 2 minutes with your machine I could show you, too. It's a sonoma bug--but fortunately only comes up with certain workflows and doesn't seem to affect audio--most importantly. Apple is "working on it" (slowly).

Oddly, my M1 Pro running Ventura is STILL "better" as the same project does not tax the CPU/GPU nearly as much (which makes no sense given the performance difference b/w M1 Pro v. M3 Max). But, the choppiness issue in the early versions of Sonoma is greatly reduced.

wow, anyway you can give a more recent direct comparison of the same project on Ventura vs Sonoma or sequoia on the M1 machine. Good to know about m3 though. There may be two issues here that was already theorized and tested on YouTube and that is M1's run really well with Logic given the performance cores vs efficiency cores. Second is the Os on the same machine. I don't think Logic is a coding priority for apple when it comes to new computers so I'm not surprised with your machine to machine findings

 

[3SQ Machine]

I'll try to do some screen captures later, but just so you know my M3 Max has 10 performance cores / 4 efficiency cores, so 2 more P cores than the M1 Pro. In an ideal world, I would run Ventura on an M3 Max to "test" whether it's the OS or the chip--but since I'm not doing that, I'll just have to go with what I can measure between the two machines.

I feel comfortable enough with the smoothness now on Sequoia on the M3 Max that I'll be comfortable moving on from Ventura on the M1 Pro in a year when the security updates stop. I'll skip Sonoma altogether, though.