Re: Cross-staff glissando with crescendo and dynamics

2022-03-22 Thread Leo Correia de Verdier
Hi David!

The issue, put in a slightly simplified way, is that the Voice context to which 
the dynamics are attached has moved away from the Staff under which the 
dynamics were originally aligned, leaving lilypond ”in doubt” about under what 
staff the \mp should be.

The answer in the linked thread solves this by creating a second Voice for the 
dynamics, that stays in the original Staff.

The other solution mentioned, which I’d prefer (but that may be a matter of 
taste) would be creating a separate Dynamics context.

HTH
/Leo

> 22 mars 2022 kl. 13:55 skrev David Santamauro :
> 
> So I figured it out based on:
>  
> https://lists.gnu.org/archive/html/lilypond-user/2016-07/msg00266.html
>  
> Not an unreasonable solution, but I still don't quite understand the 
> underlying issue.
>  
> Thanks
>  
>  
> From: David Santamauro 
> Date: Tuesday, March 22, 2022 at 8:36 AM
> To: lilypond-user@gnu.org 
> Cc: GMAIL 
> Subject: Cross-staff glissando with crescendo and dynamics
> 
> Hi, I'm not understanding the warnings I'm getting with the following 
> snippet. I've included a possible work-around that is musically identical, 
> but visually unappealing:
>  
> %%
> \version "2.22.2"
>  
> \include "english.ly"
>  
> \score {
>   \new PianoStaff \with { instrumentName = "Harp" } <<
> \new Staff = "s_harp_upper" {
>   \relative c'' {
> \clef "treble"
> s1|
> s4 r4 r2  |
>  
> % work around without warnings
> R1*2
>   }
> }
> \new Staff = "s_harp_lower" {
>   \relative c {
> \clef "bass"
>  
> f,1\p\glissando\<
> \change Staff = "s_harp_upper"
> bf'''4\!\mp
> \change Staff = "s_harp_lower"
> r4 r2
>  
> % work around without warnings
> f,,,1\p\glissando\< \clef "treble" bf'''4\!\mp   r4 r2
>   }
> }
>   >>
> }
> %%
>  
> For the cross-staff I get 4 of these:
>  
> programming error: My pure_y_common is a VerticalAlignment, which might 
> contain several staves.
> continuing, cross fingers
>  
> Can someone explain what those warnings mean and how to code the cross-staff 
> gliss with dynamics and crescendo. correctly?
>  
> Thanks




Re: Cross-staff glissando with crescendo and dynamics

2022-03-22 Thread Jean Abou Samra




Le 22/03/2022 à 13:36, David Santamauro a écrit :


Hi, I'm not understanding the warnings I'm getting with the following 
snippet. I've included a possible work-around that is musically 
identical, but visually unappealing:


%%

\version "2.22.2"

\include "english.ly"

\score {

  \new PianoStaff \with { instrumentName = "Harp" } <<

    \new Staff = "s_harp_upper" {

\relative *c''* {

\clef "treble"

*s1*       |

*s4* *r4* *r2*  |

        % work around without warnings

*R1*2*

      }

    }

    \new Staff = "s_harp_lower" {

\relative *c* {

\clef "bass"

*f,1*\p\glissando\<

\change Staff = "s_harp_upper"

*bf'''4*\!\mp

\change Staff = "s_harp_lower"

*r4* *r2*

        % work around without warnings

*f,,,1*\p\glissando\< \clef "treble" *bf'''4*\!\mp *r4* *r2*

      }

    }

  >>

}

%%

For the cross-staff I get 4 of these:

programming error: My pure_y_common is a VerticalAlignment, which 
might contain several staves.


continuing, cross fingers

Can someone explain what those warnings mean and how to code the 
cross-staff gliss with dynamics and crescendo. correctly?






Getting cross-staff cases right is depressingly hard. I've opened
https://gitlab.com/lilypond/lilypond/-/issues/6306

However, I think you need to clarify how you expect it to
render in the first place. Normally, consecutive dynamics
stay vertically aligned on the same baseline. Here this
does not work, because the mp needs to jump in the
upper staff. What would you do to typeset this if you
were LilyPond?

Jean





Re: Cross-staff glissando with crescendo and dynamics

2022-03-22 Thread David Santamauro
So I figured it out based on:

https://lists.gnu.org/archive/html/lilypond-user/2016-07/msg00266.html

Not an unreasonable solution, but I still don't quite understand the underlying 
issue.

Thanks


From: David Santamauro 
Date: Tuesday, March 22, 2022 at 8:36 AM
To: lilypond-user@gnu.org 
Cc: GMAIL 
Subject: Cross-staff glissando with crescendo and dynamics
Hi, I'm not understanding the warnings I'm getting with the following snippet. 
I've included a possible work-around that is musically identical, but visually 
unappealing:

%%
\version "2.22.2"

\include "english.ly"

\score {
  \new PianoStaff \with { instrumentName = "Harp" } <<
\new Staff = "s_harp_upper" {
  \relative c'' {
\clef "treble"
s1|
s4 r4 r2  |

% work around without warnings
R1*2
  }
}
\new Staff = "s_harp_lower" {
  \relative c {
\clef "bass"

f,1\p\glissando\<
\change Staff = "s_harp_upper"
bf'''4\!\mp
\change Staff = "s_harp_lower"
r4 r2

% work around without warnings
f,,,1\p\glissando\< \clef "treble" bf'''4\!\mp   r4 r2
  }
}
  >>
}
%%

For the cross-staff I get 4 of these:

programming error: My pure_y_common is a VerticalAlignment, which might contain 
several staves.
continuing, cross fingers

Can someone explain what those warnings mean and how to code the cross-staff 
gliss with dynamics and crescendo. correctly?

Thanks



Cross-staff glissando with crescendo and dynamics

2022-03-22 Thread David Santamauro
Hi, I'm not understanding the warnings I'm getting with the following snippet. 
I've included a possible work-around that is musically identical, but visually 
unappealing:

%%
\version "2.22.2"

\include "english.ly"

\score {
  \new PianoStaff \with { instrumentName = "Harp" } <<
\new Staff = "s_harp_upper" {
  \relative c'' {
\clef "treble"
s1|
s4 r4 r2  |

% work around without warnings
R1*2
  }
}
\new Staff = "s_harp_lower" {
  \relative c {
\clef "bass"

f,1\p\glissando\<
\change Staff = "s_harp_upper"
bf'''4\!\mp
\change Staff = "s_harp_lower"
r4 r2

% work around without warnings
f,,,1\p\glissando\< \clef "treble" bf'''4\!\mp   r4 r2
  }
}
  >>
}
%%

For the cross-staff I get 4 of these:

programming error: My pure_y_common is a VerticalAlignment, which might contain 
several staves.
continuing, cross fingers

Can someone explain what those warnings mean and how to code the cross-staff 
gliss with dynamics and crescendo. correctly?

Thanks