Re: PianoPedalBracket.to-barline doesn't always work as expected

2024-04-09 Thread Aaron Hill
On 2024-04-09 2:55 pm, Maurits Lamers via LilyPond user discussion 
wrote:
Only when the \sustainOff is placed outside of the tremolo, the bracket 
extends to the barline:


%%%

\version "2.24.0"
\score {
  \new Staff {
    \clef bass
    \time 6/8
    \relative c' {
  c8 b a g e c |
  \set Staff.pedalSustainStyle = #'mixed
  \override Staff.PianoPedalBracket.to-barline = ##t
  \repeat tremolo 12 { b,32\sustainOn b' } |
  \repeat tremolo 12 { b,32 b' }  \sustainOff |
  c8 e f g a
    }
  }
}

%%%

However, this leads to Lilypond complaining about an unattached 
SustainEvent. Is this a bug?



Does the empty chord construct help?

  <>\sustainOff

(I'm away from my normal environment, so I cannot test this locally to 
confirm.)



-- Aaron Hill



PianoPedalBracket.to-barline doesn't always work as expected

2024-04-09 Thread Maurits Lamers via LilyPond user discussion

Hey all,

I encountered a situation where the PianoPedalBracket setting to-barline 
doesn't always do what you'd expect. Given the following code, the pedal 
bracket is not extended to the end of the bar:


%%%

\version "2.24.0"
\score {
  \new Staff {
    \clef bass
    \time 6/8
    \relative c' {
  c8 b a g e c |
  \set Staff.pedalSustainStyle = #'mixed
  \override Staff.PianoPedalBracket.to-barline = ##t
  \repeat tremolo 12 { b,32\sustainOn b' } |
  \repeat tremolo 12 { b,32 b'\sustainOff  } |
  c8 e f g a
    }
  }
}

%%%

Only when the \sustainOff is placed outside of the tremolo, the bracket 
extends to the barline:


%%%

\version "2.24.0"
\score {
  \new Staff {
    \clef bass
    \time 6/8
    \relative c' {
  c8 b a g e c |
  \set Staff.pedalSustainStyle = #'mixed
  \override Staff.PianoPedalBracket.to-barline = ##t
  \repeat tremolo 12 { b,32\sustainOn b' } |
  \repeat tremolo 12 { b,32 b' }  \sustainOff |
  c8 e f g a
    }
  }
}

%%%

However, this leads to Lilypond complaining about an unattached 
SustainEvent. Is this a bug?


cheers

Maurits





Re: Lead sheets: Maj. 7 chords

2024-04-09 Thread Ivan Kuznetsov
And that was it!
Thank you so much.

On Tue, Apr 9, 2024 at 3:50 PM Aaron Hill  wrote:
>
> You need to adjust the majorSevenSymbol [1].
>
> [1]:
> https://lilypond.org/doc/v2.25/Documentation/notation/customizing-chord-names#chord-name-major7
>



Re: Lead sheets: Maj. 7 chords

2024-04-09 Thread Aaron Hill

On 2024-04-09 1:43 pm, Ivan Kuznetsov wrote:

have been creating some lead sheets in
the style of the "Real Book", using
the \chords{} syntax.  However,
I do not like the way the default
notates "major 7 chords", that is,
a major triad with a major seventh.

The default is to use a "triangle"
to notate such a chord (shown below
in my example" but I much prefer
the way the Real Book notates
such chords, by writing out
"maj7".

How can I get the \chords {} syntax
to notate "major 7 chords as
I prefer, using the notation
"maj7" ?



You need to adjust the majorSevenSymbol [1].

[1]: 
https://lilypond.org/doc/v2.25/Documentation/notation/customizing-chord-names#chord-name-major7



-- Aaron Hill



Lead sheets: Maj. 7 chords

2024-04-09 Thread Ivan Kuznetsov
 have been creating some lead sheets in
the style of the "Real Book", using
the \chords{} syntax.  However,
I do not like the way the default
notates "major 7 chords", that is,
a major triad with a major seventh.

The default is to use a "triangle"
to notate such a chord (shown below
in my example" but I much prefer
the way the Real Book notates
such chords, by writing out
"maj7".

How can I get the \chords {} syntax
to notate "major 7 chords as
I prefer, using the notation
"maj7" ?

Thank you for your help.


\score {

  <<
  \chords { bf1:maj7 }
  \new Staff = "mel"
  {
\time 4/4
\clef "treble"
c''1

  }
  >>

}



Re: Organ pedal marks in various styles, including pedal glides: new snippet 1184

2024-04-09 Thread Fernando Gil
This is extremely helpful, thank you so much!

El mar, 9 abr 2024 a las 6:40, Rudolf Cardinal ()
escribió:

> Dear Lilypond users with an interest in organ music,
>
> Lilypond's standard commands for organ pedal marks are: \lheel, \ltoe,
> \rheel, \rtoe. However, there are several recognized ways of displaying
> pedal marks visually. I struggled a little to get Lilypond's organ pedal
> marks into a style that I was most familiar with. I note previous
> discussion about this and related issues at e.g.
>
>-
>https://lists.gnu.org/archive/html/lilypond-user/2010-12/msg00387.html,
>re: organ pedalboard fingerings;
>-
>https://lists.gnu.org/archive/html/lilypond-user/2007-12/msg00333.html,
>organ pedal marks and substitution;
>-
>https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00683.html,
>organ pedal foot substitution;
>-
>https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00713.html,
>globally change organ pedal articulations;
>-
>https://lists.gnu.org/archive/html/lilypond-user/2016-05/msg00206.html,
>question about same-foot organ pedal substitutions;
>-
>https://lists.gnu.org/archive/html/lilypond-user/2016-11/msg00087.html,
>follow-up: organ pedal toe-to-heel-shift.
>
>
> I've created a snippet to address this. It allows you to pick the pedal
> mark style:
>
>- Lilypond default with outward-pointing toes and outward-pointing
>heels;
>- "modern" with inward toes and circle heels (e.g. Trevor 1971, "The
>Oxford Organ Method");
>- "traditional" with upward toes and downward heels (e.g. Bach/Novello
>1948).
>
>
> After choosing the style, you can use standard pedal commands.
>
> The snippet also defines some new pedal indicator commands, including for
> heel/toe transitions; foot slide marks (for sliding a foot forward/backward
> on a pedal); "foot behind"/"foot in front" marks, for crossing feet; "foot
> forward/backward" marks, for when feet are adjacent; and "foot
> substitution" (foot change, foot transition) marks, for swapping feet
> whilst pressing a single pedal. These augmented marks follow Trevor (1971,
> as above), and can be used with any of the pedal mark styles.
>
> Finally, it defines an engraver allowing foot glide/glissando marks using
> the standard "\glide" command.
>
> The snippet is at https://lsr.di.unimi.it/LSR/Item?id=1184. It includes a
> demonstration, but that can be chopped off to provide a file for inclusion
> by any other music, as described in the snippet.
>
> Many thanks to Thomas "Harm" Morley for feedback, and to all those who
> maintain Lilypond and the Lilypond Snippet Repository, including Sebastiano
> Vigna and Werner Lemberg.
>
> all the best,
> Rudolf.
>
>


Re: Fwd: nested beaming

2024-04-09 Thread Paul Scott
It looks like I was wrong about \set subdivideBeams = ##f canceling \set 
subdivideBeams = ##t . It was another part in a score where it wasn't 
canceled affect the line I was working on.


Paul

On 4/9/24 9:28 AM, Paul Scott wrote:


Forgot to send to list.



 Forwarded Message 
Subject:Re: nested beaming
Date:   Tue, 9 Apr 2024 09:26:22 -0700
From:   Paul Scott 
To: Carl Sorensen 



On 4/8/24 3:59 PM, Carl Sorensen wrote:



On Mon, Apr 8, 2024 at 4:51 PM Carl Sorensen 
 wrote:




On Mon, Apr 8, 2024 at 11:14 AM Paul Scott
 wrote:


The case at the moment is with long groups of triplets of
which the
following is now a part:

{
   \time 2/4
   \tuplet 3/2 8 {
 a'16 16 \set stemRightBeamCount = 1 16 \set
stemLeftBeamCount = 1
16 16 16
   }
}

I think that after last summer's GSOC project on beaming,
this now works correctly out of the box:



My mistake.  These changes didn't get in until 2.25

\version "2.25.11"  % but earlier 2.25 versions may work
{
   \time 2/4
   \set subdivideBeams = ##t
   \tuplet 3/2 8 {
     a'16 16  16
16 16 16
   }
}


Carl


It worked for the triplets but \set subdivideBeams = ##f doesn't turn 
it off for following music.


Paul




Fwd: nested beaming

2024-04-09 Thread Paul Scott

Forgot to send to list.



 Forwarded Message 
Subject:Re: nested beaming
Date:   Tue, 9 Apr 2024 09:26:22 -0700
From:   Paul Scott 
To: Carl Sorensen 



On 4/8/24 3:59 PM, Carl Sorensen wrote:



On Mon, Apr 8, 2024 at 4:51 PM Carl Sorensen 
 wrote:




On Mon, Apr 8, 2024 at 11:14 AM Paul Scott
 wrote:


The case at the moment is with long groups of triplets of
which the
following is now a part:

{
   \time 2/4
   \tuplet 3/2 8 {
 a'16 16 \set stemRightBeamCount = 1 16 \set
stemLeftBeamCount = 1
16 16 16
   }
}

I think that after last summer's GSOC project on beaming, this
now works correctly out of the box:



My mistake.  These changes didn't get in until 2.25

\version "2.25.11"  % but earlier 2.25 versions may work
{
   \time 2/4
   \set subdivideBeams = ##t
   \tuplet 3/2 8 {
     a'16 16  16
16 16 16
   }
}


Carl


It worked for the triplets but \set subdivideBeams = ##f doesn't turn it 
off for following music.


Paul



Re: nested beaming

2024-04-09 Thread Hans Åberg


> On 8 Apr 2024, at 18:46, Simon Albrecht  wrote:
> 
> On 08.04.24 18:22, Paul Scott wrote:
>> Many years ago I could nest square brackets in Lilypond. How can I write 
>> this now incorrect code:
>> 
>> a16[[ 16 16] 16[ 16 16]]  i.e. two groups of 3 beamed 16th notes joined by a 
>> single beam.
> 
> The question is: what is the context and why do you want this?

In the past, it was possible to give 9/16 the beat structure [[2 2] [2 3]], as 
a 2/4 with an extra 1/16 at the end, like in the Bulgarian Daichovo, but 
currently it is only possible with [4 2 3] as in:
 \time 9/16
 \set beatStructure = #'(4 2 3)
Or [2 2 2 3]. But [[2 2] [2 3]] is easier to read.

> Normally, this is called subdividing beams and there is a context property to 
> turn it on. This is explained in the NR at Rhythms -> Beams -> Setting 
> automatic beam behaviour (or similar). There have recently been significant 
> improvements to how LilyPond handles this, but IIRC it’s not fully ‘there’ 
> yet and in some situations manual intervention is needed besides defining 
> baseMoment etc.

But this has not yet been implemented?





Organ pedal marks in various styles, including pedal glides: new snippet 1184

2024-04-09 Thread Rudolf Cardinal
Dear Lilypond users with an interest in organ music,

Lilypond's standard commands for organ pedal marks are: \lheel, \ltoe, \rheel, 
\rtoe. However, there are several recognized ways of displaying pedal marks 
visually. I struggled a little to get Lilypond's organ pedal marks into a style 
that I was most familiar with. I note previous discussion about this and 
related issues at e.g.

  *
https://lists.gnu.org/archive/html/lilypond-user/2010-12/msg00387.html, re: 
organ pedalboard fingerings;
  *
https://lists.gnu.org/archive/html/lilypond-user/2007-12/msg00333.html, organ 
pedal marks and substitution;
  *
https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00683.html, organ 
pedal foot substitution;
  *
https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00713.html, 
globally change organ pedal articulations;
  *
https://lists.gnu.org/archive/html/lilypond-user/2016-05/msg00206.html, 
question about same-foot organ pedal substitutions;
  *
https://lists.gnu.org/archive/html/lilypond-user/2016-11/msg00087.html, 
follow-up: organ pedal toe-to-heel-shift.

I've created a snippet to address this. It allows you to pick the pedal mark 
style:

  *
Lilypond default with outward-pointing toes and outward-pointing heels;
  *
"modern" with inward toes and circle heels (e.g. Trevor 1971, "The Oxford Organ 
Method");
  *
"traditional" with upward toes and downward heels (e.g. Bach/Novello 1948).

After choosing the style, you can use standard pedal commands.

The snippet also defines some new pedal indicator commands, including for 
heel/toe transitions; foot slide marks (for sliding a foot forward/backward on 
a pedal); "foot behind"/"foot in front" marks, for crossing feet; "foot 
forward/backward" marks, for when feet are adjacent; and "foot substitution" 
(foot change, foot transition) marks, for swapping feet whilst pressing a 
single pedal. These augmented marks follow Trevor (1971, as above), and can be 
used with any of the pedal mark styles.

Finally, it defines an engraver allowing foot glide/glissando marks using the 
standard "\glide" command.

The snippet is at https://lsr.di.unimi.it/LSR/Item?id=1184. It includes a 
demonstration, but that can be chopped off to provide a file for inclusion by 
any other music, as described in the snippet.

Many thanks to Thomas "Harm" Morley for feedback, and to all those who maintain 
Lilypond and the Lilypond Snippet Repository, including Sebastiano Vigna and 
Werner Lemberg.

all the best,
Rudolf.