You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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?
The text was updated successfully, but these errors were encountered: