Hi again,
> On Oct 28, 2021, at 2:03 PM, Kieren MacMillan <[email protected]>
> wrote:
>
> 2. Maybe even better: Would a Scheme engraver be able to extract (and
> “delete”/omit) *all* dynamics from one context (e.g., the piano_upper
> context) and inject them into a second context (e.g., piano_dynamics)? If so,
> what would be the most elegant way of indicating that a single/particular
> dynamic marking *shouldn’t* be extracted/pushed by the engraver?
In other words, is something like this possible?
\version "2.22.1"
Dynamics_mover_engraver = FOO
piano_upper = {
c'4\p d' e' f'
g'1\mp
g'4\f f' e' d'
c'1
}
piano_lower = {
\clef bass
c1
g,1
g,1
c1\ff
}
\score {
<<
\new PianoStaff <<
\new Staff \with { \consists Dynamics_mover_engraver } \piano_upper
\new Dynamics #(skip-of-length piano-upper)
\new Staff \with { \consists Dynamics_mover_engraver } \piano_lower
>>
>>
}
where all the dynamics in either of the two Staff contexts would appear in the
Dynamics context instead?
Thanks,
Kieren.
________________________________
Kieren MacMillan, composer (he/him/his)
‣ website: www.kierenmacmillan.info
‣ email: [email protected]
