Dear Harm,
You did it! You solved my problem, and have saved me from countless
tweak-recompile-tweak-recompile cycles with the way I was doing things
before. I can now set the vertical spacing of the chord/lyric lines in
relation to a single-line staff and move on, as I wanted. I am grateful
2018-06-11 4:17 GMT+02:00 dfro :
> A P.S. to my beginner musings:
>
> Perhaps, the VerticalAxisGroup stretchability variable could be adjusted in
> its behavior, so that when it is at 0, no bounding box/skyline safeguards
> are considered for the nonstaff-relatedstaff-spacing property at all - the
A P.S. to my beginner musings:
Perhaps, the VerticalAxisGroup stretchability variable could be adjusted
in its behavior, so that when it is at 0, no bounding box/skyline
safeguards are considered for the nonstaff-relatedstaff-spacing property
at all - the 'text baseline to staff center'
On 6/10/18 1:16 AM, Aaron Hill wrote:
On 2018-06-09 19:43, dfro wrote:
Dear code wizards,
I still have more to solve on this issue, if possible.
I think I have discovered why most of the shifting is happening: The
skyline rather than the baseline of the lyric line text is being
referenced by
On 2018-06-09 19:43, dfro wrote:
Dear code wizards,
I still have more to solve on this issue, if possible.
I think I have discovered why most of the shifting is happening: The
skyline rather than the baseline of the lyric line text is being
referenced by LilyPond when calculating vertical
Dear code wizards,
I still have more to solve on this issue, if possible.
I think I have discovered why most of the shifting is happening: The
skyline rather than the baseline of the lyric line text is being
referenced by LilyPond when calculating vertical placement.
What I am going for is
On 6/9/18 9:45 AM, Werner LEMBERG wrote:
Care to prepare a patch? You seem to be a native speaker, and
being a novice helps a lot in finding the right point of view for
the documentation...
I would be honored to contribute in this way. How may we proceed?
This depends on your experience with
>> Care to prepare a patch? You seem to be a native speaker, and
>> being a novice helps a lot in finding the right point of view for
>> the documentation...
>
> I would be honored to contribute in this way. How may we proceed?
This depends on your experience with programming. Assuming that
On 6/8/18 1:02 AM, Werner LEMBERG wrote:
In my humble opinion, I think the direction that nonstaff elements
are looking is a very important foundational concept that should be
included in the Notation Reference documentation, the Internal
Reference, and perhaps even the Learning Manual, and some
> In my humble opinion, I think the direction that nonstaff elements
> are looking is a very important foundational concept that should be
> included in the Notation Reference documentation, the Internal
> Reference, and perhaps even the Learning Manual, and some snippets
> could be added to the
On 6/7/18 5:19 PM, Thomas Morley wrote:
2018-06-07 20:15 GMT+02:00 dfro :
It seems like Verses2, 3, and 4 are looking down when using the padding
variable. How can I get them to look up to the verses and staff above? The
command - \override VerticalAxisGroup.staff-affinity = #UP - does not
2018-06-07 20:15 GMT+02:00 dfro :
> It seems like Verses2, 3, and 4 are looking down when using the padding
> variable. How can I get them to look up to the verses and staff above? The
> command - \override VerticalAxisGroup.staff-affinity = #UP - does not change
> the looking down behavior for
On 6/7/18 4:41 AM, Thomas Morley wrote:
Hi,
I'll soon have to run for my regular job, so I limit my reply to
alignAbove/BelowContext.
2018-06-07 5:03 GMT+02:00 dfro :
If I use the command - alignBelowContext = "Upper" - on the Lyrics to verse3
and verse4, then the texts switch place.
[...]
Hi,
I'll soon have to run for my regular job, so I limit my reply to
alignAbove/BelowContext.
2018-06-07 5:03 GMT+02:00 dfro :
> If I use the command - alignBelowContext = "Upper" - on the Lyrics to verse3
> and verse4, then the texts switch place.
[...]
> Why is this
> happening?
In short,
I am still trying to work out why the lyric lines are shifting from one
staff system to the next in my manuscripts.
In studying the documentation and experimenting with code snippets, I
have noticed some curious lyric line behavior when using the
VerticalAxisGroup spacing properties. I took
On Fri 01 Jun 2018 at 12:25:21 (-0400), Kieren MacMillan wrote:
> Hi David,
>
> > I just want to thank you promptly for you very quick response.
>
> Glad it helped.
>
> > It also looks like you have solved the text clashing with the bar lines.
> > Any advice on where I might study how to
Hi David,
> I just want to thank you promptly for you very quick response.
Glad it helped.
> It also looks like you have solved the text clashing with the bar lines. Any
> advice on where I might study how to control this better?
I’m not sure exactly… Lyrics are designed not to clash with
Kieren,
Thank you, this is a great improvement! It looks like I need to study
Chapter 4.4 of the Notation Reference and many of the links. I will play
with the code you shared and do some homework before I ask more
questions which are arising on this topic.
I just want to thank you promptly
Hi David,
> May I ask for some advice?
That’s what this list is for!
> I would like to have a single line staff that is grouped with other staffs,
> which I use to display chords and lyrics into rows above and below the line.
Does the modified snippet (below) do what you want?
n.b. I was only
Hi everyone,
May I ask for some advice?
I would like to have a single line staff that is grouped with other
staffs, which I use to display chords and lyrics into rows above and
below the line. I am using the following tweak on each lyric line, where
'y' is adjusted:
20 matches
Mail list logo