Subject: Re: [linux-audio-dev] ladspa GUI round 2
From: Iain Sandoe (iain_AT_sandoe.co.uk)
Date: Fri Mar 30 2001 - 15:31:10 EEST
>>But, the GUI now contains two totally different tasks: the GUI and
>>the effect controls. The plug-in can be used only with the original
>>GUI toolkit because the effect controls (room size settings etc.) are
>>within the GUI code.
>
> No! Or rather, not necessarily. This depends entirely on the approach
> of the plugin designer. If the plugin has a control port corresponding
> to "room size" (e.g. Freeverb), then your claim above is false. If the
> author, on the other hand, uses, lets say, 3 control ports whose
> aggregate effect is to control "room size", but then has a GUI which
> has a single control for "room size", then yes, you're right. But I
> think that this kind of design would be considered poor. The controls
> in the GUI should map more or less exactly to the actual control ports
> of the plugin.
That depends on your view as to where "UI-specific" code belongs. That is,
the algorithm implemented by the plug-in may make use of a parameterisation
that is "counter intuitive" to users - but efficient for run-time.
You might want the GUI to translate between this and something that users
can deal with.
Iain.
This archive was generated by hypermail 2b28 : Sat Apr 07 2001 - 15:56:26 EEST