Yes, thats what I suggested a few days ago.
Something like ~/.ladspa/presets/<idnum>/foo.whatever and
/usr/local/share/ladspa/presets/...
I think it's better to make it LADSPA specific though. Cuts down the
complexity, but you could make the DTD extensible to other plugin
formats.
There are some important comlexity/usefulness tradeoffs though, do you
extend it to 'lambda' nets? How about host specific information? (not sure
what it would be, but...)
- Steve
On Fri, Dec 15, 2000 at 02:39:01AM -0500, Rick Burnett wrote:
> Me thinks that it also shouldn't be entirely handled my the host :)
> Because its unlikely that the host should come up with some sample
> presets for the plugin. Instead, if it were up to me, I would just
> come up with a standard that is seperate to the plugin, but supplied
> by the plugin developer (if they want to :). Like [plugin].presets or
> something. So you standardize the structure for storing things maybe
> in LADSPA so that the host could do the loading and applying to the
> plugin. Make any sense?
>
> Rick
>
> Thursday, December 14, 2000, you wrote:
>
> DO> On Monday 11 December 2000 13:07, Frank Neumann wrote:
> >> Hi,
> >> I hope this topic hasn't already been discussed earlier; it's
> >> sometimes a bit hard to follow the daily mail on LAD. :-)
> >>
> >> Anyway, I was wondering if people have already thought about how to
> >> keep preset data with plugins. Looking at VST plugins, I see e.g. a
> >> Reverb plugin that comes with a list of "Small Room, Large Room,
> >> Chapel, Live Stage" and more presets. Something similar should be
> >> possible in conjunction with LADSPA, too, me thinks.
> DO> [...]
>
> DO> Yes, all good thinking, but my first thought is "It should not be
> DO> done by the plugins."
>
> DO> Why should it, when a preset is just stored state of the plugin's
> DO> control ports? I'm thinking of presets as being closely related to
> DO> automation, and thus, it becomes pretty obvious that it's the *host*
> DO> that deals with it - not the plugins.
>
> DO> Anyway, I still think there should be some kind of standard way of
> DO> managing presets, just like we need standard ways to manage audio
> DO> data and EDLs. Don't know if it should or has to be LADSPA specific,
> DO> but some standard way of storing the data would be handy. Libraries
> DO> to deal with it would help developers a great deal, of course.
>
>
> DO> //David
>
> DO> .- M A I A -------------------------------------------------.
> DO> | Multimedia Application Integration Architecture |
> DO> | A Free/Open Source Plugin API for Professional Multimedia |
> DO> `----------------------> http://www.linuxaudiodev.com/maia -'
> DO> .- David Olofson -------------------------------------------.
> DO> | Audio Hacker - Open Source Advocate - Singer - Songwriter |
> DO> `--------------------------------------> [EMAIL PROTECTED] -'
>
