Add note to staff on either sounds A, B, or the top note on Tenor drums, or sounds A&B on Bass Drum in "Small Marching Band" Score.
Click on note or use back arrow to select note.
First part of sound plays and then Musescore crashes
I can't reproduce, can you give better and more exact steps and maybe a sample score? Also pleam mention which OS you're on (and whether you really are using MuseScore 2.2.1)
I am using 2.2.1, and these are the notes that make it crash. I tried reproducing it on a different score with just tenor and bass drums, but it was working normally there. It only messes up on my current score as far as I know. It works perfectly fine when putting those notes in by double clicking the note selector. However, MuseScore crashes when I try to select the note by changing an existing note's position using up and down arrow keys, click the note after putting it down, click the measure that the note is in, or highlight the note with the left and right arrow keys.
Comments
I can't reproduce, can you give better and more exact steps and maybe a sample score? Also pleam mention which OS you're on (and whether you really are using MuseScore 2.2.1)
I am using 2.2.1, and these are the notes that make it crash. I tried reproducing it on a different score with just tenor and bass drums, but it was working normally there. It only messes up on my current score as far as I know. It works perfectly fine when putting those notes in by double clicking the note selector. However, MuseScore crashes when I try to select the note by changing an existing note's position using up and down arrow keys, click the note after putting it down, click the measure that the note is in, or highlight the note with the left and right arrow keys.
In reply to I am using 2.2.1, and these… by SpooderNoob892
Attach the score that crashes and tell us what you do that makes it crash.
Based in the picture, seems likely to be something like #271325: Adjusting a note outside the range of a piano causes a crash when the piano keyboard is visible., already fixed for 2.3.
Automatically closed -- issue fixed for 2 weeks with no activity.