Issues for MuseScore

Add new issue
Title Status Priority Version Replies Last updated
Dashed/dotted lines stop scaling with zoom once line thickness equals one pixel active 4 6 years
Properties Not Changing needs info 3.4 5 1 year
Mixer settings treated inconsistently as part of score in the context of saving active 3.0 2 2 years
Add back textual tempo texts active 2.1 99 3 years
‘virtual void QWidget::setVisible(bool)’ was hidden [-Woverloaded-virtual] during build of master needs info 4.x-dev 1 2 weeks
spacing clash with ledger lines and rehearsal letters outline active 2 6 years
Document lost after unrolling needs info 3.4 1 1 year
Allow X to move chord symbols below the staff PR created 3.0 3 2 years
"Hide instrument name if there is only 1 instrument" doesn't work if there is only one visible instrument but others exist active 9 6 years
MuseScore prevents some OS to initialize screen saver, sleep/hibernation,auto turn off display active 3.4 0 1 year
Playback stops when I set the tempo I want. needs info 3.0 7 2 years
Add temple blocks instrument active 25 2 years
Musecore 3 is very unstable! needs info 3.0 2 2 years
stemlet (stems over rests) active 29 3 weeks
Unable to set Dynamic Range to "Staff." active 3.4 1 1 year
Shift + Click does not select notes in chord consistently in tablature active 3.0 1 2 years
Glitches needs info 3.4 4 1 year
Feature Requst: Move units selection to preferences as a global setting active 3.0 2 2 years
Quitting MuseScore needs info 2 5 years
Arpeggio collides with repeat barline active 3.5 1 1 year
App closes when no score loaded needs info 3.0 2 2 years
Include dimensions in names of page sizes in Page Settings active 3.0 7 1 year
Musescore follows the guitar fretboard diagram when using the "Realize Chord Symbol" tool on a guitar tablature or linked staff.. active 3.5 2 1 year
Figured bass text could be translated to extra notes active 3.0 6 2 years
Score becomes invisible and other artefacts active 2.1 5 3 years