VST Persist Compatibility (VPC)

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?

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

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.

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

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. 

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

http://obiwanjacobi.blogs...lugin-persistence.html

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

Sorry to be a "tease", but for the eZine I just added a little screen grab of the source code for graphic interest. Noel had given me the source code even though I am clueless about programming, because it's so well-commented I could figure out what it did well enough to write about it.

EvilDragon

Noel BorthwickIt is indeed a big deal since no plugin specification today has a general way to handle persist compatibility.

Wrong. AU has it.

Can you give a link to that interface?

EvilDragon
AudioUnits plugins, on Mac. It's called AU plugin migration. NI Kontakt has it implemented since version 5.0.3.

I know what is AU and "Audio Units plug-in Migration in Kontakt 5" is easy to Google. But I am interested in how it is implemented. And that is much harder to find ("Plug-in Migration" search does not output any link to Apple developers site. I have also tried to find something in AU v3 reference pages, but I do not see user friendly form like v2). That is why I have asked about direct link... But thanks in any case.

EvilDragon
Might be a good idea to ask NI about how it's implemented then... They seem to have managed to get some docs about it from Apple. Weird that Apple didn't document it though.

That could be some cooperation between NI and Apple (Like CW is doing for ProChannel).
NI is already known as a producer of INTERNAL standards (NKS)

I don't think NI will be interested since what you have is VST3 only. Backport it to VST2 and they might bite, since VST3 is not on NI's plate for quite some time yet.

BTW I really think this is a feature of AU format, it's just (for whatever reason) not documented. I am pretty sure that this is not something NI concocted with Apple solely because of Kontakt, based on my direct interaction with NI devs as alpha and beta tester...
 
 
Also, NKS is not an "internal" standard, other devs are using it as well, and the number of devs signing up to it is steadily increasing...

Hi EvilDragon. I'm assuming you're the same guy Korgforums?
 
Noel, as far as I know Pro Q and Pro C 1/2 are fully sonically compatible with the new versions just having a bunch more options and better CPU handling. The 2 versions already load presets from the 1 versions. But that'll be up to them then I guess. 

Sanderxpander
Hi EvilDragon. I'm assuming you're the same guy Korgforums?

Indeed I am :)

If I understand correctly, there's two important features lost in the process of upgrading from TH2 to TH3.
Both was associated with "generic" Amp module, which itself is no more presented, replaced by separate Amp modules.
First is SLR - kind of sonic morphing between two Amp models, second is VariFire - special sound variation control for Amp module.
Well, so, I don't understand: how TH3 can replace missing TH2 instance and be sonically identical, if that TH2 instance (or preset) used features wich is just missing in TH3?..