Issues for MuseScore

Add new issue
Title Status Priority Version Replies Last updated
Capo Chords below or above main chords active 9 11 months
Slur and phrase end notes should play at 90% length active 37 2 years
Mscore font from 1.3 used in preference to 2.0 on some Linux systems active 10 8 years
Text styles not applied by command line option -S active 9 1 month
Clef Between Grace Notes active 5 1 year
Issues with cross-staff beams & slurs in imported 1.3 score active 10 8 years
Cross-staff slur missing or incorrect when a part is created active P2 - Medium 2 3 years
[MusicXML export] Grace after note active 0 7 years
Printing blank needs info 1 7 years
broken permalinks for long threads active 0 4 years
Audit all import filters for the new TPC1/TPC2 construct active 4 8 years
Cross-staff notes ignore accidentals active P2 - Medium 10 2 years
Dotted line at end of first segment of continued line goes to bad location if endpoint is on different page active 1 8 years
Update Copyright statements in Code Files active 1 2 years
Brackets and braces should nest active 3 2 years
[MusicXML import] note with print-object=no still has visible stem active 2 3 years
Remove "Enable MIDI input" option in Preferences active 1 10 years
Ancrusis writing active 3 1 year
Embedded markup in instrument long and short name after importing MuseScore 1.3 mscx file active 4 3 years
Piano Roll editor undo button doesn't actually undo pitch changes active 1 2 years
Allow for 'noninteractive' reading of scores active 0 7 years
The continuous panel flashes a few times when it's first displayed active 1 8 years
Stack alterations for complex jazz chords active 0 11 years
change articulation anchor for ["Fade In/Out", "Swell", "Wiggle Sawtooth/Vibrato"] from CHORD to TOP_STAFF active P1 - High 6 4 years
curScore.version not initiated for imported files continued from last session active 2 10 years