Subject: Re: [linux-audio-dev] +momentary, consolidated (ladspa.h.diff)
From: Fons Adriaensen (fons.adriaensen_AT_skynet.be)
Date: Mon Mar 08 2004 - 23:29:51 EET
On Mon, Mar 08, 2004 at 05:58:48PM +0000, Steve Harris wrote:
> I dont think that scale markings, / enumerations, defaults and units are
> logically connected to the same extent that upper and lower bounds are.
> That is a matter of opinion of course.
Well, for me ENUMs on an integer param that maps to a multiway switch, a set
of radio buttons or a menu are not 'meta'. Without them you have *no* idea what
the switch is doing, so they seem IMHO as essential as Min / Max on a slider.
Same for TRIGGER, the host needs to know this, but then I suspect most triggers
would never be in a GUI but rather external or from another module.
Scale points on a floating point param are an entirely different matter even
if they could be mapped to a similar data structure - that's a coincidence and
doesn't mean anything. Separate unit strings are, for me, a luxury. I agree
that both could be in the RDF only. And other than AUDIO / CONTROL which are
not compatible at the 'physical' level, I think there should be no port typing
in LADSPA.
As to defaults, the current system is limited, but for me it is sufficient.
The only thing defaults should be used for is to make sure the plugin start
in a sensible state. Anything beyond this can become a preset, if required.
-- Fons
This archive was generated by hypermail 2b28 : Mon Mar 08 2004 - 23:24:11 EET