Unofficial MusicXML test suite

All pitches from G to c”” in ascending steps; First without accidentals, then with a sharp and then with a flat accidental. Double alterations and cautionary accidentals are tested at the end.

01a-Pitches-Pitches.xml

[image of music]

All pitch intervals in ascending jump size.

01b-Pitches-Intervals.xml

[image of music]

The <voice> element of notes is optional in MusicXML (although Dolet always writes it out). Here, there is one note with lyrics, but without a voice assigned. It should still be correctly converted.

01c-Pitches-NoVoiceElement.xml

[image of music]

Some microtones: c flat-and-a-half, d half-flat, e half-sharp, f sharp-and-a half. Once in the lower and once in the upper region of the staff.

01d-Pitches-Microtones.xml

[image of music]

Accidentals can be cautionary or editorial. Each measure has a normal accidental, an editorial, a cautionary and an editioal and cautionary accidental.

01e-Pitches-ParenthesizedAccidentals.xml

[image of music]

Microtone accidentals can be cautionary or editorial. Each measure has a normal accidental, an editorial, a cautionary and an editioal and cautionary accidental.

01f-Pitches-ParenthesizedMicrotoneAccidentals.xml

[image of music]

All different rest lengths: A two-bar multi-measure rest, a whole rest, a half, etc. until a 128th-rest; Then the same with dotted durations.

02a-Rests-Durations.xml

[image of music]

Rests can have explicit pitches, where they are displayed. The first rest uses no explicit position and should use the default position, all others are explicitly positioned somewhere else.

02b-Rests-PitchedRests.xml

[image of music]

Four multi-measure rests: 3 measures, 15 measures, 1 measure, and 12 measures.

02c-Rests-MultiMeasureRests.xml

[image of music]

Multi-Measure rests should always be converted into durations that are a multiple of the time signature.

02d-Rests-Multimeasure-TimeSignatures.xml

[image of music]

In some cases, a rest might not have its type attribute set (this happens, for example, with voices in Finale, where you don’t manually insert a rest).

02e-Rests-NoType.xml

[image of music]

All note durations, from long, brevis, whole until 128th; First with their plain values, then dotted and finally doubly-dotted.

03a-Rhythm-Durations.xml

[image of music]

Two voices with a backup, that does not jump to the beginning for the measure for voice 2, but somewhere in the middle. Voice 2 thus won’t have any notes or rests for the first beat of the measures.

03b-Rhythm-Backup.xml

[image of music]

Although uncommon, the divisions of a quarter note can change somewhere in the middle of a MusicXML file. Here, the first half measure uses a division of 1, which then changes to 8 in the middle of the first measure and to 38 in the middle of the second measure.

03c-Rhythm-DivisionChange.xml

[image of music]

Several durations can be written with dots. For multimeasure rests, we can also have durations that cannot be expressed with dotted notes (like 5/8).

03d-Rhythm-DottedDurations-Factors.xml

[image of music]

No divisions attribute

03e-Rhythm-No-Divisions.xml

[image of music]

Various time signatures: 2/2 (alla breve), 4/4 (C), 2/2, 3/2, 2/4, 3/4, 4/4, 5/4, 3/8, 6/8, 12/8

11a-TimeSignatures.xml

[image of music]

A score without a time signature (but with a key and clefs)

11b-TimeSignatures-NoTime.xml

[image of music]

Compound time signatures with same denominator: (3+2)/8 and (5+3+1)/4.

11c-TimeSignatures-CompoundSimple.xml

[image of music]

Compound time signatures with separate fractions displayed: 3/8+2/8+3/4 and 5/2+1/8.

11d-TimeSignatures-CompoundMultiple.xml

[image of music]

Compound time signatures of mixed type: (3+2)/8+3/4.

11e-TimeSignatures-CompoundMixed.xml

[image of music]

A time signature of 3/8 with the symbol=" cut" attribute and two symbol="single-number" attributes with compound time signatures. Shall the symbol be ignored in this case?

