Using VSTs freezes LMMS

[Naride]

I tried using the 32 bit version instead, and it worked great. Moving projects over from the yum distro to the WINE version went much smoother than I had expected, and Synth1 loads with no complaining.

So for anyone who happens to have this problem: If you have Fedora (or some other hard-to-work-with flavor of Linux) and you're trying to make VSTs work with the apt-get/yum/dnf distro of LMMS, here's your answer:

You can't. Use WINE instead, and download the 64bit or 32bit versions of LMMS, depending on your WINE build.

However, there's still one problem for me: The VSTi window isn't working.



The normal display flashes for a fraction of a second when I open the window, then it changes to whatever was behind it when it opened. Only individual components of the regular display show up, and that's only when they change (like if I moved my mouse over a control and it highlighted itself, that control would show up)

The main problem has been solved, and this new problem will probably prove to be nothing more than a minor annoyance, but any help you can offer would be appreciated.

Update on new problem: I ran LMMS in terminal, and I discovered that every time that I move my mouse over the VSTi window, the debug is flooded with this one line:

Code: Select all

fixme:class:CLASS_GetClassLong offset -12 (GCLP_HCURSOR) not supported on other process window 0xe004a

I don't know if this is relevant, I guess it might be time to get a new graphics driver lol

[Gps]

lmms.exe on Linux ?

Is that supposed to be there ?

WINE is a tool that you can use to run Windows programs in Linux in the same manner that Windows would.

(Correct me if I'm wrong.)

You are right, but I am a bit confused.

I run LMMS on Linux the native version. I only use wine to load the vst ( .dll file)

I do not run lmms through wine. OpenSUSE leap 42.1

I am a Linux fan, but get rather disappointed by how many people seem to have issues with lmms on Linux.
Have you tried talking to the fedora guys (the package builders)

I had to do that ones on openSUSE, and why I am telling this, the first question I got back from them: What is not working, and what is lmms supposed to do ?
They build packages but don't have time to test program like lmms in depth.
So they check if it starts and then they are happy.

They need us, the users to tell them, if vst is missing from lmms and or their wine version is causing issues.

https://admin.fedoraproject.org/pkgdb/p ... rpms/lmms/

[musikbear]

Use WINE instead, depending on your WINE build.

No no no Dont run windows-lmms through wine on your linux!
No just as Gps says, you only run Vestige through WINE, not LMMS!

However, there's still one problem for me: The VSTi window isn't working.

Yes, bevause you have win-lmms on linux

The main problem has been solved

No it has not

and this new problem will probably prove to be nothing more than a minor annoyance,

You completely looses all of the options to automate -Not trivial!

debug is flooded : I don't know if this is relevant,

very relevant

I guess it might be time to get a new graphics driver lol

No

You need :
Safecopy your own stuff, and De-instal everything you have now
then
FEDORA WINE for 64 bit (because your box+ fedora is 64 bit -right???)
LMMS for LINUX-Fedora (Contact pack-man)

I removed 'solved' because others should not follow your method. Only Vestige should run through WINE

[Naride]

Oh.

Now I feel even worse.

I'm in uncharted territory here, plus I'm still no less a nubcake than I was a year ago, so can you give instructions on how to run only VeSTige with WINE?

[Naride]

I tried "sudo lmms" just to see what would happen, and it actually seems like it would work better.

Here are the debug messages that I got:

Code: Select all

VST sync support disabled in your configuration
fixme:winediag:start_process Wine Staging 1.7.55 is a testing version containing experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.

It looks like it's running the VST separately with wine. (I'm almost certain of this because I always get the NVIDIA driver error message when Wine is started, but it didn't give me the message before I tried to load the VST.) Whereas, when running it normally, Wine doesn't even start. No debug messages, nothing. So I know for a fact that it's doing something this time.

However the VST still won't load.

These are the possible problems that I thought of off the top of my head:
- "VST sync support disabled in your configuration" - probably need to change that, derp (nope didn't do anything)
- I have an unstable version of Wine, apparently
- Broken NVIDIA driver (very, very highly unlikely)
- I'm trying to use a VST in my normal lmms folder while running lmms as root
- I'm still being a doofus and making a big deal over the completely wrong "solution"
- I'm running the .dll inside the Synth1 folder (which I'm pretty sure is the correct way to do it, but hey, what do I know)

This is probably a very bad idea. I probably need to stop

[musikbear]

This is probably a very bad idea. I probably need to stop

Before giving up i think you should contact pac-man for your distro.
Inform them that the distro does not support lmms, and ask them to read this thread.
They need to know that there are modules missing in the fedora distro

Unfortunately its all jibberish to me, cause im not using linux, as i told you. Contact pac-man, they are usually happy to help, because it help themself

[Gps]

On modern Linux distro's it should be as easy as adding a repository then download and install lmms and wine.

If its not working tell the guys who build the package, I already found the guy to contact for you.

The only other good option you have is to compile lmms yourself, but I would not advise that.
Also why make it hard for yourself if emailing the package guys will solve it.

The openSUSE guys were happy with me telling them it was not working, I am pretty sure the fedora guys will react the same way.