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

Allow URI to be specified in PlugData #2056

Open
hellocatfood opened this issue Jan 28, 2025 · 2 comments
Open

Allow URI to be specified in PlugData #2056

hellocatfood opened this issue Jan 28, 2025 · 2 comments

Comments

@hellocatfood
Copy link

In PlugData when exporting a patch to a plugin the plugin URI cannot be fully specified. Instead the project name is appended to the default URI of urn:hvcc:.

Can an option for specifying the URI name be added to the GUI of plugdata?

@dromer
Copy link
Contributor

dromer commented Jan 28, 2025

It can certainly be added, however there are many more options missing and we'll need to make some choices of what makes sense.

URI is only used for LV2 plugins, for CLAP you need the plugin_clap_id field. If we add one we should also add the other.
This can quickly spiral into an overload of additional/optional input fields which will clutter the UI ever further.

My proposal would be to instead allow the entire section to be overridden by pointing to a json file where the user can use all the available definitions. This adds much more flexibility without sacrificing usability in the UI.

Would that work for you?

@dromer
Copy link
Contributor

dromer commented Jan 28, 2025

An example json that uses nearly all the options: https://github.com/Wasted-Audio/wstd-3q/blob/master/wstd_3q.json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants