After copy/paste operation with dotted half note chords and ties, 4/4 bar ends up with only 3 beats in it
This happens on Mac OS X 10.9 with a 2.0 nightly build downloaded yesterday.
Steps to reproduce:
- Create a new score with one staff (I used organ and removed the two bass clefs in the wizard).
- In the first beat of the first bar, add a chord with 3 notes, each one a dotted half note. (I used F B E).
- Shift-drag to select the chord, copy it, then select the quarter rest in beat 4 and paste it.
- Select the top note of the quarter-note chord in beat 4 and click the eighth note button to change it to an eighth note and break the tie.
- Shift-drag to select the half-note chord in beat 1 of bar 2, then delete it.
- You'll notice that bar 2 now only has three beats in it, as shown in the attached screenshot.
Attachment | Size |
---|---|
3_beats_in_44_bar.png | 17.78 KB |
Comments
Looks like corruption
The example in the original bug report can be solved by adding:
c2->setDuration(d.fraction());
at line 413 of libmscore/paste.cpp
However, there is a similar bug also resent in 1.3 which is not solved by this:
1- Create a new score with one staff (e.g. flute);
2- In the first beat of the first bar, add a chord with 3 notes, each one a dotted half note;
3- Select the 1/4 rest of first bar and click the eighth note button to change it to two 1/8 rests;
3- Shift-drag to select the chord, copy it, then select the second 1/8 rest in beat 4 and paste it.
4- The score is corrupt at this point, see attached image. The second measure contains 3/4 + 1/8 + 1/4 = 9/8 = 4/4 + 1/8
Windows 8.1, commit ae475eb
Notes:
The problem arises because a single note of duration 5/8 (=3/4 - 1/8) does not exist. The note should be splitted in 1/2 + 1/8.
This bug is also present in MuseScore 1.3.
Should this be submitted as a separate bug report?
Sounds separate, so if you don't mind...
Surprised this went unnoticed/unreported so long!
Patch by ABL at https://github.com/musescore/MuseScore/pull/1087
Fixed in 33e006409f
Automatically closed -- issue fixed for 2 weeks with no activity.