13 Aug
2009
13 Aug
'09
7:53 p.m.
On Thu, Aug 13, 2009 at 09:27:20PM +0100, Steve Harris wrote:
On 13 Aug 2009, at 20:01, David Robillard wrote:
That, IMHO, is a different problem space.
If the original problem is 'how to define a mono plugin so it can
be replicated for multichannel or polyphonic use' then I'd agree.
There is a world of difference between a plugin that is meant to
be a single-function module in a larger application (e.g. a filter
in a mixer, an envelope generator in a synth) and one that is really
a complete and probably complex application on its own, e.g. a mixer,
or a complete synthesiser.
The latter you can't 'configure' just by setting port types, unless
the concept is abused in some way to carry data that is not really
describing just a port.
And I'm not yet convinced that even the simple 'replicate a mono
plugin' problem can be solved by port types only.
How would a port type tell e.g. a multichannel limiter plugin if
it has to limit each channel separately, or use the same gain
reduction, based on the loudest one, on all ?
Ciao,
--
FA
Io lo dico sempre: l'Italia รจ troppo stretta e lunga.
I'm
assuming the only ports to be replicated are those which have
say a
multiPort property. I don't see why replication would not be the same
in a plugin instance, across all ports with that property.
Because larger plugins can have several completely different signal
paths. Synthesis and effects, or several channels on a mixer, or...