Subject: RE: [linux-audio-dev] Problem with XML for LADSPA GUI?
From: David Benson (daveb_AT_idealab.com)
Date: Fri May 26 2000 - 16:56:17 EEST
a lot of ideas these aren't doable with ladspa
standard anyway.[1] and i doubt the remaining would
be feasible with vstgui (unless it has a free-form drawing
widget, not sure).
we have little chance of competing with an entirely
unportable, integrated application. (would these
guis even make perfect sense outside soundforge?)
the point of plugins is the decoupling.
a more fair comparison would be against vst plugins.
an even more fair comparison would be: how would this compare
to other ladspa-extensions for gui support?
also, this *is* feasible within the framework
if we allow plugins to provide new widget types,
but if that were the norm, it would indeed be pointless.
frankly, *i* think that most plugins that just
implement special effects really do have "standard" controls,
whatever that means; and so the xml will often be sufficient.
- dave
[1] time-shifting isn't doable by definition of the run function.
fade and envelope really want to have an arbitrary number of parameters.
> I've just flicked through the Sound Forge menus to find out how many
> component GUI's we could not render using XML (as I understand it). This is
> a rather old version of Sound Forge so things are probably worse now. Linux
> would *not* be able to provide the following GUIs:
>
> EQ (Paragraphic)
> EQ (Parametric)
> Fade (Graphic)
> Pan/Expand
> Multi-tap Delay
> Dynamics (Graphic)
> Dynamics (Multiband)
> Envelope
> Pitch (Bend)
>
> I don't know if XML allows calculations (i.e. the value in a field depends
> on other inputs). If it doesn't then we also lose the following:
>
> Gapper/Snipper
> Pitch Shift
> Time Compress/Expand
This archive was generated by hypermail 2b28 : Fri May 26 2000 - 19:50:45 EEST