Make sure you are running the latest version of LMMS before troubleshooting issues. The latest version can be found at https://lmms.io/download.
Some users report that they can't save their settings. This is a recurring Windows issue, with reason not known in depth. To solve this problem, follow these steps:
Close LMMS. Make sure nothing from LMMS is running in the background. You can look for this in your "Task Manager". (If you don't know how to use "Task Manager", restarting your PC is a good alternative.)
In versions older than Windows 8, "Documents and Settings" is the folder you are looking for. In Windows 10, look in your "C:\Users\<Username>\. There is a file called
Use the search tool to find this file. .lmmsrc.xmlYou can't rename this file, but you can move it.
Move it to one of the folders you have there, e.g. plugins. Now restart LMMS.
You should be now asked to enter new settings, and these settings should be persistent.
A terminal command version of this process exists:
Run CMD as administrator
Paste this command:
move %USERPROFILE%|.lmmsrc.xml %USERPROFILE%|.lmmsrc.xml.bak
Try adding exceptions in your antivirus for files the project depends on, such as:
Plugins and their related data
Your buffer size may be too small, resulting in buffer underruns. To fix this, increase your buffer size. Note that this will increase latency.
Certain audio interface configurations don't play nice with LMMS on some systems. If you are on macOS or Windows, make sure you have SDL selected. On Linux, if PulseAudio is producing these unwanted artifacts, try ALSA instead.
Your audio within LMMS may be too loud, resulting in digital clipping. This can be fixed by reducing the volume of the instruments in LMMS (either with the "VOL" knobs or through the mixer).
If an instrument has attack or release values small enough, the rapid change in volume can sound like clicks or pops at the beginning or end of each note. Increasing the attack and release values for the culprit instrument's volume envelope can fix this kind of clicking.
Certain audio interface configurations (specifically Dummy) just don't work. If you are on macOS or Windows, make sure you have SDL selected. Try to avoid PortAudio if possible.
If you have JACK selected as your audio interface and you are experiencing no audio output, JACK-transport might not be running. Start an application like
qjackctl and click on "play" or its equivalent. LMMS should automatically should start JACK-transport on startup, but this fails on some systems.
You may also need to connect LMMS to your sound card, using the patch bay in
Buffer size is directly related to latency. If you can, try decreasing your buffer size to minimize latency.
Try using a shell script:
#!/bin/bashexport QT_AUTO_SCREEN_SCALE_FACTOR="0"export QT_SCREEN_SCALE_FACTORS="eDP-1=2.5;HDMI-1=2.5;DP-0=2.5".<absolute path to lmms AppImage>
chmod +x <script name> and then make a symlink in a desired location.
Use the GNU Debugger to run LMMS again, and try to replicate the crash:
$ gdb lmmsGNU gdb 6.XCopyright (C) 2006 Free Software Foundation, Inc....(gdb) rStarting program: lmms...
If a segfault happens, LMMS will freeze and you'll get some information on the terminal. Entering
bt full will show a backtrace you can report.
Make sure you have debugging symbols in LMMS. That usually means compiling with the
-g flag and not stripping the symbols afterwards.
Make sure you didn't pass
-fomit-frame-pointer in a FLAG-parameter to configure. This is known to lead to an unusable LVSL (LMMS VST Support Layer).