@HARMAN_PKarr, regarding iLok machine activations: It turns out that a critical step, at least in my case, is to deactivate the licenses from your physical iLok dongle first. As soon as I did that, the licenses immediately showed up as activatable to both my computer and the physical iLok.
So it might be that the fact that some people don't see the possibility to activate to the computer right away is not because of some rollout process that takes time, but rather because of some strange behavior on Pace's side that can be fixed by just deactivating all Lexicon licenses, after which the user's iLok account apparently miraculously reflects the machine activation option correctly.
I don't know if you're aware of this, but this should be mentioned in the update announcement and any accompanying instructions.
@plf said: @HARMAN_PKarr, regarding iLok machine activations: It turns out that a critical step, at least in my case, is to deactivate the licenses from your physical iLok dongle first. As soon as I did that, the licenses immediately showed up as activatable to both my computer and the physical iLok.
So it might be that the fact that some people don't see the possibility to activate to the computer right away is not because of some rollout process that takes time, but rather because of some strange behavior on Pace's side that can be fixed by just deactivating all Lexicon licenses, after which the user's iLok account apparently miraculously reflects the machine activation option correctly.
I don't know if you're aware of this, but this should be mentioned in the update announcement and any accompanying instructions.
This is fantastic news! We were able to confirm this on our end.
IF YOUR LICENSE DOES NOT YET SHOW MACHINE AUTHORIZATION, TRY ACTIVATING TO YOUR ILOK USB FIRST
This may not work still for licenses purchased before a certain time. If this doesn't work for you, hang in there.
@plf said: @HARMAN_PKarr, regarding iLok machine activations: It turns out that a critical step, at least in my case, is to deactivate the licenses from your physical iLok dongle first. As soon as I did that, the licenses immediately showed up as activatable to both my computer and the physical iLok.
So it might be that the fact that some people don't see the possibility to activate to the computer right away is not because of some rollout process that takes time, but rather because of some strange behavior on Pace's side that can be fixed by just deactivating all Lexicon licenses, after which the user's iLok account apparently miraculously reflects the machine activation option correctly.
I don't know if you're aware of this, but this should be mentioned in the update announcement and any accompanying instructions.
Hi, the new versions of the plugins are still crashing Logic Pro for me over and over just like the old ones. I can send you a Logic crash report for your new team. What is a good email to send it to?
Hi, the new versions of the plugins are still crashing Logic Pro for me over and over just like the old ones. I can send you a Logic crash report for your new team. What is a good email to send it to?
VST2 has long since been discontinued. Users have been asking for a VST3 version.
If you have both VST2 and VST3 versions installed, the VST3 version should take priority and that's the one the user accesses.
VST2 has not been discontinued across the board, just because Steinberg came up with the VST format does not mean other software/plugin makers are following suit and discontinuing support for it. Could you imagine the nightmare of old projects being brought up for remixes and remasters from years ago to have to redo everything from scratch cause CuBase decided it doesn't want to use VST2 plugins anymore? I think you're making hay unnecessarily here
Sessions containing the VST2 version should automatically migrate to the VST3 version. The user should be able to remove all VST2 versions from the system and have the sessions open with the VST3 version now and continue from there.
I can can guarantee you that most plugin manufacturers do not do this, and their option is the workaround that has been presented here (I've had to do it with Toontrack, Slate, many others). Sure it would be nice but this isn't an industry standard
If you want to continue to use the VST2 version for whatever reason then don't install the VST3 version.
The option to install either/or is in most plugin installers though?
Having VST2 and VST3 versions with different IDs creates an administrative headache for the end-user. Having to open every single instance, save a preset, load the VST3 version, load that preset is frankly an insane and time consuming "workaround". It might be easy if you use the same preset all the time but when you tweak settings in a mix and almost every session is unique then it's a huge amount of extra effort.
Update your ongoing working projects with the VST3, I've done it, many others have too - yes it is time consuming. Oh well, cry or get to work!
Again, please reconsider. As it is now the VST3 version is next to useless unless you're starting fresh.
@eldis1981 said:
VST2 has not been discontinued across the board, just because Steinberg came up with the VST format does not mean other software/plugin makers are following suit and discontinuing support for it. Could you imagine the nightmare of old projects being brought up for remixes and remasters from years ago to have to redo everything from scratch cause CuBase decided it doesn't want to use VST2 plugins anymore? I think you're making hay unnecessarily here
It's worth clarifying that while some hosts still support VST2 plugins, Steinberg has officially ended support for VST2 and has not issued VST2 licenses for quite some time now. So while legacy support exists, new plugin development is generally limited to VST3 going forward — not just because Steinberg says so, but because developers can't legally obtain a VST2 license anymore.
Sessions containing the VST2 version should automatically migrate to the VST3 version. The user should be able to remove all VST2 versions from the system and have the sessions open with the VST3 version now and continue from there.
I can can guarantee you that most plugin manufacturers do not do this, and their option is the workaround that has been presented here (I've had to do it with Toontrack, Slate, many others). Sure it would be nice but this isn't an industry standard
Most of the well known plugin developers — Slate included — implement it successfully. Of course, there are cases where significant internal changes make automatic migration difficult or impossible, but as Flux has demonstrated with their new builds, migration is technically feasible. Given that, it's reasonable to expect developers to prioritize this kind of compatibility.
If you want to continue to use the VST2 version for whatever reason then don't install the VST3 version.
The option to install either/or is in most plugin installers though?
True, although it's important to remember that developers offering VST2 versions now are likely doing so under old agreements. Once those are phased out, we’ll probably see fewer and fewer dual-install options.
Update your ongoing working projects with the VST3, I've done it, many others have too - yes it is time consuming. Oh well, cry or get to work!
I'm not sure about your situation but updating projects can be tedious, especially in larger production environments with multiple workstations where compatibility is key. From a forward-compatibility standpoint, the shift to VST3 is happening across the industry, and ensuring session migration support just seems like the most pragmatic and user-friendly path forward. Hopefully more developers continue to take that seriously.
PCM plugs for AAX have been renamed from PCM Native to Lex so they aren't being auto detected. Here is my example: In my old session there is PCM Native Room that could not be located. I thought that Flux hadn't installed the PCM versions but went to my plugin folder and found that the plugs were installed (to a new location btw) and that the actual plugins are named identically to the older versions but in the Pro Tools plugins menu in tracks it is now called "LexRoom" instead of PCM Native Room.
You can see in the track's top slot an unfound PCM Native Room above the newly instantiated LexRoom which has the same preset when opening the older version in Rosetta.
Comments
THX 👍
@HARMAN_PKarr, regarding iLok machine activations: It turns out that a critical step, at least in my case, is to deactivate the licenses from your physical iLok dongle first. As soon as I did that, the licenses immediately showed up as activatable to both my computer and the physical iLok.
So it might be that the fact that some people don't see the possibility to activate to the computer right away is not because of some rollout process that takes time, but rather because of some strange behavior on Pace's side that can be fixed by just deactivating all Lexicon licenses, after which the user's iLok account apparently miraculously reflects the machine activation option correctly.
I don't know if you're aware of this, but this should be mentioned in the update announcement and any accompanying instructions.
This is fantastic news! We were able to confirm this on our end.
IF YOUR LICENSE DOES NOT YET SHOW MACHINE AUTHORIZATION, TRY ACTIVATING TO YOUR ILOK USB FIRST
This may not work still for licenses purchased before a certain time. If this doesn't work for you, hang in there.
Nope. Did not work for me.
For me too. (activated\deactivated couple times)
Now licenses updated 👍 Thanks
@HARMAN_PKarr
Hi, the new versions of the plugins are still crashing Logic Pro for me over and over just like the old ones. I can send you a Logic crash report for your new team. What is a good email to send it to?
Best
Messaging you!
VST2 has not been discontinued across the board, just because Steinberg came up with the VST format does not mean other software/plugin makers are following suit and discontinuing support for it. Could you imagine the nightmare of old projects being brought up for remixes and remasters from years ago to have to redo everything from scratch cause CuBase decided it doesn't want to use VST2 plugins anymore? I think you're making hay unnecessarily here
I can can guarantee you that most plugin manufacturers do not do this, and their option is the workaround that has been presented here (I've had to do it with Toontrack, Slate, many others). Sure it would be nice but this isn't an industry standard
The option to install either/or is in most plugin installers though?
Update your ongoing working projects with the VST3, I've done it, many others have too - yes it is time consuming. Oh well, cry or get to work!
🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄
It's worth clarifying that while some hosts still support VST2 plugins, Steinberg has officially ended support for VST2 and has not issued VST2 licenses for quite some time now. So while legacy support exists, new plugin development is generally limited to VST3 going forward — not just because Steinberg says so, but because developers can't legally obtain a VST2 license anymore.
Most of the well known plugin developers — Slate included — implement it successfully. Of course, there are cases where significant internal changes make automatic migration difficult or impossible, but as Flux has demonstrated with their new builds, migration is technically feasible. Given that, it's reasonable to expect developers to prioritize this kind of compatibility.
True, although it's important to remember that developers offering VST2 versions now are likely doing so under old agreements. Once those are phased out, we’ll probably see fewer and fewer dual-install options.
I'm not sure about your situation but updating projects can be tedious, especially in larger production environments with multiple workstations where compatibility is key. From a forward-compatibility standpoint, the shift to VST3 is happening across the industry, and ensuring session migration support just seems like the most pragmatic and user-friendly path forward. Hopefully more developers continue to take that seriously.
PCM plugs for AAX have been renamed from PCM Native to Lex so they aren't being auto detected. Here is my example: In my old session there is PCM Native Room that could not be located. I thought that Flux hadn't installed the PCM versions but went to my plugin folder and found that the plugs were installed (to a new location btw) and that the actual plugins are named identically to the older versions but in the Pro Tools plugins menu in tracks it is now called "LexRoom" instead of PCM Native Room.
You can see in the track's top slot an unfound PCM Native Room above the newly instantiated LexRoom which has the same preset when opening the older version in Rosetta.