-
|
Hi, I'm in the last testing phases before releasing a CLAP version of a previously VST 2.4 plugin. So I might be asking a few questions later just to make sure I don't get something wrong. In clap_plugin_descriptor_t, is it OK to have an id with spaces. Like when instrument name actually contains spaces. Example: |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
It is not being prevented, yet, I would stick with a proper id string without spaces. Replace spaces with underscores if you want? |
Beta Was this translation helpful? Give feedback.
-
|
I see. Yeah I'll probably use underscores or even dashes. |
Beta Was this translation helpful? Give feedback.
-
|
The spec says "any uff-8 string is valid" so in theory your id could be `superAwesome MyThing 💯' and I know some of the plugin developers have made test plugin with names like that to stress test daws. But I agree with defiant nerd. For an id keeping in the ascii-no-spaces subset of UTF-8 makes it less likely your plugin is the one which leads to a DAW bug report :) |
Beta Was this translation helpful? Give feedback.
-
|
Thanks paul. Makes sense :) |
Beta Was this translation helpful? Give feedback.
The spec says "any uff-8 string is valid" so in theory your id could be `superAwesome MyThing 💯' and I know some of the plugin developers have made test plugin with names like that to stress test daws.
But I agree with defiant nerd. For an id keeping in the ascii-no-spaces subset of UTF-8 makes it less likely your plugin is the one which leads to a DAW bug report :)