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

bronsoncox

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

That is as old as... VST
 
VPC is a way to "extend" it.
 
 

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.

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

Wrong. AU has 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?

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

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.

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.

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)

There isn't anything in the AU developers guide. Its most likely something specific to Kontakt that NI developed. I can ask their dev's. I'm sure they will be interested in what we have.
What we have is a generic API to handle persist migration of any vst to another compatible one. It can could also be used to handle migration of an AU to a VST3 if the VST3 can understand the AU format.