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".
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 [be624a], which tries to prevents "e4. [ ]" cases in LilyPond output.
Related
Commit: [be624a]
Last edit: Ted Felix 2022-01-14
Added to
https://www.rosegardenmusic.com/wiki/dev:summer_code
(Formerly Bug #1705430)
Last edit: Ted Felix 2022-01-14
OK - another old bug. I looked into this and noticed that doing autoBeam after the collapse sorts things out (at least in most cases). So what if we automatically autoBeam in the collapse...
I have attempted an improvement.
See merge request #87.
Last edit: Ted Felix 2023-01-23
I'm not quite clear on the test case here, so I've written up the two mentioned in the original post. Please review and let me know if I'm wrong here. Everything looks good, but I'm not sure I'm testing the right thing and I'm not sure I'm getting the expected results.
Case #1: 8-8-8 -> 4.
.
.
.
Case #2: 8-8-8-8 -> 8-4-8
.
.
.
Yes that is exactly right !
I noticed the problem was easy to fix, when it occurred, by doing autobeam on the damaged notes. So I just added the autobeam to the collapse notes (if it is set on in the settings).
Pushed as [d78deb]. Please test latest git.
Related
Commit: [d78deb]