Hello everyone, I’ve been scratching my head over this for an hour or so now and can’t explain it. I’m importing an xml file with nested tuples and it’s not displaying what I’d expect. Here’s what I’d expect (excuse my handwritten notation on an iPad):
I’ve been staring at the xml code (attached) and can’t find the error (no guarantee that it’s correct
I’ve attached it here. If I sum all the durations in the file (9 9 9 18 10 5 10 5 5 10 15 15 15 30), I get 165, which is what I’d expect, at least, for a 3/4 bar where the divisions tag specifies 55 (per quarter note, as far as I understand).
Ok though, this is Dorico 5.1.81 (must update) so maybe some kind soul could import into Dorico 6 and post what they see. Maybe the upgrade will solve the problem. If not I’d be very happy and grateful if someone with music xml chops could take a look and tell me what I’m overlooking.
(And your calculation is wrong on the handwritten image … the trailing rest will be a dotted quaver because your intermediate rest is a quaver rather than a semi.)
And if you change that so it just reads 3/4, you’ll get rid of the extra rest at the end. And then you can use force duration and beam together to get the look you want.
>(And your calculation is wrong on the handwritten image … the trailing rest will be a dotted quaver because your intermediate rest is a quaver rather than a semi.)
I admire your confidence in deeming it ‘wrong’ but I would certainly challenge that: there are 11 quavers in the time of 6; in the 5:3 tuplet we have 3 quavers, in the second simpler triplet there are also 3 quavers (9 semiquavers in the time of 6), leaving 5 quavers to fill the 11, hence 3 of those plus the crotchet rest. There are however, with these kinds of tuplets, often more than one way of displaying things.
Ah, I think this got lost in translation in the XML. The file has – and Dorico reproduces – a 3:2e tuplet covering the first 4 notes, leaving the G# semiquaver and the quaver rest out of the tuplet.
Thanks for this. Although it’s nice to be able to force a fix, I’d prefer Dorico to import things correctly. For instance in the xml file that triplet (2nd bracket) should extend over 5 notes and the next rest. It’s surely incorrect to stop at an earlier bar position than that given in the xml file?
I can see why it might get confused but 3:2 is mathematically correct given 1/8 + 1/16 (quaver + semi) three times in a row. And if Dorico respected the tuplet stop tag on the 10th item in the bar, all would be well.
I don’t think this is correct. Yes, 9:6 and 3:2 are the same ratio, but the base of the 3:2 would need to be a dotted quaver, and tuplets don’t work that way in Dorico – the base needs to be a plain note value. Edit: Dorico can in fact use dotted base notes – seen John Price’s answer.
The XML might be faulty but I’d appreciate it, if you know, why that is so? As I wrote, the durations sum correctly, to my knowledge. I might be missing something though.
BTW that’s damned close to what I’d expect and notated by hand. I can’t see where the second triplet bracket ends but it only has to run to the 1/8 rest and it would be perfect.
It’s indicating 3:2e, which is not correct. And both Finale and Dorico render the tuplet as specified. It’s true that Dorico does give you extra time in the measure, which is probably a result of trying to make things add up that don’t. Finale doesn’t do that, but because it leaves the G# semi and the quaver rest out of the tuplet, I think its bar doesn’t have the right number of beats either.
Edit: A 3:2e tuplet would be correct if it contained three 3:2x tuplets.
