Issues for MuseScore

Add new issue
Title Status Priority Version Replies Last updated
Accidental::isMicrotonal() function name is misleading active P2 - Medium 3.3 1 2 years
Accidental policy added in pitchspelling.cpp (changes with accidental chosen for MIDI input) active 5 3 years
Accidental collides with ledger lines active 3.5 3 1 year
Accidental collides with beam active 0 9 years
Acciaccatura stroke in Select section of Inspector active 2.2 3 5 years
Acciaccatura before note connected with glissando has wrong playback active 3.0 6 3 years
Acciaccatura after note active P2 - Medium 11 1 year
Accessibility issues for MacOS 10.15 upwards active 3.5 0 1 year
Accessibility and Fingering active 3.3 4 1 year
Access via QML on some Measure property active 0 8 years
Access to Scoreview and Repeats list with plugins active P3 - Low 6 2 years
Access to Harmony and fingering in plugin framework active 4 9 years
Accents placed too far from some notes with accidental active P2 - Medium 3.0 3 3 years
Accents do not sound on non-playing dynamics with 80 velocity active 3.x-dev 4 1 year
Accent playback inconsistent - too harsh for piano, too subtle for flute active P1 - High 3.5 15 3 months
Accent is placed differently on beamed notes compared to unbeamed notes active P3 - Low 3.x-dev 1 3 years
Accent height above note when bulk copying and pasting sometimes is too high/not right above note or previous articulation/ornament needs info 3.0 4 3 years
Accent cannot be played in the .mscz files transferred from 2.x needs info 3.1 8 2 years
Accacciatura double slashed active 2 9 years
Absurd bug needs info 3.6 2 5 months
About API needs info 3.6 1 6 months
Abort adding "Staff text" on macOS needs info 3.0 1 3 years
Abnormal behavior in cross-staff triplets active P2 - Medium 3.1 2 3 years
Able to tie fret marks on different strings of the same note needs info 2.1 4 5 years
Able to edit trillsegment like linesegment active 0 9 years