Issues for MuseScore

Ajouter un incident
Title Status Priority Version Replies Last updated
Play middle C on Midi enabled keyboard and an F# show up on the measure. needs info 3.0 7 1 an
Bad sound quality when playing scores active 4.x-dev 7 5 mois
Handbook: images have too much vertical space; and inline images have wrong vertical alignment active 3.6 7 5 mois
End of score pause (fermata) crash active 3.4 7 2 ans
Adjusting measure width with } shortcut creates many extra zeroes in "Measure width" property GitHub issue 4.0 7 2 mois
Extending lines faster (crescendo, staff and system texts, accel., etc.) needs info 4.x-dev 7 5 mois
N.C. over bass note chord symbol doesn't auto-format flats and sharps active 3.4 7 2 ans
crash while opening a capella-file active 3.5 7 2 ans
Playback Issues on Repeats needs info 3.5 7 2 ans
Reset dialog too large active 3.6 7 1 an
style settings for repeats active P3 - Low 7 3 ans
[GPx import] Missing clef in MusicXML generated from file in #34781 active 7 3 ans
Tuplet numbers: default distance is too far from beams active P2 - Medium 3.0 7 3 ans
rehearsal, segno and coda markings collide with measure number on first measure of system active 7 8 ans
Plugins bar needs info 3.0 7 3 ans
Wind chimes use cabasa sound active 7 4 ans
Improvements to the mixer GUI active 3.1 7 3 ans
Position of measure numbers on one-line staff should be relative to top of barline, not top line active 7 7 ans
In tablature, if "Show rests" is unchecked, the hidden rests still obey collision avoidance rules: may result in larger than expected vertical spacing active P2 - Medium 3.2 7 2 ans
Tempo Attributes Appear Corrupted - Tempo Can't be Changed needs info 7 7 ans
midi remote control bug needs info 2.1 7 5 ans
Staff properties: Apply/OK does not update changes to previous staves active 2.1 7 6 ans
3.3.4 MacOS: Can't quit Plugin Manager dialog active 3.3 7 3 ans
Guitar Capo Setting active 3.3 7 3 ans
Handbook navigation suggestions active 7 5 ans