Re: Pianostaff 4-part writing and rests
Thanks to everyone in the thread who has given code and tips. I agree that it would be very nice if something were included in Lily herself to solve this. -- View this message in context: http://lilypond.1069038.n5.nabble.com/Pianostaff-4-part-writing-and-rests-tp170926p171718.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pianostaff 4-part writing and rests
Michael Rivers wrote: I just engraved a piece for which the standard solutions given in this thread worked especially badly. There were many 8th notes alternating with 8th rests (which should be merged by Lilypond, but can't be automatically), so switching back and forth between a polyphonic structure and \oneVoice was not workable. Tedious to enter and tedious to read, but it should work. A standard manual solution, not yet mentioned in this thread - defines a sequential music variable for just the shared 'r' - includes this as \oneVoice in parallel with the other voices - all these other voices have 's' where the shared rests are Features: - this variable can be thought of as associated with the staff - it can be left untransposed while the other voices are transposed - that way, the positioning produced by using '\rest' is stable - none of the other voices has a special role regarding shared rests You may find this somewhat tedious to enter, but it is a lot easier to read. Cheers, Robin ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pianostaff 4-part writing and rests
Hi all, Cool solution, but still a shame that it is necessary … I agree that it’s a clever solution… *and* that it’s a shame it’s necessary. In particular, this solution introduces a non-content “voice” in order to solve a presentation problem — yuck (as a requirement, not as a solution!). Here’s hoping something like merge-rests-on-positioning gets rolled into the distro soon. Cheers, Kieren. ___ Kieren MacMillan, composer www: http://www.kierenmacmillan.info email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pianostaff 4-part writing and rests
Hi Kieren! I’ll check that! Thanks! /P Peter Danemo +46-70-653 21 91 E-post: petedom...@gmail.com Web: danemo.com 10 feb 2015 kl. 13:21 skrev Kieren MacMillan kieren_macmil...@sympatico.ca: Hi Peter, I tried your suggestion but got this error message Did you fix any mailing-list “reformatting” problems? Sometimes, for example, “” gets replaced with “| |”. Hope this helps, Kieren. ___ Kieren MacMillan, composer www: http://www.kierenmacmillan.info email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pianostaff 4-part writing and rests
Am 10. Februar 2015 11:53:54 MEZ, schrieb Robin Bannister r...@dataway.ch: Michael Rivers wrote: I just engraved a piece for which the standard solutions given in this thread worked especially badly. There were many 8th notes alternating with 8th rests (which should be merged by Lilypond, but can't be automatically), so switching back and forth between a polyphonic structure and \oneVoice was not workable. Tedious to enter and tedious to read, but it should work. A standard manual solution, not yet mentioned in this thread - defines a sequential music variable for just the shared 'r' - includes this as \oneVoice in parallel with the other voices - all these other voices have 's' where the shared rests are Features: - this variable can be thought of as associated with the staff - it can be left untransposed while the other voices are transposed - that way, the positioning produced by using '\rest' is stable - none of the other voices has a special role regarding shared rests You may find this somewhat tedious to enter, but it is a lot easier to read. Cool solution, but still a shame that it is necessary ... Cheers, Robin ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pianostaff 4-part writing and rests
Hi Peter, I tried your suggestion but got this error message Did you fix any mailing-list “reformatting” problems? Sometimes, for example, “” gets replaced with “| |”. Hope this helps, Kieren. ___ Kieren MacMillan, composer www: http://www.kierenmacmillan.info email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pianostaff 4-part writing and rests
I just engraved a piece for which the standard solutions given in this thread worked especially badly. There were many 8th notes alternating with 8th rests (which should be merged by Lilypond, but can't be automatically), so switching back and forth between a polyphonic structure and \oneVoice was not workable. I used b8\rest for centering the rests in the treble clef and d8\rest for the bass, but then the singer wanted me to transpose the whole score down a step, and I had to manually rewrite all the 8th rests in the score which got transposed too. Not fun. Rests in multiple voices not merging by default or having a setting to merge them is one of the two most common frustrations I encounter with Lilypond (the staves in a grand staff failing to widen to allow for cross-staff beams is the other). -- View this message in context: http://lilypond.1069038.n5.nabble.com/Pianostaff-4-part-writing-and-rests-tp170926p171659.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pianostaff 4-part writing and rests
Hello Kieren! I tried your suggestion but got this error message Starting lilypond 2.19.15 [Untitled]... Processing `/var/folders/57/18mvczhs3qj389_tr12w2s34gn/T/frescobaldi-rmF3d0/tmprtTcu5/document.ly' Parsing... /var/folders/57/18mvczhs3qj389_tr12w2s34gn/T/frescobaldi-rmF3d0/tmprtTcu5/document.ly:72:1 applewebdata://763F6953-C2E8-494F-99B9-4EC424C54285/0: error: syntax error, unexpected '}' } /var/folders/57/18mvczhs3qj389_tr12w2s34gn/T/frescobaldi-rmF3d0/tmprtTcu5/document.ly:78:1 applewebdata://763F6953-C2E8-494F-99B9-4EC424C54285/1: error: syntax error, unexpected '}' } fatal error: failed files: /var/folders/57/18mvczhs3qj389_tr12w2s34gn/T/frescobaldi-rmF3d0/tmprtTcu5/document.ly Exited with return code 1. /Peter Peter Danemo +46-70-653 21 91 E-post: m...@danemo.com Web: danemo.com 9 feb 2015 kl. 20:14 skrev Kieren MacMillan kieren_macmil...@sympatico.ca: Hi Michael, There were many 8th notes alternating with 8th rests (which should be merged by Lilypond, but can't be automatically) Did you try the merge-rests-on-positioning trick? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pianostaff 4-part writing and rests
Hi Michael,
There were many 8th notes alternating with 8th rests
(which should be merged by Lilypond, but can't be automatically)
Did you try the merge-rests-on-positioning trick?
\version 2.19.15
#(define (rest-score r)
(let ((score 0)
(yoff (ly:grob-property-data r 'Y-offset))
(sp (ly:grob-property-data r 'staff-position)))
(if (number? yoff)
(set! score (+ score 2))
(if (eq? yoff 'calculation-in-progress)
(set! score (- score 3
(and (number? sp)
(= 0 2 sp)
(set! score (+ score 2))
(set! score (- score (abs (- 1 sp)
score))
#(define (merge-rests-on-positioning grob)
(let* ((can-merge #f)
(elts (ly:grob-object grob 'elements))
(num-elts (and (ly:grob-array? elts)
(ly:grob-array-length elts)))
(two-voice? (= num-elts 2)))
(if two-voice?
(let* ((v1-grob (ly:grob-array-ref elts 0))
(v2-grob (ly:grob-array-ref elts 1))
(v1-rest (ly:grob-object v1-grob 'rest))
(v2-rest (ly:grob-object v2-grob 'rest)))
(and
(ly:grob? v1-rest)
(ly:grob? v2-rest)
(let* ((v1-duration-log (ly:grob-property v1-rest 'duration-log))
(v2-duration-log (ly:grob-property v2-rest 'duration-log))
(v1-dot (ly:grob-object v1-rest 'dot))
(v2-dot (ly:grob-object v2-rest 'dot))
(v1-dot-count (and (ly:grob? v1-dot)
(ly:grob-property v1-dot 'dot-count -1)))
(v2-dot-count (and (ly:grob? v2-dot)
(ly:grob-property v2-dot 'dot-count -1
(set! can-merge
(and
(number? v1-duration-log)
(number? v2-duration-log)
(= v1-duration-log v2-duration-log)
(eq? v1-dot-count v2-dot-count)))
(if can-merge
;; keep the rest that looks best:
(let* ((keep-v1? (= (rest-score v1-rest)
(rest-score v2-rest)))
(rest-to-keep (if keep-v1? v1-rest v2-rest))
(dot-to-kill (if keep-v1? v2-dot v1-dot)))
;; uncomment if you're curious of which rest was chosen:
;;(ly:grob-set-property! v1-rest 'color green)
;;(ly:grob-set-property! v2-rest 'color blue)
(ly:grob-suicide! (if keep-v1? v2-rest v1-rest))
(if (ly:grob? dot-to-kill)
(ly:grob-suicide! dot-to-kill))
(ly:grob-set-property! rest-to-keep 'direction 0)
(ly:rest::y-offset-callback rest-to-keep)))
(if can-merge
#t
(ly:rest-collision::calc-positioning-done grob
alternating_A = {
c''8 r d'' r e'' r d'' r c''1
}
alternating_B = \transpose c'' c' \alternating_A
\score {
\new Staff \with { \override RestCollision.positioning-done =
#merge-rests-on-positioning }
{ \voiceOne \alternating_A } \\ \new Voice { \voiceTwo \alternating_B }
}
\score {
\new Staff \with { \override RestCollision.positioning-done =
#merge-rests-on-positioning }
\transpose c'' d'' { \voiceOne \alternating_A } \\ \new Voice {
\voiceTwo \alternating_B }
}
Hope this helps!
Kieren.
___
Kieren MacMillan, composer
www: http://www.kierenmacmillan.info
email: i...@kierenmacmillan.info
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pianostaff 4-part writing and rests
Hi Keith, I'll try to change the title and add an example of what we want it to do. Saw the update — looks great. Thanks for doing that. Cheers, Kieren. ___ Kieren MacMillan, composer www: http://www.kierenmacmillan.info email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pianostaff 4-part writing and rests
Hello! Thanks Kieren! I'll look in to the snippet link you sent. It'll probably require some understanding from my part. There's so many things with Lilypond that's so difficult. Especially for me without any experience at all in the type of workflow that Lilypond use. Best wishes! P Peter Danemo Krukmakargatan 33 B 118 51 Stockholm Tel: +46-70-653 21 91 24 jan 2015 kl. 22:55 skrev Kieren MacMillan kieren_macmil...@sympatico.ca: Hi all, Lastly got this help from Marc Hohl: http://lsr.di.unimi.it/LSR/Item?id=336 The linked issue (https://code.google.com/p/lilypond/issues/detail?id=1228) currently has a status of “abandoned” — well, at least the associated patch does, if not the whole issue. Is there a technical reason why the most up-to-date engraver (e.g., https://github.com/openlilylib/openlilylib/blob/c53380f5ca460d244a017389dc4bcb79a3f04d14/editorial-tools/merge-rests-engraver/definition.ily) has not been (or cannot be) rolled into the main Lilypond codebase? Or is it technically sound, and now it's only a matter of somebody making an appropriate/official patch and submitting it? The merged output is definitely standard engraving practice, so it would be nice to see this enhancement in Lilypond, if the coding is already done (or at least very close). Thanks, Kieren. ___ Kieren MacMillan, composer www: http://www.kierenmacmillan.info email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pianostaff 4-part writing and rests
Kieren MacMillan kieren_macmillan at sympatico.ca writes: The linked issue (https://code.google.com/p/lilypond/issues/detail? id=1228) currently has a status of “abandoned” — well, at least the associated patch does, if not the whole issue. Is there a technical reason why the most up-to-date engraver (e.g., https://github.com/openlilylib/openlilylib/blob/ c53380f5ca460d244a017389dc4bcb79a3f04d14/editorial-tools/merge-rests- engraver/definition.ily) has not been (or cannot be) rolled into the main Lilypond codebase? Or is it technically sound, and now it's only a matter of somebody making an appropriate/official patch and submitting it? The latest code looks reasonable. It needs testing and somebody willing to potentially modify it to cooperate with the rest of the code. It sets merged rests to staff-position 0, so it might interfere in mysterious ways people setting their rests by hand... the automated testing reveals things like this. It is a layer over the existing rest_collision_engraver, so either we check that each layer has a distinct-enough job that they won't confuse each other, or integrate the two rest-collision engravers into one. I never looked at this patch because from the issue title \override RestCollision #'positioning-done = #merge-rests-on-positioning I didn't recognize what problem it was trying to solve, even though I am often annoyed by that problem. I'll try to change the title and add an example of what we want it to do. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pianostaff 4-part writing and rests
Am 25. Januar 2015 21:19:26 MEZ, schrieb Keith OHara k-ohara5...@oco.net: Kieren MacMillan kieren_macmillan at sympatico.ca writes: The linked issue (https://code.google.com/p/lilypond/issues/detail? id=1228) currently has a status of “abandoned” — well, at least the associated patch does, if not the whole issue. Is there a technical reason why the most up-to-date engraver (e.g., https://github.com/openlilylib/openlilylib/blob/ c53380f5ca460d244a017389dc4bcb79a3f04d14/editorial-tools/merge-rests- engraver/definition.ily) has not been (or cannot be) rolled into the main Lilypond codebase? Or is it technically sound, and now it's only a matter of somebody making an appropriate/official patch and submitting it? The latest code looks reasonable. It needs testing and somebody willing to potentially modify it to cooperate with the rest of the code. It sets merged rests to staff-position 0, so it might interfere in mysterious ways people setting their rests by hand... the automated testing reveals things like this. It is a layer over the existing rest_collision_engraver, so either we check that each layer has a distinct-enough job that they won't confuse each other, or integrate the two rest-collision engravers into one. I never looked at this patch because from the issue title \override RestCollision #'positioning-done = #merge-rests-on-positioning I didn't recognize what problem it was trying to solve, even though I am often annoyed by that problem. I'll try to change the title and add an example of what we want it to do. That would be great. It would be a goid thing if LilyPond would do the right thing here without the awkward workarounds. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pianostaff 4-part writing and rests
Hi all, Lastly got this help from Marc Hohl: http://lsr.di.unimi.it/LSR/Item?id=336 The linked issue (https://code.google.com/p/lilypond/issues/detail?id=1228) currently has a status of “abandoned” — well, at least the associated patch does, if not the whole issue. Is there a technical reason why the most up-to-date engraver (e.g., https://github.com/openlilylib/openlilylib/blob/c53380f5ca460d244a017389dc4bcb79a3f04d14/editorial-tools/merge-rests-engraver/definition.ily) has not been (or cannot be) rolled into the main Lilypond codebase? Or is it technically sound, and now it's only a matter of somebody making an appropriate/official patch and submitting it? The merged output is definitely standard engraving practice, so it would be nice to see this enhancement in Lilypond, if the coding is already done (or at least very close). Thanks, Kieren. ___ Kieren MacMillan, composer www: http://www.kierenmacmillan.info email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pianostaff 4-part writing and rests
On Jan 24, 2015, at 10:44 AM, Peter Danemo petedom...@gmail.com wrote: I need it to be just one. I learned how to make a rest invisible, but that doesn't change the position for the remaining rest. Use 's' instead of 'r' for one of the rests. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pianostaff 4-part writing and rests
Hi, Lastly got this help from Marc Hohl: http://lsr.di.unimi.it/LSR/Item?id=336 Hope this helps Franck 2015-01-24 11:41 GMT-05:00, Mark Stephen Mrotek carsonm...@ca.rr.com: Peter, A rest can be positioned by using a pitch name, duration, \rest, e.g., c8\rest puts an eighth rest where c would be (depending on the clef). The attached example might be clearer. Mark -Original Message- From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Peter Danemo Sent: Saturday, January 24, 2015 7:44 AM To: lilypond-user@gnu.org Subject: Pianostaff 4-part writing and rests Hello! I'm a pretty unexperienced Lilypond user. I'm working on the layout of a small piece. It's basically a hymn written using a piano staff. If both voices have a rest on the first beat and start on the second beat I get two quarter note rests. I need it to be just one. I learned how to make a rest invisible, but that doesn't change the position for the remaining rest. Is there a easy way of doing this? Furthermore, the piece ends with just 3 bars on the last line. But i fills upp the whole page anyway. Is there a way of getting the 3 bars to take up the same as the bars above? Making a 4th invisible bar!? Best wishes! /Peter ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pianostaff 4-part writing and rests
On Jan 24, 2015, at 16:55 , Kieren MacMillan kieren_macmil...@sympatico.ca wrote: Hi all, Lastly got this help from Marc Hohl: http://lsr.di.unimi.it/LSR/Item?id=336 The linked issue (https://code.google.com/p/lilypond/issues/detail?id=1228) currently has a status of “abandoned” — well, at least the associated patch does, if not the whole issue. Is there a technical reason why the most up-to-date engraver (e.g., https://github.com/openlilylib/openlilylib/blob/c53380f5ca460d244a017389dc4bcb79a3f04d14/editorial-tools/merge-rests-engraver/definition.ily) has not been (or cannot be) rolled into the main Lilypond codebase? Or is it technically sound, and now it's only a matter of somebody making an appropriate/official patch and submitting it? The merged output is definitely standard engraving practice, so it would be nice to see this enhancement in Lilypond, if the coding is already done (or at least very close). FYI, for two voices per staff, recent (2.19.16) changes to the part combiner are supposed to merge both rests and multi-measure rests when appropriate. Of course, you must be willing to accept the part combiner's decisions about solo passages etc. or use those tedious \partcombineX commands. It would be nice if concurrent simultaneous rests could be merged without requiring the part combiner. Then we could simplify the part combiner. (You might be a programmer if you enjoy undoing hours worth of work as much as doing it in the first place.) — Dan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pianostaff 4-part writing and rests
- Original Message - From: Peter Danemo petedom...@gmail.com To: lilypond-user@gnu.org Sent: Saturday, January 24, 2015 3:44 PM Subject: Pianostaff 4-part writing and rests Hello! I'm a pretty unexperienced Lilypond user. I'm working on the layout of a small piece. It's basically a hymn written using a piano staff. If both voices have a rest on the first beat and start on the second beat I get two quarter note rests. I need it to be just one. I learned how to make a rest invisible, but that doesn't change the position for the remaining rest. Is there a easy way of doing this? Use \voiceOne and \voiceTwo when the parts have separate notes, and \oneVoice and a spacer rest when you want a single centred rest. Furthermore, the piece ends with just 3 bars on the last line. But i fills upp the whole page anyway. Is there a way of getting the 3 bars to take up the same as the bars above? Making a 4th invisible bar!? Look up ragged in the Notation Reference. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Pianostaff 4-part writing and rests
Peter,
A rest can be positioned by using a pitch name, duration, \rest, e.g.,
c8\rest puts an eighth rest where c would be (depending on the clef). The
attached example might be clearer.
Mark
-Original Message-
From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of
Peter Danemo
Sent: Saturday, January 24, 2015 7:44 AM
To: lilypond-user@gnu.org
Subject: Pianostaff 4-part writing and rests
Hello!
I'm a pretty unexperienced Lilypond user. I'm working on the layout of a
small piece. It's basically a hymn written using a piano staff. If both
voices have a rest on the first beat and start on the second beat I get two
quarter note rests. I need it to be just one. I learned how to make a rest
invisible, but that doesn't change the position for the remaining rest.
Is there a easy way of doing this?
Furthermore, the piece ends with just 3 bars on the last line. But i fills
upp the whole page anyway. Is there a way of getting the 3 bars to take up
the same as the bars above? Making a 4th invisible bar!?
Best wishes!
/Peter
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
\version 2.18.0
\paper {
print-all-headers = ##t
}
\score {
\new PianoStaff
\new Staff = upper
\relative c'' {
\clef treble
\key cis \minor
\time 4/4
\new Voice \relative c' { \voiceOne
b'4\rest cis cis cis |
}
\new Voice \relative c' { \voiceTwo
s4 e e e |
}
}
\new Staff = lower
\relative c {
\clef bass
\key cis \minor
\time 4/4
\new Voice \relative c { \voiceOne
dis4\rest gis gis gis |
}
\new Voice \relative c { \voiceTwo
s4 cis, cis cis |
}
}
\layout {
indent = 0
}
\header {
title = title goes here
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pianostaff 4-part writing and rests
and is automagic! 2015-01-24 17:25 GMT-05:00, Ali Cuota alicuota...@gmail.com: 4 me works best, F 2015-01-24 16:55 GMT-05:00, Kieren MacMillan kieren_macmil...@sympatico.ca: Hi all, Lastly got this help from Marc Hohl: http://lsr.di.unimi.it/LSR/Item?id=336 The linked issue (https://code.google.com/p/lilypond/issues/detail?id=1228) currently has a status of “abandoned” — well, at least the associated patch does, if not the whole issue. Is there a technical reason why the most up-to-date engraver (e.g., https://github.com/openlilylib/openlilylib/blob/c53380f5ca460d244a017389dc4bcb79a3f04d14/editorial-tools/merge-rests-engraver/definition.ily) has not been (or cannot be) rolled into the main Lilypond codebase? Or is it technically sound, and now it's only a matter of somebody making an appropriate/official patch and submitting it? The merged output is definitely standard engraving practice, so it would be nice to see this enhancement in Lilypond, if the coding is already done (or at least very close). Thanks, Kieren. ___ Kieren MacMillan, composer www: http://www.kierenmacmillan.info email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pianostaff 4-part writing and rests
4 me works best, F 2015-01-24 16:55 GMT-05:00, Kieren MacMillan kieren_macmil...@sympatico.ca: Hi all, Lastly got this help from Marc Hohl: http://lsr.di.unimi.it/LSR/Item?id=336 The linked issue (https://code.google.com/p/lilypond/issues/detail?id=1228) currently has a status of “abandoned” — well, at least the associated patch does, if not the whole issue. Is there a technical reason why the most up-to-date engraver (e.g., https://github.com/openlilylib/openlilylib/blob/c53380f5ca460d244a017389dc4bcb79a3f04d14/editorial-tools/merge-rests-engraver/definition.ily) has not been (or cannot be) rolled into the main Lilypond codebase? Or is it technically sound, and now it's only a matter of somebody making an appropriate/official patch and submitting it? The merged output is definitely standard engraving practice, so it would be nice to see this enhancement in Lilypond, if the coding is already done (or at least very close). Thanks, Kieren. ___ Kieren MacMillan, composer www: http://www.kierenmacmillan.info email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
