Re: Chapter 2.1 Vocal music of LPNR
Here is an MWE showing my problem.
What I don’t understand is why and extra ‘_2’ is needed in lyricsManual to
obtain the same alignment as in the two automatic cases.
The snippet comes from Rameau’s Les Indes Galantes.
Thanks for your help!
JM
%%%
\version "2.19.83"
music = \relative c'' {
fis2 fis4 fis8 gis | % 40
ais!8 [ gis fis gis ] ais [ b cis d ] ( | % 41
e2 ) e4 d8 cis | % 42
d2 b8 cis d e | % 43
\break | % 44
}
lyricsManual = \lyricmode {
"mats!"2
"Et"4 "tu"8 "ré"8 -- "pands"8 __ _ _ _ _ _ _ _ _2 HERE
"dans"4 "nos"8 "cli" -- "mats"2
"Ta"8 "plus"8 "é" -- "cla"8
}
lyricsAutomatic = \lyricmode {
"mats!"2
"Et"4 "tu"8 "ré"8 -- "pands"8 __ _ _ _ _ _ _ _ HERE
"dans"4 "nos"8 "cli" -- "mats"2
"Ta"8 "plus"8 "é" -- "cla"8
}
lyricsAutomaticSimpler = \lyricmode {
mats!
Et tu ré -- pands __ _ _ _ _ _ _ _ HERE
dans nos cli -- mats
Ta plus é -- cla
}
<<
\new Staff = "Part_PFour_Staff_One"
<<
\context Voice = "Part_PFour_Staff_One_Voice_One" <<
\music
>>
\new Lyrics
\with {
associatedVoice = "Part_PFour_Staff_One_Voice_One"
}
\lyricsManual
>>
>>
<<
\new Staff = "Part_PFour_Staff_One"
<<
\context Voice = "Part_PFour_Staff_One_Voice_One" <<
\music
>>
\new Lyrics {
\lyricsto "Part_PFour_Staff_One_Voice_One" {
\lyricsAutomatic
}
}
>>
>>
<<
\new Staff = "Part_PFour_Staff_One"
<<
\context Voice = "Part_PFour_Staff_One_Voice_One" <<
\music
>>
\new Lyrics {
\lyricsto "Part_PFour_Staff_One_Voice_One" {
\lyricsAutomaticSimpler
}
}
>>
>>
%%%
> Le 26 août 2019 à 20:36, Simon Albrecht a écrit :
>
> Hi Jacques,
>
> this doesn’t exactly answer your question, but I’ve always found that manual
> alignment of lyrics is a huge pain to get working and thus never use it…
>
> Best, Simon
>
> On 26.08.19 17:39, Jacques Menu wrote:
>> Hello folks,
>>
>> The more I read this chapter, and the more I feel it is a kind of imbroglio,
>> mixing automatic and manual alignment of lyrics to the voice.
>>
>> Do you also feel this would merit a rewrite?
>>
>> JM
>>
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Melisma breaking converting from 2.18 to 2.19
Hi Vaughan, On 27.08.19 04:40, Vaughan McAlley wrote: Hi, I’m trying to convert a large choral project to 2.19. When I compile with 2.19, melismas don't work at all. For example: c'4 \melisma d' e' \melismaEnd f puts a note on every syllable. I made a MWE which works perfectly. Diffs between the old and new files have no changes except for the \version line and removing parser and location in music functions. No file sets melismaBusyProperties. Does this ring a bell with anyone? Unfortunately not—that sounds like a really annoying problem, and I’m afraid the only way might be progressively reducing the score to a minimal example and checking at which point the problem goes away… How do you align the lyrics to the notes? \lyricsto? Best, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Melisma breaking converting from 2.18 to 2.19
Am 27.08.19 um 04:40 schrieb Vaughan McAlley:
I’m trying to convert a large choral project to 2.19. When I compile
with 2.19, melismas don't work at all. For example:
c'4 \melisma d' e' \melismaEnd f
puts a note on every syllable.
[…]
Does this ring a bell with anyone?
Yes, it does. The following two scores look the same in 2.18.2 and
different in 2.19.83:
%%
\version "2.18.2"
%\version "2.19.83"
global = {
s1
\bar "|."
}
sop = \relative {
c'4( d) e f
}
soptext = \lyricmode {
Me -- lis -- ma
}
\new Staff << \global \sop >> \addlyrics \soptext
\new Staff << \global \sop \addlyrics \soptext >>
%%
Is this a bug/regression?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Melisma breaking converting from 2.18 to 2.19
Am 27.08.19 um 10:56 schrieb Malte Meyn: Yes, it does. The following two scores look the same in 2.18.2 and different in 2.19.83: This changed somewhere between 2.19.13 and 2.19.14. Without testing it looks like commit df3457d8 “Allow \addlyrics to work with arbitrary contexts” could be the reason. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Chapter 2.1 Vocal music of LPNR
On 2019-08-27 1:12 am, Jacques Menu wrote: Here is an MWE showing my problem. What I don’t understand is why and extra ‘_2’ is needed in lyricsManual to obtain the same alignment as in the two automatic cases. [ . . . ] It appears that you are trying to use both automatic and manual syllable durations at the same time. If I were the doc writer, I would want to know how you got down this path. I could not find an example in the NR that uses both techniques at the same time. Ultimately, you should either just specify the durations by hand or not at all relying on \addlyrics or \lyricsto. As far as I can tell, the reason for the behavior you are seeing is that \set associatedVoice in the \with block is having no effect. You are actually relying solely on manual durations for that test case. And you need to specify the duration of that final "_" syllable to match the timing of the notes, since the preceding, and thusly inherited, duration is an eighth note. For the second test case, your use of \lyricsto is properly overriding any durations you specify based on the notes in the context named. The fact that "_" is input as an implicit eighth does not matter then. To circle back to the docs, where did you see \set associatedVoice used within a \with block? Near as I can tell, it is only used to *change* the context for timing when used within an \addlyrics or \lyricsto block. It does not appear to be intended for use alone. -- Aaron Hill ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Melisma breaking converting from 2.18 to 2.19
Hey all,
This bit me way back when. Here’s the fix (note the \new Voice):
\version "2.19.83"
global = {
s1
\bar "|."
}
sop = \relative {
c'4( d) e f
}
soptext = \lyricmode {
Me -- lis -- ma
}
\new Staff \new Voice << \global \sop >> \addlyrics \soptext
\new Staff \new Voice << \global \sop \addlyrics \soptext >>
Hope that helps!
Kieren.
Kieren MacMillan, composer (he/him)
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Melisma breaking converting from 2.18 to 2.19
Hi David, > I'm not sure that it does. Did you compile my example? The melisma shows correctly in both staves, where it doesn’t in the original MWE. Isn’t that what needed fixing? Confused, Kieren. Kieren MacMillan, composer (he/him) ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Melisma breaking converting from 2.18 to 2.19
On Tue 27 Aug 2019 at 08:32:30 (-0400), Kieren MacMillan wrote:
> Hey all,
>
> This bit me way back when. Here’s the fix (note the \new Voice):
>
> \version "2.19.83"
>
> global = {
> s1
> \bar "|."
> }
>
> sop = \relative {
> c'4( d) e f
> }
>
> soptext = \lyricmode {
> Me -- lis -- ma
> }
>
> \new Staff \new Voice << \global \sop >> \addlyrics \soptext
>
> \new Staff \new Voice << \global \sop \addlyrics \soptext >>
>
> Hope that helps!
I'm not sure that it does. It looks to me as if both your \addlyrics
are adding the lyrics to a Voice, whereas Malte's example (and thanks
for the MWE!) looks as if \addlyrics applies to the Staff.
I played around with the latter when I read here that it could be
done. It seems as if it might be an alternative to NullVoice,
where you have to make an alignment voice by breaking up long notes
in one part so you can match the rhythm in another. With this
Staff method, you don't have to touch the music, but you have to
write a lyric syllable to match every note-start in every part,
and that holds for melismas too, else it would defeat the whole
object of the new construction.
I think the last bar of this MWE gives you the idea. Sorry I
haven't got a melismatic example handy, but I see the feature
as more useful for hymns (pace Bruckner) because all the best
ones are full of these rhythmic differences. I set counterpoint
on separate staves, like most people.
AIUI all 2.18.2 did iin Malte's MWE is to \addlyrics to the
last Voice it saw, not to the Staff, because the feature
didn't exist.
Cheers,
David.
\version "2.18.2"
\language english
ll = \lyricmode { \once \override LyricText.self-alignment-X = #LEFT }
%%\include "Choral-bits.lily"
\paper {
#(set-paper-size "a6")
}
global = {
\key c \major
\time 4/4
s1 * 12
}
soprano = \relative {
c''2. b4
a2 g4 r4
r4 g4 a4 e4
g4. g8 f4 r4
\barNumberCheck #5 | % soprano
d'2. c4
c2 b4 r4
r4 d4 e4 g4
f4. f8 e4 r4
r4 f4 f4 e4
\barNumberCheck #10 | % soprano
r4 f,2 e4
d2. c4
b4
}
alto = \relative {
e'2. e4
e2 e4 r4
r4 e4 e4 e4
d4. d8 d4 r4
\barNumberCheck #5 | % alto
fs2. fs4
fs2 g4 r4
r4 g4 g4 g4
g4. g8 g4 r4
r4 g4 g4 g4
\barNumberCheck #10 | % alto
r4 d2 c4
b2 g2
g4
}
sopranotext = \lyricmode {
Lo -- cus i -- ste a De -- o fac -- tus est,
lo -- cus i -- ste a De -- o fac -- tus est,
a De -- o,
De -- o fac -- tus est,
}
altotext = \lyricmode {
Lo -- cus i -- ste a De -- o fac -- tus est,
lo -- cus i -- ste a De -- o fac -- tus est,
a De -- o,
De -- o fac -- tus est,
}
stafftext = \lyricmode {
Lo -- cus i -- ste a De -- o fac -- tus est,
lo -- cus i -- ste a De -- o fac -- tus est,
a De -- o,
De -- o fac -- \ll tus _ est,
}
\score {
\new Staff <<
\clef treble \global
\new Voice { \voiceOne \soprano }
\addlyrics { \sopranotext }
\new Voice { \voiceTwo \alto }
\addlyrics { \altotext }
>>
\addlyrics { \stafftext }
\layout { }
}
mel.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Chapter 2.1 Vocal music of LPNR
On Tue 27 Aug 2019 at 10:12:01 (+0200), Jacques Menu wrote:
> Here is an MWE showing my problem.
>
> What I don’t understand is why and extra ‘_2’ is needed in lyricsManual to
> obtain the same alignment as in the two automatic cases.
> The snippet comes from Rameau’s Les Indes Galantes.
>
> %%%
>
> \version "2.19.83"
>
>
> music = \relative c'' {
> fis2 fis4 fis8 gis | % 40
> ais!8 [ gis fis gis ] ais [ b cis d ] ( | % 41
> e2 ) e4 d8 cis | % 42
> d2 b8 cis d e | % 43
> \break | % 44
> }
>
> lyricsManual = \lyricmode {
> "mats!"2
>
> "Et"4 "tu"8 "ré"8 -- "pands"8 __ _ _ _ _ _ _ _ _2 HERE
In manual mode, you've supplied durations to the lyrics, and they're
being used. The 2 has the same function as the 4 on the next line:
it changes the implied duration of the next lyric if it doesn't have
an explicit duration attached. Without the 2, the final _ would
have a duration like the others, 8.
> "dans"4 "nos"8 "cli" -- "mats"2
> "Ta"8 "plus"8 "é" -- "cla"8
> }
>
> lyricsAutomatic = \lyricmode {
> "mats!"2
>
> "Et"4 "tu"8 "ré"8 -- "pands"8 __ _ _ _ _ _ _ _ HERE
With \lyricsto, these automatic lyrics don't need durations,
and so they're ignored. You've removed just the solitary 2.
Try removing all the 4s and 8s. They're all ignored.
> "dans"4 "nos"8 "cli" -- "mats"2
> "Ta"8 "plus"8 "é" -- "cla"8
> }
>
> lyricsAutomaticSimpler = \lyricmode {
> mats!
>
> Et tu ré -- pands __ _ _ _ _ _ _ _ HERE
> dans nos cli -- mats
> Ta plus é -- cla
> }
>
> <<
> \new Staff = "Part_PFour_Staff_One"
> <<
> \context Voice = "Part_PFour_Staff_One_Voice_One" <<
> \music
> >>
>
> \new Lyrics
> \with {
> associatedVoice = "Part_PFour_Staff_One_Voice_One"
> }
> \lyricsManual
> >>
> >>
>
> <<
> \new Staff = "Part_PFour_Staff_One"
> <<
> \context Voice = "Part_PFour_Staff_One_Voice_One" <<
> \music
> >>
>
> \new Lyrics {
> \lyricsto "Part_PFour_Staff_One_Voice_One" {
> \lyricsAutomatic
> }
> }
> >>
> >>
>
> <<
> \new Staff = "Part_PFour_Staff_One"
> <<
> \context Voice = "Part_PFour_Staff_One_Voice_One" <<
> \music
> >>
>
> \new Lyrics {
> \lyricsto "Part_PFour_Staff_One_Voice_One" {
> \lyricsAutomaticSimpler
> }
> }
> >>
> >>
>
> %%%
> > On 26.08.19 17:39, Jacques Menu wrote:
> >> Hello folks,
> >>
> >> The more I read this chapter, and the more I feel it is a kind of
> >> imbroglio, mixing automatic and manual alignment of lyrics to the voice.
> >>
> >> Do you also feel this would merit a rewrite?
Cheers,
David.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Melisma breaking converting from 2.18 to 2.19
On Tue 27 Aug 2019 at 11:16:00 (-0400), Kieren MacMillan wrote: > Hi David, > > > I'm not sure that it does. > > Did you compile my example? > The melisma shows correctly in both staves, where it doesn’t in the original > MWE. > Isn’t that what needed fixing? > > Confused, Yes, but I'm not sure I needed to. Just to make it clear—my reply was aimed at Malte's MWE and not at the OP who hasn't yet shown us what their problem is. Malte has: \new Staff << \global \sop >> \addlyrics \soptext reducing to: \new Staff << >> \addlyrics \soptext ie \addlyrics applied to a Staff. You have: \new Staff \new Voice << \global \sop >> \addlyrics \soptext \new Staff \new Voice << \global \sop \addlyrics \soptext >> reducing to: \new Voice << >> \addlyrics \soptext ie \addlyrics applied to a Voice. \new Voice << \global \sop \addlyrics \soptext >> ie \addlyrics applied to a Voice. As far as 2.18.2 is concerned, it doesn't know how to apply \lyrics to a Staff, so it just uses the last seen Voice as the context instead. I would hazard a guess that the OP could have been relying on this, and now it's suddenly broken because LP does what it's told. Disclaimer: I'm working from observations. I don't know how LP looks at the guts of Contexts, like some people here evidently do. Cheers, David. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Melisma breaking converting from 2.18 to 2.19
Hi David, > Just to make it clear—my reply was aimed at Malte's MWE > and not at the OP who hasn't yet shown us what their problem is. Ah, okay. =) I was just noting (for the OP) that a whole bunch of my scores with lyrics "stopped working" early in the 2.19s, and adding \new Voice before the << >> solved every single one of the issues. Thanks, Kieren. Kieren MacMillan, composer (he/him) ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Chapter 2.1 Vocal music of LPNR
On Mon 26 Aug 2019 at 20:36:53 (+0200), Simon Albrecht wrote:
> Hi Jacques,
>
> this doesn’t exactly answer your question, but I’ve always found that
> manual alignment of lyrics is a huge pain to get working and thus
> never use it…
The only piece I've used them in was as an exercise in writing code
that would generate a correctly notated score containing repeats, but
would also generate correctly repeating MIDI output from the same code
merely by adding \unfoldRepeats. I started a thread about the problem:
https://lists.gnu.org/archive/html/lilypond-user/2015-09/msg00499.html
but I don't remember how the thread evolved, if at all.
Suffice it to say, I don't make a habit of this, preferring to set the
score and the MIDI separately. Attached is the code I came up with.
To compile it properly, you'd need some library files. "Midi-satb.lily"
is the boilerplate code to produce MIDI "teach tapes" for each part.
The attached score used the unmangled source, with \unfoldRepeats
commented out, and the libraries included of course.
> On 26.08.19 17:39, Jacques Menu wrote:
> > Hello folks,
> >
> > The more I read this chapter, and the more I feel it is a kind of
> > imbroglio, mixing automatic and manual alignment of lyrics to the voice.
> >
> > Do you also feel this would merit a rewrite?
(I'd have to read it in its new incarnation.)
Cheers,
David.
\version "2.18.2"
\language english
%%\include "Choral-bits.lily"
accident = { \accidentalStyle choral-cautionary } % put in voices in Staff
%%\include "Beam-crochets.lily"
%%\include "Number-2-bars.lily"
%%\include "Midi-bits.lily"
%%\include "Letter.lily"
%%\include "Margins-10-15.lily"
heading = "2015-10-02"
\header {
title = \markup { "Fair Phyllis I saw" }
subtitle = \markup { " " \vspace #5 }
composer = \markup { "John Farmer" \italic "(1565–1605)" }
tagline = \markup {
\vspace #2
\smaller
\fill-line {
\heading
"Manhattan, KS"
\concat { "LilyPond version " $(lilypond-version) }
}
}
}
miditempo = { \tempo 2=72 }
%% 15: 2pp rpt, 19: 3pp rpt
%% #(set-global-staff-size 15) pgbrk = { \pageBreak }
#(set-global-staff-size 19) pgbrk = { }
global = {
\key f \major
\time 2/2
s1
\repeat volta 2 {
s1
s1
s1
\barNumberCheck #5 | % global
s1
s1
}
\alternative {
{ s1 }
{ s1 }
}
s1
\barNumberCheck #10 | % global
s1
s1
s1
s1
s1
\barNumberCheck #15 | % global
s1
s1
s1
s1
\pgbrk
\repeat volta 2 {
s1
\barNumberCheck #20 | % global
s1
s1
s1
s1
s1
\barNumberCheck #25 | % global
s1
s1
s1
s1
s1
\barNumberCheck #30 | % global
s1
s1
s1
\time 3/4
s2.
s2.
\barNumberCheck #35 | % global
\time 2/2
s1
\time 3/4
s2.
s2.
s2.
s2.
\barNumberCheck #40 | % global
s2.
s2.
\time 2/2
}
\alternative {
{ s1 }
{ s1 }
}
\bar "|."
}
soprano = \relative {
f'1
\repeat volta 2 {
a4. bf8 c4 c4
bf4 a g f
c'2 c4. c8
\barNumberCheck #5 | % soprano
c4 d2 c4
bf4 a g g
}
\alternative {
{ a2 r4 f }
{ a2 r4 f }
}
c'4. c8 a4 a8 c
\barNumberCheck #10 | % soprano
bf4 a g8 f g g
a2 r2
R1
f4 a8 bf c4 c~
c8 g c4 c2 % variant: g is a in some versions
\barNumberCheck #15 | % soprano
a4 a c a8 d
c4 a r2
r4 c c b
c1
\repeat volta 2 {
r2 r4 d8 c
\barNumberCheck #20 | % soprano
bf4. a8 g4 f
r4 d'8 c bf4. a8
g4 f r2
r4 c'2 g4
e4. f8 g4 g
\barNumberCheck #25 | % soprano
r4 c8 c g4 a
e4 f g8 bf a4
g4 f2 ( e4 )
f2 r
r4 a a b
\barNumberCheck #30 | % soprano
c4 g a2
g2 f
e1
R2.
R2.
\barNumberCheck #35 | % soprano
r2 c'
d2 c4
bf4 g2
a4. bf8 c4
c4. bf8 a4
\barNumberCheck #40 | % soprano
g2 f4
f4 e2
}
\alternative {
{ f4 f r2 }
{ f2 f }
}
}
alto = \relative {
R1
\repeat volta 2 {
R1
R1
r2 f'4. f8
\barNumberCheck #5 | % alto
f4 f2 f4
f8 f f2 e4
}
\alternative {
{ f1 }
{ f1 }
}
r4 c f4. f8
\barNumberCheck #10 | % alto
d4 f e8 d e e
f2 r
r2 r4 f
a8 bf c4 a f~
f4 e f2
\barNumberCheck #15 | % alto
f4 f a f8 bf
a4 f r2
r4 f g4. f8
e2 r
\repeat volta 2 {
r4 f8 e d2
\barNumberCheck #20 | % alto
r4 d'8 c bf4. a8
g4 f r d'8 c
bf4. a8 g4 ( f )
e2 r4 c'~
c4 g e4. f8
\barNumberCheck #25 | % alto
g4 g r c8 c
g4 a e ( f )
e4 c c2
c2 r
r4 f f d
\barNumberCheck #30 | % alto
c4 c r d~
d8 c c2 ( b4 )
c2 g'
a2 g4
f4 d2
\barNumberCheck #35 | % alto
e4 e g2
g4 f2
g4 e2
f4. g8 a4
a4. g8 f4
\barNumberCheck #40 | % alto
e2 c4
d4 c2
}
\alternative {
{ c2 c }
{ c2 c }
}
}
tenor = \relative {
R1
\repeat volta 2 {
R1
R1
r2 a4. a8
\barNumberCheck #5 | % tenor
a4 bf2 c4
d8 d c2 c4
}
\al
Cue tremolo
Hello everybody,
beams on cue notes are thinner and closer to each other than on regular
notes. The same is, however, not the case for tremolo beams.
Since one has to add them manually to quotedCueEventTypes, am I even
right in including them in the cue? I feel like they should be there,
since they change the rhythmic gesture so much.
If yes, they should be adapted like regular beams are, shouldn’t they?
If yes, by how much?
Best, Simon
%%
\version "2.19.83"
\layout {
\context {
\Score
quotedCueEventTypes = #'(note-event
rest-event
tie-event
beam-event
tuplet-span-event
tremolo-event
articulation-event)
}
}
t = { c'4:32 c'32 d' c'8. }
\addQuote test \t
\new Voice {
\cueDuring test #-1 r2
\voiceTwo \t
}
%%
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Melisma breaking converting from 2.18 to 2.19
On Wed, 28 Aug 2019, 02:22 Kieren MacMillan wrote: > Hi David, > > > Just to make it clear—my reply was aimed at Malte's MWE > > and not at the OP who hasn't yet shown us what their problem is. > > Ah, okay. =) > > I was just noting (for the OP) that a whole bunch of my scores with lyrics > "stopped working" early in the 2.19s, and adding \new Voice before the << > >> solved every single one of the issues. > > Thanks, > Kieren. > > > Kieren MacMillan, composer (he/him) > ‣ website: www.kierenmacmillan.info > ‣ email: i...@kierenmacmillan.info > > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user Thanks Kieran! After I sent the original message I was halfway into stripping my score to something more minimal, but life got in the way. I'm fussy about lyrics and have a lot of stuff in the \layout \Lyrics section I thought might have something to do with it. But Kieran’s memory came up with the goods. I do normally use \addlyrics because as someone else mentioned, life is too short to put vocal polyphony on to one line. It's a bit strange that the 2.19 \addlyrics sees the implied voice enough to put the lyrics on but not enough to respect melismas. \addlyrics has a small section in the 2.19 manual and seems to imply \new Voice is unnecessary: http://lilypond.org/doc/v2.19/Documentation/notation/common-notation-for-vocal-music#automatic-syllable-durations Vaughan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cue tremolo
> beams on cue notes are thinner and closer to each other than on > regular notes. The same is, however, not the case for tremolo beams. > [...] This is issue #5506; see commit 9c0e1363accceec8a686c868a6a5e5340317c331 Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Melisma breaking converting from 2.18 to 2.19
On Tue 27 Aug 2019 at 12:21:39 (-0400), Kieren MacMillan wrote:
> Hi David,
>
> > Just to make it clear—my reply was aimed at Malte's MWE
> > and not at the OP who hasn't yet shown us what their problem is.
>
> Ah, okay. =)
>
> I was just noting (for the OP) that a whole bunch of my scores with lyrics
> "stopped working" early in the 2.19s, and adding \new Voice before the << >>
> solved every single one of the issues.
Ah, I see what you're saying now. In which case, my guess (again, from
observations and not from any knowledge of the inner workings of LP)
is that you relied upon LP instantiating a Voice context outside the
<< >>, whereas it chose inside (attached).
Why did its behaviour change? I would assume it's because if it chose
outside, then it would snooker its new-found ability to set lyrics to
multiple voices at the same time (my Bruckner snippet).
So I don't think it's a bug or a regression, but a side effect of a
new feature, documented at the first bullet point on page 11 of
2.19.83 changes. I suppose it's a case of "Beware all ye that rely
on implied instantiations!"
Cheers,
David.
global = {
s1
\bar "|."
}
sop = \relative {
c'4( d) e f
}
soptext = \lyricmode {
Me -- lis -- ma
}
\new Staff << \new Voice \global \new Voice \sop >> \addlyrics \soptext
\new Staff << \new Voice \global \new Voice \sop \addlyrics \soptext >>
possible.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cue tremolo
On 28.08.19 06:03, Werner LEMBERG wrote: beams on cue notes are thinner and closer to each other than on regular notes. The same is, however, not the case for tremolo beams. [...] This is issue #5506; see commit 9c0e1363accceec8a686c868a6a5e5340317c331 Oh good, thanks for taking care of it! Best, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
