Tuplets incorrectly reported to cross measures

• Jan 17, 2017 - 15:30
Type
Functional
Severity
S4 - Minor
Status
closed
Regression
No
Workaround
No
Project

When entering certain tuplets, MS believes that they cross measure lines. When entered they display properly and play back properly. The problem becomes evident if you attempt to copy them.
To duplicate the attached file and error:
New Score in 4/4 time
Add any instrument (I initially found this on the harp)
make the first beat of a measure a 1/4 rest
make beats 2-4 a dotted 1/2 rest.
select the dotted 1/2 rest and change it to a tuplet
click Notes|Tuplets|Other...
change ratio to 16/12
click "OK"
Enter notes in the tuplet (I used 16th notes of course and filled it up)
copy the entire tuplet
paste to first beat of any other measure
Error "Tuplet cannot cross barlines"

Attachment Size
tuplet bug.mscz 4.28 KB

Comments

And actually, you may have trouble just on the copy operation - before you attempt to paste. Click first note / shift+click last reports "Please select the complete tuplet" when you try to copy.

FWIW, there are two different root causes of issues like this.

One is roundoff error in tuplet calculations, where the end point of the last note of the tuplet doesn't work out to an even multiple of 480 or whatever the internal tick resolution is for the version of MuseScore being used. We tried to include fudge factors for calculations like that, but they aren't perfect.

The other possible root cause is the problem is actually unrelated but due to the way the code is structured, that is the only error message that was convenient to pop up (eg, a function that returns a simple value of "false" on failure and the calling function has no idea what went wrong, so it guesses it is a tuplet issue when it is actually something else.

Pretty sure we're looking at the first of these here. But FWIW, it works fine in 3.0, which I gather has re-implemented some of these functions to rely less on the "fudge factors".

Status active fixed
Reported version 2.1  
Regression No
Workaround No

Fixed most probably since long. (Probably by the switch to fractions instead of ticks for note durations)
I can't reproduce with latest version: 3.4.2.9788, revision: 148e43f
OS: Windows 10 (10.0), Arch.: x86_64