Issues for MuseScore

Title Status Priority Sort descending Version Replies Last updated
Position of measure numbers on one-line staff should be relative to top of barline, not top line active 7 6 years
[Accessibility] - Implement cross-staff or cross-voice slur input via keyboard PR created 3.4 3 10 months
Play Panel as study guide active 3.6 2 2 months
Step-wise playback active 3.2 7 1 year
Unexpected visible/invisible ledger lines depending on visible/invisible notes active 3.0 27 5 months
[MusicXML] Export missing instrument-sound tag PR created 3.6 12 4 months
Paint Format active 3.6 2 8 months
[MusicXML import] corruption from a MusicXML file with incorrect note types active 28 2 years
Notes/staff exceed page active 3.6 3 6 months
[Musicxml im-export] - New Instrument name disappears active 3.2 24 3 years
implement OpenSL ES audio driver backend for android active 3 6 years
Add a "7" fingering for trombone active 3.6 8 5 months
Request for option to prevent text crossing barlines active 3.x-dev 1 3 years
Starting barline able to be inspected again active 3.0 6 2 years
[MusicXML] Doesn't show chord symbols when open XML file active 4.x-dev 7 3 months
"Select workspace" dropdown occupies an extra toolbar in MS3.3 RC2 active 3.2 6 3 years
Auto insert spacer by holding ctrl+shift+dragging active 3.0 0 6 years
Musescore crashes on opening "File" Menu active 4.x-dev 2 2 months
[EPIC] Support W3C MNX active 3.3 2 3 years
Automatically adjust staff space to fit instruments on page active 3.0 7 2 years
MusicXML's justify parameter is not respected active 3.6 1 4 weeks
Allow turns on (post) grace notes active 3.3 3 2 years
MIDI input should use all selection types to determine note active 2.1 0 6 years
[MusicXML export] Lyrics do not handle flat and sharp signs needs info 13 2 years
(Autoformat) Anchorpoints change only based on the distance of the notation, ignoring lyrics belonging to the system active 3.2 12 2 years