Is this the right decision for everybody? Not necessarily: the apps and plugins you use might not be as happy working under Rosetta as the ones I use, but the mission-critical ones for me (Intel-only Stutter Edit 1 for live shows!!!) seem to be just fine. I found the techniques in this video very helpful in tracking down outdated software on the new mac: I've stripped out all the cruft I can find on my system: all the 32bit apps/plugins etc are gone gone gone. Even my most demanding showload, which also has Live triggering Full HD video clips in Modul8 using MIDI sent from Live to Modul8 via the IAC Bus. I've thrown my most mission-critical existing projects at it - the live showloads for three different artists - and it all feels rock-solid.Ĭoming from a 2015 RMBP the M1 Max is just eating everything up with headroom to spare in all departments.
I've been keeping an eye in Activity Monitor for the CPU hit introduced by the Rosetta AUHostingCompatibilityService, and it's negligible for my needs. I'm seeing absolutely no problems running Live Beta 11.1 in M1-native mode and having the occasional plugin get translated by Rosetta on-the-fly.
After migration, I updated my apps and plugins to Apple Sillicon-native versions where possible.Īnd here's the thing.
and I have to say I'm blown away! As expected, I lost a bunch of 32bit apps and plugins (this is a macOS issue, rather than an M1 issue - 32bit support got dropped after Mojave).
Ableton live m1 pro install#
So the M1 Max machine arrived, and I thought I'd try out a Migration Assistant with the intention of seeing what worked / what didn't, with the idea that I can always go do a clean install if things were too horrendous.
0 kommentar(er)
