Musescore did not completely save my percussion parts. The pitches are correct on the playback, but the written notation is all the same note. When, I try to fix the notation, Musescore force closes.
Well, if it's a score imported from Sibelius then, this issue is already fixed in the current version of MuseScore (although I think it's really a bug in Sibelius). So update to 2.0.2 and re-import the score and the crash will go away, although it still won't display reasonably because Sibelius is failing to include that information in the MusicXML file.
OK, then as stated, we need you to attach the score you are having problems with in order to help, also it would be useful if you could describe how the score got into this state - a series of stpes that led to this condition.
I believe I have already stated that Musescore force closes too soon for me to attach anything. I wrote the percussion part, then some other parts. I saved my work and exited. When I opened musescore the next day, everything was as I had left it except for the percussion part. The playback is correct, but the notation is incorrect. Anything I clicked, past that point made musescore close.
@Melani, use the "File attachments" option at the bottom of the page, just above the Save and Preview buttons when you're typing your post, and simply drag the file *.mscz from the folder to the button
@Stoichi The part originally played back on "drumset" but it sounded as a piano no matter what, so I changed the sounding instrument. Is there another way to get the sound I want without this problem occuring?
I assume the reason certain drums sounded like piano is that you used the instruments from the Marching Percussion section of the instrument list, and these instruments require a special-purpose soundfont. That is because the General MIDI standard does not have any concept of these sounds, so most GM-compatible soundfonts won't provide them. The solution indeed would have been to load the soundfont, not to change the instrument.
I am guessing that somewhere along the line you might have tried changing to an instrument that is not an unpitched percussion instrument, and in the process you lost the drumset definition for the staff. You can see this in the Mixer - the Drumset box is not checked. I guess maybe you might have unchecked that yourself, but I'm guessing not, it probably happened as a result of some experimentation you were doing trying to solve the playback problem.
But of course, none of this should lead to crashes. Confusion over which line to display pitches on would be normal indeed now that the drumset information is lost, but I think the crash is due to a bug in 2.0 that was fixed some months ago. In any case I am unable to reproduce a crash in the currentl released version 2.0.2. So definitely, update to 2.0.2 to get that and hundreds of other bugs fixed.
Once you update to 2.0.2, you should be to open this score, use Staff Properties to change the staff back to Tenor Drum (even though it reports that it already is), and this will re-establish the necessary information to display the notes properly. They will playback correctly once you load the correct soundfont.
Meanwhile, if you can remember the exact steps that led to the loss of the drumset information and can reproduce the problem in a new score created from scratch, let us know. It could be there is still a bug that caused the drumset information to be lost. But I'm guessing it is the (correct) result of having tried changing to a pitched instrument at some point and/or having manually unchecked the box in the Mixer.
Comments
Please attach the score (if possible) and steps on how you try to fix the notation so others might help you better.
Also mention the Version of MuseScore and which OS you are using
Also, it would help to explain something of how the score was created. If it was the result of importing a MusicXML file generated by Sibelius, then this could be related to a known issue caused by Sibelius' failure to include the necessary information in the MusicXML file - see #57751: Import of MusicXML file with no drum set info should assume reasonable defaults and #55501: [MusicXML import] crash if midi-instrument is missing from drum set part
It force closes too soon.
I'm using Musescore 2.0 revision 6e47f74 on a Windows 10 computer.
Well, if it's a score imported from Sibelius then, this issue is already fixed in the current version of MuseScore (although I think it's really a bug in Sibelius). So update to 2.0.2 and re-import the score and the crash will go away, although it still won't display reasonably because Sibelius is failing to include that information in the MusicXML file.
The score is not an import.
OK, then as stated, we need you to attach the score you are having problems with in order to help, also it would be useful if you could describe how the score got into this state - a series of stpes that led to this condition.
I believe I have already stated that Musescore force closes too soon for me to attach anything. I wrote the percussion part, then some other parts. I saved my work and exited. When I opened musescore the next day, everything was as I had left it except for the percussion part. The playback is correct, but the notation is incorrect. Anything I clicked, past that point made musescore close.
@Melani, use the "File attachments" option at the bottom of the page, just above the Save and Preview buttons when you're typing your post, and simply drag the file *.mscz from the folder to the button
Eagle March.mscz
I see in the mixer the Tenor drum set to "castanets", try right-click> Properties ... Stave / Change Instrument>
an attempt (HTH)
but I have done something wrong
@Stoichi The part originally played back on "drumset" but it sounded as a piano no matter what, so I changed the sounding instrument. Is there another way to get the sound I want without this problem occuring?
have you installed the soundfont?
Take a look here: https://musescore.org/en/node/21722#comment-392896
if you settle for a trick (the best that I can think of): I made "your" stave invisible and silenced the one that I added
I assume the reason certain drums sounded like piano is that you used the instruments from the Marching Percussion section of the instrument list, and these instruments require a special-purpose soundfont. That is because the General MIDI standard does not have any concept of these sounds, so most GM-compatible soundfonts won't provide them. The solution indeed would have been to load the soundfont, not to change the instrument.
I am guessing that somewhere along the line you might have tried changing to an instrument that is not an unpitched percussion instrument, and in the process you lost the drumset definition for the staff. You can see this in the Mixer - the Drumset box is not checked. I guess maybe you might have unchecked that yourself, but I'm guessing not, it probably happened as a result of some experimentation you were doing trying to solve the playback problem.
But of course, none of this should lead to crashes. Confusion over which line to display pitches on would be normal indeed now that the drumset information is lost, but I think the crash is due to a bug in 2.0 that was fixed some months ago. In any case I am unable to reproduce a crash in the currentl released version 2.0.2. So definitely, update to 2.0.2 to get that and hundreds of other bugs fixed.
Once you update to 2.0.2, you should be to open this score, use Staff Properties to change the staff back to Tenor Drum (even though it reports that it already is), and this will re-establish the necessary information to display the notes properly. They will playback correctly once you load the correct soundfont.
Meanwhile, if you can remember the exact steps that led to the loss of the drumset information and can reproduce the problem in a new score created from scratch, let us know. It could be there is still a bug that caused the drumset information to be lost. But I'm guessing it is the (correct) result of having tried changing to a pitched instrument at some point and/or having manually unchecked the box in the Mixer.
Thank you so much!
As per comment #20 above