Subject: [linux-audio-dev] GUI<->Plugins
From: Alexander Ehlert (ehlert_AT_phys.unsw.edu.au)
Date: pe maalis 10 2000 - 00:46:41 EST
Hi,
I just had another wierd idea that could actually be a problem :)
Just imagine a plugin that want's to have a LUT as one parameter, e.g.
a waveshaper, generic filter... That seems to be no problem with ladspa,
parameter ports just take a pointer to whatever float/array of floats?
But for defining a LUT in a GUI you surely want to have a widget in your
host application using splines, freedrawing, blabla...
A plugin like that may be easy on the LADSPA layer, but you can't just
write a plugin like that without a GUI in mind. And that's highly
dependend on the actual host application. One way would be to define a set
of commonly used control datatypes in ladspa that allow hosts to construct
reasonable GUI's, another way that someone already mentioned is to write
an own GUI for your filter. But even then you would need a sane way for
GUI to communicate with its plugin through the host. There's no way
running the gui from within the plugin thread.
Any thoughts ?
Cheers, Mag
-------------------------------------------------------------------------------
When I am told, I forget
When I see, I remember,
When I do, I understand
(Confucius)
This archive was generated by hypermail 2b28 : su maalis 12 2000 - 09:14:06 EST