Re: Controlling Slur Marks

2022-08-31 Thread Simon Albrecht

Hi Greg,

great to hear you’re starting with LilyPond!

On 30/08/2022 21:52, Greg Lindstrom wrote:
I see later in the documentation there is a snippet on how to merge 
voices, so that's next on my list.



There’s one bit of important advice that usually makes the experience of 
learning LilyPond (which can be steep and/or daunting) much better: 
fully read and understand the Learning Manual at least once. It’s 
important to grasp some fundamental concepts such as to avoid 
misunderstandings down the line.


Voices are one of those concepts, so you’re definitely on the right 
track there ;)


Best, Simon




Re: Padding paper setting not honored

2022-08-31 Thread Knute Snortum
On Tue, Aug 30, 2022 at 4:45 PM Jean Abou Samra  wrote:
>
> Le 31/08/2022 à 01:33, Knute Snortum a écrit :
> > Hi everyone,
> >
> > I have a problem that is unfortunately very difficult to reproduce.
> > It seems in some circumstances that the padding setting in the paper
> > block is not honored.  I've attached a screenshot.  In the middle you
> > can see that the slur from the bottom stave is going through the pedal
> > marking of the top stave.  It looks like the padding is measured from
> > the ottava bracket and not the slur, but that's just a guess.
> >
> > I have tried and failed to create a MWE.  I've attached my attempt but
> > unfortunately it does not reproduce the problem. (I couldn't get the
> > ottava bracket below the slur which may be why the MWE fails.)
> >
> > For the brave, I have uploaded my source files to GitHub:
> > https://github.com/ksnortum/chopin-opus-25/tree/main
> >
> > If anyone is willing to tackle this problem, it would be much appreciated.
>
>
>
> Well, here is a reasonably minimal example:
>
> \version "2.23.12"
>
> veryHigh =
>\shape #'((0 . 0) (0 . 10) (0 . 10) (0 . 0)) \etc
>
> <<
>\new Staff {
>  R1
>  \break
>  % OK
>  c'''2\veryHigh ( 2)
>  \break
>  % KO
>  c'''2\veryHigh ( \change Staff = down 2)
>}
>\new Staff = down {
>  s1*3
>}
>  >>
>
>
> Unfortunately, this is hard to fix. The second is cross-staff. Because of
> this, its shape, and consequently its height, depend on the exact distance
> between the staves (inside one system). But that distance depends itself
> on everything else that is on the page (other systems), as LilyPond will
> try to find a good fit for the page globally. So LilyPond needs to space
> the staves before it can know how tall the slur it is.
>
> (*Maybe* it would be possible to let LilyPond reuse the pure height
> estimation
> in this case. I'm not sure, and I haven't tried.)
>
> For now, I am afraid you need to resort to manual system positioning,
> as described on
>
> https://lilypond.org/doc/v2.22/Documentation/notation/explicit-staff-and-system-positioning
>
> Best,
> Jean
>
>

Thanks Jean, for looking into this, and for the MWE.

--
Knute Snortum



More efficient way to code some fingering?

2022-08-31 Thread Joseph Srednicki
The example below shows some fingerings as I would like them to appear. 
Is there a better and more efficient way to code this music and achieve the 
same result without using multiple \finger commands for the same note?
(I am placing the fingerings above the notes to indicate clearly that they 
pertain to right hand. In some places, the left hand must strike some notes in 
the second or lower voice. My score places any fingering pertaining to the left 
hand below the notes in the second voice. Therefore, I do not want to place any 
right-hand fingerings below the notes of the second voice.)
If the Lilypond documentation or snippets provide a good example of a better 
way to do what I am trying to achieve and I missed it, please point me to 
appropriate references.
Thanks for any advice.
Joe Srednicki
* 
\version "2.22.2"\language "english"
global = {  \key c \major  \numericTimeSignature  \time 2/4}
rightOne = \relative c'' {  \global  e4^5 fs^\finger "2" ^\finger "5" | }
rightTwo = \relative c'' {  \global    c16 b c^\finger "2" ^\finger "5-4" d c e 
d c | }
\score {  \new PianoStaff  <<    \new Staff = "right" << \rightOne \\ \rightTwo 
>>  >>}

Re: More efficient way to code some fingering?

2022-08-31 Thread Valentin Petzel
Hello Joseph,

\finger is only really necessary for using a markup as fingering indication 
(like in \finger "5-4"). For simple numeric fingerings you can always use ^/-/_ 
with a number. So instead of fs^\finger "2" ^\finger "5" simply do ^2^5.

Cheers,
Valentin

Am Mittwoch, 31. August 2022, 20:48:29 CEST schrieb Joseph Srednicki:
> The example below shows some fingerings as I would like them to appear. 
> Is there a better and more efficient way to code this music and achieve the
> same result without using multiple \finger commands for the same note? (I
> am placing the fingerings above the notes to indicate clearly that they
> pertain to right hand. In some places, the left hand must strike some notes
> in the second or lower voice. My score places any fingering pertaining to
> the left hand below the notes in the second voice. Therefore, I do not want
> to place any right-hand fingerings below the notes of the second voice.) If
> the Lilypond documentation or snippets provide a good example of a better
> way to do what I am trying to achieve and I missed it, please point me to
> appropriate references. Thanks for any advice.
> Joe Srednicki
> * 
> \version "2.22.2"\language "english"
> global = {  \key c \major  \numericTimeSignature  \time 2/4}
> rightOne = \relative c'' {  \global  e4^5 fs^\finger "2" ^\finger "5" | }
> rightTwo = \relative c'' {  \globalc16 b c^\finger "2" ^\finger "5-4" d
> c e d c | } \score {  \new PianoStaff  <<\new Staff = "right" <<
> \rightOne \\ \rightTwo >>  >>}



signature.asc
Description: This is a digitally signed message part.