App launching PT Native vs. PT Rosetta?

[Ben Jenssen]

Originally Posted by Darryl Ramm

Nice.
macOS is just not going to allows both to run concurrently. Trust me... (Mac enters space-time wormhole and the universe is destroyed...).

So if the os will not allow it, I guess my procedure is even more viable; you can't inadvertently run both simultaneously.

[Darryl Ramm]

Originally Posted by Ben Jenssen

So if the os will not allow it, I guess my procedure is even more viable; you can't inadvertently run both simultaneously.

Yep. But any scenario where you can actually launch Pro Tools is unlikely to have any problems with concurrent versions running e.g. if you install multiple different versions of Pro Tools you can't run them concurrently... that would cause total havoc, corrupt the heck out of prefs, etc.

The mechanism is actually Pro Tools checking another instance is not already running... and that will work whether apps are using Rosetta or now... lots of other things would break if this just casually did not work if one app instance was in Rosetta and the other not. It would take specific coding that allowed that scenario to happen, and nobody's going to do that... and based on other things I see Pro Tools seems to have a pretty paranoid checking in place (good).

I'm not going to speculate on things like Avid Link. I don't trust it and never run it.

There might well be undocumented developer ways to run multiple Pro Tools version concurrently for testing/comparison (e.g. with different root directories for prefs and plugins) but Avid's not going to let mere mortals do stuff like that. We had multiple protections we could undo in VMware products with undocumented flags that were super helpful for QA testing.

[Ben Jenssen]

Many thanks for the clarifications, Darryl. thumbsup

[Eric Lambert]

Originally Posted by Ben Jenssen

I bypassed it by right-clicking and selecting 'Open', and it launched PT in Rosetta mode

Interesting. Do you need to right-click-open each time you go to launch PT?

[Darryl Ramm]

No.

[moogboy100]

Co Install 2023.3 with 2022.12.

use 2023.3 in native mode, since it's more functional than the public beta

use 20222.12 in Rosetta mode.

Job done.

[Eric Lambert]

Originally Posted by Darryl Ramm

No.

So the error only pops up that initial time then. Good.

It's an interesting approach. My brain is saying that something about this isn't ideal, but as I sit here typing I can't think of what it might be. I'll give it a go.

I do wish I could more easily (automatically) toggle that Get Info "Rosetta" dialogue box. I'd just feel better about it.

[its2loud]

There’s absolutely nothing wrong with installing two versions of pro tools on the same machine. Both will work fine and won’t interfere with each other. Enjoy the flexibility of having both.

There have been time when I’ve had more than two versions on my machine.

[Ben Jenssen]

Originally Posted by its2loud

There’s absolutely nothing wrong with installing two versions of pro tools on the same machine. Both will work fine and won’t interfere with each other. Enjoy the flexibility of having both.

There have been time when I’ve had more than two versions on my machine.

This is not what this thread is about.

[Eric Lambert]

Originally Posted by Ben Jenssen

This is not what this thread is about.

He might be referring to the duplicated version of ProTools (as you'd suggested) as a different version, even if they're both 2023.3, meaning that we're all talking about the same thing.