Hi Kieren,

In your example, the rehearsal letters printed twice at the top of the
winds group. I don't know if it matters that I am on version 2.20, whereas
you specified 2.21.2, which is not publicly available from the LP website.

Also, if I am reading the code correctly, in a passage where only the brass
and strings play, no marks would print on that system. The example assumes
that winds will always be present. That is why I had a MarkLine at the top
of the score outside of any group.

Thanks
Marc

On Sat, Oct 17, 2020 at 9:53 AM Kieren MacMillan <
[email protected]> wrote:

> Hi Marc,
>
> > What I want is to print the MarkLine twice, once above Violin I, and
> once at the top of each system.
>
> In recent versions, you can just add the engravers to the appropriate
> StaffGroup contexts (see below). Does that solve your problem?
>
> Cheers,
> Kieren.
>
> %%%%
> \version "2.21.2"
>
> \layout {
>   \context {
>     \Score
>     \override StaffGroup.SystemStartBracket.collapse-height = #4
>     \remove Mark_engraver
>     \remove Metronome_mark_engraver
>   }
> }
>
> global = {
>   \mark \default
>   \key f \major
>   \time 4/4
>   s1*7
>   \mark \default
>   s1*7
> }
>
> fakemusic = {
>   \relative c' { \repeat unfold 56 { c4 } }
> }
>
> \score {
>   <<
>     \new StaffGroup = "winds"
>     \with { \consists Mark_engraver \consists Metronome_mark_engraver }
>       <<
>         \new Staff << \global \fakemusic >>
>         \new Staff << \global \fakemusic >>
>       >>
>     \new StaffGroup = "brass"
>       <<
>         \new Staff << \global \fakemusic >>
>         \new Staff << \global \fakemusic >>
>         \new Staff << \global \fakemusic >>
>       >>
>     \new StaffGroup = "strings"
>     \with { \consists Mark_engraver \consists Metronome_mark_engraver }
>       <<
>         \new Staff << \global \fakemusic >>
>         \new Staff << \global \fakemusic >>
>       >>
>   >>
> }
> %%%%
> ________________________________
>
> Kieren MacMillan, composer (he/him/his)
> ‣ website: www.kierenmacmillan.info
> ‣ email: [email protected]
>
>

-- 
Marc Shepherd

Reply via email to