Musescore detects corrupt file when using sextuplet
Hi everybody,
my score uses a sextuplet (see attached file "Problem.mscz" to reproduce the error message, I reduced it to the minimum to show the problem), but when I open the file I get the following error message:
"Measure 2 Staff 1 incomplete: Expected: 2/4; Found 24/96"
If I press button "Ignore" I can open the score anyway. I already changed the measure as expected to 2/4, but the error still appears.
I found this error with version 2.3.1.
So I downloaded the latest version 2.3.2, there the error also appears. The detailed version number I use right now is
OS: Windows , Arch.: x86_64, MuseScore version (32-bit): 2.3.2, revision: 4592407
Is this a bug? Or is my score faulty?
Thanks for your help.
| Attachment | Size |
|---|---|
| Problem.mscz | 3.54 KB |
Comments
What exactly is that tuplet supposed to be, 6 16th in the space of what?
The actual duration shows 2/4 yet measure 2 shows only one beat (the tuplet) with no quarter rest following, so...
I did the "swap voices twice" technique to fix: Problem2a.mscz
(Also, I deleted an errant equals sign in the first measure, under the second notehead.)
See:
https://musescore.org/en/node/54721
Also, here's a copy in 4/4 without all the actual/nominal duration complications:
Problem2b.mscz
Regards.
Did you create this score from scratch in 2.3.1, or did you perhaps create it with an earlier version and then load it into 2.3.1? There was a known bug in an earlier version - 2.1, I think - where sextuplets could cause corruption on copy and paste or some other operations. This was fixed either in 2.2 or 2.3 but there could still be cases where "partially corrupted" scores from earlier versions might not be handled correctly. Anyhow, if that's what happened, I'd just delete the measure and re-enter.
if you created this from scratch in 2.3.1, we'd want to know precise steps to reproduce the problem - how you actually entered that tuplet.
In reply to Did you create this score… by Marc Sabatella
Hi, thanks for all the replies and sorry for my belated answer.
First of all: I now managed to avoid the corruption error when opening the score. I created the sextuplet from scratch with the latest version 2.3.2 ;-)
The file where the error occured was created with an earlier version, 2.0.3 I think, and then in the meantime I updated to 2.3.1 and there the error occured when I re-opened the old file.
So everything is fine now, no possible bug to report.