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 descending Replies Last updated
[MusicXML] Not all pedal types exported correctly active 9 4 years
Fa notehead is not shared. active 11 1 year
[2.0] [linux] default page size is Letter despite locale being A4 active 8 8 years
[GPx import] Missing clef in MusicXML generated from file in #34781 active 7 4 years
Too Many Instruments Will Push Score off the Paper active 8 8 years
Integrate Parnassus font in MuseScore active 3 8 years
Issues with cross-staff beams & slurs in imported 1.3 score active 10 9 years
Tablature: fret marks are incorrectly reset (to default positions) after a transposition then UNDO active 2 2 years
[Trunk] Tempo Text not preserved after deleting bars, instruments or staves active 6 10 years
Add support for "broken" voltas active 2 8 years
some template files don't define ranges for the instruments they use active 9 3 years
Add default shortcuts for intervals below active P2 - Medium 10 3 years
Reorder Text Styles active 1 8 years
Add temple blocks instrument active 28 1 year
Multi-voice grace notes not aligned active P2 - Medium 15 4 years
MIDI Input selector grayed-out (Windows 7 64-bit) active 6 5 years
Incomplete demo Adeste Fideles active 1 5 years
Default paper size is A4 instead of letter active 17 1 year
Freeze file name during use active 10 4 years
Add license wizard for to promote Creative Commons based licenses needs info 3 8 years
Note in MusicXML pastes unbeamed active 2 4 years
Beam doesn't break after pasting active 5 10 years
Auto-hide navigator active P3 - Low 5 4 years
User lines do not preserve correct appearance when saved to palette active P2 - Medium 6 3 years
When silently changing the key to enharmonic equivalent during transposition, change notes too active 9 8 years