[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Make merge rests on positioning work

From: Thomas Morley
Subject: Re: Make merge rests on positioning work
Date: Sun, 20 Nov 2011 17:40:08 +0100

Hi Xavier,

2011/11/20 Xavier Scheuer <address@hidden>

Someone on the French users mailing list basically wants the features of
 \override RestCollision #'positioning-done = #merge-rests-on-positioning

Issue #1228 is tagged as "Patch-abandoned", LSR #336 is not working
with current version.
I had no problems compiling the LSR-Snippet with "2.14.2" and "2.15.13".  Of course this snippet doesn't define merging MultiMeasureRests.

However, the code given by Wilbert in the first comment works, except
that the MMRs appears below the 3rd (middle) line, instead of below the
4th line (normal position).  Apparently
 MultiMeasureRest #'staff-position  changed from #0 to #2 for the
normal position between 2.12 and 2.14/2.15.

Could a "power user" give some help in order to make it work correctly
with 2.14/2.15?  Even better if a dev could implement it (correctly) in
LilyPond, but in the meantime I'm sure the French users would be happy
with a hack!

Thanks in advance.


Also, I didn't notice any problem with the code given by Wilbert when using "2.14.2".

In the code below I integrated Neil's suggestion making the second MMR transparent. (To avoid printing a second MultiMeasureNumber I made the second number transparent manually. As Neil remarked an engraver would be better, but this is beyond my knowledge.)
But with "2.15.13" there is a difference between merging a single MMR and merging \compressFullBarRests R1*9. Perhaps a bug?

I added some conditions reading out the measure-count and the used lilypond-version to deal with the behaviour of the different versions.

It's a hack, but I hope it will work with "2.14." and "2.15". Please let me know.


Description: Text Data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]