Hi Aaron,
> The baselines are aligned. It is just that "g" in the default font lies
> above the baseline, so it looks odd. Change _"g" to _"gb" and you can see
> that the b's align.
Ah! Yes. Actually, changing it to 'q' makes more sense, so that the set above
and below the staff are identica
On 2018-10-20 5:49 pm, Aaron Hill wrote:
On 2018-10-20 5:45 pm, Kieren MacMillan wrote:
The baselines above the staff seem aligned, but not below the staff.
Is that expected behaviour?
Hi Kieren,
The baselines are aligned. It is just that "g" in the default font
lies above the baseline, so i
On 2018-10-20 5:45 pm, Kieren MacMillan wrote:
Hi Aaron,
\version "2.19.82"
{
\override TextScript.staff-padding = #(lambda (grob)
(let ((dir (ly:event-property (event-cause grob) 'direction)))
(if (> dir 0) 2.5 3.5)))
g' _"g" ^"q"
g' _"b" ^"b"
}
The baselines above the s
Hi Aaron,
>
> \version "2.19.82"
> {
> \override TextScript.staff-padding = #(lambda (grob)
>(let ((dir (ly:event-property (event-cause grob) 'direction)))
> (if (> dir 0) 2.5 3.5)))
> g' _"g" ^"q"
> g' _"b" ^"b"
> }
>
The baselines above the staff seem aligned, but not belo
On 2018-10-20 2:51 pm, David Kastrup wrote:
Torsten Hämmerle writes:
The only thing I do not like about staff-padding is that, strictly
speaking,
we'd need different values for up and down direction:
Above the stave, just the descenders go between stave and text
baseline,
whereas below the s
Am Sa., 20. Okt. 2018 um 23:11 Uhr schrieb Jean-Julien Fleck
:
>
> Hi everyone,
>
> I have been searching how to indicate some optionnal finger indication in
> parenthesis but found no direct way. I ended up using some quite complicated
> hack:
>
> doigte = \markup { \halign #-0.5 \override #'(fo
Hi Kieren,
Am 20.10.2018 um 21:22 schrieb Kieren MacMillan:
Hi Urs,
Is there a way to force text elements to a common *baseline* (as long as
collision avoidance doesn't force them farther away from the staff?
This is a long-standing irritation of mine, with respect to Lily’s text/markup
ha
Torsten Hämmerle writes:
> The only thing I do not like about staff-padding is that, strictly speaking,
> we'd need different values for up and down direction:
> Above the stave, just the descenders go between stave and text baseline,
> whereas below the stave, the baseline has to be sufficiently
Hi everyone,
I have been searching how to indicate some optionnal finger indication in
parenthesis but found no direct way. I ended up using some quite
complicated hack:
doigte = \markup { \halign #-0.5 \override #'(font-encoding . fetaText)
\magnify #0.5 (4)}
and then {re-0-\doigte}.
It worked
The only thing I do not like about staff-padding is that, strictly speaking,
we'd need different values for up and down direction:
Above the stave, just the descenders go between stave and text baseline,
whereas below the stave, the baseline has to be sufficiently far away from
the stave so that th
Urs Liska writes:
> Hi,
>
> I'm trying to place a number of TextScript elements on a common
> baseline (similar to how lyrics are typeset).
>
> Using outside-staff-padding on first sight seems to work but it
> doesn't really do the job.
>
> \version "2.19.82"
>
> {
> \override TextScript.outsid
Hi Urs,
> Is there a way to force text elements to a common *baseline* (as long as
> collision avoidance doesn't force them farther away from the staff?
This is a long-standing irritation of mine, with respect to Lily’s text/markup
handling…
The only hack I’ve found so far is to force a common
Hi,
I'm trying to place a number of TextScript elements on a common baseline
(similar to how lyrics are typeset).
Using outside-staff-padding on first sight seems to work but it doesn't
really do the job.
\version "2.19.82"
{
\override TextScript.outside-staff-padding = 2
g' _"g" ^"q"
On 20.10.2018 15:01, Kieren MacMillan wrote:
I do think the \after function is a good one to know — useful and flexible
enough that it should probably be in the main distro!
IIRC, there are two main reasons why it isn’t (apart from the usual
“nobody added it”): the name is a little to ‘improm
Hi Lucas,
> Note that you could almost certainly use the tag system to build "extenders"
> out of existing variables/notes, thus avoiding the need for a whole separate,
> manually-created variable.
e.g.
%%% SNIPPET BEGINS
\version "2.18.2"
\language"english"
upper = {
c'1
R1
}
lower = {
Hi Lucas,
> I’d prefer a solution that doesn’t require eyeballing a close-enough value.
Best Solution: Lilypond should have a switch/parameter to do what you’re asking
(defaulting to ##f, to mimic current behaviour).
Next Best Solution: Someone could build a Scheme engraver that searches across
Hi Pierre,
> How about a shorter way:
Yes! Thanks for pointing that one out.
I’m glad to see it isn’t ruined by music after it:
\version "2.18.2"
\language"english"
\relative{
\time 2/4
c2 \f \< <>\!
c2
}
I do think the \after function is a good one to know — useful and flexible
enough
On Thu, 18 Oct 2018 at 08:01, Lucas Werkmeister
wrote:
> Hi everyone,
>
> I’m transcribing an old choral score for LilyPond (full source at [1]),
> and while I’ve been mostly successful so far, one thing I haven’t
> figured out yet is the extenders. In the original score, several notes
> have ext
Fine David, thanks!
JM
> Le 20 oct. 2018 à 11:16, David Kastrup a écrit :
>
> Jacques Menu writes:
>
>> Thanks David. Are after grace notes simply handled with positive grace time?
>
> Notation Reference, "Grace Notes":
>
> If you want to end a note with a grace, use the ‘\afterGrace’
> c
Jacques Menu writes:
> Thanks David. Are after grace notes simply handled with positive grace time?
Notation Reference, "Grace Notes":
If you want to end a note with a grace, use the ‘\afterGrace’
command. It takes two arguments: the main note, and the grace notes
following the main note.
Thanks David. Are after grace notes simply handled with positive grace time?
Jm
> Le 20 oct. 2018 à 00:35, David Kastrup a écrit :
>
> Jacques Menu writes:
>
>> Hello folks,
>>
>> IIUC, at some point in its work, LilyPond represents the music as a
>> sequene of events, each with a position i
Hi,
How about a shorter way:
\version "2.18.2"
\language"english"
\relative{
\time 2/4
c2 \f \< <>\!
}
Cheers,
Pierre
Le sam. 20 oct. 2018 à 03:36, Kieren MacMillan <
kieren_macmil...@sympatico.ca> a écrit :
> Hi Ethan,
>
> > Try something like this:
> >
> > \version "2.18.2"
> > \languag
22 matches
Mail list logo
