This seems like a really big deal, if other vendors jump on board.  Are you at liberty to tell us if any other plugin vendors are offering this?

The new mastering plugs don't include it? Cake should jump on board first.

And they need to publish the whole "source code". Like half of it is already on ezine, but the second half is hidden

Well,i've just try to remove TH2 from my system to see if the new TH3 will be loaded automatically in substitution of TH2 in an older project but...same pop-up of missing plugin!
LOL,same,old marketing ****s?

Hi folks,
 
It is indeed a big deal since no plugin specification today has a general way to handle persist compatibility. Users have to run through hoops to convert projects to use a new plugin because of this. With VPC, you just load the project and everything happens behind the scenes. You can try this for yourself with any of your old projects with TH2. Simply unistall TH2 or rename the DLL, then start SONAR let it scan and then load your old project. All TH2 instances will be automatically moved to TH3 and all envelopes will auto map to the new parameters. Its pretty slick - try doing that process manually and see how long it takes :)
 
I will be publishing the header file the VST community soon. I just need to write up some documentation for it showing some details about the plugin and host side implementation before that. I hope other hosts and plugin vendors implement it since it makes life easier for everyone, users and vendors alike.
 
I have already in fact talked to Steinberg about this last year as well as several other plugin vendors and got a very positive response. Overloud is the first vendor to implement it. Keep in mind that the main reason for VPC is to allow for automatic substitution of plugins that a actually sonically compatible. e.g. TH3 can replace an older version of TH2 and yet be sonically identical. OTOH we didn't implement VPC for the new LP EQ because it is not exactly sonically compatible with the old LP-64 EQ. We may however choose to do so for the upcoming maximizer if we can map the parameters in a compatible way.
 
IN short if you know of other plugin vendors that might benefit from this let them know so they can consider implementing it.

KWILD
Well,i've just try to remove TH2 from my system to see if the new TH3 will be loaded automatically in substitution of TH2 in an older project but...same pop-up of missing plugin!
LOL,same,old marketing ****s?

Which version of SONAR and TH3 are you using? This only works in 2016.04 and higher and the version of TH3 shipped with SONAR. TH3 full should also support it. 
 
Follow these steps:

1. Remove TH2 from your system
2. Make sure TH3 VST3 is installed
3. Run SONAR and ensure that it runs the VST scan process (it should remove TH2 and load TH3)
4. Go to Preferences | VST and make sure "Replace if possible on project load" is checked. (default)
5. Now open any project containing TH2 is loaded

Note that step 3 is very important since otherwise SONAR won't know that TH2 was removed. This should automatically happen if scan on startup is enabled. If not you will need to manually scan.
 
Now open your project containing TH2 and SONAR will automatically replace with TH3.
 

Ok,i've solved checkin "Replace if possible on project load" now TH2 is correctly replaced by TH3.
Well done.
 

Noel Borthwick [Cakewalk]
I have already in fact talked to Steinberg about this last year as well as several other plugin vendors and got a very positive response. 
 
the upcoming maximizer

Great news, good to know that! Is the new maximizer going to be a Boost11 replacement?

Cool, did you guys talk to FabFilter yet? They always seem to adopt new standards quickly and have ProQ and ProC 1 and 2. And perhaps more in the future. 

I will forward it to them. Note that compatibility depends on whether the plugin is really sonically compatible however.