OSC: Support addressing plugins by name #2011
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Otherwise a path like /Carlaz0/... works. Signed-off-by: Asahi Lina <[email protected]>
Signed-off-by: Asahi Lina <[email protected]>
Signed-off-by: Asahi Lina <[email protected]>
Owner
|
that makes sense actually, since plugin names are unique within a single carla instance we can indeed just use them. |
Author
|
Any chance this could be merged? ^^ |
Owner
|
Yes of course, I just want to give it a test myself first. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On a complex patchbay, it's very difficult to keep plugins at a known, consistent ID. Removing a plugin would shift the IDs of all subsequent plugins. This makes using OSC to control them very cumbersome.
Add support for addressing plugins by name, such as
/Carla/Audio Gain (Mono)/set_parameter_value. For complex patchbays, the user can then rename the plugins to have helpful names indicating their purpose (and, if desired, avoid spaces), making the OSC addressing more natural and less error-prone.