Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#1047 Beaming groups erroneous after merging notes

One Of These Days
open
nobody
notation (282)
2
2012-10-02
2007-04-22
Heikki Junes
No

If you merge in RG Notation beamed notes

e8 e8 e8

into

e4.

the beaming group is not changed. Instead, the beaming group should be always recalculated after a note merge.
Here the beaming group should disappear.

Strange results may appear when you merge for example notes in the middle of a group:

e8 e8 e8 e8

to

e8 e4 e8

In the example above RG notations shows flagged e8 in "e8 e4 e8". If these notes are in the same beaming group, e8 notes should have beams, not flags.

Erroneous beaming groups results in wrong beaming groups in LilyPond output for "e8 e4 e8".

Discussion

  • Heikki Junes
    Heikki Junes
    2007-04-22

    Logged In: YES
    user_id=30776
    Originator: YES

    This is a bug in the RG Notation Engine: e.g. if "e8 e8 e8" is merged into "e4.", "e4." should not for a beamed group.

    This creates LilyPond compile errors for cases like "e4. [ ]".

    Committed revision 8022, which tries to prevents "e4. [ ]" cases in LilyPond output.

     
    • milestone: --> One Of These Days