opensheetmusicdisplay VS Velato

On a related note, VexFlow is a project for rendering music notation in the browser.

https://github.com/vexflow/vexflow/

OpenSheetMusicDisplay is a higher-level library that uses VexFlow to render entire MusicXML documents.

https://github.com/opensheetmusicdisplay/opensheetmusicdispl...

Not mentioned in the article, but a couple of notable open-source libraries for rendering music notation in the browser:

A JavaScript library for rendering music notation and guitar tablature - https://github.com/0xfe/vexflow

OpenSheetMusicDisplay renders sheet music in MusicXML format - https://github.com/opensheetmusicdisplay/opensheetmusicdispl...

Hi, I'm the creator of Velato. I will be reworking the website to include more examples later this year. In the mean time, the latest version of the compiler is on github: https://github.com/rottytooth/Velato

No one has yet written a quine although I would love to see one -- perhaps outputting its representation in lilypond format.

In 2009, I made Velato, an esolang where code is written in pitch values (https://github.com/rottytooth/Velato) encoded as MIDI files. So sort of the opposite of writing algorithmic music (where the human programmer writes music to satisfy conditions of the program). Before switching to LilyPond, I'd used GUIDO with a GUIDO-to-MIDI generator, but it was always awkward. Part of the challenge is that notes can be sounded simultaneously to make the score work better musically, but still need to appear in the correct sequence in the MIDI file for the program to succeed; something that LilyPond handles correctly. There's a transparency to how LilyPond functions that is not always there with programs that try to be "helpful" and clean-up or rearrange information.