# トラブルシューティング ## Audio Troubleshooting ### My Audio is Crackling! #### Buffer Size Your [buffer size](/user-manual/jp_2/getting-started/setup.md#buffer-size) may be too small, resulting in buffer underruns. To fix this, increase your buffer size. Note that this will increase latency. #### Audio Interface Certain [audio interface configurations](/user-manual/jp_2/getting-started/setup.md#audio-interface) 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. #### Track Volume 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). #### Volume Envelopes 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. ### I Can't Hear Anything! #### Dummy Certain [audio interface configurations](/user-manual/jp_2/getting-started/setup.md#audio-interface) (specifically Dummy) just don't work sometimes. If you are on macOS or Windows, make sure you have SDL selected. Try to avoid PortAudio if possible. #### JACK-transport 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 `qjackctl`. ### The Audio Lags or is Delayed! #### Buffer Size [Buffer size](/user-manual/jp_2/getting-started/setup.md#buffer-size) is directly related to latency. If you can, try decreasing your buffer size to minimize latency. ## Development Troubleshooting ### LMMS Segfaults and There are No Error Messages on the Console! Use the GNU Debugger to run LMMS again, and try to replicate the crash: ``` $ gdb lmms GNU gdb 6.X Copyright (C) 2006 Free Software Foundation, Inc. ... (gdb) r Starting program: lmms ... ``` If a segfault happens, LMMS will freeze and you'll get some information on the terminal. Entering `bt` or `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. ### I Compiled LMMS With VST-Support, but it Doesn't Work at All! 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). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.lmms.io/user-manual/jp_2/getting-started/troubleshooting.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.