[LV2] lv2 state#Dirty
Hanspeter Portner
ventosus at airpost.net
Thu Oct 13 12:33:05 PDT 2016
On 13.10.2016 16:42, Robin Gareus wrote:
> Hi LV2ers,
>
> If an LV2 plugin has an internal state and that state changes, a host is
> non the wiser. The host cannot mark the session as dirty (modified,
> needs save).
>
> e.g. Save the session or plugin-preset (marked "clean") then load a new
> sample into a synth (using a custom plugin GUI). On the outside nothing
> changes. Now close the session, quit the host: The changes are lost
> (same for presets or any state that needs saving).
>
> I propose http://lv2plug.in/ns/ext/state/#Dirty which allows a plugin
> that has a state interface to notify the host about state changes using
> an Atom message:
>
> state:Dirty
>
>
> a rdfs:Class ;
> rdfs:label "State modified message" .
Sounds great and very useful indeed.
How does this event look like?
Is it a new atom type or set via the patch extension?
e.g.
[]
a patch:Set ;
patch:property <http://lvplug.in/ns/ext/state#Dirty> ;
patch:value true .
More information about the Devel
mailing list