Youβve scanned your sheet music, corrected it, and exported itβ
but once you open it in MuseScore, Sibelius, or another notation program, things fall apart:
- lyrics are misaligned
- chords are missing or incorrect
- tempo markings appear multiple times
- rhythms donβt make sense
π The issue is almost never the export itself.
Your MusicXML export is only as good as your preparation.
π§ Why MusicXML Often Fails
MusicXML is not an image or audio format.
Itβs a structured representation of your music, including:
- notes
- voices
- time signatures
- key signatures
- text elements
- navigation
π This means:
If your scan contains structural errors,
they will be exported exactly as they are.
According to the guide:
π The quality of MusicXML directly depends on the corrections made beforehand
π« The 7 Most Common Causes of Broken MusicXML Exports
β 1. Unresolved Blue Errors
Blue markings indicate:
- too many or too few beats in a measure
π Problem:
- rhythm is incorrect
- export becomes unstable
π Solution:
- fix all blue errors before exporting
β 2. Incorrect Voice Assignment
Typical issues:
- everything placed in Voice 1
- mixed or overlapping voices
π Result:
- incorrect notation
- broken rhythmic structure
π Solution:
- separate voices properly
β 3. Wrong Text Types
Examples:
- chord symbols recognized as lyrics
- dynamics treated as plain text
π Result:
- incorrect display in notation software
π Solution:
- assign correct text categories
β 4. Incorrect Instruments
If instruments are misassigned:
- wrong names
- incorrect transposition
π Result:
- wrong playback
- incorrect export
β 5. Broken Navigation
Issues with:
- Coda
- Segno
- repeat structures
π Result:
- incorrect playback
- structural errors in the score
β 6. Incorrect Time Signatures
If the time signature is wrong:
- rhythms appear incorrect
- measures donβt align
π Rule:
π Always fix time signatures before editing rhythm
β 7. Incorrect Key Signatures
A wrong key signature leads to:
- incorrect accidentals
- misleading notation
β The Perfect Pre-Export Checklist
Before exporting to MusicXML, verify the following:
β Rhythm
- no remaining blue errors
β Voices
- clearly separated
- logically structured
β Text
- lyrics correctly assigned
- chord symbols properly classified
- dynamics correctly labeled
β Structure
- systems are correct
- instruments are assigned properly
β Time & Key Signatures
- fully accurate throughout the score
β Navigation
- repeats, Coda, Segno correctly placed
π These steps are essential for a clean export
π§ The Perfect Export Workflow
Step 1: Check structure
β systems, instruments, measures
Step 2: Check details
β voices, lyrics, chords
Step 3: Test playback
β does everything sound correct?
Step 4: Export
β choose MusicXML
Step 5: Verify in notation software
β open in MuseScore, Sibelius, etc.
β οΈ Common Problems After Export
Problem: Lyrics are shifted
π Cause: incorrect note anchoring
Problem: Tempo appears multiple times
π Cause: incorrect classification
Problem: Chords are missing
π Cause: wrong text type
Problem: Rhythm is broken
π Cause: unresolved blue errors
Problem: Instruments are incorrect
π Cause: wrong assignment
π§ Pro Tips
- Export is the final stepβnot the main one
- Always fix errors in ScanScore, not in the notation software
- Test your MusicXML files
- Fix small issues early
π When to Fix Issues β ScanScore vs Notation Software
π General rule:
Fix in ScanScore:
- structure
- rhythm
- voices
- text types
Fix in notation software:
- layout
- engraving
- visual refinement
β Conclusion
If your MusicXML export is broken,
the issue almost always comes from earlier steps.
π The export itself is not the problemβ
π your preparation is.
The most important rule:
π Clean structure = clean export
Follow this, and you will:
- save time
- avoid frustration
- achieve reliable results
