Runtime error
I am having a problem that I tried copying a measure from one score to another but when I did it said that the tuplets cannot cross barlines. I checked and there were no tuplets over barlines. Then I tried deleting tuplets and the second one I deleted came up with the error in the picture then musescore shut down. I tried doing this multiple times and The same thing happened each time.
I copyed the 4th measure from the copy score to the paste score. And I deleted 2 of the three 3rd voice triplets on that measure.
| Attachment | Size |
|---|---|
| MuseScore 2_ scn14748 3_3_2018 3_02_24 PM.png | 132.91 KB |
| Moonlight_Sonata paste.mscz | 16.67 KB |
| Moonlight_Sonata copy.mscz | 44.85 KB |
Comments
4/4 vs 3/4 = tuplets over barlines
In reply to 4/4 vs 3/4 = tuplets over… by Shoichi
I don't see what you mean
In reply to I don't see what you mean by Xdroid19
Try selecting the measure (I used selection filter)
Change the Time Signature on 'Paste' ->Paste. (Or right-click the measure ->Bar Properties and change the 'Actual' value to 4/4)
I can see some suspected rests (Voice 3). I think they are side effects of copy&paste
Indeed, the fourth measure presents a problem. The algorithms for triplets are bit approximate and sometimes things that technically wouldn't overlap still get flagged as if they would do to round-off error in the calculation of the note lengths. In this case it seems to be the quarter notes in voice 3 creating the confusion; the error goes away if you delete those. I notice if I swap voices 1 & 3, I get some strange additional rests, suggesting there was a problem with the initial file anyhow.
I think the problem is the deleted rests in voice 3 are making it difficult for MuseScore to figure out exactly where to place the quarter. Works better if you hide the rests.
I couldn't reproduce a crash, but if you can find the exact sequence of steps that led to it, we can investigate further.
In reply to Indeed, the fourth measure… by Marc Sabatella
I filed a bug report relating to this, see #270043: Corruption on deleting initial rest in voice 2 tuplet.
I propose we disallow deleting rests within tuplets, as these sorts of problems will be hard to fix otherwise. Unfortunately, that isn't enough to help with scores that already have this going on. I can actually create corruptions or crash or other errors in multiple ways given your score, and probably there are lots of places in the code where these sorts of holes won't be handled well.