Corruption reading empty measure with 7/4 actual duration

• May 21, 2015 - 07:02
Type
Functional
Severity
S2 - Critical
Status
closed
Project
MuseScore

Ubuntu 14.04, GIT commit: 9f62965

1) new score, treble clef template
2) drag 3/4 time signature to first bar
3) right click second measure, measure properties
4) set actual duration to 7/4
5) save
6) reload

Result: measure is corrupt.

I think the file is actually fine. What seems to be happening is that during the read, the whole rest is being converted to a full measure rest.

Comments

• May 21, 2015 - 09:44

I say more. It's a very former issue: I can reproduce constantly in the time until 2014, May 19. The following image has been produced with this Nightly: 56177c3
may 19 corruption.jpg

Reply

• May 21, 2015 - 12:53

The problem arises from the if statement at lines 254 of libmscore/cordrest.cpp
https://github.com/musescore/MuseScore/blob/master/libmscore/chordrest…
this was apparently done for compatibility with old scores. However, a file saved with MuseScore 1.3 already uses the distinction between measure and whole durationTypes.
Why don't we add as an AND condition a further check on MuseScore version to the if statement?
Something like:
score()->mscVersion() < 114(????)
where the versione number is the one corresponding to the introduction of the distinction between measure and whole durationTypes (the oldest MuseScore on my pc is 1.3, I can't verify which versions were still using whole for both cases).

Reply

• May 21, 2015 - 14:13

Hmm. The comment says, appropriately, that the conversion should only happens for measures that are 4/4 or less (so the rest can be assumed to fill the measure). But I don't see us consulting the measure duration at all. The final test against 4/4 is for duration(), but that's the duration of the rest itself. I think it needs to be measure()->duration(), assuming measure() is valid at this point. It might not be; we very possibly haven't actually added the rest to a segment yet.

Reply

• May 21, 2015 - 19:50

As I feared, at the point where this code is hit, the rest has not yet been added to a segment, so there is no way to know if the current measure is in fact 4/4 or less.

Without knowing exactly what conditions might have led older versions to write a whole rest when a measure rest would have been preferable, I'm inclined to just remove this whole conversion, or relegate it to sufficiently old scores only. I don't know if there are conditions where 1.3 would write rests that way, but I haven seen any.

Reply