Exporting PlugData GUI to VST3 #2368
Replies: 1 comment 3 replies
-
|
Short answer: no Long answer: we are working on a feature that can export basic control and UI elements. You can see an example implementation here: https://github.com/Wasted-Audio/pdvg-example-plugin It will only be possible to assign very specific controls and some other elements: https://github.com/Wasted-Audio/PDVG#objects
If you enable GUI export right now you will get a generic Dear ImGui based UI. Using manual adjustments to the generated C++ code you can get some very compelling UIs -> https://github.com/Wasted-Audio/wstd-fl3ngr |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I'm working on a project in PlugData and I've created a custom GUI using the [popmenu] object. Everything works correctly inside PlugData, but when I export the project (especially as a VST3 plugin), the GUI is not included or does not appear as expected.
I have a couple of questions:
Is there currently a way to export a PlugData patch as a VST3 while preserving the custom GUI (including [popmenu] and other GUI objects)?
If this is not yet supported, is it planned for a future update?
Are there any recommended workarounds for creating a plugin with a functional custom GUI?
I'd appreciate any information about the current limitations and the roadmap regarding GUI export for VST3 plugins.
Thank you for your work on PlugData!
Beta Was this translation helpful? Give feedback.
All reactions