11f-TimeSignatures-SymbolMeaning.xml

[image of music]

Time signature displayed as a single number.

11g-TimeSignatures-SingleNumber.xml

[image of music]

Senza-misura time signature

11h-TimeSignatures-SenzaMisura.xml

[image of music]

Various clefs: G, C, F, percussion, TAB and none; some are also possible with transposition and on other staff lines than their default (e.g. soprano/alto/tenor/baritone C clefs); Each measure shows a different clef (measure 17 has the " none" clef), only measure 18 has the same treble clef as measure 1.

12a-Clefs.xml

[image of music]

A score without any key or clef defined. The default (4/4 in treble clef) should be used.

12b-Clefs-NoKeyOrClef.xml

[image of music]

Various key signature: from 11 flats to 11 sharps (each one first one measure in major, then one measure in minor)

13a-KeySignatures.xml

[image of music]

All different modes: major, minor, ionian, dorian, phrygian, lydian, mixolydian, aeolian, and locrian; All modes are given with 2 sharps.

13b-KeySignatures-ChurchModes.xml

[image of music]

Non-traditional key signatures, where each alteration is separately given. Here we have (f sharp, a flat, b flat) and (c flatflat, g sharp sharp, d flat, b sharp, f natural), where in the second case an explicit octave is given for each alteration.

13c-KeySignatures-NonTraditional.xml

[image of music]

Non-traditional key signatures with microtone alterations: (g flat-and-a-half, a flat, b half-flat, c natural, d half-sharp, e sharp, f sharp-and-a-half).

13d-KeySignatures-Microtones.xml

[image of music]

The number of staff lines can be modified by using the staff-lines child of the staff-details attribute. This can happen globally (the first staff has one line globally) or during the part at the beginning of a measure and even inside a measure (the second part has 5 lines initially, 4 at the beginning of the second measure, and 3 starting in the middle of the third measure).

14a-StaffDetails-LineChanges.xml

[image of music]

One simple chord consisting of two notes.

21a-Chord-Basic.xml

[image of music]

Some subsequent (identical) two-note chords.

21b-Chords-TwoNotes.xml

[image of music]

Some three-note chords, with various durations.

21c-Chords-ThreeNotesDuration.xml

[image of music]

Chords in the second measure, after several ornaments in the first measure and a p at the beginning of the second measure.

21d-Chords-SchubertStabatMater.xml

[image of music]

Check for proper chord detection after a pickup measure (i.e. the first beat of the measure is not aligned with multiples of the time signature)!

21e-Chords-PickupMeasures.xml

[image of music]

Between the individual notes of a chord there can be direction or harmony elements, which should be properly assigned to the chord (or the position of the chord).

21f-Chord-ElementInBetween.xml

[image of music]

Different note styles, using the <notehead> element. First, each note head style is printed with four quarter notes, two with filled heads, two with unfilled heads, where first the stem is up and then the stem is down. After that, each note head style is printed with a half note (should have an unfilled head by default). Finally, the Aiken note head styles are tested, once with stem up and once with stem down.

22a-Noteheads.xml

[image of music]

Staff-connected note styles: slash notation, hidden notes (with and without hidden staff lines)

22b-Staff-Notestyles.xml

[image of music]

Different note styles for individual notes inside a chord, using the <notehead> element.

22c-Noteheads-Chords.xml

[image of music]

Parenthesized note heads. First, a single parenthesized note is tested, once with a normal and then with a non-standard notehead, then two chords with some/all parenthesized noteheads and finally a parenthesized rest.

22d-Parenthesized-Noteheads.xml

[image of music]

Some tuplets (3:2, 3:2, 3:2, 4:2, 4:1, 7:3, 6:2) with the default tuplet bracket displaying the number of actual notes played. The second tuplet does not have a number attribute set.

23a-Tuplets.xml

[image of music]

Different tuplet styles: default, none, x:y, x:y-note; Each with bracket, slur and none. Finally, non-standard 4:3 and 17:2 tuplets are given.

