Issues for MuseScore (deprecated)

NOTICE: This issue tracker will be removed after March 10th, 2024.

If you are experiencing difficulties with MuseScore, please ask for help in the Support and bug reports forum. Thank you!

Title Status Priority Version Sort ascending Replies Last updated
Instruments with one stave shouldn't have tick box closed 3 10 years
time signature displayed incorrectly after staff size change closed 11 5 years
"Thickness" and "Width" both used to express the same concept closed 14 9 years
make mp3 support optional closed 20 8 years
Tie chords closed 15 8 years
Notes jump up an octave after disabling Concert Pitch closed 4 11 years
Chord name style's Y offset change does not take effect until reload closed 3 10 years
[Ubuntu] Extension not attached upon first save closed 15 9 years
Soft Pedal Playback active 5 5 years
No sound closed 1 7 years
[Trunk] Crash when inserting a measure before the first one closed 13 5 years
[Trunk] Voice shortcuts are incorrect closed 1 12 years
Notehead changed to Brevis in 1.3 score appears as cross closed 7 10 years
Adjacent-note chords in different voices separated by a second not offset active 12 4 years
Split chord across staves duplicate P2 - Medium 11 4 years
[Trunk] Broken font in score if 1.0 already has one open closed 3 11 years
Keyboards that use usb instead of midi closed 18 2 years
Memory leak during playback closed 2 10 years
Double concert tunning closed 5 5 years
Can't 'Apply To All Parts' closed 3 4 years
remove -Wformat compiler complaints from qDebug statements in capella.cpp and capxml.cpp when build debug closed 16 8 years
[Mac] Paste of text does not work closed 2 14 years
Accidental policy added in pitchspelling.cpp (changes with accidental chosen for MIDI input) active 5 5 years
[Mac OSX] Start Up dialogue should not appear if score opens MuseScore closed 8 11 years
Tie direction for single-stemmed chords open issues 4 9 years