On Displaying Musical Scores » History » Version 23

Chris Cannam, 2016-01-08 11:24 AM

1 1 Chris Cannam
h1. On Displaying Musical Scores
2 1 Chris Cannam
3 3 Chris Cannam
h3. Use cases
4 1 Chris Cannam
5 3 Chris Cannam
 # Illustrating recordings by attaching a full publication-style score
6 4 Chris Cannam
 ** ...where the score is not intended to be read closely, but rather used as a sort of key-frame reference for navigating the audio
7 4 Chris Cannam
 ** ...or where user expects to be able to zoom the score far enough to actually read it properly
8 3 Chris Cannam
 # Linear rather than page-based score that a user is expected to read, e.g. to play along with, or to check specific notes in a transcription or spectrogram
9 3 Chris Cannam
 # On-the-fly score display of transcriptions and related annotation layers (score from MIDI)
10 3 Chris Cannam
 # Score editing for correction (making usually small edits to substantial scores)
11 3 Chris Cannam
 # Score editing for annotation (generating small scores from scratch)
12 1 Chris Cannam
13 3 Chris Cannam
h3. Sources of score data
14 1 Chris Cannam
15 3 Chris Cannam
 * Score-encoding formats, e.g. MusicXML, MEI
16 3 Chris Cannam
 * PDFs of published scores
17 3 Chris Cannam
 * "Tidy" MIDI files and other cleaned-up annotation data (e.g. chord charts)
18 3 Chris Cannam
 * Untidy output from transcription methods and the like, in MIDI or MIDI-like formats
19 1 Chris Cannam
20 3 Chris Cannam
h3. Possible implementations
21 3 Chris Cannam
22 7 Chris Cannam
 # Integrate code from an existing application (most likely one that is also in C++ using Qt)
23 1 Chris Cannam
 ** Suitable for all use cases, with limitation of requiring score to be available in a digital format
24 19 Chris Cannam
 ** Has drawback of greatly adding to complexity of SV codebase, which is already quite complex
25 7 Chris Cannam
 ** Only possibility if editing is required (but note that adding editing is likely to be very involved even with this approach, maybe prohibitively so)
26 3 Chris Cannam
 ** MuseScore -- most obvious option
27 3 Chris Cannam
 ** Rosegarden -- has a notation editor component but is primarily a sequencer (but does have the advantage that I wrote much of it and so know a lot of the code!)
28 7 Chris Cannam
 # Invoke external application to render to PDF or sequence of images, then display PDF/image pages
29 20 Chris Cannam
 ** Suitable for use case 1; unsuitable for use cases 2, 4, 5 (no way to do linear notation); uncertain for use case 3
30 1 Chris Cannam
 ** Replaces problem of "integrating score display" with problem of "integrating PDF/image page display"
31 19 Chris Cannam
 ** Could possibly draw from existing image layer display in SV
32 6 Chris Cannam
 ** Could use MuseScore as the external application (it has a batch mode) or Lilypond, or something else like VexFlow, or more than one option depending on platform & input format
33 6 Chris Cannam
 ** Has advantage of also introducing ability to display other PDF material than scores
34 5 Chris Cannam
 ** Adds access to non-digital (scanned) score content
35 3 Chris Cannam
36 8 Chris Cannam
Both have their technical challenges, but there is also a conceptual question about how to align score pages or bars in the time axis (more on this below).
37 2 Chris Cannam
38 8 Chris Cannam
h3. Which code to use for option 1?
39 1 Chris Cannam
40 23 Chris Cannam
I think the only reasonable options are MuseScore and Rosegarden. MuseScore produces much better output and has fairly well-organised code. Rosegarden has a more limited renderer and currently lacks MusicXML import. The only reason to consider anything other than MuseScore is that I'm quite familiar with the Rosegarden code myself already (and, I suppose, that it might be possible to contribute improvements to Rosegarden as well). At any rate, Rosegarden makes a useful baseline comparison.
41 1 Chris Cannam
42 8 Chris Cannam
Here are some examples, deliberately choosing small sizes in order to see how a zoomed-out scale looks, and considering both linear and paginated layouts.
43 8 Chris Cannam
44 8 Chris Cannam
h4. Linear layouts with "good" source material
45 8 Chris Cannam
46 8 Chris Cannam
Both applications are displaying their own example files here, so we have two different pieces but both are pieces that are expected to work well.
47 8 Chris Cannam
48 8 Chris Cannam
h5. MuseScore
49 8 Chris Cannam
50 2 Chris Cannam
51 1 Chris Cannam
52 8 Chris Cannam
h5. Rosegarden
53 2 Chris Cannam
54 1 Chris Cannam
55 1 Chris Cannam
56 8 Chris Cannam
h4. Paginated layouts with "good" source material
57 1 Chris Cannam
58 8 Chris Cannam
Same pieces as above.
59 2 Chris Cannam
60 8 Chris Cannam
h5. MuseScore
61 8 Chris Cannam
62 2 Chris Cannam
63 1 Chris Cannam
64 8 Chris Cannam
h5. Rosegarden
65 2 Chris Cannam
66 1 Chris Cannam
67 2 Chris Cannam
68 8 Chris Cannam
h4. Imported from an approximate transcription
69 2 Chris Cannam
70 14 Chris Cannam
This is an input that is not expected to work well -- a transcription obtained from the Silvet Vamp plugin of a MAPS database recording of Chopin mazurka op 7 no 1, exported to MIDI. Shown below is the result of taking that MIDI file as exported by Sonic Visualiser and importing it into each application with the default quantization/tidying settings.
71 12 Chris Cannam
72 18 Chris Cannam
Despite their substantially different appearances, these are both displaying the same MIDI data. Besides quantization differences, they use different numbers of staffs and different clefs, keys, and time signatures. None of those are given in the MIDI file here and both programs contain logic to guess them. MuseScore has guessed the wrong key (according to the original score) but the right time signature. Rosegarden has the right key but the wrong time signature.
73 2 Chris Cannam
74 8 Chris Cannam
h5. MuseScore
75 8 Chris Cannam
76 2 Chris Cannam
77 2 Chris Cannam
78 8 Chris Cannam
h5. Rosegarden
79 1 Chris Cannam
80 1 Chris Cannam
81 21 Chris Cannam
82 21 Chris Cannam
h3. How much code is involved?
83 21 Chris Cannam
84 21 Chris Cannam
MuseScore's @libmscore@ appears to contain the rendering code (not sure about file I/O). That is 136 .cpp files plus headers, 128K lines total including headers.
85 21 Chris Cannam
86 22 Chris Cannam
Rosegarden doesn't have a dedicated library structure. Its notation code is divided between @base@ and @gui/editor/notation@ directories, with MIDI file I/O elsewhere (a small fraction of the code in a @sound/@ directory). @base@ is 53 .cpp files, @gui/editors/notation@ is 42, combined they have 76K lines including headers.
87 21 Chris Cannam
88 21 Chris Cannam
h3. Aligning score pages and bars in the time axis