kneed spacing too tight, as of git 4 august (recently introduced regression)
%{
LilyPond chooses too tight spacing: the stems of kneed notes are too close and
the spacing too tight. This also occurs in one of my larger projects, where
the stems even are in the wrong order and sometimes outside the beams.
It seems that the optical spacing of kneed beamed notes (put stems at more
equal distances) does not work fully correct, as of git 4 august 2007
%}
\version "2.11.28" % git as of 4 august
\paper { line-width = 14.4 \cm }
rh = \change Staff = "rh"
lh = \change Staff = "lh"
\new PianoStaff <<
\new Staff ="rh" {
s1*3
}
\new Staff ="lh" {
\clef bass
\repeat unfold 12 { \rh a'16 \lh d \rh a' \lh d }
}
>>
with best regards,
Wilbert Berendsen
--
http://www.wilbertberendsen.nl/
"You must be the change you wish to see in the world."
-- Mahatma Gandi
<>___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: kneed spacing too tight, as of git 4 august (recently introduced regression)
On Monday 06 August 2007 16:33, Wilbert Berendsen wrote:
> %{
> LilyPond chooses too tight spacing: the stems of kneed notes are too close
> and the spacing too tight. This also occurs in one of my larger projects,
> where the stems even are in the wrong order and sometimes outside the
> beams. It seems that the optical spacing of kneed beamed notes (put stems
> at more equal distances) does not work fully correct, as of git 4 august
> 2007 %}
Does the problem still exist in the jneeman branch of git? If it does, I'd be
particularly interested in seeing examples with stems in the wrong order.
Joe
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: kneed spacing too tight, as of git 4 august (recently introduced regression)
Hello Joe,
can you look into fixing this problem, and merging the fixes into
master? Due to time-pressure, I don't want to delay 2.11.29 any
further, but shipping it breaks one of the major rules for lilypond
development: every release should be strictly better than the
preceding one.
thanks,
2007/8/6, Joe Neeman <[EMAIL PROTECTED]>:
> On Monday 06 August 2007 16:33, Wilbert Berendsen wrote:
> > %{
> > LilyPond chooses too tight spacing: the stems of kneed notes are too close
> > and the spacing too tight. This also occurs in one of my larger projects,
> > where the stems even are in the wrong order and sometimes outside the
> > beams. It seems that the optical spacing of kneed beamed notes (put stems
> > at more equal distances) does not work fully correct, as of git 4 august
> > 2007 %}
>
> Does the problem still exist in the jneeman branch of git? If it does, I'd be
> particularly interested in seeing examples with stems in the wrong order.
>
> Joe
>
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> http://lists.gnu.org/mailman/listinfo/bug-lilypond
>
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: kneed spacing too tight, as of git 4 august (recently introduced regression)
Hello, Joe wrote: Does the problem still exist in the jneeman branch of git? If it does, I'd be particularly interested in seeing examples with stems in the wrong order. Sorry, I'm on holiday right now, I cant't use git from this pc... will check next week, when I'm home! Best regards, Wilbert ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: kneed spacing too tight, as of git 4 august (recently introduced regression)
Op dinsdag 7 augustus 2007, schreef Joe Neeman:
> On Monday 06 August 2007 16:33, Wilbert Berendsen wrote:
> > %{
> > LilyPond chooses too tight spacing: the stems of kneed notes are too
> > close and the spacing too tight. This also occurs in one of my larger
> > projects, where the stems even are in the wrong order and sometimes
> > outside the beams. It seems that the optical spacing of kneed beamed
> > notes (put stems at more equal distances) does not work fully correct, as
> > of git 4 august 2007 %}
>
> Does the problem still exist in the jneeman branch of git? If it does, I'd
> be particularly interested in seeing examples with stems in the wrong
> order.
This is an example of the stems in the wrong order. Unfortunately I can't
create a smaller example. This is still git as of 4 august.
ly: http://www.xs4all.nl/~wbsoft/p78.ly
pdf: http://www.xs4all.nl/~wbsoft/p78.pdf (see p 2, meas 34)
closeup of stems in wrong order: http://www.xs4all.nl/~wbsoft/p78-closeup.png
Will try jneeman branch later.
w best regards,
Wilbert Berendsen
--
http://www.wilbertberendsen.nl/
"You must be the change you wish to see in the world."
-- Mahatma Gandi
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: kneed spacing too tight, as of git 4 august (recently introduced regression)
Op donderdag 16 augustus 2007, schreef Wilbert Berendsen: > after that I tested the jneeman branch of my file I meant "I tested the jneeman branch on my file" :-) w best regards, Wilbert Berendsen -- http://www.wilbertberendsen.nl/ "You must be the change you wish to see in the world." -- Mahatma Gandi ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: kneed spacing too tight, as of git 4 august (recently introduced regression)
On Thursday 16 August 2007 08:19, Wilbert Berendsen wrote: > Op dinsdag 7 augustus 2007, schreef Joe Neeman: > > Does the problem still exist in the jneeman branch of git? If it does, > > I'd be particularly interested in seeing examples with stems in the wrong > > order. > > git master as of today still shows the same too tight spacing choice as in > my previous mail with the results of git 4 august. That's strange because I merged jneeman into master a little while ago. Does 'git log master' show that commit 2a6bf54a5ebf426 is part of master? > after that I tested the jneeman branch of my file. This one makes the PDF 4 > pages long instead of 3, with a much more open spacing. and the stems in > the kneed beams are at nice even distances: > http://www.xs4all.nl/~wbsoft/p78jneeman.pdf > > I have to say, I like the slightly tighter spacing better (resulting in 3 > pages), but of course not the too tight spacing in the kneed beams. This is not entirely unexpected, since part of the bug was that lilypond was too willing to compress kneed beams. If the piece was tight on 3 pages before, the bug fix could easily have pushed it over to 4. Do the standard methods of tightening spacing (section 11.6.3) work? Joe ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: kneed spacing too tight, as of git 4 august (recently introduced regression)
Op vrijdag 17 augustus 2007, schreef Joe Neeman: > That's strange because I merged jneeman into master a little while ago. > Does 'git log master' show that commit 2a6bf54a5ebf426 is part of master? somehow git log master|grep 2a6bf54a5ebf426 shows nothing. I did git-checkout master and git-pull but still the log ends with Mon Aug 6 "typo" (commit 89cf7da059c6f8c2624d55c6d80ccf621e90a90c) What did I do wrong? (still newbee with git...) w best regards, Wilbert Berendsen -- http://www.wilbertberendsen.nl/ "You must be the change you wish to see in the world." -- Mahatma Gandi ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: kneed spacing too tight, as of git 4 august (recently introduced regression)
Op vrijdag 17 augustus 2007, schreef Wilbert Berendsen: > What did I do wrong? (still newbee with git...) now I did git checkout origin/master instead of git checkout master and that gave me the more recent logs and files. Is that the correct way? :) with best regards, Wilbert Berendsen -- http://www.wilbertberendsen.nl/ "You must be the change you wish to see in the world." -- Mahatma Gandi ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re[2]: kneed spacing too tight, as of git 4 august (recently introduced regression)
Op dinsdag 7 augustus 2007, schreef Joe Neeman: > Does the problem still exist in the jneeman branch of git? If it does, I'd > be particularly interested in seeing examples with stems in the wrong > order. git master as of today still shows the same too tight spacing choice as in my previous mail with the results of git 4 august. after that I tested the jneeman branch of my file. This one makes the PDF 4 pages long instead of 3, with a much more open spacing. and the stems in the kneed beams are at nice even distances: http://www.xs4all.nl/~wbsoft/p78jneeman.pdf I have to say, I like the slightly tighter spacing better (resulting in 3 pages), but of course not the too tight spacing in the kneed beams. w best regards, Wilbert Berendsen -- http://www.wilbertberendsen.nl/ "You must be the change you wish to see in the world." -- Mahatma Gandi ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