23b-Tuplets-Styles.xml

[image of music]

Displaying tuplet note types, that might not coincide with the displayed note. The first two tuplets take the type from the note, the second two from the <time-modification> element, the remaining pair of tuplets from the <tuplet> notation element. The tuplets in measure 3 specify both a number of notes and a type inside the <tuplet-actual> and <tuplet-normal> elements, the ones in measure 4 specify only a note type (but no number), and the ones in measure 5 specify only a number of tuplet-notes (but no type, which is deduced from the note’s type). The first tuplet of measures 3-5 uses ’display-type=" actual"’, the second one ’display-type="both"’. FIXME: The tuplet-normal should coincide with the real notes!

23c-Tuplet-Display-NonStandard.xml

[image of music]

Tuplets can be nested. Here there is a 5:2 tuplet inside a 3:2 tuple (all consisting of written eighth notes).

23d-Tuplets-Nested.xml

[image of music]

Tremolo tuplets are tuplets on single notes with a tremolo ornament. The application shall correctly import these notes with 2/3 or their time...

23e-Tuplets-Tremolo.xml

[image of music]

Some " triplets" on the end of the first and in the second staff, using only <time-modification>, but not explicit tuplet bracket. Thus, the duration of the notes in the second staff should be scaled properly in comparison to staff 1, but no visual indication about the tuplets is given.

23f-Tuplets-DurationButNoBracket.xml

[image of music]

Different kinds of grace notes: acciaccatura, appoggiatura; beamed grace notes; grace notes with accidentals; different durations of the grace notes.

24a-GraceNotes.xml

[image of music]

Chords as grace notes.

24b-ChordAsGraceNote.xml

[image of music]

A grace note that appears at the measure end (without any steal-from-* attribute set). Some applications need to convert this into an after-grace.

24c-GraceNote-MeasureEnd.xml

[image of music]

Some grace notes and after-graces (indicated by steal-time-previous and steal-time-following).

24d-AfterGrace.xml

[image of music]

A grace note on a different staff than the actual note.

24e-GraceNote-StaffChange.xml

[image of music]

A grace note with a slur to the actual note. This can be interpreted as acciaccatura or appoggiatura, depending on the existence of a slash.

24f-GraceNote-Slur.xml

[image of music]

All <direction> elements defined in MusicXML. The lyrics for each note describes the direction element assigned to that note.

31a-Directions.xml

[image of music]

Tempo Markings: note=bpm, text (note=bpm), note=note, (note=note), (note=bpm)

31c-MetronomeMarks.xml

[image of music]

All <notation> elements defined in MusicXML. The lyrics show the notation assigned to each note.

32a-Notations.xml

[image of music]

Text markup: different font sizes, weights and colors.

32b-Articulations-Texts.xml

[image of music]

It should not make any difference whether two articulations are given inside two different notation elements, inside two different articulations children of the same notation element or inside the same articulations element. Thus, all three notes should have a staccato and an accent.

32c-MultipleNotationChildren.xml

[image of music]

Different Arpeggio directions (normal, up, down, non-arpeggiate)

32d-Arpeggio.xml

[image of music]

Several spanners defined in MusicXML: tuplet, slur (solid, dashed), tie, wedge (cresc, dim), tr + wavy-line, single-note trill spanner, octave-shift (8va,15mb), bracket (solid down/down, dashed down/down, solid none/down, dashed none/up, solid none/none), dashes, glissando (wavy), bend-alter, slide (solid), grouping, two-note tremolo, hammer-on, pull-off, pedal (down, change, up).

33a-Spanners.xml

[image of music]

Two simple tied whole notes

33b-Spanners-Tie.xml

[image of music]

A note can be the end of one slur and the start of a new slur. Also, in MusicXML, nested slurs are possible like in the second measure where one slur goes over all four notes, and another slur goes from the second to the third note.

33c-Spanners-Slurs.xml

[image of music]

