Mark, that's true, and it's possible I may end up going that way. I'm using percents in the parts at the moment to help differentiate between repeated measures and similar-looking changed measures. I'll also try the code from http://lists.gnu.org/archive/html/lilypond-user/2016-11/msg01162.html to see if I can unfold only the percents, leaving the voltas intact.
But I did want to address the disappearing rest and solo designation specifically, because either of those might be considered bugs. On Fri, Dec 2, 2016 at 6:44 PM, Mark Stephen Mrotek <carsonm...@ca.rr.com> wrote: > Garrett, > > > > When I replace “percent” with “unfold” everything appears as you want. > > > > Mark > > > > *From:* lilypond-user [mailto:lilypond-user-bounces+carsonmark= > ca.rr....@gnu.org] *On Behalf Of *Garrett Fitzgerald > *Sent:* Friday, December 02, 2016 3:42 PM > *To:* lilypond-user@gnu.org > *Subject:* Issues with combined parts and repeat percent > > > > Evening, all. I'm trying to write individual horn parts for a march, but > combine them in the score to save vertical space. However, I'm running into > problems with percent repeats where Horn 2 plays the same notes longer than > Horn 1 does. > > > > \version "2.18.2" > > > > hornOne = \relative c'' { r8 a a r a a | r8 g g r g g | } > > hornTwo = \relative c'' { \repeat percent 2 { r8 e, e r e e | } } > > > > \new Staff { > > \time 6/8 > > \partcombine \hornOne \hornTwo > > } > > > > \new Staff { > > \time 6/8 > > << \hornOne \\ > > \hornTwo >> > > } > > > > [image: Inline image 1] > > > > In the first example, we lose the first rest altogether, and we get a > marked "Solo" where there shouldn't be one. In both examples, the percent > clashes with the upper part. > > > > It's likely I can deal with this using the unfold-percent-only code that > was posted the other day, but it would be nice if the handling could be > fixed to print the first rest and lose the solo notation. It would be > wonderful if the percent could be automatically slipped downward to not > clash, but I suspect that would be a bit harder to deal with. Thanks! >
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
