MacBook Pro Music Studio Migration

[Sekops]

Hey legends,

I'm picking up a new M4 Max MacBook Pro next week, which comes with Sequoia. My current M1 Max MacBook Pro is running Ventura. My main DAW is fully supported on Sequoia and so far, largely anecdotal evidence seems to indicate this is one of the less impactful upgrades for producers, considering plugin support.

I'm weighing up the choice of either:

1) Updating the M1 to Sequoia, then using Migration assistant to handle to Migration to the M4, which has lots of benefits in minimising setup time. M1 is pretty loaded with software for DJing, Music Production, coding, python / pip dependencies, home brew etc. Big benefit seems to consistency and maintaining all software configurations over the last 3 years.

2) Clean install on the new M4. I have all my music production install files on a portable SSD. I'm less concerned about plugins, which, in the main can just be copied across, but there's quite a few exceptions that install native software too and deleting those / not having access to those can break things. Then plugin presets will have to be migrated. Benefits seem to be minimising SSD utilisation and reducing software complexity to minimise problems. Perhaps!

I can deal with the downtime if I have to, just prefer not to. Just depends home much benefit there is from a clean install vs migration.

I'll be selling the M1 asap to recoup as much as possible towards the cost of the M4, so ideally won't have too much time where I still have both machines available.

I can backup the M1 with Time Machine and try and keep that image indefinitely, so if I go ahead with a new install and it's just too painful, I believe I can still using Migration Assistant from the Time Machine backup?

So, keen to hear from people that have gone through this recently to learn from your wisdom and minimise the pain!

One aspect I'm particularly unclear about is plugin licence activations. Some plugins are single machine only, most are more. Some are iLok. What's the best steps to ensure I don't inadvertently use up an activation and it can be considered a migration?

Thanks

[uOpt]

Yes, the route through TM backup and then restoring is the way to go. Better than machine-to-machine with a TB cable.

I would start with restoring from the backup disk, not with a fresh install.

I'm not sure you even have to update the M1 first. The OS is fetched from Apple.com even if you migrate. But I'd update just to be sure.

[Funky40]

I have same ahead !

I'm not sure you even have to update the M1 first. The OS is fetched from Apple.com even if you migrate. But I'd update just to be sure.

That´s the question ?
I´d prefer not to update my old system first.
With hundreds of plugins installed i´d like to avoid a fresh install anyway.

One aspect I'm particularly unclear about is plugin licence activations. Some plugins are single machine only, most are more. Some are iLok. What's the best steps to ensure I don't inadvertently use up an activation and it can be considered a migration?
Thanks

From what i can tell there is no plugin activating itself on itself. I´ve not seen that ever happen.

for I-lok, the best way is to have all your licences on the Ilok USB stick !
if you have some or all (I-loks) on your computer, "then" you ***HAVE*** to deactivate those licenses from your old machine in question.
Stumbling block here: selling the old mac without doing that.
You have to have your old mac around for the deactivation process !


The real "problem" are all those plugins who DO require a deactivation from within the plugin, from within your mac in question. Or from within a specific management SW, but handled from within the machine in question. These are the problem. For example the Serato sample player. Sylenth1 i guess, and several more. One should have notes in that regard

From there: a quick sell of the old machine is not exactly what i would recommend.
2nd hand prices are anyway at the time short past the new releases the worst.

a plugin that has not been activated on the new machine will just tell you !
again: the real point is the deactivation process.
and here: those plugins who require to do so from your old mac.

Many many plugins do handle their activation/deactivation process in the meantime from within the useraccount on that specific page. These can be handled from any computer. you just need to remember the name of all your PCs .

some have license keys. these should be straight forward.

vs. ilok and others, just check now !

[uOpt]

You can always make one backup of the M1 before the update, in case you want to take the M1 back, and another one after the update, for migration of the M4.

Or you can just migrate from the pre-update backup and see what happens. You don't lose anything except a bit of time if it doesn't do.

[keyman_sam]

Migration assistant has never worked for me. I wish it did. The last time I had to fully install everything from scratch. That was intel to m1 though.

Maybe m1 to m4 you’ll have better luck.

[Sekops]

Some good guidance here, thanks, particularly about some plugins needing to be de-activated natively before I sell the M1. I had no idea about that. Sylenth1 (although you can also de-activate from the Customer Area on their website). Serato Sample seems to allow this in their web console, now checking for more, wondering if there's a good source for that?

So am leaning towards these steps, but welcome any suggestions:

1) Timemachine Backup of M1 on Ventura
2) Upgrade M1 to Sequioa as recommended by Apple before using Migration Assistant
3) Timemachine Backup of M1 on Sequioa
4) De-activate all iLok licences locked to M1
5) Attempt Migration Assistant direct M1 <> M4 connected via Thunderbolt 4 (quicker than Wi-Fi or external SSD)

[zvenx]

...

I'm not sure you even have to update the M1 first. The OS is fetched from Apple.com even if you migrate. But I'd update just to be sure.

Unless something has changed in the last few weeks, they don't have to.
rsp

[Sekops]

It's recommended to update the machine being transferred: https://support.apple.com/en-au/102613

How critical is it? No idea!

[zvenx]

Interesting.. I dont' think I ever did that but can't hurt of course.
rsp

[Sekops]

Came across this list of plugins relating to the deactivation process.

https://vi-control.net/community/thread ... ter.73806/

Fabfilter seems to be another one. Can't find a de-activate option on their website, but can be De-Authorised from the Help Menu. Wonder if Tech Support can do that too?

[Funky40]

Sylenth1 (although you can also de-activate from the Customer Area on their website). Serato Sample seems to allow this in their web console,

Great ! things have changed. Or i was not aware. Thanks

1) Timemachine Backup of M1 on Ventura
2) Upgrade M1 to Sequoia as recommended by Apple before using Migration Assistant
3) Timemachine Backup of M1 on Sequoia

Ok, i´ll follow up on that too, then.
Not interested to do a fresh install right now. while i should

i run btw. a own thread for the plugin deactivation listing in this subforum.
i´ll update it with the VI-control link

viewtopic.php?t=615785

[uOpt]

5) Attempt Migration Assistant direct M1 <> M4 connected via Thunderbolt 4 (quicker than Wi-Fi or external SSD)

I had some problems with Thunderbolt cable migrations. Don't remember the details.

Switched to harddrive from backup and that works for me. I also don't think it is much slower.

[BONES]

Interesting aside - the base model M4 Max MB Pro costs more than the last three laptops I've purchased for music production and motion graphics work, combined.

[Sekops]

Yeah, it's got to stupid levels of pricing. I'm all in with production; it's my primary hobby, so don't mind spending on it, but the price of the M4 Macbook Pro Max 64GB / 4TB / Nano Display was let's just say a little extravagant. I don't care. It's worth it to me.

[revvy]

Congrats on your new MBP.

My own M1 MBP is still such a great laptop.

And no need to justify your purchase to bones, 70 years old but still trolling Mac threads for his idea of fun.