Re: Aesthetics question -- how would you typeset this?
On Wed, Jul 3, 2019 at 12:21 AM Evan Driscoll wrote: > (That obviously *isn't* playable. Answers I'm considering include... > playing open A instead of open D) > Strike that; reverse it. Evan > > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Aesthetics question -- how would you typeset this?
On Tue, Jul 2, 2019 at 11:55 PM Malte Meyn wrote: > Am 03.07.19 um 06:36 schrieb Evan Driscoll: > > It's for cello, and just the part, no score. > > Is that playable? I sadly haven’t touched my cello for a few months now > and it’s 350 km away so I can’t try but I think I couldn’t play that > passage despite having long fingers … > The violin part has b flat in the lower voice, not g. That makes it > playable on the cello too but brings me to the question how you’ll > arrange the following measure … > Crap, these two questions are related to each other. I made a mistake when copying the part into the reduced part (I didn't copy and paste) and it was always supposed to be B flat in the lower note. (That said, I don't think that changes much about my "problem" or the solutions. At most it might speak slightly more favorably toward my \stemDown answer.) (As for the following measure, assuming you're talking about the one where the main line goes 'd8 e fs d fs a4' at the top of the treble staff in double stop with the A below middle C, I'm undecided. (Sorry for the English note names; I got into the habit of using that and from then on could never remember -es/-is being sharp/flat.) That obviously *isn't* playable. Answers I'm considering include dropping the lower notes entirely, playing open A instead of open D, or playing the A an octave up on the D string. I need to play around with this.) If it’s hard to read because of a “ton of stems and staff lines and > such” maybe there is a layout problem, f. e. too small staff size, > staves not far enough apart. Changing the stem direction shouldn’t be > necessary. > I put a screenshot of the relevant part of the score at https://i.imgur.com/3gMB5iP.png so it can be seen in context, in case that helps. I can certainly leave sleeping dogs lie if you think it looks fine and no one else chimes in. :-) (I haven't yet fixed the typo in this version, so there will be a couple wrong notes.) It's laid out for letter paper; there are eight systems on that page. Thanks a lot for your feedback, by the way; I appreciate it! I'm only an occasional user of Lilypond, but this mailing list is always so responsive... Evan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Aesthetics question -- how would you typeset this?
Am 03.07.19 um 06:36 schrieb Evan Driscoll:
It's for cello, and just the part, no score.
Is that playable? I sadly haven’t touched my cello for a few months now
and it’s 350 km away so I can’t try but I think I couldn’t play that
passage despite having long fingers …
It's a transcription of the violin part of the violin+piano arrangement
of Danse Macabre. For the violin, it's up an octave and the problem I
have with it doesn't arise -- it's comes out much the same as tenor
clef. Lots of it can't be reasonably written without treble clef, so
being capable in that clef is necessary; the high note I think is a'' /
A5 (the A just above the top of the treble staff)
The violin part has b flat in the lower voice, not g. That makes it
playable on the cello too but brings me to the question how you’ll
arrange the following measure …
> { s4^"The default, but melody 'lost' in the other visual
noise" }
Looks fine IMO.
I also got rid of some elaboration of why I thought this was a problem
in the first place, which is that I find it difficult to see the line of
the top notes there; to me, the inter-note intervals are kind of buried
amidst a ton of stems and staff lines and such. In fact, that actually
held one of just two typos I've found that made it through all my
proofreading and to the point where I started to actually work from the
part. But who knows... maybe I'm the odd one out here and most people
*wouldn't* have any problem with it; maybe I'm too stuck up on the fact
that I made a typo and am trying to overcorrect.
If it’s hard to read because of a “ton of stems and staff lines and
such” maybe there is a layout problem, f. e. too small staff size,
staves not far enough apart. Changing the stem direction shouldn’t be
necessary.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Aesthetics question -- how would you typeset this?
On Tue, Jul 2, 2019 at 11:21 PM Malte Meyn wrote:
> Important question: What instrument(s) will play this? Is this from a
> part or a full score?
>
Sorry, I should have included that. I edited out a bunch of wordiness in my
email and that went with it.
It's for cello, and just the part, no score.
It's a transcription of the violin part of the violin+piano arrangement of
Danse Macabre. For the violin, it's up an octave and the problem I have
with it doesn't arise -- it's comes out much the same as tenor clef. Lots
of it can't be reasonably written without treble clef, so being capable in
that clef is necessary; the high note I think is a'' / A5 (the A just above
the top of the treble staff).
> > { s4^"The default, but melody 'lost' in the other visual noise" }
>
> Looks fine IMO.
>
I also got rid of some elaboration of why I thought this was a problem in
the first place, which is that I find it difficult to see the line of the
top notes there; to me, the inter-note intervals are kind of buried amidst
a ton of stems and staff lines and such. In fact, that actually held one of
just two typos I've found that made it through all my proofreading and to
the point where I started to actually work from the part. But who knows...
maybe I'm the odd one out here and most people *wouldn't* have any problem
with it; maybe I'm too stuck up on the fact that I made a typo and am
trying to overcorrect.
Evan
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Aesthetics question -- how would you typeset this?
Am 03.07.19 um 05:54 schrieb Evan Driscoll:
I've got a couple measures that I'm struggling to even figure out what I
want the result from Lilypond to be. I've pasted the snippet below. As
picky connoisseurs of good notation, I'm wondering what other people
would do or like to see. :-) I'm leaning toward the second option but am
uncertain.
Important question: What instrument(s) will play this? Is this from a
part or a full score?
{ s4^"The default, but melody 'lost' in the other visual noise" }
Looks fine IMO.
{ s4^"I like this more but is forcing the stems departing too much
from standard practice?" }
This needs too much space on the lower side. IMO that departs too much.
{ s4^"This also works well but this is an area already with tons of
clef changes and this adds two more"}
What instrument(s) is this for? Piano/harp/violin(s)/…: NO! They don’t
know that clef. Bassoons/cello(s): Yes, use treble clef only if really
necessary (in most cases); either this or the first solution is fine.
Trombones: YES! AFAIK they don’t know treble clef.
r4^"I don't like this but for completeness..."
Piano? → depends on whether this should be played with one (big) or two
hands. Two instruments/divisi: Maybe better than the first solution. One
or unisonon violins: the first solution is better.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Aesthetics question -- how would you typeset this?
I've got a couple measures that I'm struggling to even figure out what I
want the result from Lilypond to be. I've pasted the snippet below. As
picky connoisseurs of good notation, I'm wondering what other people would
do or like to see. :-) I'm leaning toward the second option but am
uncertain.
As a bonus question on Lilypond itself -- what are the differences between
<< { g bf g a ... } { g, g g g } >>
and
in this context? Aside from the octave changes working relative to
different notes, is there any difference? When should I prefer one to
another?
Thanks again,
Evan
\language "english"
\relative c'' {
\key g \minor
\time 3/4
<<
{ s4^"The default, but melody 'lost' in the other visual noise" }
{ r4 g8[ bf g a] | bf4 a8 bf g bf | a([ g)] g bf g a | bf4 r2 }
{ s4 g,8 g g g | g4 g8 g g g | g g g g g g | g4 s2 }
>>
\break
\stemDown
<<
{ s4^"I like this more but is forcing the stems departing too much from
standard practice?" }
{ r4 g'8[ bf g a] | bf4 a8 bf g bf | a([ g)] g bf g a | bf4 r2 }
{ s4 g,8 g g g | g4 g8 g g g | g g g g g g | g4 s2 }
>>
\break
\stemNeutral
\clef "tenor"
<<
{ s4^"This also works well but this is an area already with tons of
clef changes and this adds two more"}
{ r4 g'8[ bf g a] | bf4 a8 bf g bf | a([ g)] g bf g a | bf4 r2 }
{ s4 g,8 g g g | g4 g8 g g g | g g g g g g | g4 s2 }
>>
\break
\clef "treble"
r4^"I don't like this but for completeness..."
<<
{ g'8[ bf g a] | bf4 a8 bf g bf | a([ g)] g bf g a | bf4 }
\\
{ g,8 g g g | g4 g8 g g g | g[ g] g g g g | g4 }
>> r2
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Flute fingering chart
Peter,
This from
http://lilypond.org/doc/v2.19/Documentation/notation/woodwind-diagrams
\version "2.19.81"
\relative c' {
c1^
\markup {
\center-column {
'flute
" "
\woodwind-diagram
#'flute
#'()
}
}
}
Mark
From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org]
On Behalf Of Peter O'Doherty
Sent: Tuesday, July 02, 2019 2:33 AM
To: lilypond-user@gnu.org
Subject: Flute fingering chart
Hi,
I'm looking for a flute fingering chart which is more akin to the style used by
the likes of Robert Dick (see attached). I can't make head nor tail of the
default lilypond chart and a professional flutist I'm working with also finds
it very idiosyncratic. Is there an alternative?
Failing that, might a workable option be for me to simply to reference an
external image in the ly file? Is it possible to include an external image and
control its XY placement on the stave?
Many thanks,
Peter
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: formatting of elided syllable in lyrics
Thanks David & Aaron,
that works nicely. The thing I was missing was the need to encompass the
entire syllable (the thing between "--" delimiters) within the markup.
-- Graham
> On 2 Jul 2019, at 20:07, Aaron Hill wrote:
>
> On 2019-07-02 9:19 am, Graham King wrote:
>> Where two syllables are set to the same note, is there a way to apply
>> formatting to the second? I hope I've not missed something obvious in
>> the NR or the Snippets Repository.
>> In the following example, "eleison" is editorial and should be
>> italicised. The upper line of lyrics has the correct spacing but not
>> the desired italics:
>> \version "2.19.82"
>> ital = \override LyricText.font-shape = #'italic
>> italx = \revert LyricText.font-shape
>> { c'1 c' d' c' }
>> \addlyrics { ky -- rie_e -- lei -- son }
>> \addlyrics { ky -- rie_ \ital e -- lei -- son \italx }
>
> You could manually construct the syllable with custom markup:
>
>
> \version "2.19.82"
>
> ital = \override LyricText.font-shape = #'italic
> italx = \revert LyricText.font-shape
>
> { c'1 c' d' c' }
> \addlyrics { ky -- rie_e -- lei -- son }
> % \addlyrics { ky -- rie_ \ital e -- lei -- son \italx }
> \addlyrics { ky -- \markup { rie \italic e } -- \ital lei -- son \italx }
>
>
>
> -- Aaron Hill
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond 2.19.83 - ragged-right problem not solved
Windows 10 Fresobaldi 3.0.1 I would like to inform everyone who has put time and effort into trying to help me solve this impass that I have decided to downgrade to Lilypond 2.18.2. This has proved to be a wise decision resulting in perfect right justification and normal pdf printouts using identical code. My own personal reflection is that it would seem to confirm the presence of a bug in later versions of Lilypond which will hopefully be corrected in the near future. It would also seem to indicate that MAC offers a better platform than Windows considering the fact that the above problem was not so prevalent there. - John McWilliam -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond 2.19.83 ragged-right problem
Windows 10 Fresobaldi 3.0.1 I would like to inform everyone who has put time and effort into trying to help me solve this impass that I have decided to downgrade to Lilypond 2.18.2. This has proved to be a wise decision resulting in perfect right justification and normal pdf printouts using identical code. My own personal reflection is that it would seem to confirm the presence of a bug in later versions of Lilypond which will hopefully be corrected in the near future. It would also seem to indicate that MAC offers a better platform than Windows considering the fact that the above problem was not so prevalent there. - John McWilliam -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: formatting of elided syllable in lyrics
Graham King writes:
> Where two syllables are set to the same note, is there a way to apply
> formatting to the second? I hope I've not missed something obvious in
> the NR or the Snippets Repository.
>
> In the following example, "eleison" is editorial and should be
> italicised. The upper line of lyrics has the correct spacing but not
> the desired italics:
>
> \version "2.19.82"
>
> ital = \override LyricText.font-shape = #'italic
> italx = \revert LyricText.font-shape
>
> { c'1 c' d' c' }
> \addlyrics { ky -- rie_e -- lei -- son }
> \addlyrics { ky -- rie_ \ital e -- lei -- son \italx }
\version "2.19.82"
ital = \temporary \override LyricText.font-shape = #'italic
italx = \revert LyricText.font-shape
{ c'1 c' d' c' }
\addlyrics { ky -- \markup { rie \italic e } -- \ital lei -- son \italx }
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: formatting of elided syllable in lyrics
On 2019-07-02 9:19 am, Graham King wrote:
Where two syllables are set to the same note, is there a way to apply
formatting to the second? I hope I've not missed something obvious in
the NR or the Snippets Repository.
In the following example, "eleison" is editorial and should be
italicised. The upper line of lyrics has the correct spacing but not
the desired italics:
\version "2.19.82"
ital = \override LyricText.font-shape = #'italic
italx = \revert LyricText.font-shape
{ c'1 c' d' c' }
\addlyrics { ky -- rie_e -- lei -- son }
\addlyrics { ky -- rie_ \ital e -- lei -- son \italx }
You could manually construct the syllable with custom markup:
\version "2.19.82"
ital = \override LyricText.font-shape = #'italic
italx = \revert LyricText.font-shape
{ c'1 c' d' c' }
\addlyrics { ky -- rie_e -- lei -- son }
% \addlyrics { ky -- rie_ \ital e -- lei -- son \italx }
\addlyrics { ky -- \markup { rie \italic e } -- \ital lei -- son \italx
}
-- Aaron Hill
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
formatting of elided syllable in lyrics
Where two syllables are set to the same note, is there a way to apply
formatting to the second? I hope I've not missed something obvious in the NR
or the Snippets Repository.
In the following example, "eleison" is editorial and should be italicised. The
upper line of lyrics has the correct spacing but not the desired italics:
\version "2.19.82"
ital = \override LyricText.font-shape = #'italic
italx = \revert LyricText.font-shape
{ c'1 c' d' c' }
\addlyrics { ky -- rie_e -- lei -- son }
\addlyrics { ky -- rie_ \ital e -- lei -- son \italx }
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond 2.19.83
On Tue, 2 Jul 2019 at 09:50, Michael Hendry wrote: > > On 2 Jul 2019, at 02:47, Stanton Sanderson wrote: > > > > > > On Jul 1, 2019, at 11:03 AM, John McWilliam > wrote: > >> > >> <25th_kosbs_test.ly> > > > > John, > > > > I’m probably missing something, but it appears to work on my machine > (Mac OS 10.14.5). pdf attached > > > > <25th_kosbs_test.pdf>___ > > lilypond-user mailing list > > lilypond-user@gnu.org > > https://lists.gnu.org/mailman/listinfo/lilypond-user > > In case you’re thinking you’re going mad, John, it doesn’t work for me > either! > > The third, fifth and seventh staves extend beyond the others, and off the > right margin of the paper. > > I’m using Lilypond 2.21.0 on an iMac, OSX 10.13.6 Interesting that you get the erroneous output as well as programming error messages on a Mac. Maybe it is system dependent since myself and Stanton Sanderson are on 10.14 and do not have any problems, where as you are on 10.13. Although Lilypond 2.21.0 means that you have compiled it yourself, right? Then the problem may also be caused by other dependencies than the official version. Sven Axelsson ++[>++>+++>++>++ ><-]>.+..>+.>+.<<-.>>+.>.<<. +++.>-.<<++.>>.<++.>>>++..>>.<. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Flute fingering chart
Hi, I'm looking for a flute fingering chart which is more akin to the style used by the likes of Robert Dick (see attached). I can't make head nor tail of the default lilypond chart and a professional flutist I'm working with also finds it very idiosyncratic. Is there an alternative? Failing that, might a workable option be for me to simply to reference an external image in the ly file? Is it possible to include an external image and control its XY placement on the stave? Many thanks, Peter ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond 2.19.83
Same here, on W10, but only occurs when paper is set to 'landscape. It reminds me: http://lilypond.1069038.n5.nabble.com/Grace-notes-and-staff-miss-alignment-td181529.html#none HTH, Cheers, Pierre Le mar. 2 juil. 2019 à 09:50, Michael Hendry a écrit : > > On 2 Jul 2019, at 02:47, Stanton Sanderson wrote: > > > > > > On Jul 1, 2019, at 11:03 AM, John McWilliam > wrote: > >> > >> <25th_kosbs_test.ly> > > > > John, > > > > I’m probably missing something, but it appears to work on my machine > (Mac OS 10.14.5). pdf attached > > > > <25th_kosbs_test.pdf>___ > > lilypond-user mailing list > > lilypond-user@gnu.org > > https://lists.gnu.org/mailman/listinfo/lilypond-user > > In case you’re thinking you’re going mad, John, it doesn’t work for me > either! > > The third, fifth and seventh staves extend beyond the others, and off the > right margin of the paper. > > I’m using Lilypond 2.21.0 on an iMac, OSX 10.13.6 > > I tried it before and after applying convert.ly. > > The log follows: > > Starting lilypond 2.21.0 [25th_kosbs_test.ly]... > Processing `/Users/michaelhendry/tmp/bagpipe/25th_kosbs_test.ly' > Parsing... > Interpreting music...[8][16][24][32] > Preprocessing graphical objects... > programming error: mis-predicted force, 157.628268 ~= 157.612550 > continuing, cross fingers > programming error: mis-predicted force, 157.628268 ~= 158.198252 > continuing, cross fingers > programming error: mis-predicted force, 157.628268 ~= 158.373999 > continuing, cross fingers > programming error: mis-predicted force, 157.628268 ~= 164.386816 > continuing, cross fingers > programming error: mis-predicted force, 157.628268 ~= 173.858594 > continuing, cross fingers > programming error: mis-predicted force, 157.628268 ~= 157.495597 > continuing, cross fingers > programming error: mis-predicted force, 157.628268 ~= 158.546509 > continuing, cross fingers > programming error: mis-predicted force, 157.628268 ~= 156.553116 > continuing, cross fingers > programming error: mis-predicted force, 157.628268 ~= 157.497148 > continuing, cross fingers > programming error: mis-predicted force, 157.628268 ~= 166.351458 > continuing, cross fingers > programming error: mis-predicted force, 157.628268 ~= 157.468665 > continuing, cross fingers > programming error: mis-predicted force, 157.628268 ~= 156.690155 > continuing, cross fingers > programming error: mis-predicted force, 157.628268 ~= 154.865500 > continuing, cross fingers > programming error: mis-predicted force, 157.628268 ~= 160.256387 > continuing, cross fingers > programming error: mis-predicted force, 157.628268 ~= 172.583956 > continuing, cross fingers > programming error: mis-predicted force, 157.628268 ~= 172.583956 > continuing, cross fingers > programming error: mis-predicted force, 157.628268 ~= 166.351458 > continuing, cross fingers > programming error: mis-predicted force, 157.628268 ~= 173.858594 > continuing, cross fingers > programming error: mis-predicted force, 157.628268 ~= 154.865500 > continuing, cross fingers > programming error: mis-predicted force, 157.628268 ~= 166.351458 > continuing, cross fingers > programming error: mis-predicted force, 157.628268 ~= 173.858594 > continuing, cross fingers > Finding the ideal number of pages... > Fitting music on 1 page... > Drawing systems... > programming error: mis-predicted force, 157.628268 ~= 172.583956 > continuing, cross fingers > programming error: mis-predicted force, 157.628268 ~= 166.351458 > continuing, cross fingers > programming error: mis-predicted force, 157.628268 ~= 173.858594 > continuing, cross fingers > Layout output to > `/var/folders/7z/6v5y7dgj181bb5j44lt_6d2wgn/T//lilypond-9acxoa'... > Converting to `25th_kosbs_test.pdf'... > Deleting > `/var/folders/7z/6v5y7dgj181bb5j44lt_6d2wgn/T//lilypond-9acxoa'... > Success: compilation successfully completed > Completed successfully in 1.5”. > > Hope this helps, > > Michael > ___ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond 2.19.83
> On 2 Jul 2019, at 02:47, Stanton Sanderson wrote: > > > On Jul 1, 2019, at 11:03 AM, John McWilliam wrote: >> >> <25th_kosbs_test.ly> > > John, > > I’m probably missing something, but it appears to work on my machine (Mac OS > 10.14.5). pdf attached > > <25th_kosbs_test.pdf>___ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user In case you’re thinking you’re going mad, John, it doesn’t work for me either! The third, fifth and seventh staves extend beyond the others, and off the right margin of the paper. I’m using Lilypond 2.21.0 on an iMac, OSX 10.13.6 I tried it before and after applying convert.ly. The log follows: Starting lilypond 2.21.0 [25th_kosbs_test.ly]... Processing `/Users/michaelhendry/tmp/bagpipe/25th_kosbs_test.ly' Parsing... Interpreting music...[8][16][24][32] Preprocessing graphical objects... programming error: mis-predicted force, 157.628268 ~= 157.612550 continuing, cross fingers programming error: mis-predicted force, 157.628268 ~= 158.198252 continuing, cross fingers programming error: mis-predicted force, 157.628268 ~= 158.373999 continuing, cross fingers programming error: mis-predicted force, 157.628268 ~= 164.386816 continuing, cross fingers programming error: mis-predicted force, 157.628268 ~= 173.858594 continuing, cross fingers programming error: mis-predicted force, 157.628268 ~= 157.495597 continuing, cross fingers programming error: mis-predicted force, 157.628268 ~= 158.546509 continuing, cross fingers programming error: mis-predicted force, 157.628268 ~= 156.553116 continuing, cross fingers programming error: mis-predicted force, 157.628268 ~= 157.497148 continuing, cross fingers programming error: mis-predicted force, 157.628268 ~= 166.351458 continuing, cross fingers programming error: mis-predicted force, 157.628268 ~= 157.468665 continuing, cross fingers programming error: mis-predicted force, 157.628268 ~= 156.690155 continuing, cross fingers programming error: mis-predicted force, 157.628268 ~= 154.865500 continuing, cross fingers programming error: mis-predicted force, 157.628268 ~= 160.256387 continuing, cross fingers programming error: mis-predicted force, 157.628268 ~= 172.583956 continuing, cross fingers programming error: mis-predicted force, 157.628268 ~= 172.583956 continuing, cross fingers programming error: mis-predicted force, 157.628268 ~= 166.351458 continuing, cross fingers programming error: mis-predicted force, 157.628268 ~= 173.858594 continuing, cross fingers programming error: mis-predicted force, 157.628268 ~= 154.865500 continuing, cross fingers programming error: mis-predicted force, 157.628268 ~= 166.351458 continuing, cross fingers programming error: mis-predicted force, 157.628268 ~= 173.858594 continuing, cross fingers Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... programming error: mis-predicted force, 157.628268 ~= 172.583956 continuing, cross fingers programming error: mis-predicted force, 157.628268 ~= 166.351458 continuing, cross fingers programming error: mis-predicted force, 157.628268 ~= 173.858594 continuing, cross fingers Layout output to `/var/folders/7z/6v5y7dgj181bb5j44lt_6d2wgn/T//lilypond-9acxoa'... Converting to `25th_kosbs_test.pdf'... Deleting `/var/folders/7z/6v5y7dgj181bb5j44lt_6d2wgn/T//lilypond-9acxoa'... Success: compilation successfully completed Completed successfully in 1.5”. Hope this helps, Michael ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 2.19.59: Bad horizontal spacing when \override LyricText#'X-offset
Thank you, Pierre, for your suggestion.
Unfortunately it is not always possible, there might be some
"Pneumonoultramicroscopicsilicovolcanoconiosis" instead of "Блаженні
голодні й спрагнені правди". And the more syllables collected in one
with quotes, the more visible this regression is.
Thank you anyway, i will test more.
On Mon, Jul 1, 2019 at 5:18 PM Pierre Perol-Schneider
wrote:
>
> Hi Dmytro,
>
> Not nice but works:
>
> \version "2.19.83"
> {
> r4
> %a
> a4*1/8 \hideNotes a a a a a a a\unHideNotes
> a2 a4 a2 s4
> }
> \addlyrics {
> \override LyricText #'X-offset = #0
> Блаженні голодні й спрагнені правди, бо вони на -- си -- тять -- ся.
> }
>
> HTH, cheers,
> Pierre
>
> Le lun. 1 juil. 2019 à 15:06, Dmytro O. Redchuk a
> écrit :
>>
>> Hi,
>>
>> is there any progress with this issue or any suggestions on how to
>> workaround?
>>
>> Thanks.
>>
>> On Sat, Apr 29, 2017 at 11:53 PM Trevor Daniels
>> wrote:
>> >
>> >
>> > Dmytro, you wrote Saturday, April 29, 2017 8:06 PM
>> >
>> > >> please, dear 'ponders, let me know what's wrong here in my email.
>> > >>
>> > >> Should I post this in bug-lilypond? Or is this spacing correct?
>> > > Oh SORRY, your replies were dropped by my gmail.
>> >
>> > No need to apologise. We've noted this as a regression introduced
>> > in 2.19.10; see https://sourceforge.net/p/testlilyissues/issues/5129/
>> >
>> > If you have an earlier release available maybe that could be used as
>> > a work-around for this piece. It seems unlikely there is an easy fix.
>> >
>> > Trevor
>> >
>> >
>> > ---
>> > This email has been checked for viruses by AVG.
>> > http://www.avg.com
>>
>>
>>
>> --
>> Dmytro O. Redchuk
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
--
Dmytro O. Redchuk
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
