On Wed, 2011-03-02 at 15:08 -0500, Paul Davis wrote:
There will be a Death To Control Ports initiative at some point. LADSPA
control ports suck.
It turns out there is a more meaningful semantic dichotomy of ports.
* "Value" ports are simply values of any type, inherently timeless
* "Signal" ports are /consumed/ and time dependent
The big thing that leads you to this is the realisation that it makes
perfect sense to have the exact same data type in either kind of port
(e.g. you can have a float value, or send a float message, and the
semantics of how the plugin interprets that are very different. If "1.6"
seems crazy as a message, consider Max/MSP). Data type is not the
The other thing is that this becomes essentially mandatory when you have
multiple contexts per plugin.
(As for control ports, they should be, and will be, events instead)
> AU, which is the only other plugin API to explicitly support
Yep. There is no question that this is the way to go. Bunch of useful
things are possible that wouldn't be otherwise... QED.
(* It took a lot of trial and error and failed attempts at extensions to
figure this one out, it may not be intuitive right away?)
Linux-audio-dev mailing list