VSLilyPond VS Velato

I've been using this one:

https://github.com/lhl2617/VSLilyPond

Its a bit old, but works very well. I contributed a few fixes years ago to make the midi more reliable, depending on the type of keyboard you have

Recently, VSCode popped up a helpful dialog informing me there's plugins for editing *.ly files. I installed VSLilypond, and wow, its great. Automatic compile on save, synctex like features (click note to find where it is in source, run command on source to find respective note in PDF output), and more.

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.