> padding (for TupletNumber) only comes into effect for Y-offset when
> considering kneed beams:
>
>
> \version "2.19.82"
> {
> \tuplet 5/2 { b8[ b'' b b'' b] }
> \once \override TupletNumber.padding = #1
> \tuplet 5/2 { b8[ b'' b b'' b] }
> }
>
>
> Otherwise, the computation is
I am combining work I did before with another person's template and the
result is below\version "2.18.2"
\paper {
left-margin = 15
top-system-spacing #'basic-distance = #10
score-system-spacing #'basic-distance = #10
system-system-spacing #'basic-distance = #10
last-bottom-spacing
>>> Amazing, thanks! Alas, the effort to get the desired effect is
>>> tremendously large.
>>
>> Yep. There's no direct relationship between a Clef of a _Voice_
>> and a specific NoteColumn of the same Voice. So it's difficult to
>> find a way from one to the other, not sure if the method I
I think you want
\override MultiMeasureRest #'expand-limit = #7 (or whatever value you
decide - the default is 10).
Brett
On 2/4/19 8:09 am, Guy Stalnaker wrote:
\version "2.19"
\language "english"
\score {
\new Staff {
\clef bass
\compressFullBarRests
\key bf \major
\time
On 2019-04-01 5:15 pm, Colin Campbell wrote:
On 2019-04-01 5:28 p.m., Gianmaria Lari wrote:
Attached to this email a screenshot of the result of this code
\version "2.21.0"
\fixed c'' {
\override Glissando.style = #'zigzag
c \glissando \hideNotes c, \unHideNotes d e f
}
Try
\version "2.21.0"
\fixed c'' {
\override Glissando.style = #'zigzag
c4*1/2 \glissando \hideNotes c,4*1/2 \unHideNotes d4 e f
}
Toine Schreurs
___
lilypond-user mailing list
lilypond-user@gnu.org
On 2019-04-01 5:28 p.m., Gianmaria Lari wrote:
Attached to this email a screenshot of the result of this code
\version "2.21.0"
\fixed c'' {
\override Glissando.style = #'zigzag
c \glissando \hideNotes c, \unHideNotes d e f
}
I think that \bendAfter #-4 (replacing
Attached to this email a screenshot of the result of this code
\version "2.21.0"
\fixed c'' {
\override Glissando.style = #'zigzag
c \glissando \hideNotes c, \unHideNotes d e f
}
I would like that c is the first quarter, d the second quarter, e the third
quarter and so on but because of the
Thomas Morley writes:
> Am Mo., 1. Apr. 2019 um 23:14 Uhr schrieb Werner LEMBERG :
>>
>>
>> > Below my current approach for adjusting the additional clef at
>> > line-begin.
>>
>> Amazing, thanks! Alas, the effort to get the desired effect is
>> tremendously large.
>
> Yep.
> There's no direct
Aaron Hill writes:
> On 2019-04-01 2:01 pm, Gianmaria Lari wrote:
>> The following function has been written by David Kastrup few years
>> ago but
>> it does not compile on lilypond 2.21
>>
>> \version "2.21.0"
>>
>> newFinger =
>> #(define-event-function (arg) (number-or-markup?)
>> #{
On 2019-04-01 2:39 pm, Valentin Villenave wrote:
On 4/1/19, Valentin Villenave wrote:
You just need to first define the number-or-markup? function, which
isn’t included in Scheme or in LilyPond out-of-the-box
… Actually, you’d better use integer-or-markup? which _is_ provided,
and which
On 2019-04-01 1:16 pm, Werner LEMBERG wrote:
Folks,
if I use `\magnifyStaff', the tuplet number is too far away from the
beam. How can I move it nearer to the beam? Looking into
`tuplet-number.cc' I see a `padding' property with a default value of
0.5 (and which is apparently completely
On 4/1/19, Valentin Villenave wrote:
> You just need to first define the number-or-markup? function, which
> isn’t included in Scheme or in LilyPond out-of-the-box
… Actually, you’d better use integer-or-markup? which _is_ provided,
and which would be more appropriate for fingerings anyway.
Am Mo., 1. Apr. 2019 um 23:10 Uhr schrieb Gianmaria Lari
:
>
> The following function has been written by David Kastrup few years ago but it
> does not compile on lilypond 2.21
>
> \version "2.21.0"
>
> newFinger =
> #(define-event-function (arg) (number-or-markup?)
> #{ -\markup \underline
Gianmaria Lari writes:
> The following function has been written by David Kastrup few years ago but
> it does not compile on lilypond 2.21
>
> \version "2.21.0"
>
> newFinger =
> #(define-event-function (arg) (number-or-markup?)
> #{ -\markup \underline \finger
> #(if (number? arg)
> Below my current approach for adjusting the additional clef at
> line-begin.
Amazing, thanks! Alas, the effort to get the desired effect is
tremendously large. I would have never been able to achieve that...
Werner
___
lilypond-user mailing
Am Mo., 1. Apr. 2019 um 23:14 Uhr schrieb Werner LEMBERG :
>
>
> > Below my current approach for adjusting the additional clef at
> > line-begin.
>
> Amazing, thanks! Alas, the effort to get the desired effect is
> tremendously large.
Yep.
There's no direct relationship between a Clef of a
On 4/1/19, Gianmaria Lari wrote:
> How can I fix it?
You just need to first define the number-or-markup? function, which
isn’t included in Scheme or in LilyPond out-of-the-box:
#(define (number-or-markup? x)
(or (number? x) (markup? x)))
Cheers,
V.
On 2019-04-01 2:01 pm, Gianmaria Lari wrote:
The following function has been written by David Kastrup few years ago
but
it does not compile on lilypond 2.21
\version "2.21.0"
newFinger =
#(define-event-function (arg) (number-or-markup?)
#{ -\markup \underline \finger
#(if (number?
All,
When the following code is compiled, the compressed full bar rests for the
R2.*8 measures at mark A do not display as does the R1*15 measures at mark
B. At mark A the meter shifts to 3/4 -- am I doing this wrong? it is R2.*8
right?
Thanks.
\version "2.19"
\language "english"
\score {
>> if I use `\magnifyStaff', the tuplet number is too far away from
>> the beam. How can I move it nearer to the beam? Looking into
>> `tuplet-number.cc' I see a `padding' property with a default value
>> of 0.5 (and which is apparently completely undocumented).
>
> There's a few ways to pad
The following function has been written by David Kastrup few years ago but
it does not compile on lilypond 2.21
\version "2.21.0"
newFinger =
#(define-event-function (arg) (number-or-markup?)
#{ -\markup \underline \finger
#(if (number? arg) (number->string arg) arg)
#})
The error I
On 4/1/2019 4:16 PM, Werner LEMBERG wrote:
Folks,
if I use `\magnifyStaff', the tuplet number is too far away from the
beam. How can I move it nearer to the beam? Looking into
`tuplet-number.cc' I see a `padding' property with a default value of
0.5 (and which is apparently completely
Folks,
if I use `\magnifyStaff', the tuplet number is too far away from the
beam. How can I move it nearer to the beam? Looking into
`tuplet-number.cc' I see a `padding' property with a default value of
0.5 (and which is apparently completely undocumented). However, doing
something like
Am 1. April 2019 20:07:47 MESZ schrieb Malte Meyn :
>
>
>Am 01.04.19 um 12:01 schrieb Johan Vromans:
>> On Mon, 1 Apr 2019 09:17:26 +0200, Malte Meyn
>wrote:
>>
>>> SMuFL integration and using Metafont for glyph creation don’t
>>> contradict, do they?
>>
>> They do, in so far that with
Am 01.04.19 um 12:01 schrieb Johan Vromans:
On Mon, 1 Apr 2019 09:17:26 +0200, Malte Meyn wrote:
SMuFL integration and using Metafont for glyph creation don’t
contradict, do they?
They do, in so far that with limited resources you cannot do both.
[sending on-list, sorry Johan for the
On Mon 01 Apr 2019 at 09:16:24 (+0200), David Kastrup wrote:
> David Wright writes:
> > On Mon 01 Apr 2019 at 11:37:42 (+1100), Andrew Bernard wrote:
> >> Hi Valentin,
> >>
> >> Thanks so much. Now to learn Metafont then. Shouldn't be too hard - I have
> >> been a programmer for more than forty
Hello Stig,
I've posted this mail twice by mistake, I have the answer now :
https://lists.gnu.org/archive/html/lilypond-user/2019-03/msg00417.html
It's what you recommend, with \omit Staff.StringNumber
I searched I read the document multiple times but I didn't understand that
finger numbering
Thank you all who replied! Yes it was a mistake in rhythm that caused the
problem. Rewriting it as an eighth note tied to half note solved the problem.
Sent from Yahoo Mail on Android
On Sat, Mar 30, 2019 at 6:20 PM, Aaron Feldman wrote:
GNU LilyPond 2.18.2
running on Ubuntu 18.04
On Mon, 1 Apr 2019 09:17:26 +0200, Malte Meyn wrote:
> SMuFL integration and using Metafont for glyph creation don’t
> contradict, do they?
They do, in so far that with limited resources you cannot do both.
___
lilypond-user mailing list
Hi Tonio,
You can use "\finger" to specify specific finger numbering for notes within a
chord. Try: "{b1\3}" in your case. See also:
http://lilypond.org/doc/v2.19/Documentation/notation/common-notation-for-fretted-strings#string-number-indications
Regards,
Stig
Tonio Rush writes:
> I would
Am So., 31. März 2019 um 20:33 Uhr schrieb Werner LEMBERG :
>
>
> The attached example demonstrates a bug in handling the extent of a
> slur within a scaled staff. [Looking into the lilypond issues I
> wasn't able to find something related; I will report the problem if no
> one comes up with an
Hi Pedro,
Am 31.03.19 um 04:30 schrieb Pedro Pessoa:
The ideia for the "local" package is to make a clear distinctions
between remote and local files. Like so:
[ root ]
|- - oll-core
|- - edition-engraver
|- - lalily-templates
|- - ... etc
|- - [ local ]
|- - common (shared functions for
Hi Aaron,
(There's a >> missing.)
Well, either you or your email client erroneously stripped the ">>"
from the original email. It did indeed contain ">>".
You're right - Mozilla Thunderbird was the culprit. @Erwinstein: I'm
sorry, no mistake on your part! (I actually did ponder whether
David Wright writes:
> On Mon 01 Apr 2019 at 11:37:42 (+1100), Andrew Bernard wrote:
>> Hi Valentin,
>>
>> Thanks so much. Now to learn Metafont then. Shouldn't be too hard - I have
>> been a programmer for more than forty years. [Despite that, I still cannot
>> come to grips with the lilypond
Am 01.04.19 um 08:59 schrieb Johan Vromans:
On Mon, 1 Apr 2019 11:37:42 +1100, Andrew Bernard
wrote:
Now to learn Metafont then. Shouldn't be too hard -
As a retired TeXnician I have deep respect for TeX and MetaFont.
Nevertheless I think the right way now is to go for widely accepted
Hi Andrew and Johan,
Am 01.04.19 um 08:59 schrieb Johan Vromans:
On Mon, 1 Apr 2019 11:37:42 +1100, Andrew Bernard
wrote:
Now to learn Metafont then. Shouldn't be too hard -
As a retired TeXnician I have deep respect for TeX and MetaFont.
Nevertheless I think the right way now is to go for
Aaron Hill writes:
> On 2019-03-31 6:14 pm, edes wrote:
>> el 2019-04-01 a las 11:37 Andrew Bernard escribió:
>>
>>> Thanks so much. Now to learn Metafont then. Shouldn't be too hard
>>
>> unlike valentin, i admire you already even if you don't succeed. i
>> don't
>> know what admire the most:
On Mon, 1 Apr 2019 11:37:42 +1100, Andrew Bernard
wrote:
> Now to learn Metafont then. Shouldn't be too hard -
As a retired TeXnician I have deep respect for TeX and MetaFont.
Nevertheless I think the right way now is to go for widely accepted
standards where possible.
So I'd rather see decent
39 matches
Mail list logo
