Re: Piano Pedal performace across a PianoStaff

[Michael Welsh Duggan]

Mats Bengtsson <address@hidden> writes:

> Interesting, you get a SIGSEGV!
>
> However, if you replace "Piano_pedal_performer" with
> "Piano_pedal_engraver", LilyPond will process the file without
> crashing. Still, it doesn't do what you want.
> The next time, you try these things, remember that "_performer":s
> deal with MIDI file creation, whereas "_engraver":s deal with
> paper typesetting. To see the default definition of the contexts,
> take a look at the file ly/engraver-init.ly.

I realize I didn't explain carefully enough, but I placed the
\context blocks within the \midi block.

> Here's a full example file for those who want to try it out more.
>
> \version "2.2.0"
>
> upper = \notes\relative c'' {
>    c4 d e \sustainDown b |
>    c c, \sustainUp \sustainDown  d8[ c]  e8[ e \sustainUp \sustainDown] |
> }
>
> lower = \notes\relative c {
>    c1
>    d1
>    f4 d \sustainUp g \sustainDown b |
>    b, \sustainUp c'
> }
>
> \score {
>    \context PianoStaff <<
>      \set PianoStaff.instrument = "Piano  " % set instrument name.
>      \context Staff = upper \upper
>      \context Staff = lower <<
>        \clef bass
>        \lower
>      >>
>    >>
>    \paper {
>       \context {
>           \VoiceContext
>           \remove "Piano_pedal_engraver"
>       }
>       \context {
>           \PianoStaffContext
>           \consists "Piano_pedal_engraver"
>       }
>   }
>    \midi { }
> }
>
>
>     /Mats
>
> Michael Welsh Duggan wrote:
>> A pedal-event is currently performed by the staff context within
>> which it is declared.  As a piano's pedal tends to affect the entire
>> output of the piano and not just one hand, it would be nice if
>> pedal-events could be automatically performed across the staves in a
>> PianoStaff.  My instinct was to use the following:
>>      \context {
>>          \VoiceContext
>>          \remove "Piano_pedal_performer"
>>      }
>>      \context {
>>          \PianoStaffContext
>>          \consists "Piano_pedal_performer"
>>      }
>> but I can see that I was wrong.  What would be necessary to make
>> something like this work?  I am willing to code it, but I would
>> appreciate a push in the right direction.
>> 

-- 
Michael Welsh Duggan
(address@hidden)