Issues for MuseScore

Title Status Priority Version Sort ascending Replies Last updated
Windows compile instructions slightly out of date active 5 1 year
[Trunk] Flag protrudes after 'Chord Articulation' active 2 2 years
Improving alterations for more ornaments active 1 6 years
Undo Beam middle produces broken beaming active 1 2 years
Cannot use a decimal dot or vulgar fractures like ½ for time signatures active 3 6 months
[EPIC] Items that cause entire score to be redrawn active 0 2 years
Sychronisation of articulations and line properties between Score and Drums-Part needs info 6 7 years
Note not displayed during drag on tablature staves active 2 7 years
Adapt the update checker to cope with all windows packages active 9 4 years
Mixer settings are saved in file but score not dirty when settings changes active 4 3 years
Adding system-flag to text does not affect linked parts (or move text to top staff in score) active P1 - High 19 3 years
treat Rehearsal Mark string as Marker for "Jump to", "Play Until", "Continue at" active 6 7 years
Bracket positioning differs between full score and part active 1 8 years
The font of fingerings and other numbers should be Feta (MScore1) by default. active 4 10 years
Instrument Sound changes every time another score is opened active 4 7 years
Allow Bluetooth-, other Sound- and MIDI-devices to be turned on after MuseScore loads active 7 11 months
"Signaler un bug" in french "Report a bug" needs info 11 6 years
PR submitted on GitHub should set the corresponding issue to "PR created" active P3 - Low 3 2 years
new option for multimesure rest active 5 7 years
Brackets of nested tuplets collide active 3 2 years
Support for (a more complex) additive time signature active 3 2 years
Add option to hide numbers on measures with rehearsal marks active 4 8 months
Issues with cross-staff beams & slurs in imported 1.3 score active 10 8 years
joined scores from album lose line alterations active 9 2 years
Half to quarter active 10 9 years