Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Port names in exported LV2 plugins don't take scope into account #203

Open
bgribble opened this issue Oct 6, 2014 · 0 comments
Open

Port names in exported LV2 plugins don't take scope into account #203

bgribble opened this issue Oct 6, 2014 · 0 comments
Labels
Milestone

Comments

@bgribble
Copy link
Owner

bgribble commented Oct 6, 2014

When exporting a patch as an LV2 plugin, the lv2:symbol (unique short name) of each inlet and outlet is taken from the MFP object's name. These names are only guaranteed to be unique if the scope is taken into account.

This is a real problem with the @clonescope method, which makes multiple identically-named copies of processors, one per scope.

Currently there's no real way to pass patch initargs to an LV2 plugin, and the inlets/outlets have to be fixed at plugin-save-time so the manifest.ttl can be created properly, so there's not a real use case for loadbang @clonescopes in plugins like there is in regular patches. So this is more a theoretical problem than a practical one until I see a specific use case that breaks.

@bgribble bgribble added the bug label Oct 6, 2014
@bgribble bgribble added this to the mfp 0.06 milestone Oct 29, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant