Whilst currently working on a score containing a lot of consecutive tuplets, I’ve noticed some strange behaviour with the n-olet tool.
First observation: if you enter chords (Q), the n-olet tool will deselect itself as soon as the second note of the chord is entered. You’ll need to re-activate the n-olet tool for the next tuplet. After that, from this second tuplet onwards, the tool remains selected for the following ones.
Second observation: whilst using the space bar allows you to remain in the n-olet tool, using the arrow keys to move through the rhythm grid systematically deactivates the n-olet tool; this is annoying if, for example, you wish to return to a previous position to correct an entry.
Dorico 6.2.10 on Mac OSX.
1 Like
I don’t know about the first observation, but the second one is expected. Pressing the arrow is a known way of exiting a tuplets chain.
Actually, I’ve tried out your first observation, and I am perfectly able to input several chord triplets in a row using the qord mode (Q) (either two or three notes chords, I did not try more). But this was after I’ve tried about the arrow to make sure I was not writing BS.
I can confirm that starting over, the first tuplet using qord simply stops after it’s been completed, which is clearly unexpected behavior.
3 Likes
I believe this is by design; at least, a quick right-left is often mentioned as a good way to get out of tuplet mode.
(Ninja’d by @MarcLarcher!)
3 Likes
OK. I’ve combed through the documentation and haven’t found any mention of this, unless it’s tucked away somewhere in those 2152 pages…
That leaves the issue of entering a chord: why, when it’s the first one, does entering the notes cause the tool to close? Mystère et boules de gomme !
It’s indeed mentionned in the Inputting Tuplets section:
3 Likes
Merci Charles ; décidément, je devrais faire un tour chez Afflelou car deux paires valent mieux qu’une.
That leaves my first point: have you found anywhere in the documentation that mentions this behaviour (when Q key is on)?
2 Likes
Well, that’s actually a bug (as in unexpected behavior) so chances are the Team has already filed it in the to-do list (with a STEAM number) 
1 Like
Well, I’m delighted to be helping to improve Dorico in this way. It’s my first bug I have ever found! Champagne ! 
So let’s wait for 6.2.2 or later. 
1 Like
