[LV2] RFC: Describing programs

David Robillard d at drobilla.net
Sun Feb 10 00:59:07 PST 2013

On Sun, 2013-02-10 at 10:56 +0200, Stefano D'Angelo wrote:
> > If they are static, can't you just stick bank and program numbers on a
> > preset description?  That may be an argument for using midi:bankNumber
> > and midi:programNumber instead of lv2:index.
> Mmm... I guess I can blame everything on DSSI API at the end of the
> day. I mean, since in DSSI a plugin is allowed to change its own input
> control port values and since MIDI program == preset, I don't think
> it's possible to do much better than what the NASPRO bridge does, that
> is to export "DSSI programs" to LV2 presets and prevent usage of
> DSSI's program change mechanism.

Is there anything wrong with that solution?  Seems fine to me.

> But, more importantly, I don't think anybody cares.

This much is true.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.lv2plug.in/pipermail/devel-lv2plug.in/attachments/20130210/72edd27c/attachment-0002.pgp>

More information about the Devel mailing list