Re: Strange space between beam and slur
Lukas-Fabian Moser writes:
> Hi Andrew,
>
> Am 25.06.19 um 10:56 schrieb Andrew Bernard:
>> What is it about 19? Is it some magic borderline number in some unit
>> system in lilypond? Do we know?
>
> I'd rather suspect there's some kind of "anthropic principle" at work
> here: The bugs (at least the one I reported) should probably occur for
> any staff size in some (staff-size-dependent) situations, but we
> notice them with staff sizes that are used in real-world situations,
> hence our MWEs expose _those_ cases. But of course I lilypond-user
> Mailinglist might be wrong, especially for the
> misplaced-note-head problem which occurs for quite a generic
> situation.
>
> Anyway: The misplaced-note-head bug
> (https://sourceforge.net/p/testlilyissues/issues/5303/) first appeared
> in 2.19.16 (I just found out that it's convenient as well as quite
> easy to keep arbitrarily many LilyPond versions installed on the same
> account).
>
> @gcc experts (hence posting to devel also): Unfortunately, I cannot
> build 2.19.15 on my machine because of errors of the type:
>
> /home/lukas/git/lilypond/lily/include/smobs.tcc:98:25: error: invalid
> conversion from 'int' to 'scm_unused_struct* (*)(SCM, SCM) {aka
> scm_unused_struct* (*)(scm_unused_struct*, scm_unused_struct*)}'
> [-fpermissive]
> scm_set_smob_equalp (smob_tag_, Super::equal_p);
>
> I suspect that this is a case of some conversions having become
> illegal for later versions of gcc. Is there a cheap way to make the
> build succeed in order to be able to bisect for the
> misplaced-note-head bug?
I think I used a few cherry-picks commits for building. Embarrassingly,
it doesn't appear like I have them in a branch. They were a few C++
commits, a few Texinfo ones, some stuff related to freetype.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange space between beam and slur
Hi Andrew,
Am 25.06.19 um 10:56 schrieb Andrew Bernard:
What is it about 19? Is it some magic borderline number in some unit
system in lilypond? Do we know?
I'd rather suspect there's some kind of "anthropic principle" at work
here: The bugs (at least the one I reported) should probably occur for
any staff size in some (staff-size-dependent) situations, but we notice
them with staff sizes that are used in real-world situations, hence our
MWEs expose _those_ cases. But of course I lilypond-user Mailinglist
might be wrong, especially for the
misplaced-note-head problem which occurs for quite a generic situation.
Anyway: The misplaced-note-head bug
(https://sourceforge.net/p/testlilyissues/issues/5303/) first appeared
in 2.19.16 (I just found out that it's convenient as well as quite easy
to keep arbitrarily many LilyPond versions installed on the same account).
@gcc experts (hence posting to devel also): Unfortunately, I cannot
build 2.19.15 on my machine because of errors of the type:
/home/lukas/git/lilypond/lily/include/smobs.tcc:98:25: error: invalid
conversion from 'int' to 'scm_unused_struct* (*)(SCM, SCM) {aka
scm_unused_struct* (*)(scm_unused_struct*, scm_unused_struct*)}'
[-fpermissive]
scm_set_smob_equalp (smob_tag_, Super::equal_p);
I suspect that this is a case of some conversions having become illegal
for later versions of gcc. Is there a cheap way to make the build
succeed in order to be able to bisect for the misplaced-note-head bug?
Best
Lukas
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange space between beam and slur
What is it about 19? Is it some magic borderline number in some unit system
in lilypond? Do we know?
Andrew
On Tue, 25 Jun 2019 at 15:49, Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com> wrote:
> So possible workarounds:
> #(set-global-staff-size 19.01)
> or using:
> \layout { #(layout-set-staff-size 19) }
> instead.
> Cheers,
> Pierre
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange space between beam and slur
So possible workarounds:
#(set-global-staff-size 19.01)
or using:
\layout { #(layout-set-staff-size 19) }
instead.
Cheers,
Pierre
Le mar. 25 juin 2019 à 01:01, Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com> a écrit :
> Hum, this staff-size 19 reminds me:
> http://lilypond.1069038.n5.nabble.com/misplacement-note-head-version-2-19-td211629.html
> Any posible relationship?
> Cheers,
> Pierre
>
> Le mar. 25 juin 2019 à 00:11, Thomas Morley a
> écrit :
>
>> Am So., 23. Juni 2019 um 11:59 Uhr schrieb Thomas Morley
>> :
>> [...]
>> Just reported in the german forum
>> https://lilypondforum.de/index.php/topic,501.0.html
>>
>> \version "2.19.82"
>>
>> % problem occurs at staff-size 19, but does not occur at staff-size 18 or
>> 20
>> #(set-global-staff-size 19)
>>
>> \new TabStaff \with { stringTunings = \stringTuning }
>> \new TabVoice
>> {
>> \stemDown
>> d8( dis) % normal position of slur above tab-notes
>> dis( e) % normal position
>> e( f) % lifted position of slur - WHY
>> f( fis) % again normal position
>> }
>>
>> a misplaced Slur, even without Beams
>>
>> Cheers,
>> Harm
>>
>> ___
>> 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: Strange space between beam and slur
Hum, this staff-size 19 reminds me:
http://lilypond.1069038.n5.nabble.com/misplacement-note-head-version-2-19-td211629.html
Any posible relationship?
Cheers,
Pierre
Le mar. 25 juin 2019 à 00:11, Thomas Morley a
écrit :
> Am So., 23. Juni 2019 um 11:59 Uhr schrieb Thomas Morley
> :
> [...]
> Just reported in the german forum
> https://lilypondforum.de/index.php/topic,501.0.html
>
> \version "2.19.82"
>
> % problem occurs at staff-size 19, but does not occur at staff-size 18 or
> 20
> #(set-global-staff-size 19)
>
> \new TabStaff \with { stringTunings = \stringTuning }
> \new TabVoice
> {
> \stemDown
> d8( dis) % normal position of slur above tab-notes
> dis( e) % normal position
> e( f) % lifted position of slur - WHY
> f( fis) % again normal position
> }
>
> a misplaced Slur, even without Beams
>
> Cheers,
> Harm
>
> ___
> 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: Strange space between beam and slur
Am So., 23. Juni 2019 um 11:59 Uhr schrieb Thomas Morley
:
[...]
Just reported in the german forum
https://lilypondforum.de/index.php/topic,501.0.html
\version "2.19.82"
% problem occurs at staff-size 19, but does not occur at staff-size 18 or 20
#(set-global-staff-size 19)
\new TabStaff \with { stringTunings = \stringTuning }
\new TabVoice
{
\stemDown
d8( dis) % normal position of slur above tab-notes
dis( e) % normal position
e( f) % lifted position of slur - WHY
f( fis) % again normal position
}
a misplaced Slur, even without Beams
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange space between beam and slur
Am So., 23. Juni 2019 um 10:54 Uhr schrieb Andrew Bernard
:
>
> Hi Lukas,
>
> May be a bug, but I always use explicit voices, not '//' constructs. I
> find it is just better but.
>
> You play with the rests, but this works:
>
>
> \new Staff
> <<
>{
> \voiceOne
> R1
> a''8( b'' b'' a'')
>}
>\new Voice {
> \voiceTwo
> R1
> r2
>}
> >>
>
>
> I'm aware this does not address the issue of whether your code shows a
> bug or not. Could be something to do with your rests running out, inside
> the '//' construct. Sorry I don't have more time to look at it now.
>
> Andrew
\new Staff
<<
{
\voiceOne
R1
a''8( b'' b'' a'')
}
\new Voice {
\voiceTwo
r4 r r r
r r r r
}
>>
exposes the problem as well.
I can confirm Lukas-Fabian's finding about first bad commit.
87eb2f9fe1be3a532675fe4b7322bbba5a60ba5c
patches `overdone_heads´ in feta-params.mf
So adding
\override NoteHead.font-size = 0.0001
to the examples fixes them in recent lily-versions
Interestingly 2.18.2 can be forced to return same bad output by
setting NoteHead.font-size accordingly:
\version "2.18.2"
\new Staff \with { \override NoteHead.font-size = 0.5 }
<<
{ R1 a''8( b'' b'' a'') } \\ { r4 }
>>
\new Staff \with { \override NoteHead.font-size = -0.0001 }
<<
{ \voiceOne R1 a''8( b'' b'' a'') }
\new Voice { \voiceTwo r4 r r r r r r r }
>>
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange space between beam and slur
Hi Lukas,
May be a bug, but I always use explicit voices, not '//' constructs. I
find it is just better but.
You play with the rests, but this works:
\new Staff
<<
{
\voiceOne
R1
a''8( b'' b'' a'')
}
\new Voice {
\voiceTwo
R1
r2
}
>>
I'm aware this does not address the issue of whether your code shows a
bug or not. Could be something to do with your rests running out, inside
the '//' construct. Sorry I don't have more time to look at it now.
Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange space between beam and slur
Hi Carl, thanks for trying this (and forgive me for explicitly CC'ng you as the author of the commit that, on my system, triggered the problem)! On 6/22/19, 3:48 PM, "Lukas-Fabian Moser" wrote: That's about as much as I can contribute, I guess. Does anybody have an idea what precisely is causing the problem? Hmm, this works for me on 2.19.82 running on OSX under Frescobaldi. No extra space. What is your system configuration? Now that's strange. The error can be reproduced on LilyBin, so it's not my system (or an installation problem) only, but your experience seems to point to a OS dependent issue. My system runs Linux Aquarium 4.15.0-52-generic #56-Ubuntu SMP Tue Jun 4 22:49:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux on Mint 19.1 (MATE 1.20.1) and the error occurs using both the 64 bit and (just tried) the 32 bit executables. Should I provide more information? Best Lukas ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange space between beam and slur
On 6/22/19, 3:48 PM, "Lukas-Fabian Moser" wrote: That's about as much as I can contribute, I guess. Does anybody have an idea what precisely is causing the problem? Hmm, this works for me on 2.19.82 running on OSX under Frescobaldi. No extra space. What is your system configuration? Thanks, Carl slur-space.pdf Description: slur-space.pdf ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
