[LV2] [solved]State example?

hermann meyer brummer- at web.de
Sat Mar 16 11:41:48 PDT 2013


Am 16.03.2013 17:38, schrieb hermann meyer:
> Am 16.03.2013 16:23, schrieb Harry van Haaren:
>> On Sat, Mar 16, 2013 at 2:53 PM, hermann meyer <brummer- at web.de 
>> <mailto:brummer- at web.de>> wrote:
>>
>>     I just need to store simple port values, nothing to add from the
>>     plug internal
>>
>>
>> Oh, simple control ports should work automatically. That's a bug 
>> somewhere in Ardour / somewhere else.
>> Perhaps save a test preset with Jalv, and see if it can restore its 
>> state properly?
>>
>> The State extension is for saving filenames (or other 
>> "non-control-port" values) that a plugin needs to restore the state.
>>
>> Sorry for the misunderstanding, -Harry
>
> Thanks for your help Harry, well it is indeed a mess with those LV2 
> preset behavior.
> Indeed jalv save presets correct, but the resulting preset is missing 
> a label
>> Preset <file:///home/brummer/.lv2/default.lv2/default.ttl> has no 
>> rdfs:label
>
> when I add per hand to the file
> <http://guitarix.sourceforge.net/plugins/gx_amp#GUITARIX#default>
>
> the preset works.
>
> Ardour3, saves the preset after some times trying correct. Mostly when 
> the session is quit, in the next started session load the preset 
> (which makes it half the way, and press save some times.
> The result is a functional preset.
>
> Umpf,

So, after I have #included "lv2/lv2plug.in/ns/ext/presets/presets.h"
in my plug header, presets are saved by ardour3 as suspected.

What makes it a bit strange is, that "just saved" presets can't be 
loaded in the same session, they are available only in the next started 
session. I guess a dir reload after save will do the trick for ardour.
What makes it nice is that qtractor use the same preset dir so that 
presets are available in qtractor to.

However, I'm happy to get it work lately-
hermann
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lv2plug.in/pipermail/devel-lv2plug.in/attachments/20130316/a5673c52/attachment-0002.htm>


More information about the Devel mailing list