## #708 Notation: Tuplet using existing note durations does not work

Live With It
wont-fix
nobody
2
2012-10-02
2005-01-26
William
No

The option to make a tuplet from a group of selected
notes without changing the existing durations of the
notes doesn't work. If you select n notes and select
"Timing is already correct; update display only" in the
n+1 notes to be played in the time of n notes; if you
correct the values to be n and n-1, respectively, the
operation actually puts only n-1 notes into the
n-tuplet and omits the n-th note from the n-tuplet.
There seems to be no way to convert exactly n notes
into a tuplet which is played in the time of n-1 notes.

## Discussion

• Chris Cannam - 2005-02-01

Logged In: YES
user_id=13489

How strange. I know that I've used this function
quite extensively myself in the past, but you're right,
it doesn't appear to be working now.

• Chris Cannam - 2005-02-11

Logged In: YES
user_id=13489

This function works in certain circumstances, namely if
the notes you've selected have a duration no longer
than the intended tuplet duration. e.g. if you record
three quavers at precisely quaver-triplet durations
and then run this function on them, it will work (although
you'll still have to correct an incorrect estimate for the
tuplet group type in the tuplet dialog first).

The underlying problem is that the function that actually
actual selection any more when it does the group
operation, so the only way it knows when to stop
grouping is to use the theoretical duration of the
resulting group. That works OK for the normal tuplet
case but not at all well for the "already correct" case.

• William - 2005-02-15

Logged In: YES
user_id=1004577

Right. I'd think that converting n selected notes into an
n-tuplet of notes played in the time of (n-1) notes is such
a basic commonly used operation we shouldn't force the user
to jump through such difficult hoops to get it right
first-time. As I recall - though it's been a while since I
tested it - there were other values of n,m in the tuplet
dialog which have similar problems.
Can't we keep the selection around somehow for the benefit
of slotTupletGroup()? Without that, I don't see how we can
make the tuplet dialog appear to do a better job for the
user.

• status: open --> wont-fix
• milestone: None --> Live With It