Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix dot problem in merge-rests-engraver #168

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

chfin
Copy link

@chfin chfin commented Nov 16, 2017

The merge-rests-engraver did not merge the dots of several dotted rests resulting in multiple stacked dots on a single merged rest (cf. #123).
This commit fixes the issue by removing the dots from all merged rests except one.
Since the engraver only merges rests with the same length, it should not matter which rest keeps the dots, so we take the first.

The merge-rests-engraver did not merge the dots of several dotted rests resulting in multiple stacked dots on a single merged rest.
This commit fixes the issue by removing the dots from all merged rests except one.
Since the engraver only merges rests with the same length, it should not matter which rest keeps the dots, so we take the first.
@uliska
Copy link
Contributor

uliska commented Nov 16, 2017

Thank you for the pull request.
I am currently in a difficult situation, so please add any new comment to this if I shouldn't review within, say, a week.

@dliessi
Copy link
Contributor

dliessi commented Mar 17, 2020

I tried this change but it throws an error when used on rests with no dots. Moreover it keeps the wrong dot, i.e., the lower one.

@dliessi
Copy link
Contributor

dliessi commented Mar 18, 2020

The Scheme engraver Merge_rests_engraver by Thomas Morley (Harm), correctly dealing with dotted rests and full-measure rests, is included in LilyPond 2.20.0 (actually it was included before 2.19.83 and was extended to deal with dotted rests in 2.19.83).
I'll use that instead of the OLL one.

The dot positioning problem is actually a bug in LilyPond.

@dliessi
Copy link
Contributor

dliessi commented Mar 18, 2020

The dot positioning problem is actually a bug in LilyPond.

...which is apparently already solved in master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants