Re: staffSize music function unreliable at LP v2.19.16
Hello,
a possible workaround would be to insert
\layout {
\context { \Voice
\override Stem.neutral-direction = #'()
\consists Melody_engraver }
}
It computes the stem direction for neutral-position (i.e. normally the
center staff line) and here also the wrongly flipped f’s such as to suit
the surrounding notes.
HTH, Simon
Am 03.03.2015 um 15:37 schrieb Cynthia Karl:
The following snippet:
\version 2.19.15
staffSize = #(define-music-function (parser location new-size) (number?)
#{
\set fontSize = #new-size
\override StaffSymbol #'staff-space = #(magstep new-size)
\override StaffSymbol #'thickness = #(magstep new-size)
#})
Ab = \relative c' { f4 g a b }
\score {
\new Staff \with { \staffSize #2 { \Ab }
\layout {}
}
produces at LP v2.19.15:
but at LP v2.19.16 produces:
Besides being wrong (see, e.g., Behind Bars by Elaine Gould, p.13),
this causes many scores to require an additional page.
Applying convert-ly to the above snippet changes only the \version number.
I tried all values for new-size between -8 and +8; the only ones that
failed were -4 and 2.
(The staffSize music-function was kindly contributed by Eluze in 2013
on this list to overcome limitations of layout-set-staff-size.)
___
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: staffSize music function unreliable at LP v2.19.16
I should add that the original code was missing a right closing brace after
\staffSize #2 to close off the \with block.
James Worlton
On Tue, Mar 3, 2015 at 9:19 AM, James Worlton jworl...@gmail.com wrote:
On Tue, Mar 3, 2015 at 8:37 AM, Cynthia Karl pck...@mac.com wrote:
The following snippet:
\version 2.19.15
staffSize = #(define-music-function (parser location new-size) (number?)
#{
\set fontSize = #new-size
\override StaffSymbol #'staff-space = #(magstep new-size)
\override StaffSymbol #'thickness = #(magstep new-size)
#})
Ab = \relative c' { f4 g a b }
\score {
\new Staff \with { \staffSize #2 { \Ab }
\layout { }
}
produces at LP v2.19.15:
but at LP v2.19.16 produces:
Besides being wrong (see, e.g., Behind Bars by Elaine Gould, p.13),
this causes many scores to require an additional page.
Applying convert-ly to the above snippet changes only the \version number.
I tried all values for new-size between -8 and +8; the only ones that
failed were -4 and 2.
(The staffSize music-function was kindly contributed by Eluze in 2013 on
this list to overcome limitations of layout-set-staff-size.)
I have been able to reproduce the problem on Windows 7 with Frescobaldi
2.17.2.
Additionally I found that sizes of 2.1, 1.4, 1.1, 0.7, 0.5, -0.2, -0.3,
-0.6, -1.3, -1.4, -2.1 also created the down stem on the F. (I only tested
2.1 to -2.1).
James Worlton
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: staffSize music function unreliable at LP v2.19.16
I can confirm the problem on windows. Using a greater range of notes produces
some interesting output...
--
Phil Holmes
- Original Message -
From: Pierre Perol-Schneider
To: James Worlton
Cc: Cynthia Karl ; lilypond-user
Sent: Tuesday, March 03, 2015 3:26 PM
Subject: Re: staffSize music function unreliable at LP v2.19.16
No problem on my side (see attached).
OS : Ubuntu 14.10
Frescobaldi 2.13
LP 2.19.16
Here's a compilable code:
\version 2.19.16
staffSize = #(define-music-function (parser location new-size)
(number?)
#{
\set fontSize = #new-size
\override StaffSymbol.staff-space = #(magstep new-size)
\override StaffSymbol.thickness = #(magstep new-size)
#})
Ab = \relative c' { f4 g a b }
\score {
\new Staff \with { \staffSize #2 } { \Ab }
\layout { }
}
Cheers,
Pierre
2015-03-03 16:19 GMT+01:00 James Worlton jworl...@gmail.com:
On Tue, Mar 3, 2015 at 8:37 AM, Cynthia Karl pck...@mac.com wrote:
The following snippet:
\version 2.19.15
staffSize = #(define-music-function (parser location new-size) (number?)
#{
\set fontSize = #new-size
\override StaffSymbol #'staff-space = #(magstep new-size)
\override StaffSymbol #'thickness = #(magstep new-size)
#})
Ab = \relative c' { f4 g a b }
\score {
\new Staff \with { \staffSize #2 { \Ab }
\layout { }
}
produces at LP v2.19.15:
but at LP v2.19.16 produces:
Besides being wrong (see, e.g., Behind Bars by Elaine Gould, p.13),
this causes many scores to require an additional page.
Applying convert-ly to the above snippet changes only the \version number.
I tried all values for new-size between -8 and +8; the only ones that
failed were -4 and 2.
(The staffSize music-function was kindly contributed by Eluze in 2013 on
this list to overcome limitations of layout-set-staff-size.)
I have been able to reproduce the problem on Windows 7 with Frescobaldi
2.17.2.
Additionally I found that sizes of 2.1, 1.4, 1.1, 0.7, 0.5, -0.2, -0.3,
-0.6, -1.3, -1.4, -2.1 also created the down stem on the F. (I only tested 2.1
to -2.1).
James Worlton
___
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
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: staffSize music function unreliable at LP v2.19.16
On Tue, Mar 3, 2015 at 8:37 AM, Cynthia Karl pck...@mac.com wrote:
The following snippet:
\version 2.19.15
staffSize = #(define-music-function (parser location new-size) (number?)
#{
\set fontSize = #new-size
\override StaffSymbol #'staff-space = #(magstep new-size)
\override StaffSymbol #'thickness = #(magstep new-size)
#})
Ab = \relative c' { f4 g a b }
\score {
\new Staff \with { \staffSize #2 { \Ab }
\layout { }
}
produces at LP v2.19.15:
but at LP v2.19.16 produces:
Besides being wrong (see, e.g., Behind Bars by Elaine Gould, p.13), this
causes many scores to require an additional page.
Applying convert-ly to the above snippet changes only the \version number.
I tried all values for new-size between -8 and +8; the only ones that
failed were -4 and 2.
(The staffSize music-function was kindly contributed by Eluze in 2013 on
this list to overcome limitations of layout-set-staff-size.)
I have been able to reproduce the problem on Windows 7 with Frescobaldi
2.17.2.
Additionally I found that sizes of 2.1, 1.4, 1.1, 0.7, 0.5, -0.2, -0.3,
-0.6, -1.3, -1.4, -2.1 also created the down stem on the F. (I only tested
2.1 to -2.1).
James Worlton
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: staffSize music function unreliable at LP v2.19.16
No problem on my side (see attached).
OS : Ubuntu 14.10
Frescobaldi 2.13
LP 2.19.16
Here's a compilable code:
\version 2.19.16
staffSize = #(define-music-function (parser location new-size)
(number?)
#{
\set fontSize = #new-size
\override StaffSymbol.staff-space = #(magstep new-size)
\override StaffSymbol.thickness = #(magstep new-size)
#})
Ab = \relative c' { f4 g a b }
\score {
\new Staff \with { \staffSize #2 } { \Ab }
\layout { }
}
Cheers,
Pierre
2015-03-03 16:19 GMT+01:00 James Worlton jworl...@gmail.com:
On Tue, Mar 3, 2015 at 8:37 AM, Cynthia Karl pck...@mac.com wrote:
The following snippet:
\version 2.19.15
staffSize = #(define-music-function (parser location new-size) (number?)
#{
\set fontSize = #new-size
\override StaffSymbol #'staff-space = #(magstep new-size)
\override StaffSymbol #'thickness = #(magstep new-size)
#})
Ab = \relative c' { f4 g a b }
\score {
\new Staff \with { \staffSize #2 { \Ab }
\layout { }
}
produces at LP v2.19.15:
but at LP v2.19.16 produces:
Besides being wrong (see, e.g., Behind Bars by Elaine Gould, p.13),
this causes many scores to require an additional page.
Applying convert-ly to the above snippet changes only the \version number.
I tried all values for new-size between -8 and +8; the only ones that
failed were -4 and 2.
(The staffSize music-function was kindly contributed by Eluze in 2013 on
this list to overcome limitations of layout-set-staff-size.)
I have been able to reproduce the problem on Windows 7 with Frescobaldi
2.17.2.
Additionally I found that sizes of 2.1, 1.4, 1.1, 0.7, 0.5, -0.2, -0.3,
-0.6, -1.3, -1.4, -2.1 also created the down stem on the F. (I only tested
2.1 to -2.1).
James Worlton
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
CK.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: staffSize music function unreliable at LP v2.19.16
The problem also exists on OSX (10.9.5) with 2.19.16.
2.18.2 still does it correctly.
I will test my linux machine later.
I'd say this constitutes a regression? The staffSize function doesn't seem
to do anything fancy or unusual.
On Tue, Mar 3, 2015 at 3:47 PM, Phil Holmes m...@philholmes.net wrote:
I can confirm the problem on windows. Using a greater range of notes
produces some interesting output...
--
Phil Holmes
- Original Message -
*From:* Pierre Perol-Schneider pierre.schneider.pa...@gmail.com
*To:* James Worlton jworl...@gmail.com
*Cc:* Cynthia Karl pck...@mac.com ; lilypond-user
lilypond-user@gnu.org
*Sent:* Tuesday, March 03, 2015 3:26 PM
*Subject:* Re: staffSize music function unreliable at LP v2.19.16
No problem on my side (see attached).
OS : Ubuntu 14.10
Frescobaldi 2.13
LP 2.19.16
Here's a compilable code:
\version 2.19.16
staffSize = #(define-music-function (parser location new-size)
(number?)
#{
\set fontSize = #new-size
\override StaffSymbol.staff-space = #(magstep new-size)
\override StaffSymbol.thickness = #(magstep new-size)
#})
Ab = \relative c' { f4 g a b }
\score {
\new Staff \with { \staffSize #2 } { \Ab }
\layout { }
}
Cheers,
Pierre
2015-03-03 16:19 GMT+01:00 James Worlton jworl...@gmail.com:
On Tue, Mar 3, 2015 at 8:37 AM, Cynthia Karl pck...@mac.com wrote:
The following snippet:
\version 2.19.15
staffSize = #(define-music-function (parser location new-size) (number?)
#{
\set fontSize = #new-size
\override StaffSymbol #'staff-space = #(magstep new-size)
\override StaffSymbol #'thickness = #(magstep new-size)
#})
Ab = \relative c' { f4 g a b }
\score {
\new Staff \with { \staffSize #2 { \Ab }
\layout { }
}
produces at LP v2.19.15:
but at LP v2.19.16 produces:
Besides being wrong (see, e.g., Behind Bars by Elaine Gould, p.13),
this causes many scores to require an additional page.
Applying convert-ly to the above snippet changes only the \version
number.
I tried all values for new-size between -8 and +8; the only ones that
failed were -4 and 2.
(The staffSize music-function was kindly contributed by Eluze in 2013 on
this list to overcome limitations of layout-set-staff-size.)
I have been able to reproduce the problem on Windows 7 with Frescobaldi
2.17.2.
Additionally I found that sizes of 2.1, 1.4, 1.1, 0.7, 0.5, -0.2, -0.3,
-0.6, -1.3, -1.4, -2.1 also created the down stem on the F. (I only tested
2.1 to -2.1).
James Worlton
___
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
___
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: staffSize music function unreliable at LP v2.19.16
Harm, On Tue, Mar 3, 2015 at 3:30 PM, Thomas Morley thomasmorle...@gmail.com wrote: thanks for testing. So this function may use as a test-case. No idea whats causing this bug, though. And because I'm not able to reproduce it, I can't help furthermore :( I don't think I could do anything either. I wouldn't know how to build LilyPond for Windows to verify any fix... --David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: staffSize music function unreliable at LP v2.19.16
I've attached the PDF output of your code, as run on my machine: Windows 7,
Frescobaldi 2.17.2, Lily 2.19.16.
James Worlton
On Tue, Mar 3, 2015 at 2:59 PM, Thomas Morley thomasmorle...@gmail.com
wrote:
2015-03-03 17:34 GMT+01:00 Kevin Barry barr...@gmail.com:
The problem also exists on OSX (10.9.5) with 2.19.16.
2.18.2 still does it correctly.
I will test my linux machine later.
I'd say this constitutes a regression? The staffSize function doesn't
seem to do anything fancy or unusual.
On Tue, Mar 3, 2015 at 3:47 PM, Phil Holmes m...@philholmes.net wrote:
I can confirm the problem on windows. Using a greater range of notes
produces some interesting output...
--
Phil Holmes
Can't confirm on my Linux-machine.
I tried to write some test-function, though.
It puts out a StaffGroup with 81 Staves with different sizes on a huge
paper.
View with zoom. ;)
Can someone on windows/OSX confirm buggy output at certain sizes?
\version 2.19.16
#(set-default-paper-size b0)
staffSize = #(define-music-function (parser location new-size) (number?)
#{
\set fontSize = #new-size
\override StaffSymbol #'staff-space = #(magstep new-size)
\override StaffSymbol #'thickness = #(magstep new-size)
#})
mus = \relative c' { f4 g a b }
\new StaffGroup
$@(map
(lambda (size nmbr)
#{
\new Staff
\with {
instrumentName =
\markup
\abs-fontsize #10
#(format #f Staff Nr. ~a, with staffSize: ~a nmbr size)
\staffSize $size
}
\mus
#})
(iota 81 4 -0.1)
(iota 81 1))
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
stembug.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: staffSize music function unreliable at LP v2.19.16
Cynthia Karl wrote
The following snippet:
\version 2.19.15
staffSize = #(define-music-function (parser location new-size) (number?)
#{
\set fontSize = #new-size
\override StaffSymbol #'staff-space = #(magstep new-size)
\override StaffSymbol #'thickness = #(magstep new-size)
#})
Ab = \relative c' { f4 g a b }
\score {
\new Staff \with { \staffSize #2 { \Ab }
\layout { }
}
produces at LP v2.19.15:
but at LP v2.19.16 produces:
Besides being wrong (see, e.g., Behind Bars by Elaine Gould, p.13), this
causes many scores to require an additional page.
Applying convert-ly to the above snippet changes only the \version number.
I tried all values for new-size between -8 and +8; the only ones that
failed were -4 and 2.
(The staffSize music-function was kindly contributed by Eluze in 2013 on
this list to overcome limitations of layout-set-staff-size.)
___
lilypond-user mailing list
lilypond-user@
https://lists.gnu.org/mailman/listinfo/lilypond-user
Screen Shot 2015-03-03 at 8.24.10 AM.png (12K)
lt;http://lilypond.1069038.n5.nabble.com/attachment/172534/0/Screen%20Shot%202015-03-03%20at%208.24.10%20AM.pnggt;
Screen Shot 2015-03-03 at 8.24.24 AM.png (12K)
lt;http://lilypond.1069038.n5.nabble.com/attachment/172534/1/Screen%20Shot%202015-03-03%20at%208.24.24%20AM.pnggt;
Hi all,
I'm not able to reproduce this on my Debian (KDE) machine using Frescobaldi
2.17.2 and LilyPond 2.19.16.
I'm trying...maybe I'm missing something? Sorry, trying to help!
Ben
-
composer | sound designer
LilyPond Tutorials (for beginners) -- http://bit.ly/bcl-lilypond
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/staffSize-music-function-unreliable-at-LP-v2-19-16-tp172534p172550.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: staffSize music function unreliable at LP v2.19.16
On Tue, Mar 3, 2015 at 3:44 PM, David Nalesnik david.nales...@gmail.com
wrote:
Harm,
On Tue, Mar 3, 2015 at 3:30 PM, Thomas Morley thomasmorle...@gmail.com
wrote:
thanks for testing. So this function may use as a test-case.
No idea whats causing this bug, though. And because I'm not able to
reproduce it, I can't help furthermore :(
I don't think I could do anything either. I wouldn't know how to build
LilyPond for Windows to verify any fix...
An observation. In the following snippet, you'll note in the log output
that the default-direction of the downstemmed F and B is 0--CENTER. This
means that Stem::calc-direction (in lily/stem.cc) will take the property
'neutral-direction. This property is supposed to specify the direction of
a note on the midline--B only in our case. F should have a
default-direction of 1.
\version 2.19.16
staffSize = #(define-music-function (parser location new-size)
(number?)
#{
\set fontSize = #new-size
\override StaffSymbol.staff-space = #(magstep new-size)
\override StaffSymbol.thickness = #(magstep new-size)
#})
Ab = \relative c' { f4 g a b c d e f }
\score {
\new Staff \with { \staffSize #2 }
{
\override Stem.after-line-breaking =
#(lambda (grob)
(format #t ~a default-direction: ~a~%
grob
(ly:grob-property grob 'default-direction)))
\Ab
}
\layout { }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: staffSize music function unreliable at LP v2.19.16
On Tue, Mar 3, 2015 at 3:59 PM, David Nalesnik david.nales...@gmail.com wrote: On Tue, Mar 3, 2015 at 3:44 PM, David Nalesnik david.nales...@gmail.com wrote: Harm, On Tue, Mar 3, 2015 at 3:30 PM, Thomas Morley thomasmorle...@gmail.com wrote: thanks for testing. So this function may use as a test-case. No idea whats causing this bug, though. And because I'm not able to reproduce it, I can't help furthermore :( I don't think I could do anything either. I wouldn't know how to build LilyPond for Windows to verify any fix... An observation. In the following snippet, you'll note in the log output that the default-direction of the downstemmed F and B is 0--CENTER. This means that Stem::calc-direction (in lily/stem.cc) will take the property 'neutral-direction. This property is supposed to specify the direction of a note on the midline--B only in our case. F should have a default-direction of 1. Note that adding \override Stem.neutral-direction = #1 fixes the problem for the bad stems. David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: staffSize music function unreliable at LP v2.19.16
2015-03-03 17:34 GMT+01:00 Kevin Barry barr...@gmail.com:
The problem also exists on OSX (10.9.5) with 2.19.16.
2.18.2 still does it correctly.
I will test my linux machine later.
I'd say this constitutes a regression? The staffSize function doesn't seem
to do anything fancy or unusual.
On Tue, Mar 3, 2015 at 3:47 PM, Phil Holmes m...@philholmes.net wrote:
I can confirm the problem on windows. Using a greater range of notes
produces some interesting output...
--
Phil Holmes
Can't confirm on my Linux-machine.
I tried to write some test-function, though.
It puts out a StaffGroup with 81 Staves with different sizes on a huge
paper.
View with zoom. ;)
Can someone on windows/OSX confirm buggy output at certain sizes?
\version 2.19.16
#(set-default-paper-size b0)
staffSize = #(define-music-function (parser location new-size) (number?)
#{
\set fontSize = #new-size
\override StaffSymbol #'staff-space = #(magstep new-size)
\override StaffSymbol #'thickness = #(magstep new-size)
#})
mus = \relative c' { f4 g a b }
\new StaffGroup
$@(map
(lambda (size nmbr)
#{
\new Staff
\with {
instrumentName =
\markup
\abs-fontsize #10
#(format #f Staff Nr. ~a, with staffSize: ~a nmbr size)
\staffSize $size
}
\mus
#})
(iota 81 4 -0.1)
(iota 81 1))
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: staffSize music function unreliable at LP v2.19.16
2015-03-03 22:15 GMT+01:00 David Nalesnik david.nales...@gmail.com: Harm, On Tue, Mar 3, 2015 at 2:59 PM, Thomas Morley thomasmorle...@gmail.com wrote: 2015-03-03 17:34 GMT+01:00 Kevin Barry barr...@gmail.com: The problem also exists on OSX (10.9.5) with 2.19.16. 2.18.2 still does it correctly. I will test my linux machine later. I'd say this constitutes a regression? The staffSize function doesn't seem to do anything fancy or unusual. On Tue, Mar 3, 2015 at 3:47 PM, Phil Holmes m...@philholmes.net wrote: I can confirm the problem on windows. Using a greater range of notes produces some interesting output... -- Phil Holmes Can't confirm on my Linux-machine. Nor on my VM. I tried to write some test-function, though. It puts out a StaffGroup with 81 Staves with different sizes on a huge paper. View with zoom. ;) Can someone on windows/OSX confirm buggy output at certain sizes? Yes, under Windows 7 64-bit, I get the flipped F at the following sizes: 3.9, 2.0, 1.4, 1.1, 0.7, 0.5, -0.1, -0.2, -0.3, -0.6, -1.3, -1.4, -3.9. -4.0 --David James, David, thanks for testing. So this function may use as a test-case. No idea whats causing this bug, though. And because I'm not able to reproduce it, I can't help furthermore :( -Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: staffSize music function unreliable at LP v2.19.16
Harm, On Tue, Mar 3, 2015 at 2:59 PM, Thomas Morley thomasmorle...@gmail.com wrote: 2015-03-03 17:34 GMT+01:00 Kevin Barry barr...@gmail.com: The problem also exists on OSX (10.9.5) with 2.19.16. 2.18.2 still does it correctly. I will test my linux machine later. I'd say this constitutes a regression? The staffSize function doesn't seem to do anything fancy or unusual. On Tue, Mar 3, 2015 at 3:47 PM, Phil Holmes m...@philholmes.net wrote: I can confirm the problem on windows. Using a greater range of notes produces some interesting output... -- Phil Holmes Can't confirm on my Linux-machine. Nor on my VM. I tried to write some test-function, though. It puts out a StaffGroup with 81 Staves with different sizes on a huge paper. View with zoom. ;) Can someone on windows/OSX confirm buggy output at certain sizes? Yes, under Windows 7 64-bit, I get the flipped F at the following sizes: 3.9, 2.0, 1.4, 1.1, 0.7, 0.5, -0.1, -0.2, -0.3, -0.6, -1.3, -1.4, -3.9. -4.0 --David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: staffSize music function unreliable at LP v2.19.16
Simon Albrecht simon.albrecht at mail.de writes: Well, there’s reason enough to redirect this to bug-lilypond, isn’t it? Thanks for finding the bug, and confirming that it is a bug and not just a misunderstanding, and narrowing down the cause, and posting to bug-lilypond. The relevant code did not change, but the version of GCC used as a cross- operating-system compiler did change. Some very useful programming languages, including C,have details where behavior is allowed to vary between systems, and here it seems LilyPond inadvertently depended on one of those details. There will probably be a couple more of these strange bugs in 2.19.16 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: staffSize music function unreliable at LP v2.19.16
On Tue, Mar 3, 2015 at 4:35 PM, Simon Albrecht simon.albre...@mail.de wrote: Well, there’s reason enough to redirect this to bug-lilypond, isn’t it? Somehow, Mozilla Thunderbird messes up the code examples, so I can’t do so well. Perhaps the OP’s and Harm’s first mails in the thread, respectively, should suffice for illustration. ~Simon You might add that it appears to be a problem related to the calculation of Stem.default-direction which appears when staff-space is changed. --David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: staffSize music function unreliable at LP v2.19.16
Well, there’s reason enough to redirect this to bug-lilypond, isn’t it? Somehow, Mozilla Thunderbird messes up the code examples, so I can’t do so well. Perhaps the OP’s and Harm’s first mails in the thread, respectively, should suffice for illustration. ~Simon Am 03.03.2015 um 23:01 schrieb David Nalesnik: On Tue, Mar 3, 2015 at 3:59 PM, David Nalesnik david.nales...@gmail.com mailto:david.nales...@gmail.com wrote: On Tue, Mar 3, 2015 at 3:44 PM, David Nalesnik david.nales...@gmail.com mailto:david.nales...@gmail.com wrote: Harm, On Tue, Mar 3, 2015 at 3:30 PM, Thomas Morley thomasmorle...@gmail.com mailto:thomasmorle...@gmail.com wrote: thanks for testing. So this function may use as a test-case. No idea whats causing this bug, though. And because I'm not able to reproduce it, I can't help furthermore :( I don't think I could do anything either. I wouldn't know how to build LilyPond for Windows to verify any fix... An observation. In the following snippet, you'll note in the log output that the default-direction of the downstemmed F and B is 0--CENTER. This means that Stem::calc-direction (in lily/stem.cc) will take the property 'neutral-direction. This property is supposed to specify the direction of a note on the midline--B only in our case. F should have a default-direction of 1. Note that adding \override Stem.neutral-direction = #1 fixes the problem for the bad stems. David ___ 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
