Re: avoiding collisions between markup, tempo, and \mark

2017-01-22 Thread Kieren MacMillan
Hi Andrew (et al.), I would suggest X-offset is perhaps a good choice: { \mark \default \once \override Score.MetronomeMark.X-offset = #11 \tempo "A tempo" 8 = 104 s2^\markup { \musicglyph #"scripts.segno" } | s2*15 \bar "||” } Or perhaps even extra-spacing-width/height, etc. In any case

Re: avoiding collisions between markup, tempo, and \mark

2017-01-22 Thread Wols Lists
On 21/01/17 02:18, Andrew Bernard wrote: > Hi Andrew, > > The manual is not well written concerning this matter. A \tempo is a > metronome mark (I don't think that is entirely obvious). > > { > \mark \default > > \once \override Score.MetronomeMark.extra-offset = #'(8 . 0) > \tempo "A temp

Re: avoiding collisions between markup, tempo, and \mark

2017-01-20 Thread Andrew Bernard
Hi Andrew, The manual is not well written concerning this matter. A \tempo is a metronome mark (I don't think that is entirely obvious). { \mark \default \once \override Score.MetronomeMark.extra-offset = #'(8 . 0) \tempo "A tempo" 8 = 104 s2^\markup { \musicglyph #"scripts.segno" } | s2

avoiding collisions between markup, tempo, and \mark

2017-01-20 Thread N. Andrew Walsh
Hi List, I have the following code: systembreaks = \new Voice { \mark \default \tempo "A tempo" 8 = 104 s2^\markup { \musicglyph #"scripts.segno" } | s2*15 \bar "||" } in a voice that contains all the tempo/key changes, and other such markings. In this case, the \markup segno is colliding