Velato VS music21

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.

I chose Python as a programming language here because, as you could probably guess, there are myriads of libraries in Python for working with music. I found mingus to be the simplest for working with guitar chords and music21 for generating the piano score. It might be possible though to do everything with music21 only, because it's extremely powerful, but I found mixing the two libraries to be easier than implementing the functionality I needed from mingus with music21.

If you are interested in doing anything with Python, be sure to check out Music21, which has a lot of cool features — including doing twelve-tone matrix stuff like this — built-in.

http://web.mit.edu/music21/ Music21 documentation.

It's definitely a viable possiblity, and there's quite a few companeis already doing it. If you want to explore doing it yourself, I'd check out https://web.mit.edu/music21/ and build some basic models using LSTM etc. to have some fun using open source MIDI data sets like https://magenta.tensorflow.org/datasets/maestro .

A little manual, but music21[0] can do the analysis!

[0]: http://web.mit.edu/music21/

There's no universally accepted term for the latter concept that I know of. For example, the music21 music processing library calls the general class that includes notes, chords and rests Music21Objects, and you'd think they'd call them something better if they could.

This Python toolkit has support for analyzing folk tunes. https://web.mit.edu/music21/

(define-public music21 (package ... (build-system python-build-system) (arguments `(#:phases (modify-phases %standard-phases (replace 'check (lambda* (#:key tests? inputs outputs #:allow-other-keys) (when tests? (add-installed-pythonpath inputs outputs) ;; See: https://github.com/cuthbertLab/music21/issues/1164 (invoke "python" "-m" "music21.stream.tests"))))))) ...))