Best Of

@HARMAN_PKarr said:
Interesting! Are you able to open the "PCMNtvRM" in the Rosetta enabled session? If so, you can click the algorithm name (the "Room" in the top left) to show the plug-in version numbers. I wonder if this version is just that old. How old is this session file? The plug-ins used to come as separate licenses (so you have one iLok license PER ALGORITHM), and the installers were separate as well instead of as the "bundle". There's likely not a workaround, unfortunately.

Yes the plugin opens properly in Rosetta mode. Version is 1.3.10; the latest Intel version from December 2021 which is newer than the session where this happened which was created in 2012 but modified over the years. I wasn't asking about a workaround just letting you know. This means all Pro Tools users will have to use Rosetta to update sessions using the PCM bundle rather than easily opening in Native mode where there should be a direct correlation. This is a bug that should be addressed. When Altiverb and other plugins updated for Apple Silicon Native this does not happen. It is probably a simple fix. Like I said the plugins themselves are named identically it is only in the Pro Tools plugin menus and track instantiations.

@BassGuru222 said:
So excited! Thanks for the update. I agree that the VST3 version ID should match the old versions so your projects open seamlessly. I for one only have a few projects so far with the old version as I only purchased the bundle a few months ago. Still, if I had tons of older projects I'd like to open, that would be a pain.

Let's be honest though... Who REALLY goes back to hundreds of OLD projects and remixes them?

What's stopping you (us) from keeping the old versions in a backup folder and just use them when you need to load an older project? Maybe I'm missing something.

Pretty easy to answer that one. It's not necessarily about "remixing" a project but when a label requests something from a session potentially years down the line, you'd better have the ability to open it and make it work.

Again, since VST2 has been discontinued and VST3 is the path forward, it's a no-brainer to expect it to do what it should do and migrate your session settings over to the VST3 version. DAWs won't support VST2 for much longer and it's not something I'd personally want to deal with having to time capsule the system (OS/hardware/DAW/plugins etc) for a developer that missed the obvious.