Skip to main content
\( \newcommand{\lt}{<} \newcommand{\gt}{>} \newcommand{\amp}{&} \)


A score may be represented in several formats: PDF output from a scorewriter (not a scan of printed sheet music), an XML file in the MusicXML format, online within MuseScore, or in Lilypond syntax. We plan to support various output options and conversions, but at this writing support is rudimentary, but evolving.

Subsection2.5.1PDF Source

Starting with a PDF that is “born digital” such as output from a scorewriter like Finale, it is possible to treat the score simply as we would any other image. The PDF version will be incorporated into the PDF output when the output is compiled, presuming the file is placed in the right location relative to the main file. For HTML output the utilities pdfcrop and pdf2svg will produce an SVG image that will work well.

This procedure will work best for very short scores, since it is treated as an indivisible image. For output, a longer score can lead to very poor page breaks, and large vertical gaps, especially in a preceding page. Or worse, the score might be longer than a single page, for which there is no solution. The piece below is inadvisably long and will likely demonstrate this behavior, though it is shorter than a page. Using scores authored, or converted to, Lilypond syntax should allow for better behavior of longer scores within a document.

<<SVG image is unavailable, or your browser cannot render it>>

Figure2.5.1Allegretto in F, Rob Hutchinson

Subsection2.5.2Embedded Interactive Musical Scores

A score hosted on MuseScore is easy to specify with two ID numbers: the user number and the score number (examine the source for details). Then an embedded interactive player is nearly trivial to embed into HTML output. Work continues on a process to realize the score within output.

Figure2.5.2String Quartet 1 by Lily He