Issues for MuseScore

Title Status Priority Version Sort descending Replies Last updated
Handle error "You must build your code with position independent code if Qt was built with -reduce-relocations. " in cmake needs info 6 2 jaren
Tablature collides with augmentation dot active 0 8 jaren
Sextuplet contains seven notes?? needs info 2 2 jaren
Seperate these content between "<" and ">" active 0 3 jaren
A tied pair of non-adjacent notes does not sustain correctly active 7 2 jaren
MuseScore grabs MIDI interfaces active 1 9 jaren
TAB: scale change in staff properties shows wrong dot size active 2 7 jaren
Kindle Fire link in musescore.org footer redirects to outdated/unsupported version active 2 11 maanden
"Close" keyboard shortcut does not affect Start Center active 2 7 jaren
[MusicXML] support capo element active 1 7 jaren
Two staves, one hidden—barline shown at beginning of each line until relayout forced active 6 3 maanden
'About' box way too wide when using an outdated translation active 7 8 jaren
Request a way to have concert key chord symbols on top of score in presence of Hide Empty Staves active 20 7 maanden
Nonstandard (possibly insufficient number or incorrect placement of) augmentation dots for certain chords active 18 7 maanden
Notes skipped in selection active 1 10 jaren
QML spanners are not exposed to plugins active 1 1 jaar
Proper use of accidentals after octave change loco. active 1 7 jaren
Glissando collides with elements before note active 19 9 jaren
[MusicXML export] Support <part-symbol> export/import for flexible and explicit multi-staff part bracketing active 0 6 jaren
Change drum instrument selection active 0 8 jaren
2.0 grace note spaced too wide on ledger lines active 8 4 jaren
Fret marks in linked staff not centre-aligned to noteheads until saving, closing and re-opening active 5 8 jaren
import of v1.2 file: arco/pizz wrong position and playback active 3 8 jaren
Losing focus for selection when zooming needs info 34 6 jaren
Glissando not drawn correctly active 1 7 jaren