8 Dec
2011
8 Dec
'11
12:21 p.m.
On Wed, Dec 07, 2011 at 11:31:51PM -0500, Caleb Reach wrote:
On Mon, 5 Dec 2011 09:40:15 +0000, Fons Adriaensen
<fons(a)linuxaudio.org> wrote:
AFAIK, a custom GUI in LV2 means either you use the same toolkit
as the host, or the plugin GUI becomes a separate process. The
latter may be fine for one or two plugins, but it doesn't scale.
The dynparam extension and init-time parameters are two separate
things. I don't know if LV2 allows the latter. Maybe with another
extension.
I may consider writing some of my apps as LV2s if and when there
is host that has all the extensions I need. That is not the case,
and I don't see it happen any time soon.
So you need to monitor what it is doing, and
that's one reason
why DPL1 has the type of display it has, and why it is not a
Ladspa plugin.
A second one is that I wrote this to have a limiter that can be
used on multichannel (mainly AMB here) mixes. Since Ladspa has
no 'create-time' parameters, this would require a different
plugin for each channel count.
Hey Fons, thanks for the limiter!
The LV2 plugin spec permits custom GUIs, and the dynparam extension
allows the number of parameters to vary (I'm not sure if there's a
built-in way to do this). By the way, I may be misreading, but wouldn't the
license in dplimit1.cc
prohibit others from making plugin ports and from including this in GPL
software?
That is correct.
Ciao,
--
FA
Vor uns liegt ein weites Tal, die Sonne scheint - ein Glitzerstrahl.