On Thu, 2011-11-24 at 13:45 +0100, Philipp Überbacher wrote:
... hm? That is the entire point of this extension.
From the opening paragraph:
The intention is for a plugin instance's state to be completely
described by port values (as with all LV2 plugins) *** and a simple
An extension is not needed for storing port values, hosts already have
access to those.
> Also regarding paths, what about windows paths and stuff like that? As
The host gets the opportunity to map paths in any way it pleases. You
can leave them be, map them to indexes into a table of actual file
paths, etc. Sessions that contain absolute paths aren't portable to
other system anyway, since the files referred to might not be there on
somebody else's computer, even if they are running the same operating
Ardour uses this facility to create symbolic links in the plugin's state
directory that point to the absolute path. e.g.
/mysession/plugins/123/sample.wav -> /home/whoever/samples/sample.wav
The nice thing about this is that any stupid tool, like tar, can be used
to archive and distribute self-contained sessions. It's also easy to
see what went wrong and fix it manually in the shell or file manager (If
you moved your samples directory, for example). I recommend this
strategy to all plugins and hosts, having absolute paths buried in some
file in who knows what syntax is evil, particularly considering the fact
that we have session storage for apps as well.
Linux-audio-dev mailing list