Re: Showing fingerings in front of slurs

[Trevor Bača]

Hi Paul,

Try setting Fingering.avoid-slur to #'ignore:

%%% BEGIN %%%

\version "2.25.19"
\language "english"

\relative
{
  \override Fingering.avoid-slur = #'ignore % <== add this
  \override Fingering.layer = 2
  \override Fingering.whiteout = ##t
  r4 r8  -1-3 ( 16 -2-4  -1-5 -2-4 -3-5 )
}

%%% END %%%

[image: Fingering-avoid-slur-ignore.png]

Trevor.


On Thu, May 9, 2024 at 10:25 AM Paul McKay  wrote:

> Hi
> I want to show fingerings in front of slurs in a manner very like that
> demonstrated in the "Using the whiteout property" snippet
>
> This is what I've tried:
> \version "2.24.0"
> \language "english"
>
> \relative {
> \override Staff.Fingering.layer = 2 % fingering should overwrite
> slurs
>  \override Staff.Fingering.whiteout = ##t
> r4 r8 -1-3( 16-2-4 -1-5-2-4-3-5)
> }
>
> but the fingerings still avoid the slurs. I want them to appear just where
> they would if the Slurs weren't there at all.
> What am I missing?
> Thanks
> Paul McKay
>


-- 
Trevor Bača
www.trevorbaca.com
soundcloud.com/trevorbaca

Re: Vertical positions of slurs and accents

[Mats Bengtsson]

  
  


On 2024-09-27 17:14, David Sumbler
  wrote:


  Thanks - that's perfect.  The difficulty I had was that I
couldn't figure out what class of object an accent is.  I had
already tried
  
  
  	\override
TextScript.avoid-slur = #'inside
  
  
  but this of course doesn't work.  I couldn't find out from
the documentation how accents etc. are classified, although I
expect it is there somewhere.

I tried Googling for "Lilypond articulations" and looking at the
  hits that pointed to the notation reference manual quickly led me
  to
https://lilypond.org/doc/v2.24/Documentation/notation/expressive-marks-attached-to-notes
  where it says:
"The type of grob that an articulation creates depends on what it
  is attached to.
  
      On notes or ordinary rests, articulations create Script
  objects.
      On multi-measure rests, articulations create
  MultiMeasureRestScript objects.
      On \caesura, articulations create CaesuraScript objects. "
  
     /Mats

  

Re: Vertical positions of slurs and accents

[Werner LEMBERG]

> The difficulty I had was that I couldn't figure out what class of
> object an accent is.  I had already tried
> 
>  \override TextScript.avoid-slur = #'inside
> 
> but this of course doesn't work.  I couldn't find out from the
> documentation how accents etc. are classified, although I expect it
> is there somewhere.

Look into `scm/script.scm`.  This is indeed not really documented.
I've created

  https://gitlab.com/lilypond/lilypond/-/issues/6753

to track that.


Werner

Re: Vertical positions of slurs and accents

[Timothy Lanfear]

On 27/09/2024 16:14, David Sumbler wrote:



On Fri, 2024-09-27 at 07:54 -0700, Knute Snortum wrote:


On Fri, Sep 27, 2024 at 7:42 AM David Sumbler  wrote:
How do I persuade Lilypond to position all accent marks inside 
slurs?  At the moment, in a passage containing numerous accents and 
slurs, I am finding that some accents are outside the slur and some 
inside, which looks a mess!




It's hard to help you with a Minimum WorkingExample (MWE, see 
https://lilypond.org/tiny-examples.html) but a sledgehammer approach 
would be to use...


\override Script.avoid-slur = #'inside

This will force ALL Scripts inside of the slurs, but that means other 
things like pralls and turns too.  You could do them one by one with:


\tweak avoid-slur = #'inside

Post a MWE for us to work with and we'll give you a better answer.


Thanks - that's perfect.  The difficulty I had was that I couldn't 
figure out what class of object an accent is.  I had already tried


\override TextScript.avoid-slur = #'inside

but this of course doesn't work.  I couldn't find out from the 
documentation how accents etc. are classified, although I expect it is 
there somewhere.


If you would like to modify the avoid-slur behaviour of all accents (but 
not other articulations) you could try this.


\version "2.24.0"

#(let* ((name 'accent)
    (newvalue '(avoid-slur . inside))
    (articulation (assoc-ref default-script-alist name)))
   (set! articulation (assoc-remove! articulation (car newvalue)))
   (set! articulation (assoc-set! articulation (car newvalue) (cdr 
newvalue)))
   (set! default-script-alist (assoc-set! default-script-alist name 
articulation)))


{
  a'4( b'^\trill c''^> d'')
}


--
Timothy Lanfear, Bristol, UK.

Re: Vertical positions of slurs and accents

[Knute Snortum]

--
Knute Snortum



On Fri, Sep 27, 2024 at 8:14 AM David Sumbler  wrote:

>
>
> On Fri, 2024-09-27 at 07:54 -0700, Knute Snortum wrote:
>
>
> On Fri, Sep 27, 2024 at 7:42 AM David Sumbler  wrote:
>
> How do I persuade Lilypond to position all accent marks inside slurs?  At
> the moment, in a passage containing numerous accents and slurs, I am
> finding that some accents are outside the slur and some inside, which looks
> a mess!
>
>
> It's hard to help you with a Minimum WorkingExample (MWE, see
> https://lilypond.org/tiny-examples.html) but a sledgehammer approach
> would be to use...
>
> \override Script.avoid-slur = #'inside
>
> This will force ALL Scripts inside of the slurs, but that means other
> things like pralls and turns too.  You could do them one by one with:
>
> \tweak avoid-slur = #'inside
>
> Post a MWE for us to work with and we'll give you a better answer.
>
>
> Thanks - that's perfect.  The difficulty I had was that I couldn't figure
> out what class of object an accent is.  I had already tried
>
> \override TextScript.avoid-slur = #'inside
>
> but this of course doesn't work.  I couldn't find out from the
> documentation how accents etc. are classified, although I expect it is
> there somewhere.
>

I don't know if this is in the documentation, but I found it by searching
for "lilypond visual grob index":

https://lilypond.org/ly-examples/visualindex.pdf

Re: Vertical positions of slurs and accents

[David Sumbler]

On Fri, 2024-09-27 at 07:54 -0700, Knute Snortum wrote:
> 
> On Fri, Sep 27, 2024 at 7:42 AM David Sumbler 
> wrote:
> > How do I persuade Lilypond to position all accent marks inside
> > slurs?  At the moment, in a passage containing numerous accents and
> > slurs, I am finding that some accents are outside the slur and some
> > inside, which looks a mess!
> > 
> 
> 
> It's hard to help you with a Minimum WorkingExample (MWE,
> see https://lilypond.org/tiny-examples.html) but a sledgehammer
> approach would be to use...
> 
> \override Script.avoid-slur = #'inside
> 
> This will force ALL Scripts inside of the slurs, but that means other
> things like pralls and turns too.  You could do them one by one with:
> 
> \tweak avoid-slur = #'inside
> 
> Post a MWE for us to work with and we'll give you a better answer.

Thanks - that's perfect.  The difficulty I had was that I couldn't
figure out what class of object an accent is.  I had already tried

 \override TextScript.avoid-slur = #'inside

but this of course doesn't work.  I couldn't find out from the
documentation how accents etc. are classified, although I expect it is
there somewhere.

David

Re: Vertical positions of slurs and accents

[Knute Snortum]

On Fri, Sep 27, 2024 at 7:42 AM David Sumbler  wrote:

> How do I persuade Lilypond to position all accent marks inside slurs?  At
> the moment, in a passage containing numerous accents and slurs, I am
> finding that some accents are outside the slur and some inside, which looks
> a mess!
>

It's hard to help you with a Minimum WorkingExample (MWE, see
https://lilypond.org/tiny-examples.html) but a sledgehammer approach would
be to use...

\override Script.avoid-slur = #'inside

This will force ALL Scripts inside of the slurs, but that means other
things like pralls and turns too.  You could do them one by one with:

\tweak avoid-slur = #'inside

Post a MWE for us to work with and we'll give you a better answer.


--
Knute Snortum

Vertical positions of slurs and accents

[David Sumbler]

How do I persuade Lilypond to position all accent marks inside slurs?
 At the moment, in a passage containing numerous accents and slurs, I
am finding that some accents are outside the slur and some inside,
which looks a mess!

David

Re: Slurs across staves, reach both notes

[Valentin Petzel]

Hello William,

this works out totally fine. It’s just that with that very tight spacing 
Lilypond’s merit algorithm cannot have the Slur go from head to head. Say if 
we drastically increase the demerit for distance to the edge points:

%%%
\score {
  <<
\new Staff = "a" {
  \override Slur.details.edge-attraction-factor = #10
  c''4^( \change Staff = "c" c'')
  \change Staff = "a" c''4_( \change Staff = "c" c'') 
}
\new Staff = "b" s1
\new Staff = "c" s1
  >>
}
 %%%

this will work out. Also if the horizontal distance between the notes was 
larger this would also work out better:

%%%
\score {
  <<
\new Staff = "a" {
  c''4^( \change Staff = "c"  s s s c'') s s s
  \change Staff = "a" c''4_( s s s \change Staff = "c" c'')
}
\new Staff = "b" s1*3
\new Staff = "c" s1*3
  >>
}
 %%%

Cheers,
Valentin

Am Freitag, 12. Juli 2024, 03:34:17 MESZ schrieb William Rehwinkel via 
LilyPond user discussion:
> Dear list,
> 
> In the following example, is there a way to make the slurs reach across 
> all the staves to reach both notes?
> 
> I'm very sorry, I could have sworn that I could make slurs across staves 
> work correctly in the past, but I must have forgotten.
> 
> Thanks,
> -William
> 
> % --
> \version "2.25.16"
> 
> \score { <<
>\new Staff = "a" << { c''4^( \change Staff = "c" c'') \change Staff = 
> "a" c''4_( \change Staff = "c" c'')  } \new Voice s1 >>
>\new Staff = "b" s1
>\new Staff = "c" s1
> 
>  >> }
> 
> % --
> 
> -- 
> William Rehwinkel (any pronouns)
> Juilliard School '26 - Oberlin Conservatory '24
> will...@williamrehwinkel.net - https://williamrehwinkel.net
> PGP Public Key: https://ftp.williamrehwinkel.net/pubkey.txt



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

Slurs across staves, reach both notes

[William Rehwinkel via LilyPond user discussion]

Dear list,

In the following example, is there a way to make the slurs reach across 
all the staves to reach both notes?


I'm very sorry, I could have sworn that I could make slurs across staves 
work correctly in the past, but I must have forgotten.


Thanks,
-William

% --
\version "2.25.16"

\score { <<
  \new Staff = "a" << { c''4^( \change Staff = "c" c'') \change Staff = 
"a" c''4_( \change Staff = "c" c'')  } \new Voice s1 >>

  \new Staff = "b" s1
  \new Staff = "c" s1
>> }
% --

--
William Rehwinkel (any pronouns)
Juilliard School '26 - Oberlin Conservatory '24
will...@williamrehwinkel.net - https://williamrehwinkel.net
PGP Public Key: https://ftp.williamrehwinkel.net/pubkey.txt


OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: Spontini line break slurs

[Paolo Prete]

This has already been reported some time ago:

https://github.com/paopre/Spontini/issues/18

You can bypass it by simply using two shapes:


%
\version "2.24.0"

\include "../lib/ly/jssvg.ly"

\score {
  \relative c' {
c d e << {s8\jsShape "1" "cpts" #'() ^( s) }{ g4 } >>
\break g4\jsShape "2" "cpts" #'() ( a b c-)
  }
}
%

HTH!
Paolo



On Sun, Jun 16, 2024 at 7:45 PM bobr...@centrum.is 
wrote:

> I think I may have run across a bug/limitation of Spontini.  I was
> adjusting slurs.  When I adjusted one that occurred over a line break I got
> unexpected results.  I eventually figured out that only the part before the
> line break was changing even if I only moved the control points of the slur
> after the line break.  Below follows a *.ly snippet without any
> alterations.  Running this in Spontini and moving the control points will
> illustrate this.
>
> -David
>
> %
> \version "2.24.2"
>
> \include "../lib/ly/jssvg.ly"
>
> \score {
>   \relative c' {
> c d e f \jsShape "1" "cpts" #'() -(
> \break
> g a b c-)
>   }
> }
> %
>

Spontini line break slurs

[bobr...@centrum.is]

I think I may have run across a bug/limitation of Spontini. I was adjusting 
slurs. When I adjusted one that occurred over a line break I got unexpected 
results. I eventually figured out that only the part before the line break was 
changing even if I only moved the control points of the slur after the line 
break. Below follows a *.ly snippet without any alterations. Running this in 
Spontini and moving the control points will illustrate this. 

-David 

% 
\version "2.24.2" 

\include "../lib/ly/jssvg.ly" 

\score { 
\relative c' { 
c d e f \jsShape "1" "cpts" #'() -( 
\break 
g a b c-) 
} 
} 
% 

Re: RehearsalMarks, slurs and ties overlapping

[Federico Sarudiansky]

Yes, playing with different combinations of ##f (an idea I've never thought
about) and different values seems to do the trick.
Thanks, Leo.

El vie, 14 jun 2024 a las 12:27, Leo Correia de Verdier (<
leo.correia.de.verd...@gmail.com>) escribió:

> Setting
>   \override Score.RehearsalMark.outside-staff-priority = ##f
> could perhaps also be an option.
>
> > 13 juni 2024 kl. 16:49 skrev Federico Sarudiansky :
> >
> > Hi again, Kieren!
> >
> > Excellent! However I wonder if there is a more general approach.
> Something «allowing» the slurs not taking the rehearsal marks into
> consideration when defining its shape parameters.
> >
> > All the best!
> >
> > F.
> >
> > El jue, 13 jun 2024 a las 11:28, Kieren MacMillan (<
> kie...@kierenmacmillan.info>) escribió:
> > Hi Federico,
> >
> > > How can I overlap the perfect tie (slur) in A with the mark position
> in B and C so to use the .whiteout and .layer properties to put the
> slur/tie behind the mark and save some vertical space?
> >
> > Maybe something like this…?
> >
> > %%%  SNIPPET BEGINS
> > \version "2.25.11"
> >
> > \relative c''' {
> >   g1~ \mark \default g1
> >   g1~ \tweak extra-offset #'(-0.25 . -1.5) \tweak whiteout #2 \mark
> \default g1
> >   g1( \tweak extra-offset #'(-0.25 . -1.5) \tweak whiteout #2 \mark
> \default e1 )
> > }
> > %%%  SNIPPET ENDS
> >
> > Hope that helps!
> > Kieren.
> > __
> >
> > My work day may look different than your work day. Please do not feel
> obligated to read or respond to this email outside of your normal working
> hours.
> >
>
>

Re: RehearsalMarks, slurs and ties overlapping

[Kieren MacMillan]

Hi Leo (and Federico!),

> Setting 
>  \override Score.RehearsalMark.outside-staff-priority = ##f
> could perhaps also be an option.

Oh, yes… much better than my “nuclear” \ignore option!

%%%  SNIPPET BEGINS
\version "2.25.11"

\layout {
  \context {
\Score
\override RehearsalMark.outside-staff-priority = ##f
\override RehearsalMark.whiteout = #2
\override RehearsalMark.layer = #3
  }
}

\relative c''' { 
  g1~ \mark \default g1 
  g1~ \mark \default g1 
  g1( \mark \default e1 )  
}
%%%  SNIPPET ENDS

Thanks,
Kieren.
__

My work day may look different than your work day. Please do not feel obligated 
to read or respond to this email outside of your normal working hours.

Re: RehearsalMarks, slurs and ties overlapping

[Leo Correia de Verdier]

Setting 
  \override Score.RehearsalMark.outside-staff-priority = ##f
could perhaps also be an option.

> 13 juni 2024 kl. 16:49 skrev Federico Sarudiansky :
> 
> Hi again, Kieren! 
> 
> Excellent! However I wonder if there is a more general approach. Something 
> «allowing» the slurs not taking the rehearsal marks into consideration when 
> defining its shape parameters. 
> 
> All the best!
> 
> F. 
> 
> El jue, 13 jun 2024 a las 11:28, Kieren MacMillan 
> () escribió:
> Hi Federico,
> 
> > How can I overlap the perfect tie (slur) in A with the mark position in B 
> > and C so to use the .whiteout and .layer properties to put the slur/tie 
> > behind the mark and save some vertical space?
> 
> Maybe something like this…?
> 
> %%%  SNIPPET BEGINS
> \version "2.25.11"
> 
> \relative c''' { 
>   g1~ \mark \default g1 
>   g1~ \tweak extra-offset #'(-0.25 . -1.5) \tweak whiteout #2 \mark \default 
> g1 
>   g1( \tweak extra-offset #'(-0.25 . -1.5) \tweak whiteout #2 \mark \default 
> e1 )  
> }
> %%%  SNIPPET ENDS
> 
> Hope that helps!
> Kieren.
> __
> 
> My work day may look different than your work day. Please do not feel 
> obligated to read or respond to this email outside of your normal working 
> hours.
> 

Re: RehearsalMarks, slurs and ties overlapping

[Kieren MacMillan]

Hi Federico,

> How can I overlap the perfect tie (slur) in A with the mark position in B and 
> C so to use the .whiteout and .layer properties to put the slur/tie behind 
> the mark and save some vertical space?

Maybe something like this…?

%%%  SNIPPET BEGINS
\version "2.25.11"

\relative c''' { 
  g1~ \mark \default g1 
  g1~ \tweak extra-offset #'(-0.25 . -1.5) \tweak whiteout #2 \mark \default g1 
  g1( \tweak extra-offset #'(-0.25 . -1.5) \tweak whiteout #2 \mark \default e1 
)  
}
%%%  SNIPPET ENDS

Hope that helps!
Kieren.
__

My work day may look different than your work day. Please do not feel obligated 
to read or respond to this email outside of your normal working hours.

Re: RehearsalMarks, slurs and ties overlapping

[Kieren MacMillan]

Hi Federico,

> However I wonder if there is a more general approach. Something «allowing» 
> the slurs not taking the rehearsal marks into consideration when defining its 
> shape parameters.

This is fairly “nuclear”, but:

%%%  SNIPPET BEGINS
\version "2.25.11"

ignoreV =
   \propertyTweak vertical-skylines ##f
   \propertyTweak extra-spacing-height #empty-interval
   \etc

\relative c''' { 
  \ignoreV Score.RehearsalMark
  \override Score.RehearsalMark.Y-offset = #2.75
  \override Score.RehearsalMark.whiteout = #2
  g1~ \mark \default g1 
  g1~ \mark \default g1 
  g1( \mark \default e1 )  
}
%%%  SNIPPET ENDS

Hope that helps!
Kieren.
__

My work day may look different than your work day. Please do not feel obligated 
to read or respond to this email outside of your normal working hours.

Re: RehearsalMarks, slurs and ties overlapping

[Federico Sarudiansky]

Hi again, Kieren!

Excellent! However I wonder if there is a more general approach. Something
«allowing» the slurs not taking the rehearsal marks into consideration when
defining its shape parameters.

All the best!

F.

El jue, 13 jun 2024 a las 11:28, Kieren MacMillan (<
kie...@kierenmacmillan.info>) escribió:

> Hi Federico,
>
> > How can I overlap the perfect tie (slur) in A with the mark position in
> B and C so to use the .whiteout and .layer properties to put the slur/tie
> behind the mark and save some vertical space?
>
> Maybe something like this…?
>
> %%%  SNIPPET BEGINS
> \version "2.25.11"
>
> \relative c''' {
>   g1~ \mark \default g1
>   g1~ \tweak extra-offset #'(-0.25 . -1.5) \tweak whiteout #2 \mark
> \default g1
>   g1( \tweak extra-offset #'(-0.25 . -1.5) \tweak whiteout #2 \mark
> \default e1 )
> }
> %%%  SNIPPET ENDS
>
> Hope that helps!
> Kieren.
> __
>
> My work day may look different than your work day. Please do not feel
> obligated to read or respond to this email outside of your normal working
> hours.
>
>

RehearsalMarks, slurs and ties overlapping

[Federico Sarudiansky]

Hi.
Please consider the following:

\version "2.25.15"

