Mac OS update query

[snerkler]

I'm currently running OSX Monterey on an M1 Max Macbook Pro and am considering updating to Sonoma due to the latest Lightroom and Photoshop updates requiring MAc OS 13.4 or higher, however I'm also concerned that some of my plugins for Logic Pro X might not be compatible as some are no longer being supported by the developer.

If I update and find that some plugins aren't compatible would reinstalling my computer from a Time Machine backup allow my to go back to Monterey or would it not allow me to do this?

Alternatively, if Sonoma caused issues with Logic plugins could I run Logic in Rosetta or would they still not be compatible regardless of whether I ran Logic native or via Rosetta with Sonoma?

Any help/advice would be appreciated.

 

[gilby101]

If I update and find that some plugins aren't compatible would reinstalling my computer from a Time Machine backup allow my to go back to Monterey or would it not allow me to do this?

Yes. But make sure that Sonoma never mounts the old TM - i.e. keep it disconnected.

 

[zevrix]

Alternatively, if Sonoma caused issues with Logic plugins could I run Logic in Rosetta or would they still not be compatible regardless of whether I ran Logic native or via Rosetta with Sonoma?

You already run them on M1 (natively, I assume). So if you have any issues with them on Sonoma then it doesn't look like it will be related to native Silicon compatibility anyway. So Rosetta probably won't make a difference. But you won't know until you try.

 

[snerkler]

Yes. But make sure that Sonoma never mounts the old TM - i.e. keep it disconnected.

Great thanks, however how do I reinstall via TM if I can’t mount it whilst Sonoma’s installed? I assume Sonoma won’t ‘interfere’ whilst in recovery mode?

You already run them on M1 (natively, I assume). So if you have any issues with them on Sonoma then it doesn't look like it will be related to native Silicon compatibility anyway. So Rosetta probably won't make a difference. But you won't know until you try.

Ok thanks for the info.

 

[Fishrrman]

"Going back" from a newer to an older version of the OS is "a job".
You don't want to do this unless there's no other way.

I have a better solution for you:
Spend $20 and buy a 2.5" SATA SSD, 128gb (yes, I realize it's small, buy a 256gb if you wish).
Then, buy a USB3 enclosure like this:
https://www.amazon.com/ORICO-External-Enclosure-Installation-Supports/dp/B01MYTZW5R/ref=sr_1_5?crid=5PV3JJBCKDBJ&keywords=ssd+enclosure+SATA+usb3.1+gen2&qid=1700148863&sprefix=ssd+enclosure+sata+usb3.1+gen2,aps,55&sr=8-5&th=1

Put the SSD into the enclosure, format it using disk utility to APFS, GUID partition format.

Now install a copy of Sonoma onto the EXTERNAL SSD.
Install the new software onto this.

Now you have an external boot drive running Sonoma so that you can experiment with your newer (and older) software, to see what works, and what doesn't.

And during this time, your internal drive will remain "untouched" -- so that if things don't work with Sonoma, you don't have to "fight your way back".

I've used this method to experiment with new OS releases BEFORE I "commit myself to them" for many years now...

 

[snerkler]

"Going back" from a newer to an older version of the OS is "a job".
You don't want to do this unless there's no other way.

I have a better solution for you:
Spend $20 and buy a 2.5" SATA SSD, 128gb (yes, I realize it's small, buy a 256gb if you wish).
Then, buy a USB3 enclosure like this:
https://www.amazon.com/ORICO-External-Enclosure-Installation-Supports/dp/B01MYTZW5R/ref=sr_1_5?crid=5PV3JJBCKDBJ&keywords=ssd+enclosure+SATA+usb3.1+gen2&qid=1700148863&sprefix=ssd+enclosure+sata+usb3.1+gen2,aps,55&sr=8-5&th=1

Put the SSD into the enclosure, format it using disk utility to APFS, GUID partition format.

Now install a copy of Sonoma onto the EXTERNAL SSD.
Install the new software onto this.

Now you have an external boot drive running Sonoma so that you can experiment with your newer (and older) software, to see what works, and what doesn't.

And during this time, your internal drive will remain "untouched" -- so that if things don't work with Sonoma, you don't have to "fight your way back".

I've used this method to experiment with new OS releases BEFORE I "commit myself to them" for many years now...

Thanks for the heads up, why is it so difficult to go back if you reninstal via TM?

 

[Fishrrman]

"why is it so difficult to go back if you reninstal via TM?"

I've never used time machine, not once, ever. So my advice below may be wrong, and I welcome correction by others.

I don't think tm will let you go from "newer" back to "older" (OS's). It will "object".
Again, I could be wrong.

A possible solution might be to create a CLONED backup using either CarbonCopyCloner or SuperDuper. These are mountable right in the finder. They may work with setup assistant (after installing a fresh copy of the old OS), or not.

From years of observation, it seems like folks who work with audio can have the most difficulties when moving from an older OS to a brand-new one (plugins don't work, etc.).

So if you want, give the upgrade a try, but realize there could be ... "complications".

Again, unless you want to end up in a situation in which you start pulling hair out, I recommend the "alternate way" I outlined in reply 2 above...

 

[snerkler]

"why is it so difficult to go back if you reninstal via TM?"

I've never used time machine, not once, ever. So my advice below may be wrong, and I welcome correction by others.

I don't think tm will let you go from "newer" back to "older" (OS's). It will "object".
Again, I could be wrong.

A possible solution might be to create a CLONED backup using either CarbonCopyCloner or SuperDuper. These are mountable right in the finder. They may work with setup assistant (after installing a fresh copy of the old OS), or not.

From years of observation, it seems like folks who work with audio can have the most difficulties when moving from an older OS to a brand-new one (plugins don't work, etc.).

So if you want, give the upgrade a try, but realize there could be ... "complications".

Again, unless you want to end up in a situation in which you start pulling hair out, I recommend the "alternate way" I outlined in reply 2 above...

Thanks. I've gone back OS's before, but never with a Silicon Mac.

 

[Weaselboy]

Thanks for the heads up, why is it so difficult to go back if you reninstal via TM?

TM no longer backs up or stores the OS on the backup drive. so going back would not be an easy task.

It used to be the case where you could install a new OS version on Dec. 5, then if it did not work out, you could option key boot to the TM and select a restore point from Dec. 4, and the old OS and all your data would be placed back in the disk. That capability no longer exists.

 

[snerkler]

TM no longer backs up or stores the OS on the backup drive. so going back would not be an easy task.

It used to be the case where you could install a new OS version on Dec. 5, then if it did not work out, you could option key boot to the TM and select a restore point from Dec. 4, and the old OS and all your data would be placed back in the disk. That capability no longer exists.

Interesting, thanks.