[LV2] Configurable channels for LV2 plugins

Harry van Haaren harryhaaren at gmail.com
Sun Mar 24 12:16:12 PDT 2013

On Sun, Mar 24, 2013 at 6:24 PM, David Robillard <d at drobilla.net> wrote:

> Yep, property wise we already have almost everything needed to describe
> this.

> The problem with this is it can only set *one* channel configuration for
> the instance.  For example it couldn't configure a plugin to mono in,
> stereo out, or stereo in + mono out, etc.
Ah yes, indeed my initial idea would limit input & output to be the same.
We definitely don't want that.

> For this reason, it probably has to be per-port, or per-group, not a
> single per-instance option.
Yeah ok.

> dyn-manifest is not designed for run-time changes.
Good to know.

> It would be much easier to create a new 'port' type that's really a
> group, and can be configured.


>  Things would work as you described, but
> you'd configure the group(s) individually.  I guess the buffer type
> could be an array of pointers to buffers?
Sound pretty logical.
So we must define a new lv2:port
which has attributes of the Port group extension
-pg:inputGroup or pg:outputGroup
-pg:group subclass (mono stereo, ambisonic  etc)
-pg:mainInput or mainOutput attributes

> See my recent reply to Julien Pommier's thread "multiple channel
> configurations in lv2 plugin" about this.

Indeed that post and the fact I'm currently writing a plugin in mono
that I also want in stereo is the cause of the OP :)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lv2plug.in/pipermail/devel-lv2plug.in/attachments/20130324/1fecdd0d/attachment-0002.htm>

More information about the Devel mailing list