Replace old (and not found) plugin version

[finotti (Luis Finotti)]

I opened a very old session (2018) and Ardour tells me that ZynAddSubFX was not found (and replaced it with the “dummy” place holder). It is probably because it is an older version of it, perhaps installed in a different way, since I do have it installed.

I would like to keep the settings from the old plugin, as I don’t remember how I obtained that particular patch. Is it possible to somehow make Ardour replace the old version of it with the new one (keeping the same settings of the old)?

[finotti (Luis Finotti)]

Since I did not get any replies, I assume there is no way to replace it. Is it possible to somehow just see the parameters set in the old plugin?

[peder (Peder Hedlund)]

Ardour stores the plugin settings in a subfolder to the plugins one, but I don’t know if there is an easy way to translate the .ttl file into a Zyn patch file.

I’m presuming the main problem comes from your session being made using Zyn v2 and that you now have v3 installed.

What OS are you using?
If it’s Windows then you could perhaps find and install v2 and see if that works.
If it’s Linux and you’re comfortable with compiling stuff then maybe try that route.

In the Linux case you could presumably trick your session into loading v3 but using the settings from v2.
I’m guessing it’s the lv2:appliesTo line in the manifest.ttl that tells Ardour which plugin to load, so if you edit that file and line to say whatever Zyn v3 announces (you can get that info by adding Zyn v3 into a new session and check the resulting manifest.ttl), and then make the same edits in the corresponding state.ttl file there is a chance you can get it to work.

[finotti (Luis Finotti)]

Thanks for the reply! That was really helpful. I cannot try it yet, but I can see what you mean:

$ cat 1799/state1/manifest.ttl
@prefix atom: <http://lv2plug.in/ns/ext/atom#> .
@prefix lv2: <http://lv2plug.in/ns/lv2core#> .
@prefix pset: <http://lv2plug.in/ns/ext/presets#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix state: <http://lv2plug.in/ns/ext/state#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

<state.ttl>
        lv2:appliesTo <http://kxstudio.sf.net/carla/plugins/zynaddsubfx> ;
        a pset:Preset ;
        rdfs:seeAlso <state.ttl> .

versus

$ cat 19875/state1/manifest.ttl
@prefix atom: <http://lv2plug.in/ns/ext/atom#> .
@prefix lv2: <http://lv2plug.in/ns/lv2core#> .
@prefix pset: <http://lv2plug.in/ns/ext/presets#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix state: <http://lv2plug.in/ns/ext/state#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

<state.ttl>
        lv2:appliesTo <http://zynaddsubfx.sourceforge.net> ;
        a pset:Preset ;
        rdfs:seeAlso <state.ttl> .

And the file state.ttl does seem to have the values for the parameters. I would be a pain to do it manually, but it could be an option.

Thanks again!

(I’m running Linux, by the way.)