Re: Tempo declaration on different staves
On 23-9-2018 08:41, arnepe wrote: hello Auke, (/bear with me, I'm not a programmer and may not know the correct terminology/) one reason would be that "voice" is a child of "staff": definitions in "staff" are inherited by "voice", plus the benefit of less typing... cheers Arne Hello Arne, In the rewrite Kieren gave of Bernhard's score the global variable is still included at the voice level. So, it seems that less typing is not the reason. Regards, Auke ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: fingering footnote
On Sun, 23 Sep 2018 at 02:55, Aaron Hill wrote:
> On 2018-09-22 10:17 am, Gianmaria Lari wrote:
> > I would like to create a footnote attached to a fingering. Ideally
> > something like this
> >
> > \version "2.19.82"
> > {b\finger "2*"}
> >
> >
> > [image: image.png]
> >
> > ... and then in the footnote I would like to give some indication about
> > the
> > fingering.
> >
> > I saw the footnote examples but I have not been able to attach them to
> > the
> > fingering. How can I do it?
>
> Does something like this help?
>
>
> \version "2.19.82"
> { \once \override Score.FootnoteItem.annotation-line = ##f
>\once \override Score.FootnoteItem.padding = #0
>b -\footnote \markup "*" #'(0.01 . 0)
> \markup { \super "*" "Something important..." }
> \finger 2 }
>
>
This is exactly what I need!
Thanks a lot Aaron
Ciao, g.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Tempo declaration on different staves
Hi all, > In the rewrite Kieren gave of Bernhard's score the global variable is still > included at the voice level. So, it seems that less typing is not the reason. No, less typing is not the reason. Here are three of the more important reasons I prefer late-stage combination: 1. It’s less likely there will be redundant information/data, which brings potential for clashes or performance slowdowns. 2. I’ve found code reuse to be easier, since things added earlier in the code chain don’t have to be removed. 3. The reused (e.g., \global) references are spread across a smaller section of the code — rather than separated by many code lines, or even contained in different files — making maintenance a little easier. Of course, a lot of it is simply personal preference/style, so there’s no big need to change if you don’t agree with my reasoning! I was just offering a possible improvement. Cheers, Kieren. Kieren MacMillan, composer ‣ 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: Tempo declaration on different staves
p.s. >> In the rewrite Kieren gave of Bernhard's score the global variable is still >> included at the voice level. And, yes, I would likely move the \global variable to the staff level(s) — or even score, if the type of global information warranted/allowed — though I didn’t go that far in my "cleanup" this time. Cheers, Kieren. On Sep 23, 2018, at 9:47 AM, Kieren MacMillan wrote: > > Hi all, > >> In the rewrite Kieren gave of Bernhard's score the global variable is still >> included at the voice level. So, it seems that less typing is not the reason. > > No, less typing is not the reason. > > Here are three of the more important reasons I prefer late-stage combination: > > 1. It’s less likely there will be redundant information/data, which brings > potential for clashes or performance slowdowns. > > 2. I’ve found code reuse to be easier, since things added earlier in the code > chain don’t have to be removed. > > 3. The reused (e.g., \global) references are spread across a smaller section > of the code — rather than separated by many code lines, or even contained in > different files — making maintenance a little easier. > > Of course, a lot of it is simply personal preference/style, so there’s no big > need to change if you don’t agree with my reasoning! I was just offering a > possible improvement. > > Cheers, > Kieren. Kieren MacMillan, composer ‣ 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: Lyrics placement
Hi Guy, Does your definition of ChoirStaff accept Lyrics? That’s usually the reason I see for "jumping" contexts… Hope that helps! Kieren. Kieren MacMillan, composer ‣ 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: Lyrics placement
- Original Message - From: "Kieren MacMillan" To: "Guy Stalnaker" Cc: "Lilypond-User Mailing List" Sent: Sunday, September 23, 2018 2:51 PM Subject: Re: Lyrics placement Hi Guy, Does your definition of ChoirStaff accept Lyrics? That’s usually the reason I see for "jumping" contexts… Hope that helps! Kieren. Kieren MacMillan, composer Alternatively, it might be that the temporary voice has disappeared prior to the lyrics being placed. Guy - you might try making the upper voice the temporary one and assigning the lyrics to the permanent voice. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Tempo declaration on different staves
On 18.09.2018 21:10, Kieren MacMillan wrote: Here’s one way. (Note that I also <<>>'ed the \global variable into each*staff* context in the score, rather than into each note variable definition; personally, I think that is better coding style, for many reasons.) I for my part don’t feel like I have arrived at a consistent way of doing this, which is a pain, because I reconsider it for every project, however it seems to also make sense to make less effort for small projects. However, I increasingly fancy the idea of putting everything exactly where it belongs, for example having a timing variable that contains only content which pertains – musically and LilyPondically – to the entire score (or, in polymetrics, everything which has the same timing). And maybe even splitting stuff up into per Staff and per Voice. Though, as I said, this is all in a kind of experimental stage and not quite thought through. Best, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics placement
Thank you both. I'm afraid I don't know enough about LP context to ferret out if that is the issue. I was hoping that my reading of the LP Learning Manual had the proper way to do this instantiation of temporary lyrics in the temporary polyphonic context, but nope. Phil's suggestion is what I've done. Guy Guy Stalnaker jimmyg...@gmail.com On Sun, Sep 23, 2018 at 9:08 AM Phil Holmes wrote: > - Original Message - > From: "Kieren MacMillan" > To: "Guy Stalnaker" > Cc: "Lilypond-User Mailing List" > Sent: Sunday, September 23, 2018 2:51 PM > Subject: Re: Lyrics placement > > > > Hi Guy, > > > > Does your definition of ChoirStaff accept Lyrics? > > That’s usually the reason I see for "jumping" contexts… > > > > Hope that helps! > > Kieren. > > > > > > Kieren MacMillan, composer > > > Alternatively, it might be that the temporary voice has disappeared prior > to > the lyrics being placed. Guy - you might try making the upper voice the > temporary one and assigning the lyrics to the permanent voice. > > -- > Phil Holmes > > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics placement
And THEN I find this: http://lsr.di.unimi.it/LSR/Item?id=781 LOL I've already redone the code to swap the voices, but I'll investigate this snippet to see if I can learn how it works. Guy ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Weird parentheses
\version "2.19.81"
\language "english"
#(define ((time-parenthesized-time up down upp1 downp1 upp2 downp2)
grob)
(grob-interpret-markup grob
(markup #:override '(baseline-skip . 0) #:number
(#:line (
(#:center-column (up down))
#:vcenter "("
(#:center-column (upp1 downp1))
#:lower 0.5 "+"
(#:center-column (upp2 downp2))
#:vcenter ")" )
\new Staff {
\override Staff.TimeSignature.stencil = #(time-parenthesized-time
"21" "8" "12" "8" "9" "8")
}
A few months ago, when I wrote the file of which the above is a small
part, it worked well, giving the required "21/8 (12/8 + 9/8)" time
signature.
Now, when I compile the file, I get an empty rectangle where the
parentheses used to be. Furthermore, if I substitute other characters
for the parentheses I get weird results: for instance, a lower case
letter generally gives a capital letter 3 places later in the alphabet
(e.g. "a" appears as "D").
I find though that the letter "p" appears as the dynamic "p". Perhaps
there is a clue here as to what is going on, but I can't figure it out.
Any suggestions?
David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Melisma line
What to do to make the melisma line continue just for the time the slur
continues from the end of measure 1 through measure 2. During measure 3
the singer shall be silent, but this melisma line indicates something
else. I have failed in every effort to stop the line after the slur
ends, by setting ignoreMelismata or melismaBusyProperties but no success.
Suggestions someone?
\version "2.18.2"
A = \relative g' { g2 g( g g) g g g g }
Txt = \lyricmode { Ah Ah __ \repeat unfold 2 { \skip 1 } Ah Ah }
\score {
\A
\addlyrics { \Txt }
\layout {}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Weird parentheses
On 23.09.2018 21:45, David Sumbler wrote:
Now, when I compile the file, I get an empty rectangle where the
parentheses used to be. Furthermore, if I substitute other characters
for the parentheses I get weird results: for instance, a lower case
letter generally gives a capital letter 3 places later in the alphabet
(e.g. "a" appears as "D").
Weird indeed.
I find though that the letter "p" appears as the dynamic "p". Perhaps
there is a clue here as to what is going on, but I can't figure it out.
Some of that sounds like using the number command may be the problem,
because the font doesn’t contain many normal glyphs. Try experimenting
with the normal-text markup command.
However, still more weird is that I don’t get any of those problems: the
markup itself looks OK, but there’s some white space instead of the
start of the staff symbol. This is on Ubuntu 16.04, with Lily 2.19.82.
I’d experiment in this direction with the markup:
%
\version "2.19.82"
\language "english"
#(define-markup-command (timesig-paren layout props opening?) (boolean?)
(interpret-markup layout props
(markup #:normal-text
#:override '(font-size . 6)
#:scale '(0.5 . 1)
#:vcenter
(if opening? "(" ")"
#(define ((time-parenthesized-time up down upp1 downp1 upp2 downp2)
grob)
(grob-interpret-markup grob
(markup #:override '(baseline-skip . 0) #:number
(#:line (
(#:center-column (up down))
#:timesig-paren #t
(#:center-column (upp1 downp1))
#:normal-text #:lower 0.5 "+"
(#:center-column (upp2 downp2))
#:timesig-paren #f )
\new Staff {
\override Staff.TimeSignature.stencil = #(time-parenthesized-time
"21" "8" "12" "8" "9" "8")
}
%
Output attached – I don’t know where that whitespace comes from.
Best, Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Melisma line
On 23.09.2018 22:34, 70147pers...@telia.com wrote:
Txt = \lyricmode { Ah Ah __ \repeat unfold 2 { \skip 1 } Ah Ah }
Try using "" or any invisible markup instead of the skips.
Best, Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Melisma line
>> Txt = \lyricmode { Ah Ah __ \repeat unfold 2 { \skip 1 } Ah Ah }
>>
>
> Try using "" or any invisible markup instead of the skips.
That did not work here. But this ugly hack does:
\lyricmode { Ah Ah __ \markup \with-color #white " " _ Ah Ah }
Actually, the color does not matter. But only an empty markup or a space
is not enough.
Best,
Joram
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Weird parentheses
Simon,
Perhaps an alternative is under "compound time signatures" at
http://lilypond.org/doc/v2.19/Documentation/notation/displaying-rhythms#polymetric-notation
Mark
-Original Message-
From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org]
On Behalf Of Simon Albrecht
Sent: Sunday, September 23, 2018 1:38 PM
To: da...@aeolia.co.uk; lilypond-user@gnu.org
Subject: Re: Weird parentheses
On 23.09.2018 21:45, David Sumbler wrote:
> Now, when I compile the file, I get an empty rectangle where the
> parentheses used to be. Furthermore, if I substitute other characters
> for the parentheses I get weird results: for instance, a lower case
> letter generally gives a capital letter 3 places later in the alphabet
> (e.g. "a" appears as "D").
Weird indeed.
> I find though that the letter "p" appears as the dynamic "p". Perhaps
> there is a clue here as to what is going on, but I can't figure it out.
Some of that sounds like using the number command may be the problem, because
the font doesn’t contain many normal glyphs. Try experimenting with the
normal-text markup command.
However, still more weird is that I don’t get any of those problems: the markup
itself looks OK, but there’s some white space instead of the start of the staff
symbol. This is on Ubuntu 16.04, with Lily 2.19.82.
I’d experiment in this direction with the markup:
%
\version "2.19.82"
\language "english"
#(define-markup-command (timesig-paren layout props opening?) (boolean?)
(interpret-markup layout props
(markup #:normal-text
#:override '(font-size . 6)
#:scale '(0.5 . 1)
#:vcenter
(if opening? "(" ")"
#(define ((time-parenthesized-time up down upp1 downp1 upp2 downp2)
grob)
(grob-interpret-markup grob
(markup #:override '(baseline-skip . 0) #:number
(#:line (
(#:center-column (up down))
#:timesig-paren #t
(#:center-column (upp1 downp1))
#:normal-text #:lower 0.5 "+"
(#:center-column (upp2 downp2))
#:timesig-paren #f )
\new Staff {
\override Staff.TimeSignature.stencil = #(time-parenthesized-time "21" "8"
"12" "8" "9" "8") } %
Output attached – I don’t know where that whitespace comes from.
Best, Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Melisma line
On 2018-09-23 1:43 pm, Noeck wrote:
Txt = \lyricmode { Ah Ah __ \repeat unfold 2 { \skip 1 } Ah Ah }
Try using "" or any invisible markup instead of the skips.
That did not work here. But this ugly hack does:
\lyricmode { Ah Ah __ \markup \with-color #white " " _ Ah Ah }
Actually, the color does not matter. But only an empty markup or a
space
is not enough.
My solution to this sort of thing is to make sure that only notes that
have lyrics assigned are in the voice in question when using \addlyrics
or \lyricsto. The two "extra" notes would be put into their own voice
so nothing tries to bind to them.
\version "2.18.2"
A = \relative g' { g2 g( g g) << { s2 s } \\ { \oneVoice g2 g } >> g g }
Txt = \lyricmode { Ah Ah __ Ah Ah }
\score { \A \addlyrics { \Txt } \layout {} }
-- Aaron Hill
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Weird parentheses
On 2018-09-23 1:37 pm, Simon Albrecht wrote:
Output attached – I don’t know where that whitespace comes from.
The whitespace is due to not having any notes in the staff. I've
encountered this before, so you have to remember to put at least one
note for the staff lines to connect fully.
But instead of doing markup in a Scheme funtion, there is what I think
is a better option:
\version "2.19.81"
\new Staff {
\compoundMeter #'(12 9 8)
\override Staff.TimeSignature.stencil = #ly:text-interface::print
\override Staff.TimeSignature.text = \markup {
\override #'(baseline-skip . 0)
\number
\line {
\center-column { 21 8 }
\vcenter "("
\center-column { 12 8 }
\vcenter "+"
\center-column { 9 8 }
\vcenter ")"
}
}
\repeat unfold 2 { b'2. b' b'4. b' b' | }
}
Here we build on top of ly:text-interface::print so we can just define a
text property as normal markup. There could of course be a way to query
the compound meter so that it renders both the parts and the sum, but
the above seems to be pretty clear even if it is "hard-coded" a bit.
-- Aaron Hill
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Melisma line
On Sun 23 Sep 2018 at 14:35:59 (-0700), Aaron Hill wrote:
> On 2018-09-23 1:43 pm, Noeck wrote:
> > > > Txt = \lyricmode { Ah Ah __ \repeat unfold 2 { \skip 1 } Ah Ah }
> > > >
> > >
> > > Try using "" or any invisible markup instead of the skips.
> >
> > That did not work here. But this ugly hack does:
> >
> > \lyricmode { Ah Ah __ \markup \with-color #white " " _ Ah Ah }
> >
> > Actually, the color does not matter. But only an empty markup or a
> > space
> > is not enough.
>
> My solution to this sort of thing is to make sure that only notes that
> have lyrics assigned are in the voice in question when using
> \addlyrics or \lyricsto. The two "extra" notes would be put into
> their own voice so nothing tries to bind to them.
>
>
> \version "2.18.2"
> A = \relative g' { g2 g( g g) << { s2 s } \\ { \oneVoice g2 g } >> g g }
> Txt = \lyricmode { Ah Ah __ Ah Ah }
> \score { \A \addlyrics { \Txt } \layout {} }
>
That's adds a lot of complexity. I prefer a simpler approach:
%%
\version "2.18.2"
A = \relative g' { g2 g( g g) g g g g }
n = \lyricmode { "" }
Txt = \lyricmode { Ah Ah __ \n _ Ah Ah }
\score { \A \addlyrics { \Txt } \layout {} }
nbsp = \markup \char ##x00A0 % safer alternative than the literal char (which
does work)
n = \lyricmode { \nbsp }
Txt = \lyricmode { Ah Ah __ \n _ Ah Ah }
\score { \A \addlyrics { \Txt } \layout {} }
%%
The first method can emit warning messages so I use the second,
defined in a library \include.
You only need one melisma stopper, and I then use _ for subsequent notes as
… a melisma __ \n
\repeat unfold 83 _
Next lyric …
is so tidy, and easily edited.
Cheers,
David.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