All types of octave shifts (15ma, 15mb, 8va, 8vb)

33d-Spanners-OctaveShifts.xml

[image of music]

Invalid octave-shifts: 27 down, 11 up.

33e-Spanners-OctaveShifts-InvalidSize.xml

[image of music]

A trill spanner that spans a grace note and ends on an after-grace note at the end of the measure.

33f-Trill-EndingOnGraceNote.xml

[image of music]

Slurs on chorded notes: Only the first note of the chord should get the slur notation. Some applications print out the slur for all notes – these should be ignored.

33g-Slur-ChordedNotes.xml

[image of music]

All different types of glissando defined in MusicXML

33h-Spanners-Glissando.xml

[image of music]

Several ties that have their end tag missing.

33i-Ties-NotEnded.xml

[image of music]

A piece with four parts (P0, P1, P2, P3; different from what Finale creates!). Are they converted in the correct order?

41a-MultiParts-Partorder.xml

[image of music]

A piece with 20 parts to check whether an application supports that many parts and whether they are correctly sorted.

41b-MultiParts-MoreThan10.xml

[image of music]

A huge orchestra score with 28 parts and different kinds of nested bracketed groups. Each part/group is assigned a name and an abbreviation to be shown before the staff. Also, most of the groups show unbroken barlines, while the barlines are broken between the groups.

41c-StaffGroups.xml

[image of music]

Two properly nested part groups: One group (with a square bracket) goes from staff 2 to 4) and another group (with a curly bracket) goes from staff 3 to 4.

41d-StaffGroups-Nested.xml

[image of music]

Part names and abbreviations can contain line breaks.

41e-StaffGroups-InstrumentNames-Linebroken.xml

[image of music]

MusicXML allows for overlapping part-groups, while many applications do not allow overlapping groups, but require them to be properly nested. In this case, one group (within parenthesis) goes from staff 1 to 4 and another group (also within parenthesis) goes from staff 3 to 5.

41f-StaffGroups-Overlapping.xml

[image of music]

A part with no id attribute. Since this piece has only one part, it is clear which part is described by the one part element.

41g-PartNoId.xml

[image of music]

This piece has more part elements than the part-list section gives. One can either convert all the parts present, but not listed in the part-list, or simply not import / ignore them.

41h-TooManyParts.xml

[image of music]

MusicXML allows part-name and part-name-display in the score-part element. If part-name-display is given, it overrides the part-name for display.

The first staff uses only part-name, while the second one (same part-name) overrides it with a custom text. Similar for the part-abbreviation used in subsequent staves.

41i-PartNameDisplay-Override.xml

[image of music]

This score has multiple display-text elements in its part-name-display block. This is handled without crashing.

41j-PartNameDisplay-Multiple-DisplayText-Children.xml

[image of music]

Two voices share one staff. Each voice is assigned some lyrics.

42a-MultiVoice-TwoVoicesOnStaff-Lyrics.xml

[image of music]

A multi-voice / multi-staff part with a clef change in the middle of a measure and a <backward> for voice 2 jumping back beyond that clef change.

42b-MultiVoice-MidMeasureClefChange.xml

[image of music]

A simple piano staff

43a-PianoStaff.xml

[image of music]

A piano staff with different keys and clefs for each of its staves. The keys and clefs for both staves are given at the very beginning of the measure.

43b-MultiStaff-DifferentKeys.xml

[image of music]

A piano staff with different keys and clefs for each of its staves. The key and clef for the second staff is given only after a backward, just before the first note of the second staff is given, but after the whole measure for staff 1 has been given.

43c-MultiStaff-DifferentKeysAfterBackup.xml

[image of music]

Staff changes in a piano staff. The voice from the second staff has some notes/chords on the first staff. The final two chords have some notes on the first, some on the second staff.

43d-MultiStaff-StaffChange.xml

[image of music]

A piano staff with dynamics and clef changes, where each element (ffff, wedge and clef changes) applies only to one voice or one staff, respectively.