\relative c''' {
  g1~ \mark \default g1

  \override Score.RehearsalMark.outside-staff-priority = #1
  \override Tie.outside-staff-priority = #2
  g1~ \mark \default g1

  \override Slur.outside-staff-priority = #2
  g1 ( \mark \default e1 )
}

It produces:

[image: image.png]
How can I overlap the perfect tie (slur) in A with the mark position in B
and C so to use the .whiteout and .layer properties to put the slur/tie
behind the mark and save some vertical space?
Thanks in advance!
Regards,
F.

Re: Showing fingering on top of slurs

[Knute Snortum]

On Thu, May 9, 2024 at 7:05 AM Paul McKay  wrote:

> Hi
> I want to show the fingering in front of the slurs. This should keep the
> fingerings evenly spaced vertically over the notes.  I have tried the
> following :
>
> \version "2.24.0"
> \language "english"
>
> \relative {
> \override Staff.Fingering.layer = 2 % fingering should overwrite
> slurs
> r4 r8 -1-3( 16-2-4 -1-5-2-4-3-5) }
>
> Fingerings still avoid the slurs.
> What am I missing?
>

I'm not sure what you want to achieve, but try adding the avoid-slur
property to the fingering:

\version "2.24.0"
\language "english"

\relative {
\override Staff.Fingering.layer = 2 % fingering should overwrite
slurs
\override Staff.Fingering.avoid-slur = #'ignore
r4 r8 -1-3( 16-2-4 -1-5-2-4-3-5) }

https://lilypond.org/doc/v2.24/Documentation/internals/slur


--
Knute Snortum

Showing fingerings in front of slurs

[Paul McKay]

Hi
I want to show fingerings in front of slurs in a manner very like that
demonstrated in the "Using the whiteout property" snippet

This is what I've tried:
\version "2.24.0"
\language "english"

\relative {
\override Staff.Fingering.layer = 2 % fingering should overwrite
slurs
 \override Staff.Fingering.whiteout = ##t
r4 r8 -1-3( 16-2-4 -1-5-2-4-3-5)
}

but the fingerings still avoid the slurs. I want them to appear just where
they would if the Slurs weren't there at all.
What am I missing?
Thanks
Paul McKay

Showing fingering on top of slurs

[Paul McKay]

Hi
I want to show the fingering in front of the slurs. This should keep the
fingerings evenly spaced vertically over the notes.  I have tried the
following :

\version "2.24.0"
\language "english"

\relative {
\override Staff.Fingering.layer = 2 % fingering should overwrite
slurs
r4 r8 -1-3( 16-2-4 -1-5-2-4-3-5) }

Fingerings still avoid the slurs.
What am I missing?
Thanks
Paul McKay

Re: slurs problem with voices

[Knute Snortum]

On Wed, May 1, 2024 at 10:55 PM Robert Garrigos  wrote:

> Oh this is a bit embarrassing, such a basic error….. sorry, I never
> realized that the parenthesis needs to be right after the first note.
>

Nothing to be embarrassed about.  It takes some getting used to.


--
Knute Snortum

Re: slurs problem with voices

[Robert Garrigos]

Oh this is a bit embarrassing, such a basic error….. sorry, I never realized 
that the parenthesis needs to be right after the first note.

Thanks all.

Robert

> El 2 maig 2024, a les 2:49, Mark Stephen Mrotek  va 
> escriure:
> 
> Timothy,
>  
> Perhaps this?
>  
> Mark
>  
> \version "2.24.3"
>  
> \relative c' {
> \time 3/4
>  
> <<{b'4 c2~ | 8 [q]} \\
>   {d4 d2 (| \stemUp e4)}>> r8  r  |
>  
> }
>  
> From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org 
>  On Behalf Of Timothy 
> Lanfear
> Sent: Wednesday, May 1, 2024 2:15 PM
> To: Robert Garrigos ; LilyPond Users 
> 
> Subject: Re: slurs problem with voices
>  
> On 01/05/2024 21:57, Robert Garrigos wrote: 
>>  
>> Why is not the first example working? I tried with explicit voicing with the 
>> same results.
>>  
>> Thanks.
>>  
>> Robert
> The slur starts at the d2 so must be placed with that note following the 
> pitch and duration, 
> { d4 d2( | \hideNotes ef8)} 
> -- 
> Timothy Lanfear, Bristol, UK.

RE: slurs problem with voices

[Mark Stephen Mrotek]

Timothy,

 

Perhaps this?

 

Mark

 

\version "2.24.3"

 

\relative c' {

\time 3/4

 

<<{b'4 c2~ | 8 [q]} \\

  {d4 d2 (| \stemUp e4)}>> r8  r  |

 

}

 

From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org 
 On Behalf Of Timothy 
Lanfear
Sent: Wednesday, May 1, 2024 2:15 PM
To: Robert Garrigos ; LilyPond Users 

Subject: Re: slurs problem with voices

 

On 01/05/2024 21:57, Robert Garrigos wrote: 

 
Why is not the first example working? I tried with explicit voicing with the 
same results.
 
Thanks.
 
Robert

The slur starts at the d2 so must be placed with that note following the pitch 
and duration, 

{ d4 d2( | \hideNotes ef8)} 

-- 
Timothy Lanfear, Bristol, UK.

Re: slurs problem with voices

[Knute Snortum]

On Wed, May 1, 2024 at 1:59 PM Robert Garrigos  wrote:

> I have this music to engrave, note the slur:
> [...]
> Why is not the first example working? I tried with explicit voicing with
> the same results.
>

Slurs in LilyPond are "post events", meaning they always go *after* the
note.   So if you want to slur from note a to note b, you write:

a( b)

The above slur will start on the note a and end on the note b.


--
Knute Snortum

Re: slurs problem with voices

[Timothy Lanfear]

On 01/05/2024 21:57, Robert Garrigos wrote:

Why is not the first example working? I tried with explicit voicing with the 
same results.

Thanks.

Robert


The slur starts at the d2 so must be placed with that note following the 
pitch and duration,


{ d4 d2( | \hideNotes ef8)}

--
Timothy Lanfear, Bristol, UK.

Re: slurs problem with voices

[Kieren MacMillan]

Hi Robert,

> I tried different approaches but cannot get that slur.

\version "2.25.14"
\language "english"

global = {
  \key ef \minor
  \time 3/4
}

\relative c' {
  \clef treble
  \global
  <<
{ bf'4 cf2 \tweak staff-position #5.1 ~ | 8 8 r8  r8  }
\\
{ d4 d2( | \hideNotes ef8) }
\\
{ s4 \tweak horizontal-shift #1 f gf8 af | s2. }
  >>
}

Note that I also turned your \once \override commands into \tweak commands 
(which feel more natural to me).

> Why is not the first example working?

You placed the slur start parenthesis in the wrong location.  :)

Hope that helps!
Kieren.
__

My work day may look different than your work day. Please do not feel obligated 
to read or respond to this email outside of your normal working hours.

slurs problem with voices

[Robert Garrigos]

I have this music to engrave, note the slur:



I tried different approaches but cannot get that slur. This is my code, with 
two examples:

\version "2.25.14"
\language "english"

global = {
  \key ef \minor
  \time 3/4
}

first_example = \relative c' {
\clef treble
  \global
  <<
{bf'4 \once \override Tie.staff-position = 5.1 cf2~ | 8 8 r8  r8 }
\\
{ d4 d2 |  \hideNotes (ef8)} % this slur doesn’t get printed
\\
{s4 \once \override NoteColumn.horizontal-shift = #1 f  gf8 af  | s2.}
  >>
}

second_example = \relative c' {
\clef treble
  \global
  <<
{bf'4 \once \override Tie.staff-position = 5.1 cf2~ | 8 8 r8  r8 }
\\
{ d4 (d2 |  \hideNotes ef8)} % this slur does get printed
\\
{s4 \once \override NoteColumn.horizontal-shift = #1 f  gf8 af  | s2.}
  >>
}

\score {
  \new Staff \first_example
}

\score {
  \new Staff \second_example
}


first example prints no slur:



second example prints a slur where it is supposed to be, according the code, 
although it is not what I want:



Why is not the first example working? I tried with explicit voicing with the 
same results.

Thanks.

Robert

Re: Schenkerian slurs and framework

[Kieren MacMillan]

Hi Ben,

> I read the 2005 article in the Linux journal about making schenkerian graphs, 
> and I feel like it covered everything except one type of slur. I think I've 
> heard it called a swan slur before. It's a slur that hooks around a note. In 
> this picture it's the slur connecting the e flat in the bass to the second b 
> flat. 
> https://i0.wp.com/johnhalle.com/wp-content/uploads/2020/08/image-3.png?ssl=1
> I feel like I need one more point to modify in the bezier curve to get it to 
> hook around like that. Is that possible?

I feel like I was able to accomplish it without that… let me see if I can find 
the code I used.

> Also, while searching for an answer to this I saw reference to a LilySchenker 
> framework but I can't find any more info about it, probably because there's 
> some famous person named Lily Schenker... Anyone have more info on that?

I was the one building that… let me see if I can find the code I used.  :)

Best,
Kieren
__

My work day may look different than your work day. Please do not feel obligated 
to read or respond to this email outside of your normal working hours.

Schenkerian slurs and framework

[Ben Bradshaw]

Hello,
I read the 2005 article in the Linux journal about making schenkerian
graphs, and I feel like it covered everything except one type of slur. I
think I've heard it called a swan slur before. It's a slur that hooks
around a note. In this picture it's the slur connecting the e flat in the
bass to the second b flat.
https://i0.wp.com/johnhalle.com/wp-content/uploads/2020/08/image-3.png?ssl=1
I feel like I need one more point to modify in the bezier curve to get it
to hook around like that. Is that possible?

Also, while searching for an answer to this I saw reference to a
LilySchenker framework but I can't find any more info about it, probably
because there's some famous person named Lily Schenker... Anyone have more
info on that?

Thanks,
Ben

Re: Multiple connected slurs

[Gerardo Ballabio]

Il giorno dom 3 mar 2024 alle ore 18:36 Jean Brefort
 ha scritto:
>
> Try this:
>   c''1:32( | c1:32 )( |  c1:32 )( | c4 ) r4 r2 |
>
> you only need three slurs not four.

Works great, thanks.

Il giorno dom 3 mar 2024 alle ore 18:32 David Kastrup  ha scritto:
> You should not ignore syntax warnings LilyPond gives you: they indicate
> a problem with your source file.

That's exactly why I asked.

Gerardo

Re: Multiple connected slurs

[Jean Brefort]

Try this:
  c''1:32( | c1:32 )( |  c1:32 )( | c4 ) r4 r2 |

you only need three slurs not four.

Hope this helps,
Jean Brefort (not the

Le dimanche 03 mars 2024 à 18:20 +0100, Gerardo Ballabio a écrit :
> Hello,
> please what is the correct way to draw multiple slurs connected to
> each other? Look at example below to see what I mean (result
> attached).
> 
> The following code does what I want but it gives multiple warnings
> like these:
> 
> Parsing...
> slur.ly:4:3: warning: Unattached SlurEvent
> Interpreting music...
> slur.ly:4:13: warning: cannot end slur
> 
> I tried using ties instead of slurs, that doesn't give warnings, but
> it doesn't look quite the same.
> 
> Thanks
> Gerardo
> 
> % slur.ly
> %%
> \version "2.24.1"
> 
> \new Staff \relative {
>   ( c''1:32 ) | ( c1:32 ) | ( c1:32 ) | ( c4 ) r4 r2 |
> }
> %%
> 
> % tie.ly
> %%
> \version "2.24.1"
> 
> \new Staff \relative {
>   c''1:32~ | c1:32~ | c1:32~ | c4 r4 r2 |
> }
> %%

Re: Multiple connected slurs

[David Kastrup]

Gerardo Ballabio  writes:

> Hello,
> please what is the correct way to draw multiple slurs connected to
> each other? Look at example below to see what I mean (result
> attached).
>
> The following code does what I want but it gives multiple warnings like these:
>
> Parsing...
> slur.ly:4:3: warning: Unattached SlurEvent
> Interpreting music...
> slur.ly:4:13: warning: cannot end slur
>
> I tried using ties instead of slurs, that doesn't give warnings, but
> it doesn't look quite the same.
>
> Thanks
> Gerardo
>
> % slur.ly
> %%
> \version "2.24.1"
>
> \new Staff \relative {
>   ( c''1:32 ) | ( c1:32 ) | ( c1:32 ) | ( c4 ) r4 r2 |
> }
> %%

You need to use the correct syntax for slurs in the first place.  Both (
and ) come right after the note they connect to, and the reason for that
is exactly because it makes it easy to make properly connected adjacent
slurs.

You should not ignore syntax warnings LilyPond gives you: they indicate
a problem with your source file.

-- 
David Kastrup

Multiple connected slurs

[Gerardo Ballabio]

Hello,
please what is the correct way to draw multiple slurs connected to
each other? Look at example below to see what I mean (result
attached).

The following code does what I want but it gives multiple warnings like these:

Parsing...
slur.ly:4:3: warning: Unattached SlurEvent
Interpreting music...
slur.ly:4:13: warning: cannot end slur

I tried using ties instead of slurs, that doesn't give warnings, but
it doesn't look quite the same.

Thanks
Gerardo

% slur.ly
%%
\version "2.24.1"

\new Staff \relative {
  ( c''1:32 ) | ( c1:32 ) | ( c1:32 ) | ( c4 ) r4 r2 |
}
%%

% tie.ly
%%
\version "2.24.1"

\new Staff \relative {
  c''1:32~ | c1:32~ | c1:32~ | c4 r4 r2 |
}
%%


slur.pdf
Description: Adobe PDF document


tie.pdf
Description: Adobe PDF document

Re: Slurs within chords, and dotted notes

[Joel C. Salomon]

On 1/7/2024 4:11 PM, Xavier Scheuer wrote:

\once \override Dots.avoid-slur = #'ignore
(Dots instead of Slur)


Thank you!  That’s what I was misunderstanding.

—Joel

Re: Slurs within chords, and dotted notes

[Xavier Scheuer]

On Sun, 7 Jan 2024 at 21:35, Joel C. Salomon  wrote:
>
> Reposting for clarity as to what I’m asking.
>
> In the second case below, instead of the slur attaching to the specific
note, it moves vertically—I assume, to avoid collision with the duration
dot.  (Though it’s interesting that a tie does not mind overlapping the
dot, as in the fourth case.)
>
> In the second case, how can I either—
>
> Allow the slur to overlap the dot (the code shown below does not work), or
> Move the left anchor of the slur horizontally past the dot, so they don’t
conflict?
>
> Obvious searches like [lilypond chord slur dotted note] do not turn up
mention of this, or of any tweak to avoid this.  Any hints?

Hello,

\once \override Dots.avoid-slur = #'ignore
(Dots instead of Slur)

Kind regards,
Xavier

Re: Slurs within chords, and dotted notes

[Jakob Pedersen]

Hello Joel

You can shape the Slur manually, like so:

\version "2.25.11"

\fixed c' {
  % undotted note: slur attaches correctly
  2
   |

  % dotted note: slur is moved vertically
  \shape #'((1 . 0.5) (0.5 . 0.3) (0.5 . 0.3) (0 . 0)) Slur %adjusting 
the numbers control the four control points of the Bézier curves

  2.
  4 |

  % undotted note tie for comparison
  2 q |

  % dotted note tie for comparison: slur overlaps dot
  2. q4 |
}

Best wishes,
Jakob

On 07.01.2024 20.16, Joel C. Salomon wrote:


Reposting for clarity as to what I’m asking.

In the second case below, instead of the slur attaching to the 
specific note, it moves vertically—I assume, to avoid collision with 
the duration dot.  (Though it’s interesting that a tie does not mind 
overlapping the dot, as in the fourth case.)


In the second case, how can I either—

  * Allow the slur to overlap the dot (the code shown below does not
work), or
  * Move the left anchor of the slur horizontally past the dot, so
they don’t conflict?

Obvious searches like [lilypond chord slur dotted note] 
 do 
not turn up mention of this, or of any tweak to avoid this. Any hints?


—Joel C. Salomon

|```
\version "2.25.11"

\fixed c' {
  % undotted note: slur attaches correctly
  2
   |

  % dotted note: slur is moved vertically
  \once \override Slur.avoid-slur = #'ignore    % does nothing
  2.
  4 |

  % undotted note tie for comparison
  2 q |

  % dotted note tie for comparison: slur overlaps dot
  2. q4 |
}
```| 

Re: Slurs within chords, and dotted notes

[Joel C. Salomon]

Reposting for clarity as to what I’m asking.

In the second case below, instead of the slur attaching to the specific 
note, it moves vertically—I assume, to avoid collision with the duration 
dot.  (Though it’s interesting that a tie does not mind overlapping the 
dot, as in the fourth case.)


In the second case, how can I either—

 * Allow the slur to overlap the dot (the code shown below does not
   work), or
 * Move the left anchor of the slur horizontally past the dot, so they
   don’t conflict?

Obvious searches like [lilypond chord slur dotted note] 
 do not 
turn up mention of this, or of any tweak to avoid this.  Any hints?


—Joel C. Salomon

|```
\version "2.25.11"

\fixed c' {
  % undotted note: slur attaches correctly
  2
   |

  % dotted note: slur is moved vertically
  \once \override Slur.avoid-slur = #'ignore    % does nothing
  2.
  4 |

  % undotted note tie for comparison
  2 q |

  % dotted note tie for comparison: slur overlaps dot
  2. q4 |
}
```|

Re: Slurs within chords, and dotted notes

[Joel C. Salomon]

I should have been clearer.  The score I’m trying to emulate has slurs—

|4.  |

—and it’s the vertical movement of the slurs I’m trying to avoid.

The fact that ties will overlap the note dots was a curiosity I found in 
trying to boil that down to a minimal working example.


—Joel

On 1/4/2024 9:28 PM, Mark Stephen Mrotek wrote:


Joel:

Is this better?

\fixed c' {

2

 |

2.

4 |

2 q |

2. q4 |

}

Mark

*From:* lilypond-user-bounces+carsonmark=ca.rr@gnu.org 
 *On Behalf Of 
*Joel C. Salomon

*Sent:* Thursday, January 4, 2024 6:11 PM
*To:* LilyPond Users 
*Subject:* Slurs within chords, and dotted notes

Somewhat surprising result, tested on 2.24 & 2.25.11:

|```|
|\version "2.24"|

|\fixed c' {|
|  2|
|   ||

|  2.|
|  4 ||

|  2 q ||

|  2. q4 ||
|}|
|```|

In the second instance, the tie attaches to the bottom of the initial 
chord, presumably to avoid colliding with the dot.  (Interestingly, 
as in examples 3 & 4, a tie will happily display overlapping the dot.)


Obvious searches (like [lilypond chord slur dotted note] 
<https://www.google.com/search?q=lilypond+chord+slur+dotted+note>) do 
not turn up mention of this, or of any tweak to avoid this.  Any hints?


—Joel C. Salomon

RE: Slurs within chords, and dotted notes

[Mark Stephen Mrotek]

Joel:

 

Is this better?

 

\fixed c' {

  2

   |

 

  2.

  4 |

 

  2 q |

 

  2. q4 |

}

 

Mark

 

From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org 
 On Behalf Of Joel C. 
Salomon
Sent: Thursday, January 4, 2024 6:11 PM
To: LilyPond Users 
Subject: Slurs within chords, and dotted notes

 

Somewhat surprising result, tested on 2.24 & 2.25.11:

```
\version "2.24"

\fixed c' {
  2
   |

  2.
  4 |

  2 q |

  2. q4 |
}
``` 

In the second instance, the tie attaches to the bottom of the initial chord, 
presumably to avoid colliding with the dot.  (Interestingly, as in examples 3 & 
4, a tie will happily display overlapping the dot.)

Obvious searches (like [lilypond chord slur dotted note] 
<https://www.google.com/search?q=lilypond+chord+slur+dotted+note> ) do not turn 
up mention of this, or of any tweak to avoid this.  Any hints?

—Joel C. Salomon

Slurs within chords, and dotted notes

[Joel C. Salomon]

Somewhat surprising result, tested on 2.24 & 2.25.11:

|```
\version "2.24"

\fixed c' {
  2
   |

  2.
  4 |

  2 q |

  2. q4 |
}
```|

In the second instance, the tie attaches to the bottom of the initial 
chord, presumably to avoid colliding with the dot. (Interestingly, as in 
examples 3 & 4, a tie will happily display overlapping the dot.)


Obvious searches (like [lilypond chord slur dotted note] 
) do 
not turn up mention of this, or of any tweak to avoid this.  Any hints?


—Joel C. Salomon

Re: Slurs running into each other

[kieren]

Hi Peter,


What can I do to avoid the outer slur colliding with the inner slurs?


Code the inner slurs as Slurs and the *outer* slur as a PhrasingSlur, 
rather than the other way around (as you did):


  f4\p\( aes8( des16. c32) |
  c8.( bes32 aes) g8\) r8 |


As a secondary question, I always find that when I use a \tempo 
indication, it always seems much too close to the staff. What is the 
most elegant way of adding some vertical space below the tempo marking? 
Most of my published music has a bigger gap, even if not much. Is there 
a way to set this as a default for ALL scores?


I’ve \tweak-ed the padding here, but you can set it in a \layout block 
and \include that file in all scores if you want(ed):


TheBusiness = \relative b' {
  \key f \minor
  \time 2/4
  \tweak padding 2 \tempo "Andante Sostenuto"
  r2 |
  f4\p\( aes8( des16. c32) |
  c8.( bes32 aes) g8\) r8 |
}

\score {
  \new Staff {
\TheBusiness
  }
  \layout {}
}

Hope that helps!
Kieren.

Slurs running into each other

[Peter Mayes]

As a beginner at Lilypond, this is the first time I have seen something 
that looks a little ugly "out of the box" (unless, of course, I am doing 
something wrong!)


What can I do to avoid the outer slur colliding with the inner slurs?

As a secondary question, I always find that when I use a \tempo 
indication, it always seems much too close to the staff. What is the 
most elegant way of adding some vertical space below the tempo marking? 
Most of my published music has a bigger gap, even if not much. Is there 
a way to set this as a default for ALL scores?


Thanks in advance.

\version "2.24.3"

TheBusiness = \relative b' {
  \key f \minor
  \time 2/4
  \tempo "Andante Sostenuto"
  r2 |
  f4\p( aes8\( des16. c32\) |
  c8.\( bes32 aes\) g8) r8 |
}

\score {
  \new Staff {
    \TheBusiness
  }
  \layout {}
}

--
Best wishes -- Peter
--
Peter Mayes

RE: slurs

[Mark Stephen Mrotek]

David,

Wow, so simple. 
Thank you for the remedy.

Mark

-Original Message-
From: David Kastrup  
Sent: Saturday, September 16, 2023 2:44 PM
To: Mark Stephen Mrotek 
Cc: lilypond-user@gnu.org
Subject: Re: slurs

"Mark Stephen Mrotek"  writes:

> Hello All:
>
>  
>
> \version "2.22.2"
>
> \relative c'' {
>
>   \slurDown 4
>
> (bes16) (a c bes d c ees d)
>
> }

Good example why it is a bad idea to use non-standard input formatting for
aesthetic reasons: you lose a proper idea about what you are actually doing.
Both ( and ) are post-events following a note and can have a direction
prescribed using _ and ^ (ok, it is only heeded for the opening brace).

So you can just write:

\version "2.22.2"

\relative c'' {
   4_(
   bes16)( a c bes d c ees d)

}


--
David Kastrup

Re: slurs

[David Kastrup]

"Mark Stephen Mrotek"  writes:

> Hello All:
>
>  
>
> \version "2.22.2"
>
> \relative c'' {
>
>   \slurDown 4
>
> (bes16) (a c bes d c ees d)
>
> }

Good example why it is a bad idea to use non-standard input formatting
for aesthetic reasons: you lose a proper idea about what you are
actually doing.  Both ( and ) are post-events following a note and can
have a direction prescribed using _ and ^ (ok, it is only heeded for the
opening brace).

So you can just write:

\version "2.22.2"

\relative c'' {
   4_(
   bes16)( a c bes d c ees d)

}


-- 
David Kastrup

slurs

[Mark Stephen Mrotek]

Hello All:

 

\version "2.22.2"

\relative c'' {

  \slurDown 4

(bes16) (a c bes d c ees d)

}

 

Produces this



 

What must be done to produce this?

 



 

Thank you for your assistance.

 

Mark

Re: s-curve slurs across staves?

[Jean Abou Samra]

Le jeudi 17 août 2023 à 12:38 -0400, Jin Choi a écrit :
> and also discussion of being able to do it in Frescobaldi under Layout Control
> Mode, which appears to have moved to Tools/Viewers/Layout Control Options but
> now has no option for displaying control points.

The reason it was removed is that the feature has been added to LilyPond itself.
Use \vshape instead of \shape to see the control points, then remove the "v".


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

Re: s-curve slurs across staves?

[Jin Choi]

It was “Adjusting slurs and ties in LilyPond”, from this group’s archives:
https://lists.gnu.org/archive/html/lilypond-user/2019-10/pdfn4OnsjHZAm.pdf

Some of the features look very handy to describe control points as polar 
coordinates, but I don’t want to drop in a whole mass of code just for that.

I did find a snippet (also from this group’s archives) for displaying the 
actual control points, which helped immensely with tweaking Lukas’s example, 
and also discussion of being able to do it in Frescobaldi under Layout Control 
Mode, which appears to have moved to Tools/Viewers/Layout Control Options but 
now has no option for displaying control points.


> On Aug 16, 2023, at 12:56 PM, William Rehwinkel 
>  wrote:
> 
> What PDF did you find this in?
> 
> -William
> 
> On 8/16/23 12:50, Jin Choi wrote:
>> I came across a PDF describing updates to \shape that let you use head 
>> centered coordinates and polar coordinates that would make this easier. But 
>> my 2.24.0 version of lilypond doesn’t seem to include \shapeII. What is the 
>> status of that?
>> 
>>> On Aug 16, 2023, at 5:33 AM, Lukas-Fabian Moser  
>>> <mailto:l...@gmx.de> wrote:
>>> 
>>> Hi Jin,
>>> 
>>> Am 16.08.23 um 04:48 schrieb Jin Choi:
>>>> Is it possible to get this style of s-curve shaped slurs across staves?
>>> It's possible, but it's not fun.
>>> 
>>> \version "2.24.0"
>>> 
>>> \new PianoStaff
>>> <<
>>>   \new Staff = upper {
>>> <<
>>>   {
>>>   r8
>>>   \shape #'((0 . 0) (4 . -2) (0 . 6) (1 . 3)) Slur
>>>   8_(   \change Staff = lower 4)
>>>   }
>>>   \new Voice { s2 r }
>>> >>
>>>   }
>>>   \new Staff = lower \with { \clef bass } {
>>> cis,4 r s r
>>> 
>>>   }
>>> Slurs live in a single voice (that's something I'm working on, but I don't 
>>> have much time for LilyPond work at the moment), so we have to create one 
>>> voice that switches to the other staff on the way. Then we have to adjust 
>>> the control points manually, a task which is made harder by the need to 
>>> manually move the right tip of the slur from "under the note" to "above the 
>>> note".
>>> 
>>> There's definitely room for improvement, both in my example and in LilyPond 
>>> proper.
>>> 
>>> Lukas
>>> 
>> 
> 
> -- 
> + --- +
> |   William Rehwinkel - Oberlin College and   |
> |  Conservatory '24   |
> |will...@williamrehwinkel.net <mailto:will...@williamrehwinkel.net>   
>   |
> | PGP key:|
> | https://ftp.williamrehwinkel.net/pubkey.txt |
> + --- +

Re: s-curve slurs across staves?

[Jean Abou Samra]

> Le 16 août 2023 à 18:52, Jin Choi  a écrit :
> 
> I came across a PDF describing updates to \shape that let you use head 
> centered coordinates and polar coordinates that would make this easier. But 
> my 2.24.0 version of lilypond doesn’t seem to include \shapeII. What is the 
> status of that?
> 


It has never been part of LilyPond proper. You can find it the code here: 
https://github.com/openlilylib/bezier/blob/master/shapeII/module.ily (I haven't 
tested it on newer versions.)

Re: s-curve slurs across staves?

[William Rehwinkel via LilyPond user discussion]

What PDF did you find this in?

-William

On 8/16/23 12:50, Jin Choi wrote:

I came across a PDF describing updates to \shape that let you use head centered 
coordinates and polar coordinates that would make this easier. But my 2.24.0 
version of lilypond doesn’t seem to include \shapeII. What is the status of 
that?


On Aug 16, 2023, at 5:33 AM, Lukas-Fabian Moser  wrote:

Hi Jin,

Am 16.08.23 um 04:48 schrieb Jin Choi:

Is it possible to get this style of s-curve shaped slurs across staves?

It's possible, but it's not fun.

\version "2.24.0"

\new PianoStaff
<<
   \new Staff = upper {
 <<
   {
   r8
   \shape #'((0 . 0) (4 . -2) (0 . 6) (1 . 3)) Slur
   8_(   \change Staff = lower 4)
   }
   \new Voice { s2 r }
 >>
   }
   \new Staff = lower \with { \clef bass } {
 cis,4 r s r

   }
Slurs live in a single voice (that's something I'm working on, but I don't have much time for 
LilyPond work at the moment), so we have to create one voice that switches to the other staff on 
the way. Then we have to adjust the control points manually, a task which is made harder by the 
need to manually move the right tip of the slur from "under the note" to "above the 
note".

There's definitely room for improvement, both in my example and in LilyPond 
proper.

Lukas





--
+ --- +
|   William Rehwinkel - Oberlin College and   |
|  Conservatory '24   |
|will...@williamrehwinkel.net  |
| PGP key:|
|https://ftp.williamrehwinkel.net/pubkey.txt  |
+ --- +



OpenPGP_signature
Description: OpenPGP digital signature

Re: s-curve slurs across staves?

[Jin Choi]

I came across a PDF describing updates to \shape that let you use head centered 
coordinates and polar coordinates that would make this easier. But my 2.24.0 
version of lilypond doesn’t seem to include \shapeII. What is the status of 
that?

> On Aug 16, 2023, at 5:33 AM, Lukas-Fabian Moser  wrote:
> 
> Hi Jin,
> 
> Am 16.08.23 um 04:48 schrieb Jin Choi:
>> Is it possible to get this style of s-curve shaped slurs across staves?
> 
> It's possible, but it's not fun.
> 
> \version "2.24.0"
> 
> \new PianoStaff
> <<
>   \new Staff = upper {
> <<
>   {
>   r8
>   \shape #'((0 . 0) (4 . -2) (0 . 6) (1 . 3)) Slur
>   8_(   \change Staff = lower 4)
>   }
>   \new Voice { s2 r }
> >>
>   }
>   \new Staff = lower \with { \clef bass } {
> cis,4 r s r
> 
>   }
> >>
> 
> Slurs live in a single voice (that's something I'm working on, but I don't 
> have much time for LilyPond work at the moment), so we have to create one 
> voice that switches to the other staff on the way. Then we have to adjust the 
> control points manually, a task which is made harder by the need to manually 
> move the right tip of the slur from "under the note" to "above the note".
> 
> There's definitely room for improvement, both in my example and in LilyPond 
> proper.
> 
> Lukas
> 

Re: s-curve slurs across staves?

[Lukas-Fabian Moser]

Hi Jin,

Am 16.08.23 um 04:48 schrieb Jin Choi:

Is it possible to get this style of s-curve shaped slurs across staves?


It's possible, but it's not fun.

\version "2.24.0"

\new PianoStaff
<<
  \new Staff = upper {
    <<
  {
  r8
  \shape #'((0 . 0) (4 . -2) (0 . 6) (1 . 3)) Slur
  8_(   \change Staff = lower 4)
  }
  \new Voice { s2 r }
    >>
  }
  \new Staff = lower \with { \clef bass } {
    cis,4 r s r

  }
>>

Slurs live in a single voice (that's something I'm working on, but I 
don't have much time for LilyPond work at the moment), so we have to 
create one voice that switches to the other staff on the way. Then we 
have to adjust the control points manually, a task which is made harder 
by the need to manually move the right tip of the slur from "under the 
note" to "above the note".


There's definitely room for improvement, both in my example and in 
LilyPond proper.


Lukas

Re: crescendo and decrescendo within slurs

[Knute Snortum]

On Sat, Aug 12, 2023 at 11:43 AM Jin Choi  wrote:

> I see that it’s possible to place textual marks inside of slurs:
> https://lilypond.org/doc/v2.25/Documentation/snippets/expressive-marks_003a-positioning-text-markups-inside-slurs
> Is it possible to get crescendo and decrescendo marks within slurs as well?
>

If you want a more global solution, try:

\relative c'' {
  \override Slur.outside-staff-priority = 500
  c2(^\< d4.)\! c8
}


--
Knute Snortum

Re: crescendo and decrescendo within slurs

[Valentin Petzel]

Hi,

you could set the outside-staff-priority of the Slur:

\version "2.24.1"

top = { \change Staff = "upper" \voiceTwo }
bottom = { \change Staff = "lower" \voiceOne }

upper = \relative c' {
  \key g \minor
  \voiceOne
d'4.^\markup {\italic "espressivo"}^"a tempo"\p^- c8\tweak outside-staff-
priority #500 ( d^\< f\! g^\> c,\!) |
}

lower = \relative c' {
  \clef bass
  \key g \minor
  f,16 bes \top d f 
  \bottom bes, d \top f bes 
  \bottom bes, d \top g bes
  \bottom a, c \top g' a |
}

\layout {
  \context {
\PianoStaff
\override StaffGrouper.staff-staff-spacing.basic-distance = #12
  }
}
\score {
  \new PianoStaff {
<<
\new Staff = "upper" \upper
\new Staff = "lower" \lower
>>
  }
}

Cheers,
Valentin

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

crescendo and decrescendo within slurs

[Jin Choi]

I see that it’s possible to place textual marks inside of slurs: 
https://lilypond.org/doc/v2.25/Documentation/snippets/expressive-marks_003a-positioning-text-markups-inside-slurs
Is it possible to get crescendo and decrescendo marks within slurs as well?

\version "2.24.1"

top = { \change Staff = "upper" \voiceTwo }
bottom = { \change Staff = "lower" \voiceOne }

upper = \relative c' {
  \key g \minor
  \voiceOne
d'4.^\markup {\italic "espressivo"}^"a tempo"\p^- c8( d^\< f\! g^\> c,\!) |
}

lower = \relative c' {
  \clef bass
  \key g \minor
  f,16 bes \top d f 
  \bottom bes, d \top f bes 
  \bottom bes, d \top g bes
  \bottom a, c \top g' a |
}

\layout {
  \context {
\PianoStaff
\override StaffGrouper.staff-staff-spacing.basic-distance = #12
  }
}
\score {
  \new PianoStaff {
<<
\new Staff = "upper" \upper
\new Staff = "lower" \lower
>>
  }
}

Re: broken slurs shorter than ties

[Werner LEMBERG]

>> Suprisingly, no – at least I couldn't find an entry.  I've now created
>> 
>> https://gitlab.com/lilypond/lilypond/-/issues/6631
> 
> And there is now https://gitlab.com/lilypond/lilypond/-/merge_requests/2043
> 
> See, if you report problems, there is a chance they actually get
> fixed :-)

Will bear that in my mind :-)

And contrary to me, you've found my previous report on that phenomenon
(#6071), thanks.


   Werner

Re: broken slurs shorter than ties

[Jean Abou Samra]

Le vendredi 16 juin 2023 à 20:21 +, Werner LEMBERG a écrit :
> Suprisingly, no – at least I couldn't find an entry.  I've now created
> 
> https://gitlab.com/lilypond/lilypond/-/issues/6631


And there is now https://gitlab.com/lilypond/lilypond/-/merge_requests/2043

See, if you report problems, there is a chance they actually get fixed :-)



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

Re: broken slurs shorter than ties

[Werner LEMBERG]

> Cough, cough. I have found this to work:
> 
> ```
> \version "2.25.5"
> 
> #(set-default-paper-size "a6")
> 
> {
>   d'4 e' g' d' |
>   d'4 e' g' d'( ~ |
>   \once \override Staff.KeySignature.break-visibility = #all-invisible
>   \break
>   d'4) e' f' d' |
>   d'4 e' f' d' |
> }
> ```

Very interesting!

> Looks like some invisible grobs are interfering.
> 
> Do we already have an issue for this problem?

Suprisingly, no – at least I couldn't find an entry.  I've now created

https://gitlab.com/lilypond/lilypond/-/issues/6631


Werner

Re: broken slurs shorter than ties

[Jean Abou Samra]

Le vendredi 16 juin 2023 à 05:37 +, Werner LEMBERG a écrit :

> In my opinion, the worst flaw of LilyPond's otherwise excellent
> formatting, a flaw that essentially everyone encounters rather
> quickly, is that broken slurs are almost always shorter than broken
> ties (it should be exactly the opposite), which is butt ugly and
> sometimes really hampers readability.
> 
> ```
> #(set-default-paper-size "a6")
> 
> {
>   d'4 e' g' d' |
>   d'4 e' g' d'( ~ | \break
>   d'4) e' f' d' |
>   d'4 e' f' d' |
> }
> ```
> 
> I know that the handling of slurs and ties is the big elephant in the
> room that nobody wants to touch because of its tremendous complexity;


I wouldn't really say that. I for one am not afraid of touching it, though it's 
not my current focus. Dan also made changes there a few months ago.


> I'm thus looking for a manual, easy workaround to lengthen broken
> slurs instead.  While using `\shape` is certainly possible, it is not
> a quick solution IMHO because of its many parameters.
> 
> Any ideas?  The LSR doesn't have something into this direction, alas.


Cough, cough. I have found this to work:

```
\version "2.25.5"

#(set-default-paper-size "a6")

{
  d'4 e' g' d' |
  d'4 e' g' d'( ~ |
  \once \override Staff.KeySignature.break-visibility = #all-invisible
  \break
  d'4) e' f' d' |
  d'4 e' f' d' |
}
```

Looks like some invisible grobs are interfering.

Do we already have an issue for this problem?


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

broken slurs shorter than ties

[Werner LEMBERG]

In my opinion, the worst flaw of LilyPond's otherwise excellent
formatting, a flaw that essentially everyone encounters rather
quickly, is that broken slurs are almost always shorter than broken
ties (it should be exactly the opposite), which is butt ugly and
sometimes really hampers readability.

```
#(set-default-paper-size "a6")

{
  d'4 e' g' d' |
  d'4 e' g' d'( ~ | \break
  d'4) e' f' d' |
  d'4 e' f' d' |
}
```

I know that the handling of slurs and ties is the big elephant in the
room that nobody wants to touch because of its tremendous complexity;
I'm thus looking for a manual, easy workaround to lengthen broken
slurs instead.  While using `\shape` is certainly possible, it is not
a quick solution IMHO because of its many parameters.

Any ideas?  The LSR doesn't have something into this direction, alas.

In a similar vein, the second-most serious issue (or probably even the
most serious, actually) is that broken ties are sometimes so short
that they become invisible.  Again, it would be great to have a
command to quickly lengthen the the broken parts before and/or after
the break of a tie by a given amount.  Note that setting the
`minimum-length` is not a good solution since it needs a lot of trial
to find a good value for a particular situation.

What I envision is a command similar to `\offset` that directly
influences the optical result, i.e., if I pass value 1, say, the slur
(or tie) becomes longer by 1 unit.


Werner

Re: Slurs inside or outside beamed notes

[GMX]

Yes, Gould does say to always place a slur outside a beam.  And I’m fine with 
that being Lilypond’s default behavior.  But I’d love the ability to tell 
Lilypond to place slurs inside of beams (when possible).

I do have one hymnal that prints slurs inside beams.  I suspect that this 
choice was related to the decision to also beam notes into beats, which I also 
prefer, but isn’t done by any of the other hymnals I have.  So one hymnal puts 
slurs inside beams, but the others only beam slurred notes (and don’t print the 
slur at all).

David

> On Feb 13, 2023, at 2:16 PM, Brian Barker  wrote:
> 
> At 11:47 13/02/2023 -0800, Aaron Hill wrote:
>> I am quite used to LilyPond's default handling of slurs with them positioned 
>> next to the beam, but should I be following the source engraving with the 
>> slurs sit inside so they are closer to the note heads? Does Gould offer 
>> advice on this?
> 
> To your latter question, yes: she says "[The slur] should always remain 
> outside a beam" (Behind Bars, p. 111).
> 
> Brian Barker 
> 
> 

Re: Slurs inside or outside beamed notes

[Brian Barker]

At 11:47 13/02/2023 -0800, Aaron Hill wrote:
I am quite used to LilyPond's default handling of slurs with them 
positioned next to the beam, but should I be following the source 
engraving with the slurs sit inside so they are closer to the note 
heads? Does Gould offer advice on this?


To your latter question, yes: she says "[The slur] should always 
remain outside a beam" (Behind Bars, p. 111).


Brian Barker 

Slurs inside or outside beamed notes

[Aaron Hill]

Attached is an image showing an excerpt from a reference score as well 
as output from LilyPond.


I am quite used to LilyPond's default handling of slurs with them 
positioned next to the beam, but should I be following the source 
engraving with the slurs sit inside so they are closer to the note 
heads?  Does Gould offer advice on this?



-- Aaron Hill

Re: Slurs not being followed in one vocal part

[Lukas-Fabian Moser]

Hi Jon,

Am 22.01.23 um 03:31 schrieb Jon Arnold:
Thanks all! Separating the voices did fix the problem. I used this 
score a long time ago and then updated the layout, so I feel like an 
update several years ago must have changed the behavior, which is 
interesting.


Compare:

\version "2.24"

mel = \relative {
  g''4.( f8 f e) d( c)
  d2 r
}

lyr = \lyricmode { Glo -- ri -- a! }

stuff = {
  \dynamicUp % try commenting this out!
  <>\f\>
  s1
  <>\!
}

\new Staff << \mel \stuff >> \addlyrics \lyr
\new Staff << \stuff \mel >> \addlyrics \lyr
\new Staff << \mel \addlyrics \lyr \stuff >>

But if you remove the \dynamicUp you'll see that LilyPond's behaviour in 
<< \A \B >> \addlyrics { ... } constructions is a bit volatile.


Lukas

Re: Slurs not being followed in one vocal part

[Jon Arnold]

Thanks all! Separating the voices did fix the problem. I used this score a
long time ago and then updated the layout, so I feel like an update several
years ago must have changed the behavior, which is interesting.

On Sat, Jan 21, 2023 at 8:27 PM David Wright 
wrote:

> On Sun 22 Jan 2023 at 11:59:06 (+1100), Vaughan McAlley wrote:
> > On Sun, 22 Jan 2023, 10:32 Jon Arnold, 
> wrote:
> >
> > > Hey folks-
> > >
> > > Can anyone tell me why the slurs are not being followed in the soprano
> > > part of the attached file? It first occurs in the 2nd half of bar 7,
> bottom
> > > of page 3. It seems to be related to the barLiner function I have (it
> goes
> > > away if I remove it), but I don't understand why this would affect the
> > > lyrics.
> > >
> > > Here's the function:
> > > barLiner = {
> > >   \repeat unfold 20 { s2 \bar "!" s2. }
> > >   \set Timing.measureLength = #(ly:make-moment 1/2)
> > >   s2 s2
> > >   \set Timing.measureLength = #(ly:make-moment 3/4)
> > >   s2. s2. \bar "|."
> > >
> > > }
> > >
> > > This is called with:
> > > \new Staff \with {
> > > midiInstrument = "choir aahs"
> > > instrumentName = "Soprano"
> > >   } { << \soprano \barLiner >> }
> > >   \addlyrics { \sopranoVerse }
> > >
> >
> > Hi Jon,
> >
> > I can't remember off the top of my head which Lilypond version things
> > changed but explicitly instantiating a voice has fixed this sort of thing
> > for me in the past:
> >
> > } \new Voice { << \soprano \barLiner >> }
>
> You need something more like:
>
> choirPart = \new ChoirStaff <<
>   \new Staff \with {
> midiInstrument = "choir aahs"
> instrumentName = "Soprano"
>   } <<
> \new Voice { \barLiner }
> \new Voice { \soprano }
> \addlyrics { \sopranoVerse }
>   >>
>   \new Staff \with {
> midiInstrument = "choir aahs"
> instrumentName = "Alto"
>   } { \alto }
>
> I presume that \addlyrics gets totally confused when asked to
> add lyrics to a construction like { << \soprano \barLiner >> }.
> How would it know to use only the \soprano line?
>
> Cheers,
> David.
>
>

Re: Slurs not being followed in one vocal part

[David Wright]

On Sun 22 Jan 2023 at 11:59:06 (+1100), Vaughan McAlley wrote:
> On Sun, 22 Jan 2023, 10:32 Jon Arnold,  wrote:
> 
> > Hey folks-
> >
> > Can anyone tell me why the slurs are not being followed in the soprano
> > part of the attached file? It first occurs in the 2nd half of bar 7, bottom
> > of page 3. It seems to be related to the barLiner function I have (it goes
> > away if I remove it), but I don't understand why this would affect the
> > lyrics.
> >
> > Here's the function:
> > barLiner = {
> >   \repeat unfold 20 { s2 \bar "!" s2. }
> >   \set Timing.measureLength = #(ly:make-moment 1/2)
> >   s2 s2
> >   \set Timing.measureLength = #(ly:make-moment 3/4)
> >   s2. s2. \bar "|."
> >
> > }
> >
> > This is called with:
> > \new Staff \with {
> > midiInstrument = "choir aahs"
> > instrumentName = "Soprano"
> >   } { << \soprano \barLiner >> }
> >   \addlyrics { \sopranoVerse }
> >
> 
> Hi Jon,
> 
> I can't remember off the top of my head which Lilypond version things
> changed but explicitly instantiating a voice has fixed this sort of thing
> for me in the past:
> 
> } \new Voice { << \soprano \barLiner >> }

You need something more like:

choirPart = \new ChoirStaff <<
  \new Staff \with {
midiInstrument = "choir aahs"
instrumentName = "Soprano"
  } <<
\new Voice { \barLiner }
\new Voice { \soprano }
\addlyrics { \sopranoVerse }
  >>
  \new Staff \with {
midiInstrument = "choir aahs"
instrumentName = "Alto"
  } { \alto }

I presume that \addlyrics gets totally confused when asked to
add lyrics to a construction like { << \soprano \barLiner >> }.
How would it know to use only the \soprano line?

Cheers,
David.

Re: Slurs not being followed in one vocal part

[Vaughan McAlley]

On Sun, 22 Jan 2023, 10:32 Jon Arnold,  wrote:

> Hey folks-
>
> Can anyone tell me why the slurs are not being followed in the soprano
> part of the attached file? It first occurs in the 2nd half of bar 7, bottom
> of page 3. It seems to be related to the barLiner function I have (it goes
> away if I remove it), but I don't understand why this would affect the
> lyrics.
>
> Here's the function:
> barLiner = {
>   \repeat unfold 20 { s2 \bar "!" s2. }
>   \set Timing.measureLength = #(ly:make-moment 1/2)
>   s2 s2
>   \set Timing.measureLength = #(ly:make-moment 3/4)
>   s2. s2. \bar "|."
>
> }
>
> This is called with:
> \new Staff \with {
> midiInstrument = "choir aahs"
> instrumentName = "Soprano"
>   } { << \soprano \barLiner >> }
>   \addlyrics { \sopranoVerse }
>

Hi Jon,

I can't remember off the top of my head which Lilypond version things
changed but explicitly instantiating a voice has fixed this sort of thing
for me in the past:

} \new Voice { << \soprano \barLiner >> }

Vaughan

>

Re: Slurs not being followed in one vocal part

[William Rehwinkel]

Dear Jon,

I'm having trouble finding exactly what is the problem here. There is a 
slur between the dotted quarter and eighth note in bar 7, looking at 
that section in the soprano block it is being rendered as I thought it 
would be. Can you please create a minimal example that demonstrates the 
problem?


-Will

On 1/21/23 18:31, Jon Arnold wrote:

Hey folks-

Can anyone tell me why the slurs are not being followed in the soprano 
part of the attached file? It first occurs in the 2nd half of bar 7, 
bottom of page 3. It seems to be related to the barLiner function I have 
(it goes away if I remove it), but I don't understand why this would 
affect the lyrics.


Here's the function:
barLiner = {
   \repeat unfold 20 { s2 \bar "!" s2. }
   \set Timing.measureLength = #(ly:make-moment 1/2)
   s2 s2
   \set Timing.measureLength = #(ly:make-moment 3/4)
   s2. s2. \bar "|."

}

This is called with:
\new Staff \with {
     midiInstrument = "choir aahs"
     instrumentName = "Soprano"
   } { << \soprano \barLiner >> }
   \addlyrics { \sopranoVerse }


--
+ -- +
|William Rehwinkel - Oberlin College and |
|   Conservatory '24 |
|  will...@williamrehwinkel.net  |
| PGP key:   |
| https://williamrehwinkel.net/static/pubkey.txt |
+ -- +


OpenPGP_signature
Description: OpenPGP digital signature

Re: slurs across voices

[Jim Cline]

Hi William and Knute,
Thanks for your suggestions.  It's nice to have two options.  I like 
Knute's since I'm not very knowledgable about the engraver functions,

which are a black box to me, while the method Knute proposes is
easily understandable and only requires tweaking the measure in question.
best regards, Jim


On Wed, 27 Jul 2022, William Rehwinkel wrote:


Hey Jim,

A little while ago I found this email which describes enabling the slur 
engraver on the staff level instead of voice level. Did you see this before, 
or give it a try?


https://lists.gnu.org/archive/html/bug-lilypond/2012-03/msg00663.html


\version "2.15.33"

\score {
  \new Staff {
    \time 2/4
    <<
  \new Voice {
    \relative c'' {
  \voiceOne
  d16( c8. a16( g8.
    }
  }
  \new Voice {
    \relative c'' {
  \voiceTwo
  g8 g') c,,8 c'8)
    }
  }
    >>
  }
  \layout {
    \context {
  \Voice
  \remove "Slur_engraver"
  \remove "Slur_performer"
    }
    \context {
  \Staff
  \consists "Slur_engraver"
  \consists "Slur_performer"
    }
  }
}

On 7/27/22 11:28, Jim Cline wrote:
I would like to create slurs between alternating notes across two voices in 
this example:


\version "2.20.0"
lower =
  \relative c {
   \time 3/4
  \clef bass
  <<{\stemUp e''16\rest cis4 bis ais8~ais16}\\{\clef treble\stemDown 
\slurDown e4 dis cis}>>|

}
\score {
    \new Staff = "lower" \lower

The documentation provides an example in 
http://lilypond.org/doc/v2.21/Documentation/snippets/expressive-marks 
("creating slurs across voices") but it only works in the case where beats 
are missing in each voice.  In my case, each voice has the full number of
beats to make a measure.  It seems like this issue was last discussed in 
2015, 
https://lists.gnu.org/archive/html/lilypond-devel/2015-03/msg00288.html

unless I missed something.  Has this limitation been addressed since then?

regards, Jim



--
William Rehwinkel

will...@williamrehwinkel.net
https://williamrehwinkel.net

Re: slurs across voices

[William Rehwinkel]

Hey Jim,

A little while ago I found this email which describes enabling the slur 
engraver on the staff level instead of voice level. Did you see this 
before, or give it a try?


https://lists.gnu.org/archive/html/bug-lilypond/2012-03/msg00663.html


\version "2.15.33"

\score {
  \new Staff {
    \time 2/4
    <<
  \new Voice {
    \relative c'' {
  \voiceOne
  d16( c8. a16( g8.
    }
  }
  \new Voice {
    \relative c'' {
  \voiceTwo
  g8 g') c,,8 c'8)
    }
  }
    >>
  }
  \layout {
    \context {
  \Voice
  \remove "Slur_engraver"
  \remove "Slur_performer"
    }
    \context {
  \Staff
  \consists "Slur_engraver"
  \consists "Slur_performer"
    }
  }
}

On 7/27/22 11:28, Jim Cline wrote:
I would like to create slurs between alternating notes across two 
voices in this example:


\version "2.20.0"
lower =
  \relative c {
   \time 3/4
  \clef bass
  <<{\stemUp e''16\rest cis4 bis ais8~ais16}\\{\clef treble\stemDown 
\slurDown e4 dis cis}>>|

}
\score {
    \new Staff = "lower" \lower

The documentation provides an example in 
http://lilypond.org/doc/v2.21/Documentation/snippets/expressive-marks 
("creating slurs across voices") but it only works in the case where 
beats are missing in each voice.  In my case, each voice has the full 
number of
beats to make a measure.  It seems like this issue was last discussed 
in 2015, 
https://lists.gnu.org/archive/html/lilypond-devel/2015-03/msg00288.html
unless I missed something.  Has this limitation been addressed since 
then?


regards, Jim



--
William Rehwinkel

will...@williamrehwinkel.net
https://williamrehwinkel.net

Re: slurs across voices

[Knute Snortum]

On Wed, Jul 27, 2022 at 8:29 AM Jim Cline  wrote:
>
> I would like to create slurs between alternating notes across two voices
> in this example:
>
> \version "2.20.0"
> lower =
>\relative c {
> \time 3/4
>\clef bass
><<{\stemUp e''16\rest cis4 bis ais8~ais16}\\{\clef treble\stemDown
> \slurDown e4 dis cis}>>|
> }
> \score {
>  \new Staff = "lower" \lower
>
> The documentation provides an example in
> http://lilypond.org/doc/v2.21/Documentation/snippets/expressive-marks
> ("creating slurs across voices") but it only works in the case where beats
> are missing in each voice.  In my case, each voice has the full number of
> beats to make a measure.  It seems like this issue was last discussed in
> 2015,
> https://lists.gnu.org/archive/html/lilypond-devel/2015-03/msg00288.html
> unless I missed something.  Has this limitation been addressed since then?

Well, here's my take on it.  There may be a better way:

First, I made your example into a MWE (minimum working example).  Then
I used the trick of reducing the duration of a note but keeping the
duration that's engraved.  I used 4*1/4 for a note that looks like a
quarter note but only takes up the duration of a sixteenth.  That gave
me this:

%%%
\version "2.20.0"

\relative c {
  \time 3/4
  <<
{ e''16\rest cis4 bis ais8~ais16 }
\\
{
  e4*1/4( \once \hideNotes cis'4*3/4)
  dis,4*1/4( \once \hideNotes bis'4*3/4)
  cis,4*1/4( \once \hideNotes ais'4*3/4)
}
  >>|
}
%%%

--
Knute Snortum

slurs across voices

[Jim Cline]

I would like to create slurs between alternating notes across two voices 
in this example:


\version "2.20.0"
lower =
  \relative c {
   \time 3/4
  \clef bass
  <<{\stemUp e''16\rest cis4 bis ais8~ais16}\\{\clef treble\stemDown 
\slurDown e4 dis cis}>>|

}
\score {
\new Staff = "lower" \lower

The documentation provides an example in 
http://lilypond.org/doc/v2.21/Documentation/snippets/expressive-marks 
("creating slurs across voices") but it only works in the case where beats 
are missing in each voice.  In my case, each voice has the full number of
beats to make a measure.  It seems like this issue was last discussed in 
2015, 
https://lists.gnu.org/archive/html/lilypond-devel/2015-03/msg00288.html

unless I missed something.  Has this limitation been addressed since then?

regards, Jim

Re: Three slurs from a single voice to three voices?

[Simon Albrecht]

Hi Kevin,

On 02/06/2022 22:56, Kevin Cole wrote:

The hand-written score I'm looking at shows an F# with three slurs
coming off of it going to each of the three notes in the following
measure. I tried the following but it only shows one slur. What did I
miss?



without context it’s hard to tell what the original notation wanted to 
achieve, so this is only one suggestion to fix some aspects that may or 
may not fit that context.


– One technical issue is this: If you write

\new Voice \voiceTwo { c4 }

then the Voice you explicitly created will contain _only_ the \voiceTwo 
command. The following music expression is separate and will again go 
into the voice context you were previously in. Move the brace:


\new Voice { \voiceTwo c4 }

Now there’s only one music expression which goes into the new Voice, and 
the \voiceTwo command works on the following music.


– LilyPond has a way of having slurs across Voices by moving 
Slur_engraver to the Staff (or a higher-level) context and linking the 
slurs like this:

{
  fs'4\=1 ( \=2 (
  <<
    { \voiceOne b'4\=1 ) }
    \new Voice { \voiceTwo d'4\=2 ) }
  >>
}

However, it isn’t very good (yet?) at making this look good, and in fact 
it can quickly get very difficult to make it look good at all.


– In general, having more than two independent parts on one Staff 
usually leads to difficult engraving issues that would generally be best 
solved by using more than one Staff, especially if it’s vocal music with 
Lyrics on top of everything.


What I suggest here is merging the bottom two parts into one Voice since 
they share the same rhythm. Note how the two music expressions end up in 
one Voice, and only the third one doesn’t because of the \new Voice.


%%%
\version "2.22.1"
\language "english"

\new Staff {
  \relative c' {
    \time 4/4
    \key d \major
    d2 r4
    <<
  {
    \voiceTwo
    fs4(
    d2) cs4 cs4  |
    d2 d2 |
  }
  {
    s4
    b2 as4 as4   |
    b2 b2 |
  }
  \new Voice {
    \voiceOne
    fs'4~
    fs4( g) g4 fs4   |
    fs4( b4) b2   |
  }
    >>
    \oneVoice
  }
}


This will work with Lyrics as well, since the Voice context first 
created continues all the way through.


HTH, Simon

Re: Three slurs from a single voice to three voices?

[Kevin Cole]

Thanks for the suggestions.

I'm working from a 3-ring binder of songs collected via photocopying
and hand-transcription that a group of us used to sing and play from
30 years ago. I have no idea who scrawled this tune in. But, seeing as
how most (if not all) of us were amateurs, it is very possible that
the person doing the transcription got something wrong. I'm still bad
enough at this that I wouldn't recognize "wrong". It's not an
original. My initial thought was to, as much as possible, faithfully
transcribe what I have in the binder.

The hand-writing is so bad that I had trouble deciphering the lyrics
-- and the title, but digging around a bit, it appears to be an
arrangement -- perhaps by one of our members from the now long-defunct
group -- of "Adoramus te Christe". (Not one of the songs we did often
enough for me to remember it.) The score looks to be SAB1B2 + Piano.
And the lyrics that I can make out don't strictly follow the lyrics
I'm finding online.  I may try to dig up a more official and
better-printed version, now that the feedback I'm getting is that the
arrangement is "odd" in that section I was asking about.

Re: Three slurs from a single voice to three voices?

[Paul Hodges]

You only start one slur, so you only get one.  If you try extra notes, you have 
to ensure that the voices are such that they will combine.  However, you could 
in this case specify a tie to the note that's the same, a slur to the note 
below, and a phrasing slur to the bottom note, so your starting note has these 
piled up after it like so: fs4~(\( .  But the result is clashing slurs, so 
you'll need to use the \shape tweak to adjust the position of at least one of 
them.


But to me this seems a very odd way to write this...


Paul



 From:   Kevin Cole  
 To:   lilypond-user mailinglist  
 Sent:   02/06/2022 21:56 
 Subject:   Three slurs from a single voice to three voices? 

Hi, 
 
The hand-written score I'm looking at shows an F# with three slurs 
coming off of it going to each of the three notes in the following 
measure. I tried the following but it only shows one slur. What did I 
miss? 
 
 
\version "2.22.1" 
\language "english" 
 
\new Staff { 
  \relative c' { 
    \time 4/4 
    \key d \major 
    d2 r4 fs4(            | 
    << 
      \voiceOne { 
        fs4)( g) g4 fs4   | 
        fs4( b4) b2       | 
      } 
      \new Voice 
      \voiceTwo { 
        d,2) cs4 cs4      | 
        d2 d2             | 
      } 
      \new Voice 
      \voiceThree { 
        b2) as4 as4       | 
        b2 b2             | 
      } 
    >> 
    \oneVoice 
  } 
} 
 
 
 (I also tried adding the starting F# to each of the three voices but 
it made a two-headed F#. I didn't go so far as to add the F# to the 
third voice, since it was messing up when I added it to the second, 
and it seemed like there was probably a better solution than fighting 
with the direction of the head for the single note, since it's one 
more thing I don't know how to do, and seemed -- to me -- 
counter-intuitive as an approach.) 
 

Three slurs from a single voice to three voices?

[Kevin Cole]

Hi,

The hand-written score I'm looking at shows an F# with three slurs
coming off of it going to each of the three notes in the following
measure. I tried the following but it only shows one slur. What did I
miss?


\version "2.22.1"
\language "english"

\new Staff {
  \relative c' {
\time 4/4
\key d \major
d2 r4 fs4(|
<<
  \voiceOne {
fs4)( g) g4 fs4   |
fs4( b4) b2   |
  }
  \new Voice
  \voiceTwo {
d,2) cs4 cs4  |
d2 d2 |
  }
  \new Voice
  \voiceThree {
b2) as4 as4   |
b2 b2 |
  }
>>
\oneVoice
  }
}


 (I also tried adding the starting F# to each of the three voices but
it made a two-headed F#. I didn't go so far as to add the F# to the
third voice, since it was messing up when I added it to the second,
and it seemed like there was probably a better solution than fighting
with the direction of the head for the single note, since it's one
more thing I don't know how to do, and seemed -- to me --
counter-intuitive as an approach.)

Re: Guitar notation - scheme function for slurs with markup

[Valentin Petzel]

Hi Stefan, hi Lukas,

I think it might be reasonable to directly annotate the Slurs instead. This 
allows for nice placement, see the appended example.

Cheers,
Valentin

Am Montag, 30. Mai 2022, 08:17:58 CEST schrieb Stefan E. Mueller:
> Hi Lukas,
> 
> yes, that is what I need, I can take it from there - many thanks for the
> quick response and solution, and the explanations!
> 
>   Stefan
> 
> --
> Stefan E. Mueller
> 
> stefan.e.muel...@gmx.de
> 
> On Sun, 29 May 2022, Lukas-Fabian Moser wrote:
> > Hi Stefan,
> > 
> > Am 29.05.22 um 22:42 schrieb Stefan E. Mueller:
> >> I am not sure yet what the difference between a scheme-function and a
> >> music-function is (the second example seems to work whichever definition
> >> is chosen).
> > 
> > A music function must return music, a scheme function can return more
> > general expressions (for instance, a new function or a list of symbols).
> > 
> >> The "-" dash in my case added an (unwanted) accentuation to
> >> the first note, I get the slur with the markup without the accent only if
> >> I remove it (not sure what it is supposed to do - manual says it is a
> >> required
> >> named direction indicator, but in my version 2.22.1 it doesn't work like
> >> that).
> > 
> > Ah, I thought you wanted the accent. :-)
> > 
> > Both the - and ^ symbols have various meanings; it's important to read
> > them
> > in order.
> > 
> > Add articulation with neutral direction/up-facing/down-facing: -!, ^!, _!
> > (here I use ! = staccatissimo as an articulation, but ( = slur, ^ =
> > marcato
> > and - = tenuto are other examples)
> > 
> > If you just want a slur that should have its direction forced upwards,
> > just
> > write ^(
> > 
> >> I thought the function-constructs were merely doing variable
> >> substitutions, but it seems there is more to this. Because now I have the
> >> problem how to describe several hammer-ons in a row with a function, like
> >> this:
> >> 
> >> \new Staff {
> >> e''8^(^\markup {\halign #-1.5 ho} f''8)^\markup {\halign #-1.5 ho} g''\8)
> >> }
> >> 
> >> Ideally, I'd like to be able to write this like
> >> 
> >> e''8 \ho f''8 \ho g''8
> >> 
> >> (with the corresponding closing brackets also provided by the function,
> >> but it may be that this is not possible).
> > 
> > I assume you want another slur to start on the f''? Then maybe something
> > like this:
> > 
> > \version "2.22"
> > 
> > ho =
> > #(define-music-function (spacing music) ((number? -1.5) ly:music?)
> >#{
> >  <>^(^\markup {\halign #spacing ho}
> >  #music
> >  <>)
> >#})
> > 
> > \new Staff {
> >   e''8 \ho f''8 \ho g''8 a''
> > }
> > 
> > Lukas

%%% Some vector functions for pairs

% Sum of vectors
#(define (vecsum v1 . rest)
   (if (null? rest)
   v1
   (let ((v2 (apply vecsum rest)))
 (cons (+ (car v1) (car v2))
   (+ (cdr v1) (cdr v2))

% Inner product of two vectors
#(define (vecip v1 v2)
   (+ (* (car v1) (car v2))
  (* (cdr v1) (cdr v2

% Normal vector
#(define (vecnv v)
   (cons (cdr v) (- (car v

% Vector norm
#(define (vecnorm v)
   (sqrt (+ (* (car v) (car v)) (* (cdr v) (cdr v)

% Scale vector by scalar
#(define (vecscale s v)
   (cons (* s (car v)) (* s (cdr v

% Normalize vector such that ||v|| = 1
#(define (vecnormalize v)
   (vecscale (/ 1 (vecnorm v)) v))

% Calculate length of projection of one vector onto another vector
#(define (vecprojection on v)
   (vecip v (vecnormalize on)))

% Calculate difference of two vectors
#(define (vecdiff v1 v2)
   (vecsum v1 (vecscale -1 v2)))

% Calculate product of matrix (given as pair of row vectors) and vector
#(define (matvecprod m v)
   (cons (vecip (car m) v) (vecip (cdr m) v)))

% Rotation matrix
#(define (matrot phi)
   (cons
(cons (cos phi) (- (sin phi)))
    (cons (sin phi) (cos phi

% Rotate vector by phi
#(define (vecrotate phi v)
   (matvecprod (matrot phi) v))

%%% Resolve a path of symbols from a nested alist
#(define* (nested-assoc-get keys alist #:optional (default #f))
   (if (list? keys)
   (if (null? keys)
   alist
   (let ((res (assoc-get (car keys) alist 'SPECIAL_STATE_NESTED_ASSOC_GET_NOT_FOUND)))
 (if (eq? res 'SPECIAL_STATE_NESTED_ASSOC_GET_NOT_FOUND)
 default
 (nested-assoc-get (cdr keys) res

Re: Guitar notation - scheme function for slurs with markup

[Stefan E. Mueller]

Hi Lukas,

yes, that is what I need, I can take it from there - many thanks for the
quick response and solution, and the explanations!

Stefan

--
Stefan E. Mueller

stefan.e.muel...@gmx.de

On Sun, 29 May 2022, Lukas-Fabian Moser wrote:


Hi Stefan,

Am 29.05.22 um 22:42 schrieb Stefan E. Mueller:

I am not sure yet what the difference between a scheme-function and a
music-function is (the second example seems to work whichever definition
is chosen).

A music function must return music, a scheme function can return more general
expressions (for instance, a new function or a list of symbols).

The "-" dash in my case added an (unwanted) accentuation to
the first note, I get the slur with the markup without the accent only if
I remove it (not sure what it is supposed to do - manual says it is a
required
named direction indicator, but in my version 2.22.1 it doesn't work like
that).


Ah, I thought you wanted the accent. :-)

Both the - and ^ symbols have various meanings; it's important to read them
in order.

Add articulation with neutral direction/up-facing/down-facing: -!, ^!, _!
(here I use ! = staccatissimo as an articulation, but ( = slur, ^ = marcato
and - = tenuto are other examples)

If you just want a slur that should have its direction forced upwards, just
write ^(


I thought the function-constructs were merely doing variable
substitutions, but it seems there is more to this. Because now I have the
problem how to describe several hammer-ons in a row with a function, like
this:

\new Staff {
e''8^(^\markup {\halign #-1.5 ho} f''8)^\markup {\halign #-1.5 ho} g''\8)
}

Ideally, I'd like to be able to write this like

e''8 \ho f''8 \ho g''8

(with the corresponding closing brackets also provided by the function,
but it may be that this is not possible).


I assume you want another slur to start on the f''? Then maybe something like
this:

\version "2.22"

ho =
#(define-music-function (spacing music) ((number? -1.5) ly:music?)
   #{
 <>^(^\markup {\halign #spacing ho}
 #music
 <>)
   #})

\new Staff {
  e''8 \ho f''8 \ho g''8 a''
}

Lukas

Re: Guitar notation - scheme function for slurs with markup

[Lukas-Fabian Moser]

Hi Stefan,

Am 29.05.22 um 22:42 schrieb Stefan E. Mueller:

I am not sure yet what the difference between a scheme-function and a
music-function is (the second example seems to work whichever definition
is chosen).
A music function must return music, a scheme function can return more 
general expressions (for instance, a new function or a list of symbols).

The "-" dash in my case added an (unwanted) accentuation to
the first note, I get the slur with the markup without the accent only if
I remove it (not sure what it is supposed to do - manual says it is a 
required
named direction indicator, but in my version 2.22.1 it doesn't work 
like that).


Ah, I thought you wanted the accent. :-)

Both the - and ^ symbols have various meanings; it's important to read 
them in order.


Add articulation with neutral direction/up-facing/down-facing: -!, ^!, 
_! (here I use ! = staccatissimo as an articulation, but ( = slur, ^ = 
marcato and - = tenuto are other examples)


If you just want a slur that should have its direction forced upwards, 
just write ^(



I thought the function-constructs were merely doing variable
substitutions, but it seems there is more to this. Because now I have the
problem how to describe several hammer-ons in a row with a function, like
this:

\new Staff {
e''8^(^\markup {\halign #-1.5 ho} f''8)^\markup {\halign #-1.5 ho} g''\8)
}

Ideally, I'd like to be able to write this like

e''8 \ho f''8 \ho g''8

(with the corresponding closing brackets also provided by the function,
but it may be that this is not possible).


I assume you want another slur to start on the f''? Then maybe something 
like this:


\version "2.22"

ho =
#(define-music-function (spacing music) ((number? -1.5) ly:music?)
   #{
 <>^(^\markup {\halign #spacing ho}
 #music
 <>)
   #})

\new Staff {
  e''8 \ho f''8 \ho g''8 a''
}

Lukas

Re: Guitar notation - scheme function for slurs with markup

[Stefan E. Mueller]

Hi Lukas,

many thanks for your quick answer. Obviously, things are more complex
than I thought.

Both of your solutions work for the problem, I tend to be more inclined
towards the second one. But I still have to understand better what is going
on here.

I am not sure yet what the difference between a scheme-function and a
music-function is (the second example seems to work whichever definition
is chosen). The "-" dash in my case added an (unwanted) accentuation to
the first note, I get the slur with the markup without the accent only if
I remove it (not sure what it is supposed to do - manual says it is a required
named direction indicator, but in my version 2.22.1 it doesn't work like that).

I thought the function-constructs were merely doing variable
substitutions, but it seems there is more to this. Because now I have the
problem how to describe several hammer-ons in a row with a function, like
this:

\new Staff {
e''8^(^\markup {\halign #-1.5 ho} f''8)^\markup {\halign #-1.5 ho} g''\8)
}

Ideally, I'd like to be able to write this like

e''8 \ho f''8 \ho g''8

(with the corresponding closing brackets also provided by the function,
but it may be that this is not possible).

Stefan


--
Stefan E. Mueller

stefan.e.muel...@gmx.de

On Sun, 29 May 2022, Lukas-Fabian Moser wrote:


Hi Stefan,

please try to always give a compilable examle, otherwise people have to
collect your ideas from your mail bit by bit :).

You could use an event-function; these are made for postfix use (i.e. after
the respective note):

\version "2.22"

ho = #(define-event-function
   (spacing)
   (number?)
   #{
 -^(^\markup {\halign #spacing ho}
   #})

\new Staff {
  e''8 f''8\ho #-1.5 a'')
}

Note that I had to escape the -1.5 with #, this is expected for negative
numbers.

With this solution, the "spacing" parameter cannot be made optional. This can
be achieved by going back to music functions and putting the (optional)
spacing first:

\version "2.22"

ho = #(define-music-function
   (spacing music)
   ((number? -1.5) ly:music?)
   #{
 <>-^(^\markup {\halign #spacing ho}
 #music
   #})

\new Staff {
  e''8 \ho #-2.5 f''8 a'')
}

\new Staff {
  e''8 \ho f''8 a'')
}

Here, I have used the "empty chord trick": <> is an empty chord that doesn't
take up time; any slurs and articulations attached to this chord will be
attached to the first bit of music coming after it.

I hope I didn't miss important parts of your question in my hurry :-).

Lukas

Re: Guitar notation - scheme function for slurs with markup

[Lukas-Fabian Moser]

Hi Stefan,

please try to always give a compilable examle, otherwise people have to 
collect your ideas from your mail bit by bit :).


You could use an event-function; these are made for postfix use (i.e. 
after the respective note):


\version "2.22"

ho = #(define-event-function
   (spacing)
   (number?)
   #{
 -^(^\markup {\halign #spacing ho}
   #})

\new Staff {
  e''8 f''8\ho #-1.5 a'')
}

Note that I had to escape the -1.5 with #, this is expected for negative 
numbers.


With this solution, the "spacing" parameter cannot be made optional. 
This can be achieved by going back to music functions and putting the 
(optional) spacing first:


\version "2.22"

ho = #(define-music-function
   (spacing music)
   ((number? -1.5) ly:music?)
   #{
 <>-^(^\markup {\halign #spacing ho}
 #music
   #})

\new Staff {
  e''8 \ho #-2.5 f''8 a'')
}

\new Staff {
  e''8 \ho f''8 a'')
}

Here, I have used the "empty chord trick": <> is an empty chord that 
doesn't take up time; any slurs and articulations attached to this chord 
will be attached to the first bit of music coming after it.


I hope I didn't miss important parts of your question in my hurry :-).

Lukas

Guitar notation - scheme function for slurs with markup

[Stefan E. Mueller]

When notating guitar music, I use a slur with a markup to indicate
hammer-ons, pull-offs, slides or bendings, like in this example:

\new Staff {
e''8^(^\markup {\halign #-1.5 ho} f''8)
}

I'd like to define a scheme function for the slur and markup, such that I
can write

\new Staff {
e''8 \ho f''8
}

I tried

ho = #(define-scheme-function
   (music spacing)
   (ly:music? number?)
   #{
 {^(^\markup {\halign #-1.5 ho} $music )}
   #})

But this only displays the note and the markup text "ho", but not the
slur. Maybe I need to escape the many special characters, but my trials
did not work.

I'd also like to pass a second parameter "spacing" to horizontally
align the markup text on the slur. But if I substitute the "-1.5" in the
function with "$spacing", I get an "error: syntax error, unexpected REAL" when
I do

\new Staff {
e''8 \ho f''8 -1.5
}

By the way, would it be possible to have this second parameter optional,
e.g. to fall back to a default value in case it is
not given?).

I have just started to work with functions in Lilypond, and it maybe that
there are better solutions to this problem than using a scheme function,
but I am obviously struggling to get it working.

Any hint would be very much appreciated,

Stefan

--
Stefan E. Mueller

stefan.e.muel...@gmx.de

Re: Dashed slurs causing score concatenation issues

[Jean Abou Samra]

> Le 6 févr. 2022 à 18:39, Trinton  a écrit :
> 
> Hi folks,
> 
> Since adding dashed slurs to my score using the \slurDashed command, I've 
> been unable to concatenate the segments of my score, getting this error:
> [48]ERROR: Wrong type (expecting exact integer): # Trill_spanner_engraver >
> I've not been able to find any hints about this message in the docs. What's 
> especially perplexing is that my individual segments render fine on their 
> own, this error only shows up during concatenation. I'll link to the files in 
> question in case there's something in them that I'm missing: 
> Score: https://github.com/tr1nt0n/trio/blob/master/trio/build/trio_score.ly
> 
> Segment for concatenation: 
> https://github.com/tr1nt0n/trio/blob/master/trio/build/04.ly
> 
> Segment illustration: 
> https://github.com/tr1nt0n/trio/blob/master/trio/segments/04/illustration04.ly
> 
> Stylesheet: 
> https://github.com/tr1nt0n/trio/blob/master/trio/build/trio-stylesheet.ily
> 
> Script used to run lilypond: 
> https://github.com/tr1nt0n/trinton/blob/main/scripts/run-lilypond
> 
> Thanks for any help!
> Trinton



As far as I can read your files from a phone, they are using stuff outside of 
the repository. Please provide an archive or something with all the files 
needed to compile your score so that we can reproduce the issue.

Thanks,
Jean

Dashed slurs causing score concatenation issues

[Trinton]

Hi folks,

Since adding dashed slurs to my score using the \slurDashed command, I've
been unable to concatenate the segments of my score, getting this error:
[48]ERROR: Wrong type (expecting exact integer): #
I've not been able to find any hints about this message in the docs. What's
especially perplexing is that my individual segments render fine on their
own, this error only shows up during concatenation. I'll link to the files
in question in case there's something in them that I'm missing:
Score: https://github.com/tr1nt0n/trio/blob/master/trio/build/trio_score.ly

Segment for concatenation:
https://github.com/tr1nt0n/trio/blob/master/trio/build/04.ly

Segment illustration:
https://github.com/tr1nt0n/trio/blob/master/trio/segments/04/illustration04.ly

Stylesheet:
https://github.com/tr1nt0n/trio/blob/master/trio/build/trio-stylesheet.ily

Script used to run lilypond:
https://github.com/tr1nt0n/trinton/blob/main/scripts/run-lilypond

Thanks for any help!
Trinton

Re: Slurs with "afterGrace"

[Richard Shann]

\afterGrace g4(-+ {a16 g16)}   }

Richard

On Sun, 2022-02-06 at 09:13 +, Alasdair McAndrew wrote:
> Thank you very much!  (But in Australia, where I am, it is early
> evening).   I did try that, but the difficulty is that I already have
> a symbol attached to the note (which I should have included in my
> example):
> 
> \afterGrace g4-+( {a16 g16} )
> 
> I've tried moving the beginning of the slur to directly after the
> note:
> 
> \afterGrace g4(-+ {a16 g16} )
> 
> but this is no good either.  I'm sorry not to have included this
> clearly important detail in my first post.
> 
> Alasdair
> 
> 
> 
> On Sunday 06 February 2022 19:31:32 (+11:00), Rip _Mus wrote:
> 
> > Good morning,
> > try:
> > 
> > \afterGrace g4( { a16 g16) }
> > 
> > The slur event must be attached directly after the note.
> > 
> > Rip_mus
> > 
> > Il dom 6 feb 2022, 08:59 Alasdair McAndrew  ha
> > scritto:
> > > This works:
> > > g4( \grace {a16 g16})
> > > 
> > > making a slur which includes the grace notes.  But in order to
> > > get the 
> > > right spacing and barring (I need grace notes to occur before the
> > > bar line, 
> > > rather than after), I need to use "afterGrace":
> > > 
> > > \afterGrace g4 {a16 g16}
> > > 
> > > However, if I attempt to include a slur:
> > > 
> > > \afterGrace g4( {a16 g16} )
> > > 
> > > I get a warning about an "Unattached SlurEvent".  Lilypond makes
> > > a good 
> > > guess at what I want and bungs a slur in anyway - but what does
> > > this 
> > > warning mean, and how can I avoid it?  Thank you!
> > > 
> > > Alasdair

Re: Slurs with "afterGrace"

[Rip _Mus]

Sorry for the hour!

It's a matter of parenthesis order and spaces:

\relative c' {
\afterGrace g4-+( { a16 g16) }
}

This works for me

Il dom 6 feb 2022, 10:13 Alasdair McAndrew  ha scritto:

> Thank you very much!  (But in Australia, where I am, it is early
> evening).   I did try that, but the difficulty is that I already have a
> symbol attached to the note (which I should have included in my example):
>
> \afterGrace g4-+( {a16 g16} )
>
> I've tried moving the beginning of the slur to directly after the note:
>
> \afterGrace g4(-+ {a16 g16} )
>
> but this is no good either.  I'm sorry not to have included this clearly
> important detail in my first post.
>
> Alasdair
>
>
>
> On Sunday 06 February 2022 19:31:32 (+11:00), Rip _Mus wrote:
>
> Good morning,
> try:
>
> \afterGrace g4( { a16 g16) }
>
> The slur event must be attached directly after the note.
>
> Rip_mus
>
> Il dom 6 feb 2022, 08:59 Alasdair McAndrew  ha scritto:
>
>> This works:
>> g4( \grace {a16 g16})
>>
>> making a slur which includes the grace notes.  But in order to get the
>> right spacing and barring (I need grace notes to occur before the bar
>> line,
>> rather than after), I need to use "afterGrace":
>>
>> \afterGrace g4 {a16 g16}
>>
>> However, if I attempt to include a slur:
>>
>> \afterGrace g4( {a16 g16} )
>>
>> I get a warning about an "Unattached SlurEvent".  Lilypond makes a good
>> guess at what I want and bungs a slur in anyway - but what does this
>> warning mean, and how can I avoid it?  Thank you!
>>
>> Alasdair
>> --
>> 0432 854 858
>> https://numbersandshapes.net
>>
>>
> --
> 0432 854 858
> https://numbersandshapes.net
>

Re: Slurs with "afterGrace"

[Richard Shann]

On Sun, 2022-02-06 at 10:00 +, Alasdair McAndrew wrote:
> Thank you!  I would never have thought of putting the ending slur
> inside 
> the grace note braces - but it works perfectly. 

well I got there because it said the error was in column 30, i.e. the
closing ) and I suspected that those are supposed to postfixed to the
note where the slur ends, not a sequence { } of notes.

Richard

>  
> Again, thanks.
> 
> Alasdair
> 
> On Sunday 06 February 2022 20:53:12 (+11:00), Richard Shann wrote:
> 
>  >
>  >
>  > \afterGrace g4(-+ {a16 g16)} }
>  >
>  > Richard
>  >
>  > On Sun, 2022-02-06 at 09:13 +, Alasdair McAndrew wrote:
>  > > Thank you very much!  (But in Australia, where I am, it is early
>  > > evening).   I did try that, but the difficulty is that I already
> have
>  > > a symbol attached to the note (which I should have included in
> my
>  > > example):
>  > >
>  > > \afterGrace g4-+( {a16 g16} )
>  > >
>  > > I've tried moving the beginning of the slur to directly after
> the
>  > > note:
>  > >
>  > > \afterGrace g4(-+ {a16 g16} )
>  > >
>  > > but this is no good either.  I'm sorry not to have included this
>  > > clearly important detail in my first post.
>  > >
>  > > Alasdair
>  > >
>  > >
>  > >
>  > > On Sunday 06 February 2022 19:31:32 (+11:00), Rip _Mus wrote:
>  > >
>  > > > Good morning,
>  > > > try:
>  > > >
>  > > > \afterGrace g4( { a16 g16) }
>  > > >
>  > > > The slur event must be attached directly after the note.
>  > > >
>  > > > Rip_mus
>  > > >
>  > > > Il dom 6 feb 2022, 08:59 Alasdair McAndrew 
> ha
>  > > > scritto:
>  > > > > This works:
>  > > > > g4( \grace {a16 g16})
>  > > > >
>  > > > > making a slur which includes the grace notes.  But in order
> to
>  > > > > get the
>  > > > > right spacing and barring (I need grace notes to occur
> before the
>  > > > > bar line,
>  > > > > rather than after), I need to use "afterGrace":
>  > > > >
>  > > > > \afterGrace g4 {a16 g16}
>  > > > >
>  > > > > However, if I attempt to include a slur:
>  > > > >
>  > > > > \afterGrace g4( {a16 g16} )
>  > > > >
>  > > > > I get a warning about an "Unattached SlurEvent".  Lilypond
> makes
>  > > > > a good
>  > > > > guess at what I want and bungs a slur in anyway - but what
> does
>  > > > > this
>  > > > > warning mean, and how can I avoid it?  Thank you!
>  > > > >
>  > > > > Alasdair
>  >
>  >
>  >

Re: Slurs with "afterGrace"

[Alasdair McAndrew]

Thank you!  I would never have thought of putting the ending slur inside 
the grace note braces - but it works perfectly.  
Again, thanks.


Alasdair

On Sunday 06 February 2022 20:53:12 (+11:00), Richard Shann wrote:

>
>
> \afterGrace g4(-+ {a16 g16)} }
>
> Richard
>
> On Sun, 2022-02-06 at 09:13 +, Alasdair McAndrew wrote:
> > Thank you very much!  (But in Australia, where I am, it is early
> > evening).   I did try that, but the difficulty is that I already have
> > a symbol attached to the note (which I should have included in my
> > example):
> >
> > \afterGrace g4-+( {a16 g16} )
> >
> > I've tried moving the beginning of the slur to directly after the
> > note:
> >
> > \afterGrace g4(-+ {a16 g16} )
> >
> > but this is no good either.  I'm sorry not to have included this
> > clearly important detail in my first post.
> >
> > Alasdair
> >
> >
> >
> > On Sunday 06 February 2022 19:31:32 (+11:00), Rip _Mus wrote:
> >
> > > Good morning,
> > > try:
> > >
> > > \afterGrace g4( { a16 g16) }
> > >
> > > The slur event must be attached directly after the note.
> > >
> > > Rip_mus
> > >
> > > Il dom 6 feb 2022, 08:59 Alasdair McAndrew  ha
> > > scritto:
> > > > This works:
> > > > g4( \grace {a16 g16})
> > > >
> > > > making a slur which includes the grace notes.  But in order to
> > > > get the
> > > > right spacing and barring (I need grace notes to occur before the
> > > > bar line,
> > > > rather than after), I need to use "afterGrace":
> > > >
> > > > \afterGrace g4 {a16 g16}
> > > >
> > > > However, if I attempt to include a slur:
> > > >
> > > > \afterGrace g4( {a16 g16} )
> > > >
> > > > I get a warning about an "Unattached SlurEvent".  Lilypond makes
> > > > a good
> > > > guess at what I want and bungs a slur in anyway - but what does
> > > > this
> > > > warning mean, and how can I avoid it?  Thank you!
> > > >
> > > > Alasdair
>
>
>
--
0432 854 858
https://numbersandshapes.net

Re: Slurs with "afterGrace"

[Alasdair McAndrew]

Thank you very much!  (But in Australia, where I am, it is early evening).  
I did try that, but the difficulty is that I already have a symbol 
attached to the note (which I should have included in my example):



\afterGrace g4-+( {a16 g16} )


I've tried moving the beginning of the slur to directly after the note:


\afterGrace g4(-+ {a16 g16} )


but this is no good either.  I'm sorry not to have included this clearly 
important detail in my first post.



Alasdair




On Sunday 06 February 2022 19:31:32 (+11:00), Rip _Mus wrote:


Good morning,
try:


\afterGrace g4( { a16 g16) }


The slur event must be attached directly after the note.


Rip_mus


Il dom 6 feb 2022, 08:59 Alasdair McAndrew  ha scritto:

This works:
g4( \grace {a16 g16})

making a slur which includes the grace notes.  But in order to get the
right spacing and barring (I need grace notes to occur before the bar line,
rather than after), I need to use "afterGrace":

\afterGrace g4 {a16 g16}

However, if I attempt to include a slur:

\afterGrace g4( {a16 g16} )

I get a warning about an "Unattached SlurEvent".  Lilypond makes a good
guess at what I want and bungs a slur in anyway - but what does this
warning mean, and how can I avoid it?  Thank you!

Alasdair
--
0432 854 858
https://numbersandshapes.net



--
0432 854 858
https://numbersandshapes.net

Re: Slurs with "afterGrace"

[Rip _Mus]

Good morning,
try:

\afterGrace g4( { a16 g16) }

The slur event must be attached directly after the note.

Rip_mus

Il dom 6 feb 2022, 08:59 Alasdair McAndrew  ha scritto:

> This works:
> g4( \grace {a16 g16})
>
> making a slur which includes the grace notes.  But in order to get the
> right spacing and barring (I need grace notes to occur before the bar
> line,
> rather than after), I need to use "afterGrace":
>
> \afterGrace g4 {a16 g16}
>
> However, if I attempt to include a slur:
>
> \afterGrace g4( {a16 g16} )
>
> I get a warning about an "Unattached SlurEvent".  Lilypond makes a good
> guess at what I want and bungs a slur in anyway - but what does this
> warning mean, and how can I avoid it?  Thank you!
>
> Alasdair
> --
> 0432 854 858
> https://numbersandshapes.net
>
>

Slurs with "afterGrace"

[Alasdair McAndrew]

This works:
g4( \grace {a16 g16})

making a slur which includes the grace notes.  But in order to get the 
right spacing and barring (I need grace notes to occur before the bar line, 
rather than after), I need to use "afterGrace":


\afterGrace g4 {a16 g16}

However, if I attempt to include a slur:

\afterGrace g4( {a16 g16} )

I get a warning about an "Unattached SlurEvent".  Lilypond makes a good 
guess at what I want and bungs a slur in anyway - but what does this 
warning mean, and how can I avoid it?  Thank you!


Alasdair
--
0432 854 858
https://numbersandshapes.net

How to place slurs above multiple objects

[Paolo Prete]

Hello,

Suppose that I have a slur that must be placed ABOVE a note which is part
of a a TupletBracket and an OttavaBracket .

As the documentation explains, TupletBrackets and OttavaBrackets  need to
have the outside-staff-priority property set to false in order to be
printed inside slurs.

However, with this method, I loose the benefits of the avoid-collisions
properties applied to these objects, because these properties are ignored
if outside-staff-priority property is set to false.

Then I wonder if is there a way to preserve the outside-staff-priority for
these objects and have a command that draws a slur regardless to its
collisions with them. In this way I would manually resolve collisions for
only one object (the slur) instead of two.

Thanks,

P

Re: Labelled slurs

[Kieren MacMillan]

Hi all,

On Nov 30, 2021, at 2:54 PM, David Kastrup  wrote:
> there may be the desire to eventually match labelled
> slurs at more than Voice-level while retaining Voice-level slurs
> locally.  However, I have no idea what kind of form this sort of feature
> could take exactly.  Could be an explicit Staff.1 label or so that would
> be required for this.

Interesting possibilities! I wonder whether it would make sense for the 
edition-engraver (or its equivalent) to leverage/share this label, or whether 
they should be separate ids?

Cheers,
Kieren.

Re: Labelled slurs

[David Kastrup]

Timothy Lanfear  writes:

> When slurs overlap, I noticed that I could omit one of the slur
> labels. Can I count on this behaviour or did I just get lucky?

You can count on it.  In a manner of speaking, "unlabelled" is a label
of its own.  With regard to whether you can count on this in eternity, I
am not as sure: there may be the desire to eventually match labelled
slurs at more than Voice-level while retaining Voice-level slurs
locally.  However, I have no idea what kind of form this sort of feature
could take exactly.  Could be an explicit Staff.1 label or so that would
be required for this.

> Taking the example from the NR 1.3.2:
>
> \version "2.22.0"
>
> \fixed c' {
>   2 
>   2 
> }

-- 
David Kastrup

Labelled slurs

[Timothy Lanfear]

When slurs overlap, I noticed that I could omit one of the slur labels. 
Can I count on this behaviour or did I just get lucky? Taking the 
example from the NR 1.3.2:


\version "2.22.0"

\fixed c' {
  2 
  2 
}

--
Timothy Lanfear, Bristol, UK.

Re: acciaccatura "slurs" are getting canceled with hide Slur

[Adam Good]

Dear Valentin,
Most excellent thank you very much for this!

Adam

On Mon, Nov 29, 2021 at 2:57 PM Valentin Petzel  wrote:

> Hi Adam,
>
> hide overrides the specified grobs to be transparent (they will still
> affect
> spacing!)
> One option would be doing something like the appended example, which
> overrides
> appoggiatura to tweak the slur to that transparent is #f.
>
> A better way would be the use \omit Slur, which sets Slur.stencil to #f
> (and
> thus prevents any graphics to be created). In that case appoggiatura needs
> to
> tweak the stencil back to ly:slur::print.
>
> Cheers,
> Valentin
>
>
> Am Montag, 29. November 2021, 19:55:13 CET schrieb Adam Good:
> > Hi Everyone,
> > Could someone help me please. Using...
> >
> > \hide Slur
> >
> > ...I would like to cancel my slur markings yet retain the small slur in
> my
> > acciaccatura. On a bit of a deadline and would appreciate any help!
> >
> > Thank you in advance.
> > Adam
> >
> > %%%
> > \relative c' {
> >   c8 (d e f) g (a b c)
> >   \acciaccatura d8 c4
> > }
> >
> > \layout {
> >   \context { \Score \remove "Bar_number_engraver" %\hide Slur
> >   }
> > }
> >
> > %%%
> > \relative c' {
> >   c8 (d e f) g (a b c)
> >   \acciaccatura d8 c4
> > }
> >
> > \layout {
> >   \context { \Score \remove "Bar_number_engraver" \hide Slur
> >   }
> > }

Re: acciaccatura "slurs" are getting canceled with hide Slur

[Valentin Petzel]

Hi Adam,

hide overrides the specified grobs to be transparent (they will still affect 
spacing!)
One option would be doing something like the appended example, which overrides 
appoggiatura to tweak the slur to that transparent is #f.

A better way would be the use \omit Slur, which sets Slur.stencil to #f (and 
thus prevents any graphics to be created). In that case appoggiatura needs to 
tweak the stencil back to ly:slur::print.

Cheers,
Valentin


Am Montag, 29. November 2021, 19:55:13 CET schrieb Adam Good:
> Hi Everyone,
> Could someone help me please. Using...
> 
> \hide Slur
> 
> ...I would like to cancel my slur markings yet retain the small slur in my
> acciaccatura. On a bit of a deadline and would appreciate any help!
> 
> Thank you in advance.
> Adam
> 
> %%%
> \relative c' {
>   c8 (d e f) g (a b c)
>   \acciaccatura d8 c4
> }
> 
> \layout {
>   \context { \Score \remove "Bar_number_engraver" %\hide Slur
>   }
> }
> 
> %%%
> \relative c' {
>   c8 (d e f) g (a b c)
>   \acciaccatura d8 c4
> }
> 
> \layout {
>   \context { \Score \remove "Bar_number_engraver" \hide Slur
>   }
> }appoggiatura =
#(define-music-function (music) (ly:music?)
   #{
   \grace { \temporary\override Stem.direction = #UP <>_\tweak transparent ##f _\tweak stencil #ly:slur::print _( #music \revert Stem.direction } <>) 
   #})


{\hide Slur c''( d'') \appoggiatura c'' d'' }
{\omit Slur c''( d'') \appoggiatura c'' d'' }

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

acciaccatura "slurs" are getting canceled with hide Slur

[Adam Good]

Hi Everyone,
Could someone help me please. Using...

\hide Slur

...I would like to cancel my slur markings yet retain the small slur in my
acciaccatura. On a bit of a deadline and would appreciate any help!

Thank you in advance.
Adam

%%%
\relative c' {
  c8 (d e f) g (a b c)
  \acciaccatura d8 c4
}

\layout {
  \context { \Score \remove "Bar_number_engraver" %\hide Slur
  }
}

%%%
\relative c' {
  c8 (d e f) g (a b c)
  \acciaccatura d8 c4
}

\layout {
  \context { \Score \remove "Bar_number_engraver" \hide Slur
  }
}

Re: Double slurs and custom part combining

[Karlin High]

On Tue, Oct 26, 2021 at 1:52 PM Jefferson Felix  wrote:
> it's not generating doubleSlurs, but when I remove the pair of numbers
> after \partCombine, doubleSlurs works.
>
> Am I doing something wrong?

I also live in a music tradition with joined-notes hymnals. I use
\partcombine #'(2 . 9)

In your example, I think the doubleSlurs ARE generating, it's just
that they both go in the same direction and appear as one. Try using
the direction indicators ^ and _ to correct this:

soprano = \relative c' {
\global
f1 a1^( g2) g
}

alto = \relative c' {
\global
f1 f1_( e2) e
}
-- 
Karlin High
Missouri, USA