[LV2] A question about plugin presets

[Iurie Nistor]

What I am thinking is (hope it makes sense)...

for example, the host user created a preset list (or a tree) of a 
particular plugin by using the host preset browser. Than to be able to 
export this list/tree into the plugin native preset files. Thus, the 
user will be able to share their created instrument/effect presets on 
the Internet or whatever.

I see that in the states saved in $HOME/.lv2 there is a field called 
state:state in the *.ttl file. I see that usually plugins provides the 
data for this filed in the same way they save the preset into a file. 
Probably using LV2 API the host can get this data, and also can get the 
file extension name and, thus, can save the preset into the file. At the 
end there will a possibility to export the entire tree in folders like:

/PluginName

    /snares

         snare1.ext

         snare2.ext

   /kicks

          kick1.ext

         kick2.ext

    etc.. etc...

Than someone just archive this and share the presets on the Internet.

Otherwise plugin authors need to implemented file dialogs (difficult to 
implement outside of the normal GUI toolkits) in order to offer users to 
save their created presets.

Yes, plugins authors will need to follow LV2 standard in order to enable 
this possibility for their plugins. Maybe even for importing presets.

On 10/10/19 7:56 PM, Robin Gareus wrote:
> On 10/10/19 3:27 PM, Filipe Coelho wrote:
>> I think ardour saves session presets in the session directory (I can be
>> wrong),
> Ardour saves plugin-presets in a shared location. In LV2's case, on
> GNU/Linux, by default $HOME/.lv2/
>
> ciao,
> robin
> _______________________________________________
> Devel mailing list
> Devel at lists.lv2plug.in
> http://lists.lv2plug.in/listinfo.cgi/devel-lv2plug.in