-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
problems loading the menu, from the Element plugin (vst) #6674
Comments
The old JUCE drop-down menu bug. It's described here and has been fixed in JUCE but projects depending on that library need to update to a later version. The workaround with No embedding above is the way to go. Try and see if there is a newer version of Element around. Here are some development versions of Element-0.47.0: https://builds.kushview.net/#element/windows/ Closing as duplicate of #3918 |
Element issue tracker here: https://gitlab.com/kushview/element/-/issues |
I'm wondering if there's some plan for LMMS to go around this? A lot of my VSTs are old or unmaintained, and there is no likelihood of a JUCE version update. |
Discussion of a possible workaround starts here: #3918 (comment) |
Hello, thanks for the excellent work done in lmms, I have used the KV_Element plugin (https://kushview.wpengine.com/element/) and when loading, it loads them well, the problem is that when you secondary click on the vst (in the interface) does not show the drop-down menu well, it shows it and closes it fast, which does not allow the menu to be displayed well, it does the same in Element FX, (vst effects) I suppose it is a problem in vestige, I have checked it with nanohost (https://www.tone2.com/nanohost.html) and DarkWave Studio 5.9.4 (https://www.experimentalscene.com/software/darkwave-studio/) and on both daws, it shows the menu alright giving secondary click, also when resizing the element interface, it is not possible,
is not allowed by vestige, which limits the size of the plugin interface or vst. thank you.
here the reference image of the open menu, in nanohost.

The text was updated successfully, but these errors were encountered: