#696 Notation: Unbeam,re-beam makes tuplet number disappear

Live With It
wont-fix
nobody
notation (282)
2
2015-11-11
2005-01-26
William
No

In the notation editor, unbeaming and then re-beaming a
tuplet causes the tuplet number to disappear.

Discussion

  • Chris Cannam

    Chris Cannam - 2005-02-11

    Logged In: YES
    user_id=13489

    This is as designed, although I appreciate it's not an ideal
    design. Unbeaming tuplets stops them being tuplets any
    more, they just become notes with durations that happen
    to match those of tuplets. And beaming is intended to
    always produce beamed groups, not tuplets (you'd want
    the tuplet function with "already have correct durations"
    for that, if it was working correctly...)

     
  • William

    William - 2005-02-14

    Logged In: YES
    user_id=1004577

    Ok. Is that set in stone or we could consider making
    unbeaming of a tuplet preserve the tuple property e.g. by
    keeping it as an attribute of each tupled note/rest?
    Re-creating tuplets that have been destroyed by
    unbeaming/re-beaming can be quite a fiddly process. Making
    tuples slightly more "durable" would be helpful when one is
    doing a lot of unbeaming/re-beaming e.g. for manually
    fine-tuning the beaming of certain tuplets, e.g. those which
    contain a mix of notes and rests inside each tuplet.

     
  • D. Michael McIntyre

    Logged In: YES
    user_id=663564
    Originator: NO

    I have confirmed that this bug still exists.

    No immediate resolution is likely.

     
  • D. Michael McIntyre

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

    David Faure - 2015-11-11

    This is in fact fixed in the SVN branch big-tuplet-rewrite.

    In that branch, when I re-beam the notes from a tuplet, the tuplet number re-appears.

    [Gah, sourceforge loses comments typed without being logged in...]

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks