LMMS freezes on VST load

[jkl]

I seem to be having *exactly* the same problem as in this thread.
The only diffence is I'm on Xubuntu 15.04 64-bit, so if it's the same bug then it's not arch only. I first found this after upgrading to 15.04 64-bit (previously i was on 14.04 32-bit) and re-enabling the kxstudio repository (as I have used in the past to get regular updates). Just in case it was something in that version, I cloned the git repo and compiled from source, but I had the same issue, so:

Reproduction (same as on the other thread, but with git-master):
Grab the source off git (master branch) and follow the instructions at https://github.com/LMMS/lmms/wiki/Compiling-lmms
(i installed everything on the page and used "cmake .. -DCMAKE_INSTALL_PREFIX=../target -DCMAKE_BUILD_TYPE=DEBUG" for cmake)

open lmms
drag a VeSTige onto the song editor & open it
click on the little green folder icon
open dll (dialog closes and 'loading plugin' box at bottom left comes up, as in their screenshot)
then lmms freezes

From what i can tell, lmms will close if it recieves any signal after the freeze (i think, i tested quite a few), so no need to send SIGKILL. I tried loading multiple VSTs with Festige (from kxstudio repo) and it worked fine. I also tried loading a few VSTs through Carla (I installed Carla from kxstudio repo before compiling lmms) and that worked fine too (I had no sound from any of the VSTs, but they loaded fine), so i don't think it's WINE. I've tried both 32- and 64-bit VSTs with VeSTige, but neither work.

I tried to compile lmms 1.1.0 (from git, without carla), to test if anything had had changed to break lmms since kxstudio's latest version (I know i was on at least 1.1.0 from kxstudio repo before the Xubuntu 15.04 upgrade), but the problem is there too. I doubt it's anything in 15.04, so I believe it must be a 64-bit problem. The version of lmms in the default Xubuntu repos doesn't come with VeSTige (i believe it's so the lmms base doesn't depend on Wine), so i didn't try with that one, although that's a bit far back anyway ('1.0.3-5' according to apt).

I tested with Wine 1.6.2 for everything previsously mentioned, and with Wine 1.7.38 with lmms from git (master) as well, just in case, but that also failed.

Any ideas on what could be wrong and how to fix it? Any help appreciated.

[musikbear]

Any ideas on what could be wrong and how to fix it? Any help appreciated.

looks like you have been trying every possible way, so im afraid not - However you dont tell us, if you have tried a specific VST, or if the failing one is in the tested VST list?
https://lmms.io/documentation/Tested_VSTs
I like to tackle stuff like this through Synth1 tests, but any one on the list would do, i guess.
But its darn difficult when it comes down to linux-fails, because the different installations are not identical :/

[jkl]

I've tested with two VSTs from that list, including synth1 (Version 1.13 beta3, 32- and 64-bit). I've also tested with DSK AkoustiK GuitarZ, but both freeze lmms. Most of the VSTs i tried aren't on that list. I'm still using lmms from git (master branch) and wine 1.7.38.

[musikbear]

I'm still using lmms from git (master branch)

I dont know exactly how the linux versions are managed, but Master is in general not production-ready.
You should only use the official tested and published versions, linked to from this
https://lmms.io/download/#linux
page
The repository Master, is a 'work in progress', and not meant for normal use.

[jkl]

I dont know exactly how the linux versions are managed

Xubuntu is derived from Ubuntu. Both Ubuntu and Xubuntu manage packages in the same way and get packages from the same repositories, and the lmms package in Ubuntu's repositories does not get updated very often. The latest version of lmms in the Ubuntu Universe repository (which contains packages supported by the community, like lmms) is lmms 1.0.3, which is old (9 Jul 2014), and doesn't come with VST support (no VeSTige). Unfortunately, the 'lmms-vst-full' package that contains VeSTige is only available from three places (as far as I can tell): the Master branch of lmms on Github, the lmms releases on Github, or from other repositories like the kxstudio repository. However, i'd rather not re-add the kxstudio repo to my system again (removing it is hard if anything like this happens again). I searched a while ago, but couldn't find any other reliable repositories that distibute lmms and VeSTige, so i'm left with Github as the only source of lmms.

Master is in general not production-ready

I am aware of this, I was just testing with Master to see if the problem was still there. As I said before, I did test with lmms 1.1.0 as well (the tarball on the 'releases' page on lmms's git repository).

You should only use the official tested and published versions

I know this is best, the only reason i wasn't using the latest stable version is for the reason above. I see the latest version for Windows on the Windows download page is lmms 1.1.3, so, i went back to wine 1.6.2 (odd-numbered sub-versions in WINE are development versions, so 1.7.x is a development version), grabbed lmms 1.1.3 from Github and tested synth1 32- and 64-bit and DSK AkoustiK GuitarZ, but both freeze lmms.

If it's best, I will stay on lmms 1.1.3 and the stable version of WINE for any further testing.

[zonkmachine]

Hello!

I first found this after upgrading to 15.04 64-bit

Did you do a reinstall or go through the update manager?

To find out on what commit (where in the master branch) you are, please give us the line from this command (run it in your lmms source tree):

Code: Select all

git log -1 | grep commit

Can you also give us some output, error messages, from the console when you run LMMS/vestige. If it's long output, please put it within "

Code: Select all

" tags.
 :) 

For the record. Here's the Ubuntu bug report discussing LMMS VST support on 64-bit machines:
https://bugs.launchpad.net/ubuntu/+source/lmms/+bug/1182604

[jkl]

Did you do a reinstall or go through the update manager?

I did a full reinstall, well, two actually (the second one was to remove the kxstudio repo).

The last commit before I cloned:

Code: Select all

user@computer:~/Source/lmms-master$ git log -1 | grep commit
commit 979fa2fb930f0b95ec408082540124bbb265b2db

As for any output, it's about as unhelpful as it could be:

Code: Select all

user@computer:~/Source/lmms-master$ ./target/bin/lmms
Notice: could not set realtime priority.
Killed

I assume you meant the output from the git Master build, although lmms 1.1.3 outputs the same two lines. I'm not sure if that's all the output it normally gives, or if 'cmake' didn't configure for debugging correctly. Is the the '-DCMAKE_BUILD_TYPE=DEBUG' option of cmake meant to add additional debugging output, or something else?

Thanks for the bug report. I think i've seen it before, but I had forgotten about it.

[zonkmachine]

Did you do a reinstall or go through the update manager?

I did a full reinstall, well, two actually (the second one was to remove the kxstudio repo).

When/if you copied your /home/ ~ folder over to your fresh install it contained, among other things, a config file for lmms '.lmmsrc.xml'.
If you haven't tried this already, rename that file to .lmmsrc.xmlBACKUP and restart LMMS.

As for any output, it's about as unhelpful as it could be:

Code: Select all

user@computer:~/Source/lmms-master$ ./target/bin/lmms
Notice: could not set realtime priority.
Killed

Yes, not much info there. I'm not sure this means either LMMS or Wine behaved bad and was terminated by the kernel but usually you get more verbose output.
Try:

Code: Select all

less /var/log/kern.log | grep lmms

And see if it gives something.

Notice: could not set realtime priority.

This just means you don't have a 'real time' kernel.

[jkl]

When/if you copied your /home/ ~ folder over to your fresh install it contained, among other things, a config file for lmms '.lmmsrc.xml'

I never copy configuration files over from an old system when i update, only my own files, just in case they break things. Although, I will have re-configured lmms in the same way as before. To test, I deleted the config file (I can re-configure again later), restarted lmms, clicked 'ok' to accept the default settings and tried again with synth1 32- and 64-bit and DSK AkoustiK GuitarZ (as they're both on the 'Tested VSTs' list), but it didn't make any difference.

After some testing, I found I get this output when opening the settings dialog box:

Code: Select all

Notice: could not set realtime priority.
VST sync support disabled in your configuration
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_route.c:947:(find_matching_chmap) Found no matching channel map
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=No such file or directory)
attempt to connect to server failed
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_route.c:947:(find_matching_chmap) Found no matching channel map
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=No such file or directory)
attempt to connect to server failed

This is after deleting my config file, although it probably happened before as well.

Also, when I have the setting 'Sync VST plugins to host playback' turned off I get this output:

Code: Select all

Notice: could not set realtime priority.
VST sync support disabled in your configuration
RemotePluginClient::shmget: No such file or directory
Killed

The 'VST sync support disabled in your configuration' is printed when the program opens and the 'RemotePluginClient::shmget: No such file or directory' is printed when you try to open a VST, just before lmms freezes.

I'm not sure this means either LMMS or Wine behaved bad and was terminated by the kernel

To clarify, I tell the kernel to terminate or kill the process myself since lmms just freezes.

After the tests above, "less /var/log/kern.log | grep lmms" doesn't give anything.

Notice: could not set realtime priority.

This just means you don't have a 'real time' kernel.

I thought it had something to do with permisions, I didn't know you needed a real-time kernel. Useful to know.

[jkl]

bump