Lexicon Software Updates 2025 - Mac support / VST3 / iLok License Updates (DOWNLOAD HERE!!!)
HARMAN_PKarr
Posts: 44
Hello everyone!
I come finally with the updates you all have been waiting for. New updates for all Lexicon plug-ins are now available and downloaded through the Flux::Center app. These updates include support for Apple silicon natively and up to the most recent OS version Sequoia. VST3 versions now included on Windows and MacOS. iLok license updates are available to authorize licenses to machine. Make sure iLok License Manager is updated to the most recent version. The rollout of this license update may take time to affect all existing licenses, so please be patient with this feature. If it is not available for you yet, sign out and then back in to iLok License Manager and see if it resolves. If not, they will get to you eventually, I promise.
View our video highlights! - 
https://www.youtube.com/watch?v=CB63HYFQy14
Download Flux::Center here! - https://www.flux.audio/download/
*you will need a Flux store account to access your plug-ins. Once you have created a Flux store account, look for the option under your account to associate your iLok user ID with your Flux account. Once done, your plug-ins should show in the Flux::Center app under My Products.
This thread will remain open for questions. Please bear with me as questions come in. You are welcome to reach out to tech support via https://help.harmanpro.com, and those e-mails will be distributed between me and my other two colleagues here to assist.
We greatly appreciate the patience that you all have had with us throughout this time of adjustment and sticking it out.
Comments
All these years waiting and now this?
"*you will need a Flux store account to access your plug-ins. "
I had it! As if it was not enough trouble to be forced to use iLok!
Understandable, but Flux::Center will at least keep your plug-ins updated. It's just for installing them, then you're free to never think about it again... until the next Mac updates roll around.
FINALLY FINALLY
Thanks for finally releasing however sessions which used the old VST2 version do not open with the VST3 version now. It's seeing it as a separate product instead of having the same ID so it replaces the old versions automatically.
Please tell me the current behaviour is not intentional?!
After some more testing it seems the new VST2 versions replace the old VST2 versions but there is a bug where the VST3 version does not replace the VST2 version. What should happen is if they share the same ID then the VST3 version should automatically replace any VST2 instance. Surprised such a fundamental bug slipped through after all this time.
Good catch and to note. This is intentional in order to preserve the VST2 format because they will have different "ID"s. I realize this will be a little of a pain the more legacy sessions you have, but the workaround is to open the VST2 version and save a user preset. Both versions access the same preset folder, so you will then be able to load your preset saved from the VST2 version.
I'm not sure there is an understanding about best practices with regards to VST2 and VST3 then? They should share the same ID. If you don't want to use the VST3 version then you don't install it and the host will see the VST2 version instead. Right now we can't install the VST3 version and have our sessions open as expected. That workaround means that we have to continue to have VST2 versions installed which kind of defeats the whole purpose to a degree.
Since we're all on "legacy" versions at the moment this workaround just creates a huge headache for end users.
Please reconsider as this is not how every other developer does it.
I'm honestly really disappointed this is intended behaviour.
To reiterate and summarize:
Again, please reconsider. As it is now the VST3 version is next to useless unless you're starting fresh.
I totally understand, believe me. I'll see if I can get an official response regarding this and see if there is a plan to update to support this but do realize that it is what it is for now and any fixes will be delayed as we await for the updates to get in people's hands and report such issues. The feedback is critical though, so keep it coming!
Thanks. I'll stick to the old version as right now it's just a headache with all the sessions and if it does change then maybe the new VST3 version will be incompatible. Still can't believe this was the intended direction.
Please can the next update have either a reworked GUI, or at the least resizing and rescaling options?
Further down the line, I’d love to see the individual plugins combined into a single bundle plugin (perhaps with a new GUI and more presets/algos). For now I’m just happy to be able to use these again.
Hi TT, with all due to respect, but this is not always the case. Rather may vary by the vendor.
Examples (who use method with differ ID, for vst2 and vst3): Softube, UJAM, Plugin Boutique, Korg, and many more.
(Examples with the same ID ("replacing" method): Native Instruments, Izotope etc)
So, this is definitely not a rule.
Although, i can understand you as musician with needs for projects compatibility.
But, there is some cases when "differ ID" method can be usefull too, for direct comparison one and the same version build behavior (inside the same DAW session), or betatesting needs for example.
Just saying.
Steinberg who developed the VST2 and VST3 spec outline best general practices. Of course not all developers adhere to those recommended practices.
https://steinbergmedia.github.io/vst3_dev_portal/pages/Tutorials/Guideline+for+VST3+replacing+VST2.html
I'm not sure about you but I would prefer to to open sessions and have it "just work" rather than spending time comparing VST2/VST3 versions. So you do a comparison once - great. That's a one-time thing versus opening sessions. As mentioned, VST2 has been long since discontinued so it's a bit of a moot point.
I've also yet to hear a compelling argument as to why you'd want separate VST2 and VST3 versions (outside of comparison testing) with different IDs. Ultimately it creates more headache for the end user.
For what it's worth I'm a mixing engineer and need project compatibility which (nearly) every other developer who migrated from VST2 to VST3 with their plugins does. Time in the day is short and my energy is better spent on the jobs rather than trying to do workarounds in software.
Hey there, I have a license for PCM Random Hall on my iLok2, but despite linking it with the Flux account online, my license there isn't showing? Any idea what's hiding it? Thank you!
Sending you a message. Please look for me there.