Issues for MuseScore

Add new issue
Title Status Priority Version Replies Last updated
[Accessibility] - Implement cross-staff or cross-voice slur input via keyboard active 3.4 1 1 year
[Accessibility] - Musescore 4 always crashes when working with NVDA active 4.x-dev 6 10 months
[Accessibility] - Music not read and played when making keyboard selection active 3.4 1 1 year
[Accessibility] - Notehead types not read active 3.5 1 7 months
[Accessibility] - Special characters windows not accessible at all active 3.4 1 1 year
[Accessibility] - Text input not read active 3.4 2 1 year
[Accessibility] - Text not on note unreadable active 3.6 3 2 months
[Accessibility] - Tuplet more than 9 seems not to be announced correctly active 3.4 1 11 months
[Accessibility] - Unable to adjust note groupings in time signature properties active 3.5 1 8 months
[Accessibility] Announce when arpeggio crosses staves or voices active 3.5 13 6 months
[Accessibility] Indicates the direction of the notes stems active 3.5 10 2 months
[Accessibility] No speech for symbols from symbols palette active 3.5 3 6 months
[Accessibility] Play Panel is confusing with Voice Over. active 3.6 1 2 months
[Automatic Placement] Unnecessary colission avoidance in figured bass active 3.5 4 4 months
[build/packaging] missing doc_??.qhc and plugins' desc./info active 4 5 years
[capella import] Destroys Fingering needs info 9 1 year
[Capella import] Triplets active 16 1 year
[CAPX Import] Tempi from Capella don't get imported active 3 1 year
[Crash Reporter] Crash in TourHandler processing routine active P1 - High 3.0 5 2 years
[Crash Reporter] Crash on Autosaving score active P1 - High 3.0 2 7 months
[EPIC] Accessibility issues/suggestions active 3.0 5 2 years
[EPIC] ALBUMS issues active 1 1 year
[EPIC] Arpeggio issues active 3.0 1 1 year
[EPIC] Bends issues active 3.0 1 2 years
[EPIC] Braille friendly musicxml export active 3.0 11 1 year