Re: Bug? Mismatched grace notes at beginning of staff cause extra clefs in other staffs
At this point shouldn't it be called a feature?
Shane
Sent from my T-Mobile 4G LTE Device
Original message From: Thomas Morley
Date: 3/10/18 7:57 PM (GMT-05:00) To: Lucas
Werkmeister Cc: lilypond-user
Subject: Re: Bug? Mismatched grace notes at beginning
of staff cause extra
clefs in other staffs
2018-03-11 0:58 GMT+01:00 Lucas Werkmeister :
> Hi everyone,
>
> I found what I suspect is a LilyPond bug, but I’m not sure yet :) minimal
> example:
>
> \version "2.18.2"
>
> <<
> \new Staff { \grace c' c' }
> \new Staff { \clef "bass" }
>>>
>
> Instead of beginning with a bass clef, the lower staff begins with a violin
> clef and then has a bass clef right after the time signature. If a different
> key signature is set (omitted in the above example for brevity), the
> accidentals are only printed after that extra clef as well, and the whole
> group (bass clef and accidentals) is shifted to the left so that it overlaps
> the time signature.
>
> This seems to happen when the two staves begin with different amounts of
> grace notes. A workaround is to add a silent grace note to the lower staff
> (\grace s) – just make sure that it’s the same duration as the real grace
> note in the upper staff: if it’s longer (e. g. a simple \grace s without
> explicit duration if the current duration is 4 and the duration of the other
> grace note is 8), then the upper staff will have the same problem instead
> (extra clef – same as the original one in this case – and accidentals only
> after that).
>
> Unfortunately, I’m unable to check if this still happens in the current
> development version of LilyPond since I’m getting an error when building
> from Git, but that’s for a different email :) perhaps someone else can check
> that, so I don’t open a bug report for something that’s already fixed? (Or
> perhaps it’s simply expected that grace notes should be aligned between
> staves? But that would surprise me.)
>
> Oh, and for the sake of people googling for this error – it also affects
> \acciaccatura, \appoggiatura and \slashedGrace.
>
> Cheers,
> Lucas
It's issue 34
https://sourceforge.net/p/testlilyissues/issues/34/
Likely our most infamous bug, not fixed.
The workaround you've found is mentioned in the docs ;)
Search for grace synchronization.
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: Bug? Mismatched grace notes at beginning of staff cause extra clefs in other staffs
At this point shouldn't it be called a feature?
Shane
Sent from my T-Mobile 4G LTE Device
Original message From: Thomas Morley
Date: 3/10/18 7:57 PM (GMT-05:00) To: Lucas
Werkmeister Cc: lilypond-user
Subject: Re: Bug? Mismatched grace notes at beginning
of staff cause extra
clefs in other staffs
2018-03-11 0:58 GMT+01:00 Lucas Werkmeister :
> Hi everyone,
>
> I found what I suspect is a LilyPond bug, but I’m not sure yet :) minimal
> example:
>
> \version "2.18.2"
>
> <<
> \new Staff { \grace c' c' }
> \new Staff { \clef "bass" }
>>>
>
> Instead of beginning with a bass clef, the lower staff begins with a violin
> clef and then has a bass clef right after the time signature. If a different
> key signature is set (omitted in the above example for brevity), the
> accidentals are only printed after that extra clef as well, and the whole
> group (bass clef and accidentals) is shifted to the left so that it overlaps
> the time signature.
>
> This seems to happen when the two staves begin with different amounts of
> grace notes. A workaround is to add a silent grace note to the lower staff
> (\grace s) – just make sure that it’s the same duration as the real grace
> note in the upper staff: if it’s longer (e. g. a simple \grace s without
> explicit duration if the current duration is 4 and the duration of the other
> grace note is 8), then the upper staff will have the same problem instead
> (extra clef – same as the original one in this case – and accidentals only
> after that).
>
> Unfortunately, I’m unable to check if this still happens in the current
> development version of LilyPond since I’m getting an error when building
> from Git, but that’s for a different email :) perhaps someone else can check
> that, so I don’t open a bug report for something that’s already fixed? (Or
> perhaps it’s simply expected that grace notes should be aligned between
> staves? But that would surprise me.)
>
> Oh, and for the sake of people googling for this error – it also affects
> \acciaccatura, \appoggiatura and \slashedGrace.
>
> Cheers,
> Lucas
It's issue 34
https://sourceforge.net/p/testlilyissues/issues/34/
Likely our most infamous bug, not fixed.
The workaround you've found is mentioned in the docs ;)
Search for grace synchronization.
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: Bug? Mismatched grace notes at beginning of staff cause extra clefs in other staffs
2018-03-11 0:58 GMT+01:00 Lucas Werkmeister :
> Hi everyone,
>
> I found what I suspect is a LilyPond bug, but I’m not sure yet :) minimal
> example:
>
> \version "2.18.2"
>
> <<
> \new Staff { \grace c' c' }
> \new Staff { \clef "bass" }
>>>
>
> Instead of beginning with a bass clef, the lower staff begins with a violin
> clef and then has a bass clef right after the time signature. If a different
> key signature is set (omitted in the above example for brevity), the
> accidentals are only printed after that extra clef as well, and the whole
> group (bass clef and accidentals) is shifted to the left so that it overlaps
> the time signature.
>
> This seems to happen when the two staves begin with different amounts of
> grace notes. A workaround is to add a silent grace note to the lower staff
> (\grace s) – just make sure that it’s the same duration as the real grace
> note in the upper staff: if it’s longer (e. g. a simple \grace s without
> explicit duration if the current duration is 4 and the duration of the other
> grace note is 8), then the upper staff will have the same problem instead
> (extra clef – same as the original one in this case – and accidentals only
> after that).
>
> Unfortunately, I’m unable to check if this still happens in the current
> development version of LilyPond since I’m getting an error when building
> from Git, but that’s for a different email :) perhaps someone else can check
> that, so I don’t open a bug report for something that’s already fixed? (Or
> perhaps it’s simply expected that grace notes should be aligned between
> staves? But that would surprise me.)
>
> Oh, and for the sake of people googling for this error – it also affects
> \acciaccatura, \appoggiatura and \slashedGrace.
>
> Cheers,
> Lucas
It's issue 34
https://sourceforge.net/p/testlilyissues/issues/34/
Likely our most infamous bug, not fixed.
The workaround you've found is mentioned in the docs ;)
Search for grace synchronization.
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Bug? Mismatched grace notes at beginning of staff cause extra clefs in other staffs
On 11.03.2018 01:29, Lucas Werkmeister wrote: > I’m not sure if the clef behavior would still qualify as a bug (in the > docs, the grace note isn’t at the very beginning of the score, so the > clef behavior doesn’t happen) And it turns out this has also been described [1]. I must just have been searching for the completely wrong terms earlier, because now I found these two links on the problem within minutes of each other while searching for a solution to a *different* grace note problem… sorry again for the noise, I think this thread is really done now. Cheers, Lucas [1]: https://stackoverflow.com/questions/37037679/lilypond-grace-note-affects-formatting ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Bug? Mismatched grace notes at beginning of staff cause extra clefs in other staffs
On 11.03.2018 00:58, Lucas Werkmeister wrote: > (Or perhaps it’s simply expected that grace notes should be aligned > between staves? But that would surprise me.) Color me surprised, then – I just found this issue mentioned in the docs [1], with the same workaround I also discovered. I’m not sure if the clef behavior would still qualify as a bug (in the docs, the grace note isn’t at the very beginning of the score, so the clef behavior doesn’t happen) – if not, sorry for the noise :D Cheers, Lucas [1]: http://lilypond.org/doc/v2.18/Documentation/notation/special-rhythmic-concerns#Known-issues-and-warnings-71 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Bug? Mismatched grace notes at beginning of staff cause extra clefs in other staffs
Hi everyone,
I found what I suspect is a LilyPond bug, but I’m not sure yet :)
minimal example:
\version "2.18.2"
<<
\new Staff { \grace c' c' }
\new Staff { \clef "bass" }
>>
Instead of beginning with a bass clef, the lower staff begins with a
violin clef and then has a bass clef right after the time signature. If
a different key signature is set (omitted in the above example for
brevity), the accidentals are only printed after that extra clef as
well, and the whole group (bass clef and accidentals) is shifted to the
left so that it overlaps the time signature.
This seems to happen when the two staves begin with different amounts of
grace notes. A workaround is to add a silent grace note to the lower
staff (\grace s) – just make sure that it’s the same duration as the
real grace note in the upper staff: if it’s longer (e. g. a simple
\grace s without explicit duration if the current duration is 4 and the
duration of the other grace note is 8), then the upper staff will have
the same problem instead (extra clef – same as the original one in this
case – and accidentals only after that).
Unfortunately, I’m unable to check if this still happens in the current
development version of LilyPond since I’m getting an error when building
from Git, but that’s for a different email :) perhaps someone else can
check that, so I don’t open a bug report for something that’s already
fixed? (Or perhaps it’s simply expected that grace notes should be
aligned between staves? But that would surprise me.)
Oh, and for the sake of people googling for this error – it also affects
\acciaccatura, \appoggiatura and \slashedGrace.
Cheers,
Lucas
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