43e-Multistaff-ClefDynamics.xml

[image of music]

A simple, repeated measure (repeated 5 times)

45a-SimpleRepeat.xml

[image of music]

A simple repeat with two alternative endings (volta brackets).

45b-RepeatWithAlternatives.xml

[image of music]

Repeats can also be nested.

45c-RepeatMultipleTimes.xml

[image of music]

Nested repeats, each with alternative endings.

45d-Repeats-Nested-Alternatives.xml

[image of music]

Some more nested repeats with alternatives. The barline between measure 7 and 8 will probably be messed up! (Should be a repeat on both sides!)

45e-Repeats-Nested-Alternatives.xml

[image of music]

Some more nested repeats with alternatives, where the MusicXML file does not make sense in the first place. How well are applications able to cope with improper repeats and alternatives?

45f-Repeats-InvalidEndings.xml

[image of music]

A forward-repeating bar line without an ending repeat bar.

45g-Repeats-NotEnded.xml

[image of music]

Different types of (non-repeat) barlines: default (no setting), regular, dotted, dashed, heavy, light-light, light-heavy, heavy-light, heavy-heavy, tick, short, none.

46a-Barlines.xml

[image of music]

Barlines can appear at mid-measure positions, without using an implicit measure!

46b-MidmeasureBarline.xml

[image of music]

A clef change in the middle of a measure, using either an implicit measure or simply placing the attributes in the middle of the measure.

46c-Midmeasure-Clef.xml

[image of music]

A 3/8 pickup measure, a measure that is split into one (incomplete, only 2/4) measure and an implicit measure, and an incomplete measure (containg 3/4).

46d-PickupMeasure-ImplicitMeasures.xml

[image of music]

Voice 2 should start at 2nd beat of first full measure.

46e-PickupMeasure-SecondVoiceStartsLater.xml

[image of music]

Measures can contain less notes than the time signature says. Here, the first and third measures contain only two quarters instead of four.

46f-IncompleteMeasures.xml

[image of music]

Pickup measure with chord names and figured bass.

46g-PickupMeasure-Chordnames-FiguredBass.xml

[image of music]

