[EPIC] MusicXML import/export issues
Reported version
3.0
Type
EPIC
Severity
S4 - Minor
Status
active
Regression
No
Workaround
No
Project
This epic aggregates all the issues related to MusicXML import/export. Some of the enumerated issues are outdated, so need to be checked on current version and closed if necessary.
- #5444: Open files with missing extension
- #14826: [MusicXML import] [trunk] import error: 31c-MetronomeMarks.xml missing beat-unit long
- #14679: [MusicXML export] [trunk] export errors high order tuplets
- #14906: [MusicXML] import/export of free text
- #15473: [MusicXML] use sound tag instead of direction name for repeat import
- #14895: support for <scoop/><plop/><doit/> and <falloff/> elements of MusicXML
- #15764: [MusicXML] Pages incorrectly exported if in Continuous View
- #17491: [MusicXML] Dots after volta numbers not exported
- #17739: [MusicXML export] Lyrics do not handle flat and sharp signs
- #19244: [MusicXML import] reversed wedge not imported
- #17499: [MusicXML] Thumb not exported
- #19459: [MusicXML] element offset handled incorrectly
- #17492: [MusicXML] Espressivo not exported
- #20400: [MusicXML import] TuxGuitar tab imported as regular staff with six lines
- #19292: [MusicXML] Glissando to grace note after note missing
- #21435: [MusicXML] always export Slur placement
- #21877: Note in MusicXML pastes unbeamed
- #23187: [MusicXML] Layout exports despite being disabled in Preferences
- #24249: [MusicXML] Import: multiple brackets in multiple part groups line up incorrectly
- #24473: [MusicXML import] empty lyrics lines (was: crash if too many lyrics)
- #24535: [MusicXML] Curly brace extends to all staves
- #24868: [MusicXML Export] group-barline missing
- #30716: [MusicXML] Sub-beam not exported
- #33406: [MusicXML Import] Incorrect barline height of staves with less than five lines
- #34456: musicxml, tablature and grace note problem
- #34116: MusicXML imports Identification information incorrectly -- Encoder tag is mangled
- #37001: [musicxml] [tablature] and the up-bow and down-bow tags
- #37796: After import of MIDI or MusicXML file, next "open" starts in bad folder
- #25900: Embedded markup in instrument long and short name after importing MuseScore 1.3 mscx file
- #40776: Instrument names of MusicXML mispositioned in Continuous View
- #35151: [GPx import] Missing clef in MusicXML generated from file in #34781
- #16884: [MusicXML] Arpeggio doesn't appear over multi-voice notes
- #41951: [Mac 10.10] Unable to open both files of same name and different extension
- #38966: [Import] Objects ignored on playback
- #40681: MusicXML import dynamics text improperly placed
- #49756: Changing staff type of 1.3 score to tablature retains treble clef
- #51611: [MusicXML import] Four beats put in 3/4 measures if full measure rests badly encoded
- #45376: [MusicXML] From a .gpx file, a Tab clef appears in each measure
- #72796: [MusicXML Import] handle stop-start order for glissandos
- #83141: [MusicXML import] note with print-object=no still has visible stem
- #93271: [MusicXML import] Markup text displayed in copyright
- #100971: [MusicXML import] corruption from a MusicXML file with incorrect note types
- #101686: MusicXML - incorrect vertical offset applied to rests on import
- #104731: Text lost when musicXML file imported
- #20766: [MusicXML] Export keeps text from first frame only
- #113456: MusicXML export: left-hand side repeat sign is included in the previous measure width
- #122996: Importing MusicXML does not assign instrument ranges from instruments.xml
- #137091: [MusicXML Import] should not create visual tempo element for <sound tempo="num"/> element
- #136446: [MusicXML Export] missing wedge stop
- #101906: MusicXML import: Strange beams above tablature; text elements reset
- #102216: MusicXML - bad export of trill lines
- #25164: [MusicXML export] qt-rich-text html tags in exported text
- #229546: Clef change export/import in MusicXML switches side of barline
- #229556: Slur placement="below" not saved in MusicXML export
- #227331: Capella to MusicXML conversion (or perhaps MusicXML export) breaks title alignment
- #257936: MusicXML file with multiple instruments at the same time in one part does not import correctly into MuseScore
- #17507: [MusicXML] Not all pedal types exported correctly
- #269926: [MusicXML export] double fermata exporting note with both fermata and grace note
- #269927: [MusicXML import] crash when importing file with fermata
- #71876: MusicXML file import causes crash
- #268241: [MusicXML import] opening results in two treble clefs
- #267176: [MusicXML export] rehearsal mark and system text missing in multi-measure rests
- #239556: Non-standard MusicXML Key Signature Import with non-Treble Clef
- #174331: [MusicXML] percussion keys on wrong line
- #163726: [MusicXML Import] Losing Tempotext when saving as mscz/mscx
- #103221: MusicXml does not set the proper font when importing from MusicXml
- #14131: [MusicXML] Import of nested tuplet does not work
- #57751: Import of MusicXML file with no drum set info should assume reasonable defaults
- #73721: [MusicXML] Support breaks in secondary beams (import and export)
- #66296: Footers not exported to Music XML
- #67711: Duplicate / corrupt lines on save/reload in file imported from MusicXML
- #58671: [MusicXML] The simple arrows in the Arpeggios palette are not exported correctly
- #36816: [MusicXML] import assumes beam=NONE if no beam information
- #56656: [XML Import] Tempi from Capella XML export don't get imported
- #48251: [MusicXML] Tempo marking with decimal not handled correctly
Comments
[musicXML] When import a musicXML file which has over 10 lyric line numbers , Musescore can't read from lines after 10th,1x th ... lyrics.
Please add that as a separate issue
In reply to (No subject) by Jojo-Schmitz
Please add #289724: Measure repeats not exported to musicxml
Also is this a bug or a feature request? #288907: Musicxml export does not included altered ontime values
There seems to be other musicxml bugs not in this EPIC list:
https://musescore.org/en/project/issues/musescore?text=musicxml&tags=&s…
feel free to put a "relates to [#270643]" into them