OrchestralLily: A Package for Professional Music ... - LilyPond

8 Generating a Template
OrchestralLily also provides a template-based
script to generate all files required for a full edition
of a score: The score information, including
instrumentation, movements, voices with lyrics,
etc., are defined in one input file. After running
the generate_oly_score.py script, one has the
full set of files for the edition, including a Makefile.
Only the music, lyrics, and the actual text
of the preface and the critical report need to be
filled in. Running make will always update all
scores and produce ready-for-print files for all
desired scores and instrumental parts.
A typical input file for the cadenza example
used above is shown here:
{
” o u t p u t d i r ” : ”Cadenza ” ,
” v e r s i o n ” : ” 2 . 1 3 . 1 1 ” ,
” template ” : ” EK Full ” ,
” d e f a u l t s ” : {
” t i t l e ” : ”A t e s t f o r O r c h e s t r a l L i l y ” ,
” composer ” : ” Reinhold Kainhofer ” ,
” composerdate ” : ”1977 −” ,
” year ” : ”2009” ,
” p u b l i s h e r ” : ” E d i t i o n Kainhofer ” ,
” scorenumber ” : ”EK−1040” ,
”basename ” : ”Cadenza ” ,
” p a r t s ” : [
{” i d ” : ”Cadenza ” , ” p i e c e ” : ”A cadenza ” ,
” p i e c e t a c e t ” : ”Cadenza t a z e t ”} ,
] ,
” i n s t r u m e n t s ” : [ ” F l I ” , ” F l I I ” , ”VI ” , ”S ” ,
”A” , ” Continuo ” ] ,
” v o c a l v o i c e s ” : [ ” S ” , ”A” ] ,
” s c o r e s ” : [ ” F u l l ” , ” Vocal ” , ” Choral ” ] ,
} ,
” s c o r e s ” : [ ” Cadenza ” ] ,
” l a t e x ” : {} ,
}
Running this file through the script generates
one definitions file for the music definition, Lily-
Pond files for each of the given scores (Full, vocal
and choral scores), as well as for each individual
instrumental part. Each of the scores
will also have a L A TEX file that includes the title
page, the preface (including the table of contents,
which is exported by LilyPond!), the score
and optionally a critical report.
All these files are tied together via a Makefile,
so all one needs to do to create a first version is
to copy in the music definition and run make.
Commons BY-NC 3.0 license [Creative Commons,
2010] as well as under the the GPL v3.0.
Its source code can be found in a public git
repository [Kainhofer, 2010a]:
http://repo.or.cz/w/orchestrallily.git.
More information about the OrchestralLily
package can be found in the documentation
at its homepage http://kainhofer.com/
orchestrallily/ (which is unfortunately not
always kept up to date) or better directly from
the source code.
10 Acknowledgements
A project like OrchestralLily would of course
never be possible without the help of many people.
The developers of LilyPond and of L A TEX –
too many to name them explicitly here – made
OrchestralLily possible in the first place by providing
excellent open source applications for
both music and text typesetting. The enormous
flexibility and configurability of both applications
(including the possibility to modify the
internals and implement required features yourself)
laid the foundation to turn a small project
into a professional music publishing framework.
The cadenza example used throughout this
article was originally written by me, until Ana
Aleksić pointed out several harmonic shortcomings
and helped me rewrite it. Similarly, Manfred
Schiebel greatly improved my dilettantish
attempts at producing a piano reduction.
References
Creative Commons. 2010. By-nc 3.0
at license. http://creativecommons.org/
licenses/by-nc/3.0/at/.
Reinhold Kainhofer. 2010a. Git repository
of OrchestralLily. http://repo.or.cz/w/
orchestrallily.git.
Reinhold Kainhofer. 2010b. The OrchestralLily
package for lilypond. http://
kainhofer.com/orchestrallily. LilyPond
and L A TEX package for professional music
typesetting.
Han-Wen Nienhuys and Jan Nieuwenhuizen
et al. 2010. GNU LilyPond. http://www.
lilypond.org/. The music typesetter of the
GNU project.
9 Availability of OrchestralLily
The OrchestralLily package [Kainhofer, 2010b]
is currently dual-licensed under the Creative