Switching between PT rosetta and native

[Ben Jenssen]

I'm getting closer to the point where I'll use my reinstatement code and get my perpetual license to PT2022.12. Especially now that SSL has released an ARM AXX update to the channelstrip and bus compressor.

I'm wondering if it's actually practical to switch between the two modes - staying on native and switching back to rosetta to access non-native plugins - and back again.

Does it cause any problems, like can they share prefs, can they use the same plugin folder content etc? Does it work or is it convoluted?

Thanks.

[its2loud]

It just works. Nothing to worry about regarding plug-in presets, prefs, templates, track presets, etc.

Whether you work under Rosetta or Natively will solely depend on you plug-in compatibility.

Switching back and forth at this point isn’t really practical for many. It’s time consuming and cumbersome to keep opening and closing the application to work in different modes. Obviously, your workflow may differ from others and if you mostly use features and plugs that are available natively then that can be your go to.

2022.12 work by default under Rosetta. If you want to open Pro Tools natively you need to open the application’s INFO (Command+I) window and uncheck the box for “Open Using Rosetta”

[Ben Jenssen]

Thanks man!

I'll be updating tonight.

I did try it when it came out, but just for a couple of days, so I know it works, good for a beta at least.

[its2loud]

Just keep in mind of what doesn’t work with the Beta…in case you use any of these

What doesn’t work in the public beta version?

AIR plugins and instruments currently bundled with Pro Tools
Not all third-party plugins are supported yet—see here for the supported list
Cloud Collaboration and Projects
ICON, C24, and Command 8 control surfaces will not be supported
X-Form Audio Suite and algorithm in Elastic Audio
ReWire support
MP3 Export (Bounce and Export Clips as Files)
AAC Import
Score Editor
Chord Extraction
Full qualification on all systems/configurations

[Ben Jenssen]

Originally Posted by its2loud

Just keep in mind of what doesn’t work with the Beta…in case you use any of these

Thank you, yes I'm aware of most of this, and none of those are very important to me.

[Gemylon]

Originally Posted by its2loud

Just keep in mind of what doesn’t work with the Beta…in case you use any of these

What doesn’t work in the public beta version?

....
ICON, C24, and Command 8 control surfaces will not be supported

Not by AVID (probably),
but they are all working fine using V-Control Pro.

[redmount]

Hello,
"slightly" off topic and maybe stupid question but is it ok to open PTools native while using other standalone apps via Rosetta 2 ?

The OS can manage native and non native apps flawlessly ?

Just want to make sure that Rosetta is a "tool" you can assign individually without considering other apps

[Darryl Ramm]

Originally Posted by redmount

Hello,
"slightly" off topic and maybe stupid question but is it ok to open PTools native while using other standalone apps via Rosetta 2 ?

The OS can manage native and non native apps flawlessly ?

Just want to make sure that Rosetta is a "tool" you can assign individually without considering other apps

Nothing to worry about here. None of this is really any different than running multiple applications at the same time without Rosetta. With maybe an extreme corner case that lots of things running under Rosetta might use a little more CPU and a little more memory and therefore load the system a little more, I doubt you'll even notice.

[redmount]

Merci

[Eric Lambert]

Originally Posted by redmount

Hello,
"slightly" off topic and maybe stupid question but is it ok to open PTools native while using other standalone apps via Rosetta 2 ?

The OS can manage native and non native apps flawlessly ?

Just want to make sure that Rosetta is a "tool" you can assign individually without considering other apps

I think I understand what you might have been thinking here and it's not a stupid question at all. With some tech, opening an interpreter forces the whole machine to slow down because data is being siphoned through that lesser/slower protocol, creating a bottleneck for every function. As Darryl said, Rosetta isn't that kind of thing.