Hi Olivier,
 
I'm sure they can fix it too. I've sent an email off to Dave Gamble - I had some other problems a year or two ago, and between Noel and Dave, we got them sorted out.
 
If you're evaluating - just use VST2 for now ;-)

This is still broken with the Kingston update...

Thank you for the information,then I can spare the time needed to download the update ,hope a fix will come soon.

Check Equilibrium out with the Lexington update - it's working correctly here now.
VST3 Equilibrium comes up as a stereo plugin on a stereo track - and when I change the track interleave to mono, it comes up as a mono plugin.

Hi John,
 
Yeah I got an email from the developer as well. This is actually a bit puzzling to me since I didn't change the VST3 code in Lexington. Are you sure this didn't work in Kingston? 
The only think that could have remotely affected this is this change "loading protocols were optimized further for the most commonly encountered project settings". i.e. when loading projects or instantiating plugins we first initialize them in stereo rather mono first then stereo as was done in earlier builds. 
I can't see why this would matter to the plugin but you never know :)
 
Can you verify if the plugin still works ok if you switch the track interleave to mono and then back to stereo?
Also test with the 64 bit engine. If it works ok we'll close out the bug.
 
best,
Noel

Noel Borthwick [Cakewalk]
Hi John,
 
Yeah I got an email from the developer as well. This is actually a bit puzzling to me since I didn't change the VST3 code in Lexington. Are you sure this didn't work in Kingston? 
The only think that could have remotely affected this is this change "loading protocols were optimized further for the most commonly encountered project settings". i.e. when loading projects or instantiating plugins we first initialize them in stereo rather mono first then stereo as was done in earlier builds. 
I can't see why this would matter to the plugin but you never know :)

 
Hi Noel,
I'm glad to hear that Dave was in touch with you - I sent hime a few emails, but never heard anything ;-)
 

Can you verify if the plugin still works ok if you switch the track interleave to mono and then back to stereo?
Also test with the 64 bit engine. If it works ok we'll close out the bug.

Yes indeed, and I just double checked.
stereo interleave track - VST3 Equilibrium loads up as a stereo plug
mono interleave track - VST3 Equilibrium loads up as a mono plug
This is as it should be and it works whether 64 bit double precision engine is ticked or not. 
 
So maybe "loading protocols were optimized further for the most commonly encountered project settings" affected it, but it definitely works now ;-)
Thanks a lot for helping with this ;-)