FR: Less smart tuplets

Could we please have the option for less smart tuplets -so that they don’t grab the next note?

  1. After 2 years I still don’t understand what triggers the smart behavior or not
  2. When it grabs the next note and put it under the tuplet, it’s 98% of the times unwanted.

Typical scenario:
-1- Starting here

-2- Next

-3- Current result

-4- Wanted result


Edited to clarify FR

2 Likes

Interestingly, the Stop Bar will … stop this, even if you’re not using Insert mode.

Though Insert mode itself doesn’t help: it gives you the rest, but deletes the next note altogether.

But yes, I’m not sure what the merits are of ‘grabbing’ the next note are; though I’m sure there’s a reason.

Admittedly, adding tuplets afterwards is not something I do often; and most of the time it’s probably just as easy to delete the notes and re-enter.

2 Likes

I don’t think Dorico is smart enough to assume you want a passing note ‘Db’ inserted in -4- between C and Eb

Yeah, I guess the expected result would be a triplet of the two sixteenth notes and one sixteenth rest.

3 Likes

I know the Stop Bar is the workaround. But why would we need to remember it every time?

It’s not part of the FR. It was just to show the end goal.
OP Updated to clearify

If you have a passage of quavers you can convert them all to triplets with a single selection and 3:2 (I use this quite frequently)

I’m saying an option, like in preferences.
So, if you use current behavior a lot, then you don’t change.

Posted in another topic:

I’d agree that Dorico’s preferences are already awash with “Before, or After?” … “With, or Without?”… “This way, or that way?” options that make learning, teaching, and troubleshooting the app difficult.

There may be improvements to Insert mode that could be made, certainly.

2 Likes

I don’t see any problems with making a preference choice here.
But, if only one choice, then yes, please remove the “smart” function.

I expected 3 16th notes without the last one being tied. But seems simple enough to solve.

It’s not a workaround since it is behaving as expected. You don’t need to remember it every time, build it into your muscle memory, it’s not a hard task.
Somehow I never encountered this issue, even though I use a lot of tuplets for a moderate irregular music.

This is fascinating indeed. Is this documented anywhere? :thinking:

It’s the expected behaviour of the stop bar, right? Nothing changing after it. Since only Insert-Mode would change things later, it got commonly confused as an “insert mode only” feature, but the stop bar exists by itself, even when insert mode isn’t activated. So I find this expected behavior.

1 Like

In principle yes.
But if I’m honest (and I’ve said it before…), the intuitive result would be, that “things” are only happening to items that are selected, which clearly isn’t the case here:
tuplets

I’d like to make a feature request for making this behavior optional, please.

Best regards,
Benji

1 Like

If I put a tuplet on the selected note, what would be the expected thing?

Adding two quaver rests, or putting the first three notes into a tuplet?

This!


Again, “stuff” just happens to selected items!
:sunglasses:

We can get from A to B by just pressing .
Would be nice if we could do the same from C to D with ex: + ..

Jesper

5 Likes

I don’t entirely consider this such a “smart” feature because it doesn’t take anything into context, such as across barlines. As evidenced in OP’s original example and a few throughout this thread, a lot of users get frustrated with wanting to add a little tuplet at the final note of a bar, but not necessarily suck the next bar over. The current feature is almost too dumb to understand that’s pretty rare to want to suck a whole note into a little 16th triplet. Regardless of where in the measure a user wants to add this, I would wager to bet most of the time people have all their primary rhythms desired, and simply wish to add a tuplet in between two notes to ornament the phrase. Whatever the scenario, I think this feature takes an all or nothing literal math approach, and doesn’t leave room for musical context.

That said, I have discovered you don’t need to use the stop bar (unless you’re doing something more complex with the insert mode etc). Simply start note input by pressing enter to show the caret at your first note, and then invoke the tuplet popover. As long as you have a rhythmic note value selected which can fill out that space with an accurate tuplet ratio, then it won’t suck other notes into it. Example you have two 8th notes at the final quarter of the bar and want to make it into an 8th note triplet:

add tuplet without stop bar

However I agree with OP and others that I would like to not have to use additional tools or modes, and be able to convert only selected notes without having it suck other notes into its orbit.

6 Likes

I see you get different result than me here, but I don’t understand why.
What’s different in your way than my way in OP?

Well, really? This would be more a typical scenerio, right?




Not really the behavior I’d want.