| 57 | | A pg:Group MUST have at least one string lv2:symbol. This symbol must |
| 58 | | be unique according to the same rules as the lv2:symbol for an lv2:Port, |
| 59 | | where group symbols and port symbols reside in the same namespace. |
| 60 | | That is, a group on a plugin MUST NOT have the same symbol as a port |
| 61 | | on that plugin. |
| 62 | | Rationale: Hosts may find it useful to construct an identifier to refer |
| 63 | | to groups for the same reasons this is useful for ports. |
| | 57 | A pg:Group MUST have at least one string lv2:symbol. This symbol must be |
| | 58 | unique according to the same rules as the lv2:symbol for an lv2:Port, where |
| | 59 | group symbols and port symbols reside in the same namespace. In other words, |
| | 60 | a group on a plugin MUST NOT have the same symbol as another group or a port |
| | 61 | on that plugin. Rationale: Hosts or bindings may find it useful to construct |
| | 62 | an identifier to refer to groups for the same reasons this is useful for ports. |
| 68 | | two audio ports in a group forming a stereo stream. Both inputs and |
| 69 | | outputs can form a group, which allows describing to the host which |
| 70 | | outputs correspond to which inputs. In this case, outputs with a given |
| 71 | | role correspond to the inputs in the same group with that role (though |
| 72 | | the output and input roles of a group do not necessarily match). |
| | 67 | two audio ports in a group forming a stereo stream. Both inputs and outputs |
| | 68 | can form a group, which allows describing to the host which outputs correspond |
| | 69 | to which inputs. In this case, outputs with a given role correspond to the |
| | 70 | inputs in the same group with that role (though the output and input roles |
| | 71 | of a group do not necessarily match). The pg:source predicate can also be |
| | 72 | used to describe this correspondence between separate ports/groups. |
| 96 | | Indicates that this port group should be considered a "side chain" of some |
| 97 | | other group. The precise definition of "side chain" depends on the plugin, |
| 98 | | but in general this group should be considered a modifier to some other |
| 99 | | |
| | 96 | Indicates that this port or group should be considered a "side chain" of |
| | 97 | some other port or group. The precise definition of "side chain" depends |
| | 98 | on the plugin, but in general this group should be considered a modifier to |
| | 99 | some other group, rather than an independent input itself. |
| 107 | | Indicates that this port group should be considered the "result" of some |
| 108 | | other group. This property only makes sense on groups with outputs when |
| 109 | | the source is a group with inputs. This can be used to convey a relationship |
| 110 | | between corresponding input and output groups with different types, e.g. |
| 111 | | |
| | 107 | Indicates that this port or group should be considered the "result" of |
| | 108 | some other port or group. This property only makes sense on groups with |
| | 109 | outputs when the source is a group with inputs. This can be used to convey |
| | 110 | a relationship between corresponding input and output groups with different |
| | 111 | types, e.g. a mono->stereo plugin. |
| 128 | | Indicates that this port group should be considered the "main" inputs/outputs |
| 129 | | of the plugin, e.g. a stereo effect has a "main" group with 2 inputs and 2 |
| 130 | | outputs. A plugin MUST NOT have more than one :mainGroup property. High-level |
| 131 | | hosts that simply want to insert an plugin in a given stream should use |
| 132 | | |
| | 128 | Indicates that this group should be considered the "main" inputs/outputs of |
| | 129 | the plugin, e.g. it probably makes sense to just connect main groups and set |
| | 130 | some controls. A plugin MUST NOT have more than one :mainGroup property. |
| | 131 | High-level hosts that simply want to insert an plugin in a given stream |
| | 132 | should use this property to determine where the plugin 'fits'. |
