Paul Davis wrote:
> (1) LADSPA as a "standard" doesn't define a preset API, but the first hosts
> agreed to use LRDF as a preset format, and to store presets in a
> host-neutral location (which is more or less what AudioUnits do). The
> plugin itself has no API to set its state, but any LADSPA's plugin state
> was intended to be representable solely in terms of its input control
> ports, so the host just loads the LRDF preset and sets the control ports.
>
> (2) LV2 has the State extension (don't balk at "extension" - almost
> everything in LV2 is an "extension) which is designed for saving plugin
> state in a host and platform neutral way.
I looked into this format, and see it is XML, found some
presets in ~/.ladspa/rdf/ardour-presets.n3
To make it easy to share presets it might be valuable to
have an app-independent way of browsing and comparing them.
We share a lot of music, here, and I hope that presets could
be shared as readily.
It surprises me, really, since without proprietary
pre-cooked offerings, everyone producing music with Linux
invests a lot of time to find suitable plugin settings.
You'd think that open source source community would share
them as well.
-- Joel Roth _______________________________________________ Linux-audio-user mailing list Linux-audio-user@email-addr-hidden http://lists.linuxaudio.org/listinfo/linux-audio-userReceived on Tue May 3 00:15:01 2016
This archive was generated by hypermail 2.1.8 : Tue May 03 2016 - 00:15:01 EEST