Musescore Crashes upon entering sextuplet
Hello,
My musescore keeps crashing whenever I enter a sextuplet into beat 4 of measure 20 in the classical guitar part.
I am using musescore 2.0.2 revision f51dc11 on a Macbook Pro running the latest version of El Capitan.
What can I do?
Thanks,
Chase
| Attachment | Size |
|---|---|
| Reminices.mscz | 86.62 KB |
Comments
This score is corrupt, as MuseScore warns you when you try to load it. Measure 20 has the wrong number of beats in it, and that is the cause of the crash. The question is, how did it get into that state? Any ideas of what might have happened to cause that corruption?
Meanwhile, best bet is to delete that measure completely, insert a new one, and re-enter the music, although you may have luck with some of the other techniques described in https://musescore.org/en/node/54721
In reply to This score is corrupt, as by Marc Sabatella
It seems as if the sextuplets are being saved as 42 sixteenth notes as opposed to 7 beats of sextuplet sixteenths. Attempting to delete the measure, and then reentering the notes is reproducing the crash.
In reply to It seems as if the sextuplets by chasejordan
I had done some test in the morning ... see if it is useful (but perhaps you've already solved)
In reply to I had done some test in the by Shoichi
I have not solved the issue. I am able to delete the corrupted information, but retyping the information is what causes the crash. I will take a look at this when I get home.
Thanks for testing :).
In reply to It seems as if the sextuplets by chasejordan
It's not enough to delete the *contents* of the measure - you need to delete the measure itself (eg, Ctrl+Delete). Then insert a new measure, then re-enter the notes. This worked for me. If not for you, then maybe you are doing something differently than I to enter the notes, so a precise series of steps to reproduce the problem would be useful.
The information is not corrupted, it is the measure containing the information that is corrupted. If you delete the information and then re-enter it this will still cause problems. You have to delete the corrupted measure entirely and then re-enter the information.
In reply to The information is not by underquark
Ok. I deleted the measure and still am having problems. The linked staff is still not transferring the sextuplets (like it did beginning measure 1-19) in measure 20. Here is a screen shot of what I am encountering.
In reply to Ok. I deleted the measure and by chasejordan
It isn't clear from the picture what you are perceiving the problem to be. It's better to post precise steps to reproduce the problem, saying exactly what you are doing, what you expect to see happen, and what happens instead.
Maybe you are referring to the fact that there are no brackets on the tuplets on the tab staff? As far as I can tell, that's not unique to that measure - the same thing happens when initially entering tuplets in any other measure of this score as well. Not sure if that's the result of some setting you made somewhere or if it's a bug that somehow affects this score only (doesn't seem to happen in new scores I create from scratch), but it doesn't seem related to the problem in measure 20.
In reply to It isn't clear from the by Marc Sabatella
1. Add 7 quarter rests in voice 2 in guitar part (not tablature).
2. Command click all quarter rests.
3. Command 6 to create sextuplets.
4. The notation staff and the tablature are linked. Therefore there should be 7 sets up sextuplet sixteenth rests in the tablature. Instead there are 42 sixteenth rests.
If you look at measures 1-19 in the original file, all sextuplets are bracketed. I have not changed any settings related to bracketing.
I think this is what is causing the corruption. This is what my corruption message shows me:
Measure 20, staff 4, voice 2 too long. Expected: 7/4; Found: 42/16
In reply to 1. Add 7 quarter rests in by chasejordan
When I try this, I get what appear to be real tuplets, no corruption at first. The only obvious glitch is that the bracket doesn't appear, but they clearly seem to be tuplets, as shown in the status line as well as the Inspector ("Tuplet" button is enabled). And again, I get this exact same result whether I try this in a newly-inserted measure 20 or in measure 1. However, if I then save the score and reload it, then the tuplets are gone and are replaced with regular sixteenths, making the score corrupt.
So it's definitely not the right behavior, but again, it doesn't seem to be the *result* of whatever was going on in measure 20. Whatever causes this symptom seems to be what caused the corruption in measure 20, but we would still need to understand how the score got into this state where creating tuplets does not seem to work properly. Because I can't reproduce anything like this in any other score.
It might have something to do with the linked part. If I delete measure 20, then delete the linked part, then save, then reload, everything seems back to normal. Is there anything unusual about how you went about creating that part? Perhaps some adding or deleting of staves after creation of parts? There are definitely known issues with that.
In reply to When I try this, I get what by Marc Sabatella
I experimented with a different tuning with the linked part. I believe it was both strings 1 and 6 tuned to an Eb.
I ended up going back to standard tuning when I cut out overtone series microtones in favor of maintaining a simpler aspect to the piece.
You can see my post here:https://musescore.org/en/node/92301 although this really isn't that important.