Issues for MuseScore

Ajouter un incident
Title Status Priority Version Replies Last updated
Glissando plays back differently for tied notes vs. a single note of the same value active 3 6 ans
Stem moves away when moving notehead active 3 8 ans
[Trunk] Flag protrudes after 'Chord Articulation' active 2 2 ans
Add plugin latest revision date and musescore version support to table view active 2 1 mois
Undo Beam middle produces broken beaming active 1 2 ans
Allow % as chord symbol active 12 2 ans
Time signature change deletes glissandi active 2 7 ans
Plugin: context of new Score() call affects resulting score active 1 7 ans
[MusicXML] Import/export hidden staves active 6 1 an
Add message box re illegal filename chars. active 5 11 ans
Ties don't re-position to avoid collision with upcoming notes active 0 8 ans
The font of fingerings and other numbers should be Feta (MScore1) by default. active 4 10 ans
2.0 Stopping Audio From Google Chrome active 3 3 ans
Instrument Sound changes every time another score is opened active 4 7 ans
Objects incorrectly positioned, or missing after changing scaling of score with empty staves hidden and empty systems present active 2 7 ans
Join Scores and crash report active P1 - High 18 2 ans
Make Page up/down active in playback mode active 1 1 an
Plugins/Issues/revisions -gives 'Access denied' active 2 4 ans
Stave lines protrude barline active 5 3 ans
incorrectly "remember" prior length of segment when toggling mm-rests and changing barline type active 0 6 ans
Add "Key Signature" to online help for key signature active 5 6 ans
Note Input State Interactions with Plugins/Plugin Creator that crash Musescore active 1 11 mois
Dragging notehead places it away from cursor active 0 8 ans
Issues with cross-staff beams & slurs in imported 1.3 score active 10 7 ans
Bracket regression active 2 7 ans