Linux
Using IMFMSynth on Linux
Requirements, the files the installer places, and what to try when the editor does not open.
Requirements
- x86_64 with glibc 2.34 or later: Ubuntu 22.04 or later, Debian 12 or later, Fedora, RHEL / Rocky / AlmaLinux 9 or later.
- An X11 or XWayland session. The formats are CLAP and VST3.
- Checked in REAPER and Bitwig Studio (CLAP, VST3) and Ardour (VST3). arm64 Linux isn't supported.
Where the files go
- Plug-ins:
~/.clap/IMFMSynth.clapand~/.vst3/IMFMSynth.vst3. - Editor runtime:
/opt/IMFMSynth/uiwhen installed with sudo,~/.local/share/IMFMSynth/uiwhen sudo was declined. The plug-in looks in that order. - To remove the plug-ins and the editor runtime, run
./uninstall.shin the folder where you extracted the archive. It keeps~/.config/IMFMSynth(your presets, settings and license); delete that folder too if you want no trace.
The editor does not open
- Run
./install.shagain in a terminal. At the end it starts the editor runtime as a check and prints what is wrong and how to fix it. - To run the check by hand, start
imfm-ui --self-checkfrom the editor runtime folder above. - If you declined sudo, the editor runs without Chromium's sandbox, and correct operation isn't guaranteed. Run
./install.shagain and accept sudo. - If the DAW itself is a Flatpak, IMFMSynth works, but the editor runs without Chromium's sandbox inside Flatpak (the same mode as without sudo). A native package of the DAW is recommended.
- If the plug-in doesn't show up in the DAW at all, check
ldd --version: glibc must be 2.34 or later. - On a minimal Ubuntu install the editor may need
libgbm1. The installer prints this hint when a library is missing.
Still stuck? Write to support@imfm-synth.com with your distribution, your DAW and the output of imfm-ui --self-check.