Subject: RE: [linux-audio-dev] Problem with XML for LADSPA GUI?
From: Richard W.E. Furse (richard_AT_muse.demon.co.uk)
Date: Fri May 26 2000 - 19:35:52 EEST
Hmm I suppose we could provide both active and passive approaches - sorry
if my brain hadn't engaged on this one. I suppose it fits in with the
toolkit negotiation process I'd been considering initially, but I'll have
to think about this some more (centralise or devolve?).
On the final section below, looking over the Sound Forge Paragraphic EQ, I
count 18 editable parameters. Whenever I change one, a frequency-response
graph updates. The underlying LADSPA DSP Paragraphic EQ could accept these
18 parameters directly through 18 input control ports. Without the graph
this would be very straightforward and could be generated automagically (or
with XML for the tarty version).
The Sound Forge Graphic Dynamic processor without modification is
problematic as this uses a response function built up of an arbitrary
number of loglinear segments. However, as long as an concrete upper limit
on the number of these segments is imposed then the breakpoint (X,Y)
co-ordinates can be passed through input control ports without difficulty.
-- Richard
-----Original Message-----
From: Paul Barton-Davis [SMTP:pbd_AT_Op.Net]
Sent: Friday, May 26, 2000 3:59 PM
To: Richard W.E. Furse
Cc: linux-audio-dev_AT_ginette.musique.umontreal.ca
Subject: Re: [linux-audio-dev] Problem with XML for LADSPA GUI?
[...]
I don't think anyone has suggested XML-only. The idea is that plugins
that don't need custom widgets can use XML. According to your brief
survey, thats about 75% of them. This fits in with my survey of the
ProTools partners catalog of TDM plugins. The other 25% can use the
toolkit of their choice. Ideally, they would use ladspaGUI (something
like vstGUI written for 1 or more Linux toolkits; alternatively, this
could be one of the existing wrapper-widget-sets like wxWin, and then
we don't have to write very much code at all!), so that they would be
[...]
However, if their decision is "sensible" (ladspaGUI, GTK+, Qt), then
it will almost certainly work out for most people. And before somebody
leaps in with "what happens in I don't run X11 or any other window
system?", I would point out that the 25% of cases we're discussing are
highly-visual plugins that *require* a GUI in order to be
useful. Unless their authors do something very clever, they are not
useful in a GUI-less environment.
IMPORTANT:
**********
Which reminds me: just *how* does LADSPA support any of the list of
plugins that Richard mentioned ? How does anything specify the curve
of a paragraphic EQ to a LADSPA plugin ? Or the transfer function of a
dynamics processor ?
--p
This archive was generated by hypermail 2b28 : Fri May 26 2000 - 20:13:59 EEST