I added a module to pyScore for generating LilyPond's input format. This means that it is possible to use LilyPond for typesetting GUIDO “Basic” scores, as an alternative to the GUIDO NoteServer.
See the examples page for some conversion examples and information on the progress so far.
Summary:
This project was my seminar work for MUMT 611 in Winter 2006. This is a detailed report of the project progress, from the end of that semester. It applies to version 0.4.0-ly.
Paper:
This paper was published in the proceedings of ISMIR 2006, in Victoria, BC.
Results & Examples:
A site showing auto-converted examples is here: http://www.music.mcgill.ca/~sinclair/ly4pyscore
As you can see, results are mixed, but many features are supported. Some additional work is definitely needed, however. Eventually it would be nice to be able to import LilyPond files as well, although this could be quite challenging, since there is often data in LilyPond files that is not semantically tagged. For example, many tweaks in LilyPond consist of sending escaped commands to the Scheme back-end, which presents a serious problem in interpreting these files without pretty much completely re-implementing LilyPond.
Software (Python source, cross-platform):
Patch for the current pyScore CVS:
Apply with these commands:
wget http://www.music.mcgill.ca/~sinclair/pyScore-0.4.0-ly.patch cvs -d :pserver:anonymous@cvs.sf.net:/cvsroot/pyscore login cvs -d :pserver:anonymous@cvs.sf.net:/cvsroot/pyscore co pyScore cd pyScore; patch -p1 <../pyScore-0.4.0-ly.patch
Alternatively, here is a pre-patched version: