Subject: [Fwd: [linux-audio-dev] Problem with XML for LADSPA GUI?]
From: Jörn Nettingsmeier (nettings_AT_folkwang.uni-essen.de)
Date: Fri May 26 2000 - 22:10:52 EEST
Jörn Nettingsmeier wrote:
>
> confused...
>
> i have no in-depth understanding of XML yet, but my SGML-based
> assumption is that you can define just about *any* extension you can
> think of (like <!DOCTYPE LADSPA widget "-//LAD//DTD AWML 1.0
> //EN">).
> the rendering engine would have to deal with it. i think the problem
> is not xml.
>
> so if i make up a tag <livepixfrommars height=60 width=60
> refresh="50usec"/> the engine *must* contact Hubble telescope and
> see what can be done :)
> same applies to an eq control like in snd:
> <graphicparamlist maxanchors=50 anchorsymbol="littleblacksquare"
> anchorxrange="-60,+10" xunit="dB" anchoryrange="20,20000" yunit="Hz"
> height=60 width=120 align="center"/>
>
> the engine is responsible to draw anchors and lines on mouse events,
> but the xml definition remains static.
> also, the engine has to know how to pass the parameters (like the
> form-action-submit tag in HTML) to the plugin and how to receive
> additional rendering data from it to update the screen.
>
> please let me know if i totally missed the point.
>
> yours,
>
> jörn
>
> "Richard W.E. Furse" wrote:
>
> > From: David Benson [SMTP:daveb_AT_idealab.com]
> > Sent: Friday, May 26, 2000 2:26 AM
> > To: Richard W.E. Furse
> > Cc: Linux Audio Developer Mailing List (E-mail)
> > Subject: Re: [linux-audio-dev] Problem with XML for LADSPA GUI?
> >
> > [...]
> > > ...
> > >
> > > Can we / How do we express GUIs for these three plugins in XML?
> >
> > xml is just a data file -- it is a lot like html, but more
> > regular, standardized and geared toward generic data presentation.
> > [...]
> > this by-and-large precludes gui effects like all those you describe.
> > [...]
>
>
> > Thanks for the info.
> >
> > In this case, and as a musician, I have no interest in an XML-based LADSPA
> > GUI. As a Linux enthusiast it's a useful marketing tool, but we've
> > successfully stripped the potential API of most of its real musical
> > usefulness.
> >
> > 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 is about a quarter of the items present and includes many of the
> > useful ones. This means that we end up with a GUI that is vastly inferior
> > to Windows. Possibly pretty, maybe even sexy, but basically useless.
> >
> > I hope I have the right end of the stick here - I'm a little scared by the
> > fact that other people aren't clamouring about this one...
> >
> > -- Richard
> >
> > -----Original Message-----
>
> --
> Jörn Nettingsmeier
> Kurfürstenstr. 49
> 45138 Essen, Germany
> http://www.folkwang.uni-essen.de/~nettings/
-- Jörn Nettingsmeier Kurfürstenstr. 49 45138 Essen, Germany http://www.folkwang.uni-essen.de/~nettings/
This archive was generated by hypermail 2b28 : Fri May 26 2000 - 21:48:57 EEST