Friday 30 March 2007 — This is over 17 years old. Be careful.
LilyPond is a music typesetting system. They take their chosen problem domain very seriously. For example, in Obsessed with putting ink on paper, they explain the challenge. One of their first examples shows two different renditions of the same music, one “good”, one “bad”. To my eyes, they are identical.
I don’t need to typeset music, but I appreciate the complexity and passion of the LilyPond work. Even simple music is more complicated to set properly than text, and complex music is really complex.
Comments
The most cringeworthy difference I see is mostly in measure 17, because the bars alternate between being above and below, whereas the notes themselves are not that different. Next is measure 19, because the lack of slant on the bars is particularly glaring.
The interface may not be the best for musicians; it reminds me mostly of LaTeX. But, as you mentioned, it can handle extremely complicated notation and the output is very high quality. I'm currently (sort of) working on an optical music recognition program and eventually want it to emit LilyPond code.
line 17 seems to be missing them as well....
something tells me this wouldn't work well in unicode....
http://www.jbrowse.com/text/unij.html
I really like this article, it reminds me of what we try to achieve when doing "good design".
Side note: Your comment system does not like non ascii characters.
Add a comment: