From bc8f4e16826abcc9a22466a151e1c4d8daf1a365 Mon Sep 17 00:00:00 2001
From: David Robillard
A bank of programs. See lv2:Program for details.
- -A Bank MUST have an rdfs:label giving a short label suitable for -presentation in a user interface, and SHOULD have an rdfs:comment if a more -detailed description is available. For MIDI compatibility, a bank SHOULD have -an lv2:index within [0,127].
-""" . - lv2:PluginBase a rdfs:Class , owl:Class ; @@ -232,31 +219,6 @@ necessarily refer to the same port on all plugins with a given URI (i.e. the index for a port may differ between plugin binaries). """ . -lv2:Program - a rdfs:Class , - owl:Class ; - rdfs:label "Program" ; - lv2:documentation """ -A plugin configuration or mode. This can describe MIDI programs, but is -more general. Implementations MAY support changing programs by any -mechanism.
- -A program MUST have an rdfs:label giving a short label suitable for -presentation in a user interface, and SHOULD have an rdfs:comment if a more -detailed description is available. For MIDI compatibility, a program SHOULD -have an lv2:index within [0,127].
- -Note that a program is an internal plugin mode, not necessarily a complete
-snapshot of plugin state (which is a preset
). The currently active
-program is a parameter, lv2:program. Programs allow plugins to implement
-internal configurations opaque to the host; in particular, a program does not
-define control input values. The distinction is analogous to hardware that
-supports program changes but also has physical controls that can not be changed
-by software. However, a program MAY be associated with a preset, or one
-resource may be both a program and a preset, to support completely changing a
-plugin instance's state via a program change.