Issues for MuseScore

Title Status Priority Version Replies Last updated
Key signature reset to no accidentals when saving a selection needs info P1 - High 3.0 3 3 months
Image resize not correctly honoring aspect ratio and staff space unit settings active P1 - High 3.0 8 3 months
"Maximum barline distance" in Format>Style>Chord Symbols is ignored active P1 - High 3.0 5 3 months
Autoplace fails to avoid melisma underscores active P1 - High 3.0 29 4 months
"Other" appearance in Time Signature Properties does not work PR created P1 - High 3.0 19 4 months
In lute tablature the dots don't appear on dotted half-notes in print-outs active P1 - High 3.0 9 4 months
Missing screenreader output to state whether you are in Note Input mode or not active P1 - High 3.0 2 5 months
Master Effects setting made in MS 2 has changed active P1 - High 3.0 3 5 months
Request alternate position key signature when using beginning repeat sign active P1 - High 3.0 15 5 months
Glissando across system is not drawn correctly when auto placement increases staff distances active P1 - High 3.0 3 5 months
Show invisible doesn't work for certain elements until next layout active P1 - High 3.0 4 6 months
Beam across a system break can disappear active P1 - High 3.0 12 6 months
Parenthesis around noteheads ignore dots and accidentals active P1 - High 3.0 7 6 months
Broken on-screen rendering of synthetically emboldened fonts active P1 - High 3.0 14 7 months
Corrupt score with empty measure crashes on load active P1 - High 3.0 9 7 months
Changes to text styles for lines do not affect text within existing lines active P1 - High 3.0 3 7 months
[EPIC] Invisible staves issues active P1 - High 3.0 4 7 months
[EPIC] Small staves issues active P1 - High 3.0 4 7 months
[EPIC] Most frequent crash reporter events active P1 - High 3.0 1 7 months
The text style for even lyric lines is not saved active P1 - High 3.0 8 7 months
Cross-beam issue: beams come and go with the slightest change to unrelated parts of a score. active P1 - High 3.0 1 7 months
[Crash Reporter] Crash on accessing QPreferences from paCallback active P1 - High 3.0 3 7 months
[Crash Reporter] Crash in TourHandler processing routine active P1 - High 3.0 5 7 months
[Crash Reporter] Crash on Autosaving score active P1 - High 3.0 1 7 months
Bad autoplacement of cross-staff accidentals active P1 - High 3.0 1 8 months