On 24/04/2015 20:23, Simon Albrecht wrote:
Please give us (code, eventually output) examples, else it’s difficult to get your point.Yours, Simon
pdf and relevant lily code attached. I know it's not compilable, but it's a fairly simple problem - look at the markup next to the seven bars rest at the segno - if the rest was wider the markup would lie flat.
And then just before the trio, the second time bar and the coda sign collide. If I could work out how to shorten the spanner the coda could drop and that would all be as it should be. (You can see the commented out attempts I made as per the docu and lsr stuff I found. Maybe it should have worked and didn't because I didn't do it right. Unfortunately the example was "how to shorten the spanner to one bar" and my spanner is one bar long ... so I had to try tweaking it without actually understanding what it was doing ...)
Cheers, Wol
Am 24.04.2015 um 18:09 schrieb Anthonys Lists:You can tell I've looked at the relevant section of the manual ...But I have two problems bugging me at the moment, and it's related to a problem I have in general with lilypond - it tries to avoid collsions by separating stuff vertically. How do I tell it to push them apart *horizontally*. Two current bugbears ...I have seven bars rest in a part. I want some markup starting at the first barline, and different markup ending at the last barline. If a part has notes, those markups will separate horizontally naturally - how can I force that to happen when there's that rest?And secondly, I want a coda sign at the end of an alternative. Of course, it collides with the repeat spanner :-( The problem with the docu or lsr snippet I found (can't remember which) was (a) it supposedly shortened all spanners - which I don't want - and (b) I couldn't get it to work anyway. I do have a different \alternative example that explicity codes each spanner without actually using "\alternative", but I couldn't get that to work either.If we're discussing usability, I think this is a major sticking point for lilypond - colliding notation is VERY common, and lily really doesn't handle it very well at all :-( When engraving parts I'm often scrabbling for space, and as soon as lily starts staircasing markup it wastes a heck of a lotCheers, Wol _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
partTromboneII-T.pdf
Description: Adobe PDF document
\version "2.10.0" voiceTimeSig = { \numericTimeSignature \time 2/4 \key ef \major \partial 8 s8 s2*8 \repeat volta 2 { s2*7 } \alternative { { s2 } { s2 } } s2*8 s2*8 \repeat volta 2 { s2*6 } \alternative { { s2*2 } { s2*2 } } s2*8 \key af \major s2*4 \repeat volta 2 { s2*16 s2*15 } \alternative { { s2 } { s2 } } s2*12 % coda s2*10 s1 s2 s2 } voiceMarkup = { \partial 8 s8 s2*8 \mark \markup { \musicglyph #"scripts.segno" } \repeat volta 2 { % s2^\markup { "Allegretto con Moto"} s2*5 s2^\markup { "Take 2nd on D.S." } <>^\markup { "Allegretto con Moto"} s2*7 <>^\markup { \right-align "Take 2nd on D.S." } } \alternative { { s2 } { s2 } } s2*8 \bar "||" s2*8 % \set Score.voltaSpannerDuration = #(ly:make-moment 1/4) \repeat volta 2 { s2*6 } \alternative { { s2*2 } { s2*2 } } % \unset Score.voltaSpannerDuration \bar "||" \once \override Score.RehearsalMark.break-visibility = #begin-of-line-invisible \mark \markup { \musicglyph #"scripts.coda" } s2*8 \bar "||" \mark \markup { Trio } <>^\markup { Piu Mosso } s2*4 \repeat volta 2 { s2*16 \bar "||" s2*15 } \alternative { { s2 } { s2 } } \bar "||" s2*12 \bar "||" \once \override Score.RehearsalMark.break-visibility = #begin-of-line-invisible \mark \markup { \right-align \line { "D.S. al" \musicglyph #"scripts.coda" } } \break <>^\markup { \large \musicglyph #"scripts.coda" } s2*10 \stopStaff \cadenzaOn s2^\markup { Extended Cadenza } \startStaff \teeny bf,4 af, g, f, ef,2\fermata \normalsize \cadenzaOff \bar "|" s2 \bar "||" }
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user