Fail to load ANY VST plugin on LMMS (Manjaro)

Having trouble with LMMS? Ask about it here.
The problem is as follows: I attempt to load a 64-bit DLL VST in LMMS via VeSTige, expecting it to load normally. However, it does not, and I mean, nothing, no errors, no crashes, it just freezes for a short time and not loads anything, staying on the same "No VST-plugin loaded". I'm using the latest .AppImage LMMS version from the official website (LMMS 1.2.2 64-bit as of now), when running the AppImage thru the Terminal, I get this error:

Code: Select all

007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
002c:fixme:ver:GetCurrentPackageId (000000000031FDB0 0000000000000000): stub
wine: failed to start L"Z:\\tmp\\.mount_lmms-1Jy97wb\\usr\\lib\\lmms\\RemoteVstPlugin.exe.so"
Application could not be started, or no application associated with the specified file.
ShellExecuteEx failed: File not found.

00d0:fixme:ver:GetCurrentPackageId (000000000031FDB0 0000000000000000): stub
remote plugin died! invalidating now.
0034:fixme:ver:GetCurrentPackageId (000000000031FDB0 0000000000000000): stub
003c:fixme:ver:GetCurrentPackageId (000000000031FDB0 0000000000000000): stub
Remote plugin did not connect.

Meaning that some /tmp files were not initialized. Trying to load the same VST plugin on Nightly build of LMMS from the same official website (LMMS g7c6ade573 as of now), I get similar error:

Code: Select all

007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
002c:fixme:ver:GetCurrentPackageId (000000000031FDB0 0000000000000000): stub
wine: failed to start L"Z:\\tmp\\.mount_lmms-1PvW2ji\\usr\\lib\\lmms\\RemoteVstPlugin64.exe.so"
Application could not be started, or no application associated with the specified file.
ShellExecuteEx failed: File not found.

00d0:fixme:ver:GetCurrentPackageId (000000000031FDB0 0000000000000000): stub
Remote plugin exit code:  1
remote plugin died! invalidating now.
0034:fixme:ver:GetCurrentPackageId (000000000031FDB0 0000000000000000): stub
003c:fixme:ver:GetCurrentPackageId (000000000031FDB0 0000000000000000): stub
Remote plugin did not connect.
I appear to have the latest wine version:

Code: Select all

$ wine --version
wine-8.8
Here's my system specs:

Code: Select all

Operating System: Manjaro Linux 
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 6.3.5-2-MANJARO (64-bit)
Graphics Platform: X11
So how do I get temporary files of LMMS to initialize right and\or avoid getting this error?
You cant use 64bit vst yet in LMMS on Linux.

I cant recall is this is a Vestige or a wine limitation.


https://github.com/LMMS/lmms/issues/4103
Gps wrote:
Tue Jun 13, 2023 2:17 pm
You cant use 64bit vst yet in LMMS on Linux.

I cant recall is this is a Vestige or a wine limitation.


https://github.com/LMMS/lmms/issues/4103
Well, the issue has nothing to do with 64-bit plugins. The behaviour with 32-bit ones, BTW, is no different, same behaviour - zero changes in VeSTige, terminal gives out (nearly) the same:

Code: Select all

007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
002c:fixme:ver:GetCurrentPackageId (000000000031FDB0 0000000000000000): stub
0034:fixme:ver:GetCurrentPackageId (000000000031FDB0 0000000000000000): stub
wine: failed to start L"Z:\\tmp\\.mount_lmms-1ARFQzs\\usr\\lib\\lmms\\RemoteVstPlugin.exe.so"
Application could not be started, or no application associated with the specified file.
ShellExecuteEx failed: File not found.

00d8:fixme:ver:GetCurrentPackageId (000000000031FDB0 0000000000000000): stub
remote plugin died! invalidating now.
003c:fixme:ver:GetCurrentPackageId (000000000031FDB0 0000000000000000): stub
Remote plugin did not connect.

So as you can see, no, It's not bit-related problem.
You have about two options.

First and easiest is to download the LMMS aplmage file and see if that works.
https://lmms.io/download#linux

Download the file, and then right click to make it executable.

Second option is to talk to the manjaro lmms package builder.

I do not know why, but it seems that about all distro fail at compiling LMMS right.

I am on openSUSE, and was using the aplmage version, not the official opensuse package.
For me these days there is a better solution though, a music repository. GeekosDaw

it gives me a fully working LMMS with Carla.

This repository exist, because of the issues with the official opensuse package.
https://geekosdaw.tuxfamily.org/en/
Gps wrote:
Tue Jun 13, 2023 5:43 pm
You have about two options.

First and easiest is to download the LMMS aplmage file and see if that works.
https://lmms.io/download#linux

Download the file, and then right click to make it executable.

Second option is to talk to the manjaro lmms package builder.

I do not know why, but it seems that about all distro fail at compiling LMMS right.

I am on openSUSE, and was using the aplmage version, not the official opensuse package.
For me these days there is a better solution though, a music repository. GeekosDaw

it gives me a fully working LMMS with Carla.

This repository exist, because of the issues with the official opensuse package.
https://geekosdaw.tuxfamily.org/en/
In the beginning of the thread I made it very clear that I HAVE tried using .AppImage from the official website - that was the only way to capture the issue (the repository version didn't output any of the wine errors on the other hand). So I guess the only acceptable choice is to compile LMMS from the source...
Oops, and yes you did.

Then it might be your best option to compile LMMS yourself.

Its a lot of work to install all dependencies, but the process by it self is not that hard.

Or use a different distro, but then the big question becomes which one.

Good luck with compiling.

https://github.com/LMMS/lmms/wiki/Compiling
At least manjaro is listed there.