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
Briefly: I upgraded LMMS by selecting a newer version and kept a handful of older projects with the AuraPlug VST effect Red Skull, which functioned wonderfully in the previous version reported. Now, the VST does not load at all, which is shown:
Through reporting with a message box that "The following errors occurred while loading: the VST plugin RedSkull (x64).dll could not be loaded."
The following (portion) of console output appears, taking a sample project as an example:
@NewActiveXObject thanks for reporting this. I've reproduced and milestones this for the 1.3 release which we're working towards.
The 32-bit VST effect seems to work fine.
The 64-bit VST crashes and does NOT work.
For now, please switch to the 32-bit VST effect until we can find someone to debug this further and thank you for finding bugs with our nightly version, it's greatly appreciated! Please feel free to tag myself directly for more items that directly related to the nightly branch. If you're interested in getting formally involved with our testing team, feel free to ping me on Discord https://lmms.io/chat
System Information
Windows 10 (x64), Intel Graphics HD 5000
LMMS Version(s)
1.3.0-alpha.1.813+9cb3ae7
Most Recent Working Version
1.3.0-alpha.1.690+gd703f3915
Bug Summary
Briefly: I upgraded LMMS by selecting a newer version and kept a handful of older projects with the AuraPlug VST effect Red Skull, which functioned wonderfully in the previous version reported. Now, the VST does not load at all, which is shown:
Expected Behaviour
Red Skull should load.
Steps To Reproduce
Download the plugin from any trusted repository and select it from any instrument.
Logs
Click to expand
Screenshots / Minimum Reproducible Project
No response
Please search the issue tracker for existing bug reports before submitting your own.
The text was updated successfully, but these errors were encountered: