Am Do., 2. Mai 2019 um 23:10 Uhr schrieb Alex Jones <
akjonesjeff...@gmail.com>:
Normally when I make cues I use the << {} \\ {} >> structure such that I
> might have code like the following, but it breaks up the multi measure
> rest, any suggestions?
>
> \version "2.18.2"
>
Hi,
don't give LilyPond any reason to split the MultiMeasureRest.
Compare:
\layout { \compressFullBarRests }
\new Staff = "splitted mmr" << R1*3 { s1 s s } >>
\new Staff = "not splitted mmr" << R1*3 { s2 s1 s s2 } >>
In your case the basic is:
\layout { \compressFullBarRests }
\new Staff = "not splitted mmr" << R1*3 { s4*11 <a' e''>4 } >>
If you need it frequently I'd recommend to work with separate named Voices,
initiated right from the start, kept alive.
Below a commented code for your image[*]
\version "2.19.82" %[**]
\layout { \compressFullBarRests }
\new Staff
<<
%% Initiate Voices "cue" and "main",
%% probably insert general settings in \with
%% Keep them alive
\new Voice = "cue" \with { fontSize = #-2 \voiceOne } { s1*6 }
\new Voice = "main" { s1*6 }
%% The actual input below
%% Instead of frequent local << ... >> one could code
%% << \context Voice = "cue" { ... } \context Voice = "main" { ... } >>
%% for the whole Staff
\context Voice = "main"
{
R1 \fermataMarkup
<<
\context Voice = "cue" { s1*11/4 <a' e''>4( <f'' a''>2) }
\context Voice = "main" {
\override MultiMeasureRest.staff-position = #0
%% `max-symbol-separation´ is a 2.19.x feature
\override MultiMeasureRest.max-symbol-separation = 1
%% Probably use `\tag´ to filter out this command where needed
\override MultiMeasureRest.X-offset = -1
R1*3 r4 c''2^( a'4~
}
>>
a'4 f'2 d'4)
}
>>
HTH,
Harm
[*]
Please attach images, or link to them. My local settings will filter out
any inline images. And I may not be the only one.
Looking in the archives is more tedious and probably one reason why this is
unanswered up to now.
[**]
Compiling my code with 2.18.2 will issue a warning for
`max-symbol-separation´, see inline comment.
I'd recommend to use most recent 2.19.83, it's a prerelease for 2.20.0
anyway.
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
