Re: Slurs not being followed in one vocal part
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
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
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
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: Override note properties in markup,note or rhythm
Le 21/01/2023 à 17:26, | || | | a écrit :
Hiya!
I'm trying to find a gentle solution for the problem I encountered.
I overrided flag stencil in general Score, but it turns out that this
doesn't influence notes in \tempo, \note and \rhythm functions. I
there a possibility to influence those ones?
I add that I know I could construct note from the beginning inside
markup and add hidden tempo change for proper tempo export, but it
seems to be overkill for this kind of problem.
That overrides in the main music do not influence \tempo,
\note or \rhythm is intentional. However, \rhythm has more
flexibility than \note because you can just put overrides
inside it, like
\version "2.24.0"
customFlag = {
\override Score.Flag.stencil = #ly:text-interface::print
\override Score.Flag.text = \markup {\raise #-0.2 \beam #1.0 #0.05 #0.5 }
}
\score {
\new Staff {
\overrideTimeSignatureSettings 4/4 1/8 #'() #'()
\time 4/4
\customFlag
\tempo \markup { Mechanical (\fontsize #-1 \rhythm { \customFlag 8
} \hspace #-0.6 = 92 )}
c'8 8 8 8 8 8 8 8
c'8 8 8 8 8 8 8 8
}
}
It's also possible to do that globally with
\version "2.24.0"
customFlag = {
\override Score.Flag.stencil = #ly:text-interface::print
\override Score.Flag.text = \markup {\raise #-0.2 \beam #1.0 #0.05 #0.5 }
}
\layout {
\context {
\Score
\customFlag
}
\context {
\StandaloneRhythmScore
\customFlag
}
}
\score {
\new Staff {
\overrideTimeSignatureSettings 4/4 1/8 #'() #'()
\time 4/4
\tempo \markup { Mechanical (\fontsize #-1 \rhythm { { 8 } }
\hspace #-0.6 = 92 )}
c'8 8 8 8 8 8 8 8
c'8 8 8 8 8 8 8 8
}
}
(Note the necessary extra braces in \rhythm { { 8 } }; this quirk has
already been solved, in the unstable version 2.25.0.)
Unfortunately, \tempo internally uses \note, which does not have the
same sort of customizability. You can use tags, though:
\version "2.24.0"
customFlag = {
\override Score.Flag.stencil = #ly:text-interface::print
\override Score.Flag.text = \markup {\raise #-0.2 \beam #1.0 #0.05 #0.5 }
}
\layout {
\context {
\Score
\customFlag
}
\context {
\StandaloneRhythmScore
\customFlag
}
}
\tagGroup midi,layout
mus =
\new Staff {
\overrideTimeSignatureSettings 4/4 1/8 #'() #'()
\time 4/4
\tag layout \tempo \markup { Mechanical (\fontsize #-1 \rhythm { { 8
} } \hspace #-0.6 = 92 )}
\tag midi \tempo 8 = 92
c'8 8 8 8 8 8 8 8
c'8 8 8 8 8 8 8 8
}
\score {
\keepWithTag layout \mus
\layout { }
}
\score {
\keepWithTag midi \mus
\midi { }
}
Best,
Jean
OpenPGP_signature
Description: OpenPGP digital signature
Re: LilyPond 2.25.1
On Sat 21 Jan 2023 at 11:38:27 (-0800), Knute Snortum wrote: > On Sat, Jan 21, 2023 at 11:33 AM Jonas Hahnfeld via LilyPond user > discussion wrote: > > > > We are happy to announce the release of LilyPond 2.25.1. This is termed > > a development release, but these are usually reliable for testing new > > features and recent bug fixes. However, if you require stability, we > > recommend using version 2.24.0, the current stable release. > > Please refer to the Installing section in the Learning Manual for > > instructions how to set up the provided binaries: > > https://lilypond.org/doc/v2.25/Documentation/learning/installing > > Am I missing something? The download page seems to still be pointing at > 2.24.0. An actual URL would help us to know what you're looking at. The download page points at the stable version. http://lilypond.org/download.html The development page points at the unstable version. http://lilypond.org/development.html Both these are available from the home page, one under the other in the top right corner. http://lilypond.org/ Cheers, David.
Re: LilyPond 2.25.1
> Le 21 janv. 2023 à 20:43, Knute Snortum a écrit : > Am I missing something? The download page seems to still be pointing at > 2.24.0. The main download page https://lilypond.org/download.html always points at the current stable release because that is what most people want. The current unstable one can be downloaded from https://lilypond.org/development.html
Re: LilyPond 2.25.1
On Sat, Jan 21, 2023 at 11:33 AM Jonas Hahnfeld via LilyPond user discussion wrote: > > We are happy to announce the release of LilyPond 2.25.1. This is termed > a development release, but these are usually reliable for testing new > features and recent bug fixes. However, if you require stability, we > recommend using version 2.24.0, the current stable release. > Please refer to the Installing section in the Learning Manual for > instructions how to set up the provided binaries: > https://lilypond.org/doc/v2.25/Documentation/learning/installing Am I missing something? The download page seems to still be pointing at 2.24.0.
LilyPond 2.25.1
We are happy to announce the release of LilyPond 2.25.1. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.0, the current stable release. Please refer to the Installing section in the Learning Manual for instructions how to set up the provided binaries: https://lilypond.org/doc/v2.25/Documentation/learning/installing signature.asc Description: This is a digitally signed message part
Override note properties in markup,note or rhythm
Hiya!
I'm trying to find a gentle solution for the problem I encountered.
I overrided flag stencil in general Score, but it turns out that this
doesn't influence notes in \tempo, \note and \rhythm functions. I there
a possibility to influence those ones?
I add that I know I could construct note from the beginning inside
markup and add hidden tempo change for proper tempo export, but it seems
to be overkill for this kind of problem.
\version "2.24.0"
\score {
\new Staff {
\overrideTimeSignatureSettings 4/4 1/8 #'() #'()
\time 4/4
\override Score.Flag.stencil = #(lambda (grob)
(grob-interpret-markup grob
#{\markup {\raise #-0.2
\beam #1.0 #0.05 #0.5 }#}))
\tempo \markup{ Mechanical (
\note {8} #1 = 92 )}
c'8 8 8 8 8 8 8 8
\tempo Mechanical 8 = 92
c'8 8 8 8 8 8 8 8
}
}
Cheers,
Tomasz
