XIxiaoyu2006·Sep 6, 2026Submission
LMMS 1.3.0-alpha.2 Release (after 5 yrs of last release)
2 points · Open discussionLMMS
lmms
C++2021–2026
LMMS / lmms
lmms
Cross-platform music production software
5Distinct people
6Mentions
0Explicit recommenders
10.6KGitHub stars
What to know before exploring
What it is
Cross-platform music production software
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year6 dated mentions
Observed mentions: 2021-03-01 15:40:30 UTC to 2026-09-06 05:25:54 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
6 sourcesIt doesn't look like LLMS supports VST3 [1], but we had a report of the Bitwig Linux version looking for a VST3 bundle, the new recommended format, instead of a single library file with a ".vst3" extension, so of I'm wrong the issue could be that as well.
Anyway, we're looking into building for LADSPA or LV2 for a future update.
[1] https://github.com/LMMS/lmms/issues/4715
In Show HN: Anyma V, a hybrid physical modelling virtual instrument.. why would you build LMMS? you can just download the latest appimage and run it: https://github.com/LMMS/lmms/releases
In Wine 8.5Wayland Problem: Alt-Tabbing between applications makes mouse input disappear
3 points · Open discussionIf you wrote a software that worked with soundflower it means that at some point you used to call either the CoreAudio API directly or any abstraction on top of it (RtAudio, PortAudio, ...). Thus harder to port to another OS :-)
Here the idea is to write the algorithms in a way that is more future-proof, by not having them to depend on any run-time API, just a generic specification (given as a set of C++20 concepts). This way the algorithms will still be useful in 10 years when everyone has moved to API N+1, unlike a metric ton of existing audio software which depends on a specific audio / media-object API for no good reason (today ! When they were written C++ wasn't advanced enough to allow this at all)
- all the objects in https://github.com/pcastine-lp/LitterPower for instance
- all the algorithms in https://github.com/MTG/essentia/tre
Read the rest
e/master/src/algorithms
- ditto for https://github.com/cycfi/q/tree/master/q_lib/include/q
- ditto for all the VCV algorithms: https://github.com/VCVRack/Fundamental/tree/v1/src
- ditto for all the Bespoke objects: https://github.com/BespokeSynth/BespokeSynth/tree/main/Sourc...
- ditto for all the LMMS plugins: https://github.com/LMMS/lmms/tree/master/plugins
etc etc, there's a couple hundred of those, which always depend on some API and are thus not easily portable across environments: if tomorrow you want to make an audio software and want to use one of the, say, VCVRack plug-ins you're going to have to bring the whole VCV run-time API along.
Related projects are Faust (https://faust.grame.fr/) and SOUL (https://juce.com/discover/stories/soul-first-public-beta-rel...) but they both are domain-specific languages with their own compilers. I wanted a pure-C++ thing instead, which allows to call directly native code, and enables more than just generic audio processing: unlike Faust and SOUL (last time I checked) it's possible to make a message-based object for Pd or Max, not just an audio filter or synthesizer.
My end goal for this is that when I make an object for the main software I'm developing, ossia score (https://ossia.io) then the whole media arts community can benefit :-)
LMMS/lmms: Cross-platform music production software
3 points · Open discussion