Issues for MuseScore

Maak een issue aan
Title Status Priority Version Replies Last updated
Musescore 3 Playback Bug needs info 3.0 1 4 jaren
Small size for lute tablature needs info P1 - High 3.0 5 4 jaren
Tempo pallet unresponsive active 3.0 8 4 jaren
3.0.5.5992 “Line” Lost Placement with “System Break” Deletion active P1 - High 3.0 1 4 jaren
Dotted Grace note and Glissando marking issue active 3.0 2 2 jaren
Tempo defaulting to 120bpm active P1 - High 3.0 8 4 jaren
Musescore 3 Playback needs info 3.0 6 2 jaren
3.0.1 crashes when the start centre pops up needs info 3.0 6 4 jaren
Bar changes needs info 3.0 2 4 jaren
Enable console output on Win nightlies when run with -d active 3.0 0 5 jaren
Grace note issue needs info 3.0 3 4 jaren
Allow use of macros in text block active 3.0 5 5 jaren
Chord symbols below the staff in MS 2.x are moved to above the staff in MS 3.x active P1 - High 3.0 1 4 jaren
Navigator not working needs info 3.0 12 4 jaren
View menu: tick box selection lost at end of session active 3.0 0 4 jaren
dinamic broken and the program block and i cant write notes terrible needs info 3.0 1 4 jaren
Changing patch during playback sometimes causes momentary glitch active P3 - Low 3.0 2 4 jaren
Tremolos collide with accidentals on tremolo'd notes active P1 - High 3.0 3 2 jaren
Beat is skipping due to too many subdivisions active 3.0 19 5 jaren
[Feedback form] Time signatures are not displayed needs info P0 - Critical 3.0 0 4 jaren
[EPIC] Visual Tests overview active 3.0 1 4 jaren
MusicXML export strips key signatures with 0 accidentals active 3.0 12 1 jaar
Bluetooths speaker does not work in MuseScore needs info 3.0 3 3 jaren
Split measure creates unwanted courtesy key signature active 3.0 1 3 jaren
need two-step tie-untie functionality for Shift+= active 3.0 0 4 jaren