Re: Learning how to use "\change Staff"; don't get it yet, obviously

[Jean Abou Samra]

> Le 22 août 2022 à 17:12, Valentin Petzel <valentin@petzel.at> a écrit :
> 
> Hi Ken,
> 
> you have two different scores, one that produces a score and one that 
> produces 
> midi (is there any specific reason not to use one score with both \layout { } 
> and \midi { }?).
> 
> The first one works fine, the seconds creates problems. Basically what’s 
> happening is that you never actually names any staves "RH" or "LH", so 
> Lilypond cannot chance context. Change the \new Staff lines to \new Staff = 
> "..." and it will work. Caveat: Changing contexts might fail if these context 
> to be changing into is not alive at that time, e.g. due to a line break.


Hi Valentin,

A minor question: the statement above is something I don’t understand, what do 
line breaks have to do with contexts being alive?

Thanks,

Jean




> 
> This means that when doing such things you need to make sure that the context 
> you want to change into is alive, for example by filling the staves with
> 
> << 
> \rh
> #(skip-of-length lh)
>>> 
> 
> or even
> 
> << 
> \rh
> #(skip-of-length rh)
> #(skip-of-length lh)
>>> 
> 
> Cheers,
> Valentin
> 
> 
> 
> Am Samstag, 30. Juli 2022, 23:48:59 CEST schrieb Kenneth Wolcott:
>> Hi;
>> 
>>  I'm learning how to engrave music that changes from one staff to another.
>> 
>>  I, obviously, do not understand yet how to do this, even after
>> reading the pertinent section in the Notation Reference.
>> 
>>  My attempt to engrave the first three bars of the harp score of Swan
>> Lake fails with the following:
>> 
>> Swan_Lake.ly:40:3: warning: cannot find context to change to: Staff = RH
>> 
>>  \change Staff = "RH"
>> Swan_Lake.ly:22:3: warning: cannot find context to change to: Staff = LH
>> 
>>  \change Staff = "LH" <> s4                                    | % m01
>> 
>>  I have attached a screenshot of the first three bars of the harp
>> score of Swan Lake, my LIlypond source code and the result of my
>> engraving attempt.
>> 
>>  I don't think that there's anything wrong with Lilypond, and there's
>> nothing wrong with the documentation, but this Lilypond user is a bit
>> dense.
>> 
>>  If I can just get the first bar engraving correctly, I think I can
>> make it the rest of the way :-)
>> 
>> Thanks,
>> Ken Wolcott
>

signature.asc
Description: Binary data