2 ms·
This is interesting, thanks! I use lilypond heavily, but not really as part of the composition workflow. So you are able to work in musescore, export, and pull
by tunesmith 4y ago
This is interesting, thanks! I use lilypond heavily, but not really as part of the composition workflow. So you are able to work in musescore, export, and pull the results into lilypond? I didn't think the musicxml story was very strong for lilypond.
- gnulinux 4y agoUnfortunately lilypond doesn't support musicxml at all, which is a bummer. I do the opposite route. MuseScore -> musicxml -> my script -> lilypond/musicxml -> PDF/MuseScore. I need this because, sometimes I want auto-generated annotations to my score. Say I write a phrase in MuseScore, I'm interested in the script adding a text with chord names, or pitch Set Class etc. MuseScore can do this with plugins, but I personally find MuseScore plugin system very buggy and hard to program. Python is much much much better and musicxml is pretty easy to deal with.