Several header fields and part names can contain quotes (" ). This test checks whether they are converted/imported without problems (i.e. whether they are correctly escaped when converting).

51b-Header-Quotes.xml

[image of music]

There can be multiple <rights> tags in the identification element of the score. The conversion shall still work, ideally using both of them.

51c-MultipleRights.xml

[image of music]

A piece with an empty (but existing) work-title, but a non-empty movement-title. In this case the movement-title should be chosen, even though the work-title exists.

51d-EmptyTitle.xml

[image of music]

Several page layout settings: paper size, margins, system margins and distances, different fonts, etc.

52a-PageLayout.xml

[image of music]

System and page breaks, given in a <print> element

52b-Breaks.xml

[image of music]

Some notes with simple lyrics: Syllables, notes without a syllable, syllable spanners.

61a-Lyrics.xml

[image of music]

Multiple (simple) lyrics. The order of the exported stanzas is relevant (identified by the number attribute in this test case)

61b-MultipleLyrics.xml

[image of music]

Lyrics assigned to the voices of a piano staff containing two simple staves. Each staff is assigned exactly one lyrics line.

61c-Lyrics-Pianostaff.xml

[image of music]

How to treat lyrics and slurred notes. Normally, a slurred group of notes is assigned only one lyrics syllable.

61d-Lyrics-Melisma.xml

[image of music]

Assigning lyrics to chorded notes.

61e-Lyrics-Chords.xml

[image of music]

Grace notes shall not mess up the lyrics, and they shall not be assigned a syllable.

61f-Lyrics-GracedNotes.xml

[image of music]

A lyrics syllable can have both a number and a name attribute. The question is: What should be used to put syllables of the same voice together. This example uses different number/name combinations to check how different applications handle this unspecified case (The advice on the MusicXML mailing list was " there is no correct way, each application can do what it thinks is best").

61g-Lyrics-NameNumber.xml

[image of music]

Beaming or slurs can indicate melismata for lyrics. Also make sure that notes without an explicit syllable are treated as if they were part of a melisma.

61h-Lyrics-BeamsMelismata.xml

[image of music]

Each note of a chord can have some lyrics attached. In this case, each note of the chord has lyrics of the form " Lyrics [123]" attached, where each lyrics has a different number attribute to distinguish them. These syllables should be imported into three different stanzas and the timing should be correct.

61i-Lyrics-Chords.xml

[image of music]

Multiple lyrics syllables assigned to a single note are implemented either using a space in the lyrics or by using the <elision> lyrics element. This testcase checks both of them. First, a note with on syllable is given, then a note with two syllables separated by a spcae and finally a note with two and one with three syllables implemented using <elision> is given.

61j-Lyrics-Elisions.xml

[image of music]

Lyrics spanners: continued syllables and extenders, possibly spanning multiple notes. The intermediate notes do not have any <lyric> element.

61k-Lyrics-SpannersExtenders.xml

[image of music]

A normal staff with several (complex) chord names displayed.

71a-Chordnames.xml

[image of music]

A staff with chord names and some fretboards shown. The fretboards can have an arbitrary number of frets/strings, can start at an arbitrary fret and can even contain fingering information.

71c-ChordsFrets.xml

[image of music]

Chords and fretboards assigned to the voices in a multi-voice, multi-staff part. There should be fret diagrams above each of the two staves.

71d-ChordsFrets-Multistaff.xml

[image of music]

Some tablature staves, with explicit fingering information and different string tunings given in the MusicXML file.

71e-TabStaves.xml

[image of music]

All chord types defined in MusicXML. The staff will only contain one c’ note (NO chord) for all of them, but the chord names should be properly printed.

71f-AllChordTypes.xml

[image of music]

There can be multiple subsequent harmony elements, indicating a harmony change during a note

71g-MultipleChordnames.xml

[image of music]

Transposing instruments: Trumpet in Bb, Horn in Eb, Piano; All of them show the C major scale (the trumpet with 2 sharp, the horn with 3 sharp).

72a-TransposingInstruments.xml

[image of music]

Various transposition. Each part plays a c”, just displayed in different display pitches. The second-to-last staff uses a transposition where the displayed c’ is an actual f”’ concert pitch. The final staff is an untransposed instrument.

72b-TransposingInstruments-Full.xml

[image of music]

An instrument change from one transposition (Clarinet in Eb) to another transposing instrument (Clarinet in Bb). The displayed instrument name should also be updated.

The whole piece is in Bb major (sounding), so first the key signature should be one flat, after the change it should have no accidentals.

72c-TransposingInstruments-Change.xml

[image of music]

Three types of percussion staves: A five-line staff with bass clef for Timpani, a five-line staff with percussion clef, and a one-line percussion staff with only unpitched notes.

73a-Percussion.xml

[image of music]

Some figured bass containing alterated figures, bracketed figures and slashed figures. The last note contains an empty <figured-bass> element, which is invalid MusicXML, to check how well applications cope with malformed files.

Note that this file does not contain any extenders!

74a-FiguredBass.xml

[image of music]

All possible accordion registrations.

75a-AccordionRegistrations.xml

[image of music]

A compressed MusicXML file, containing a simple MusicXML score and the corresponding .pdf output for reference.

90a-Compressed-MusicXML.mxl

[image of music]

Dolet 3 for Sibelius (5.1) did not print out any closing beam tags, only starting and continuing beam tags. For such files, one either needs to ignore all beaming information or close all beams

99a-Sibelius5-IgnoreBeaming.xml

[image of music]

If we properly ignore all beaming information from the Dolet 3 for Sibelius export file, make sure that the lyrics syllables are still assigned to the correct notes.

99b-Lyrics-BeamsMelismata-IgnoreBeams.xml

[image of music]


Unofficial MusicXML test suite v2.23.82 (development-branch).