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
Describe the bug
The bug in question is that the VST plugin - BellSynth 2 specifically - is red in the plugin list and says that it couldn't be initialised. A similar error message pops up whenever I try dragging and dropping the DLL.
To Reproduce
Steps to reproduce the behavior:
Put BellSynth 2 in the path list
Go to the Plugin list
Do a scan
Scroll down to BellSynth 2 in the list
Expected behavior
Normally, it should just load up a window with BellSynth 2 ready.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: Windows 10
Version 22H2
Standalone or Plugin
It occurs in both the standalone Element application and the VST plugin version.
Additional context
The file name is TheoK_BellSynth_2.dll, and it is located at C:/Program Files/VstPlugins - it's not anywhere weird.
This very same plugin worked flawlessly in FL Studio, so it's likely not a problem with my VST plugin itself.
The text was updated successfully, but these errors were encountered:
Describe the bug
The bug in question is that the VST plugin - BellSynth 2 specifically - is red in the plugin list and says that it couldn't be initialised. A similar error message pops up whenever I try dragging and dropping the DLL.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Normally, it should just load up a window with BellSynth 2 ready.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Standalone or Plugin
It occurs in both the standalone Element application and the VST plugin version.
Additional context
The file name is TheoK_BellSynth_2.dll, and it is located at C:/Program Files/VstPlugins - it's not anywhere weird.
This very same plugin worked flawlessly in FL Studio, so it's likely not a problem with my VST plugin itself.
The text was updated successfully, but these errors were encountered: