LilyPond
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
3recommend
2warn against
Dec 4, 2025first mention
Aug 2, 2026latest mention
Why people recommend it
“I always considered it superior to Finale and Sibelius anyway.”
Show 1 more
“Lilypond isn't well-known enough!”
Caveats and dissent
“some serious flaws in LilyPond regarding Gregorian notation”
“Lilypond is a very good tool, but the part on Gregorian chant is not maintained”
Who recommends it in their own words
Threads where it came up
- The Gregorio project – GPL tools for typesetting Gregorian chant 2 mentions
- Twenty Years of RISC OS Open 1 mention
- The Git history command deserves more attention 1 mention
- Ask HN: What Are You Working On? (May 2026) 1 mention
- Experiments with Ableton-MCP 1 mention
- Programming languages used for music 1 mention
Data: lilypond.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 8
“I wonder if at some level of complexity the job would be better served by a markup language? https://lilypond.org”
“I always considered it superior to Finale and Sibelius anyway.”
“I don't know if you can write drum sheet music with it.”
“some serious flaws in LilyPond regarding Gregorian notation”
“Lilypond is a very good tool, but the part on Gregorian chant is not maintained”
“a VST that leverages an LLM that can create LilyPond format music”
“inspired by LilyPond”
“Lilypond isn't well-known enough!”