f-4 g-2 a\3 b-4 c'\5}
and this is the result:
This is ok, but because it is only the fingering that change it is better
to separate music from fingering. I do it with "addFingering" snippet here:
http://lsr.di.unimi.it/LSR/Item?id=768
Using this snippet the previous code can b
David Wright wrote:
> But your response here addresses a second point, the
> interpretation of \repeat unfold. Looking at my attached
> example, it seems to me that you want "\repeat unfold 2 { foo }"
> to behave like "foo foo" (B and C).
Yes, that's exact!
> But, if that's what you want,
> wh
whole-note-rests.
Cheers,
David.
\include "addFingering.ly"
fragment = {c' d' e' f'}
%%\markup "Plain" {\fragment}
%%\markup "Inversion" {\inversion c' c' \fragment}
%%\markup "Transpose"{\transpose c c, \fragment}
%%\mark
uot;I(T())"{ \inversion c' c' {\transpose c c, \fragment }}
\markup "repeat" {\repeat unfold 2 \fragment}
\markup "addFingering" {\addFingering \fragment #"12"}
\markup "R(F())" {\repeat unfold 2 {\addFingering \fragment #
On Sat 14 Jan 2017 at 11:47:49 (+0100), Gianmaria Lari wrote:
> > \repeat unfold is not evaluated at all. It stays a repeat expression
> > until it gets interpreted. One reason it is implemented that way is in
> > order to keep the repeats in
> >
> > \relative c' { \repeat unfold 4 { c e g } }
>
Gianmaria Lari writes:
>> \repeat { }
>>
>> generates a repeat expression. Whether that is "unfold" or not.
>> And relativity works "linearly" across the expression even when
>> alternatives are involved where having to write \relative each time
>> would be a royal pita.
>> --
>> David
> \repeat { }
>
> generates a repeat expression. Whether that is "unfold" or not.
> And relativity works "linearly" across the expression even when
> alternatives are involved where having to write \relative each time
> would be a royal pita.
> --
> David Kastrup
Yes that's clear.
But
Gianmaria Lari writes:
>> \repeat unfold is not evaluated at all. It stays a repeat expression
>> until it gets interpreted. One reason it is implemented that way is in
>> order to keep the repeats in
>>
>> \relative c' { \repeat unfold 4 { c e g } }
>>
>> in the same octave rather than get
>>
> \repeat unfold is not evaluated at all. It stays a repeat expression
> until it gets interpreted. One reason it is implemented that way is in
> order to keep the repeats in
>
> \relative c' { \repeat unfold 4 { c e g } }
>
> in the same octave rather than get
>
> \relative c' { c e g c e g c e
Thank you David Kastrup and Nalesnik and Gilles for you answer your help
and your explication!
I don't like the idea to use a custom repeat instead of the standard. But I
will make some test and see.
Thank you again!
___
lilypond-user mailing list
lilyp
On Fri, Jan 13, 2017 at 7:21 PM, David Nalesnik
wrote:
> On Fri, Jan 13, 2017 at 11:50 AM, Gilles THIBAULT
> wrote:
>> Le vendredi 13 janvier 2017, 14:06:23 Gianmaria Lari a écrit :
>>> I have a problem with (the fantastic) addFingering snippet.
>>>
On Fri, Jan 13, 2017 at 11:50 AM, Gilles THIBAULT
wrote:
> Le vendredi 13 janvier 2017, 14:06:23 Gianmaria Lari a écrit :
>> I have a problem with (the fantastic) addFingering snippet.
>>
>> Here it is my simple code.
>>
>> \version "
Le vendredi 13 janvier 2017, 14:06:23 Gianmaria Lari a écrit :
> I have a problem with (the fantastic) addFingering snippet.
>
> Here it is my simple code.
>
> \version "2.19.54"
> \include "addFingering.ly"
>
> {
> \addFingering {a b a b} #&qu
Gianmaria Lari writes:
> I probably figured out the reason of this behavior. The function
> "addFingering" is evaluated before evaluating the repeat. So lilypond
> evaluate this
>
> \addFingering {\repeat unfold 2 {a b}} #"12"
>
>
> as
>
I probably figured out the reason of this behavior. The function
"addFingering" is evaluated before evaluating the repeat. So lilypond
evaluate this
\addFingering {\repeat unfold 2 {a b}} #"12"
as
\repeat unfold 2 {a-1 b-2}
instead of
\addFingering {a b a b} #&
I have a problem with (the fantastic) addFingering snippet.
Here it is my simple code.
\version "2.19.54"
\include "addFingering.ly"
{
\addFingering {a b a b} #"12"
}
{
\addFingering {\repeat unfold 2 {a b}} #"12"
}
I expected that the two genera
On 2012-08-02 17:33, and...@andis59.se wrote:
On 2012-08-02 17:18, Thomas Morley wrote:
2012/8/2 and...@andis59.se :
I'm using the scheme function \addFingering to add string numbers to
a music
part.
You could call the function below in \melody
(I named it \xy. You may want to change
I can't get this to work!
Where should I put the overrides?
// Anders
Ok, I figured it out!
The problem was that I'm using \addFingering but your override uses
StringNumber.
When I changed it to
\override Fingering #'font-name = "Garamond"
\override Fingering #'
On 2012-08-02 17:08, -Eluze wrote:
I think you have to use another font,
e.g.
\override StringNumber #'font-name = "Garamond bold"
and override the size to your needs: \override StringNumber #'font-size =
#-1
hth
Eluze
I can't get this to work!
Where should I put the overrides?
// A
On 2012-08-02 17:18, Thomas Morley wrote:
2012/8/2 and...@andis59.se :
I'm using the scheme function \addFingering to add string numbers to a music
part.
You could call the function below in \melody
(I named it \xy. You may want to change this uninspired term.) :)
xy =
\override StringN
2012/8/2 and...@andis59.se :
> I'm using the scheme function \addFingering to add string numbers to a music
> part.
> Since my music is supposed to be played on a Pedal Steel Guitar I need some
> special string numbers.
>
> On the Pedal Steel Guitar there are 10 string (m
and...@andis59.se wrote:
>
> I'm using the scheme function \addFingering to add string numbers to a
> music part.
> Since my music is supposed to be played on a Pedal Steel Guitar I need
> some special string numbers.
>
> On the Pedal Steel Guitar there are 10 s
22 matches
Mail list logo
