Re: Possible bug with tempo mark spacing
Hi Malte, > That sounds like a really special case: MarkLine context AND hidden Staff AND > this staff contains notes (why is it hidden then?) AND Y-offset is set AND > extra-spacing-width is set … That "really special case" includes >50% of my choral writing, which comprises >50% of my composition and engraving projects. =) 1. I use a MarkLine context 100% of the time. 2. That MarkLine context has Y-offset and extra-spacing-width set in its definition. 3. In a choral score containing both divisi and combined staves, it is essentially guaranteed that there will be at least one (and likely multiple) hidden Staff contexts which contain notes. > I’m not sure, maybe it’s expected behaviour in many cases and only your case > is so special that it looks buggy even if it’s consistent. I’ve considered it a bug [for several years], and simply worked around it. I’m glad someone else has found it and reported it — I have always been under too much pressure to try to create a MWE [i.e., backing out and compressing into a single file my very extensive \include hierarchy]. > Using \markLengthOn instead of \override MetronomeMark.extra-spacing-width = > #'(0 . 0) works for me. Would that help in your use case? I’ve always used that (or the manual equivalent), injected via the edition-engraver. Hopefully it works for Saul as well. Cheers, Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Possible bug with tempo mark spacing
It's not that special of a case. Hiding a staff containing notes and using
a MarkLine are normal techniques for managing a large ensemble score.
>From property-init.ly:
markLengthOn = {
\override Score.MetronomeMark.extra-spacing-width = #'(0 . 1.0)
\override Score.RehearsalMark.extra-spacing-width = #'(-0.5 . 0.5)
% Raise as much as four staff-spaces before pushing notecolumns right
\override Score.MetronomeMark.extra-spacing-height = #'(4 . 4)
\override Score.RehearsalMark.extra-spacing-height = #'(4 . 4)
}
So it appears the relevant difference is setting some positive
extra-spacing-height when setting extra-spacing-width. On further testing
with ledger lines and placing a staff above the MarkLine, the right setting
seems to be MetronomeMark.extra-spacing-height = #'(4 . 0), rather than
#'(4 . 4).
I still wonder if there is a bug in the interaction with hidden staves.
Staves shouldn't be affecting spacing on systems where they are dead.
On Fri, Dec 28, 2018 at 6:47 AM Malte Meyn wrote:
>
>
> Am 28.12.18 um 04:54 schrieb Saul Tobin:
> >
> > When using a context like MarkLine for tempo marks, if the staff
> > immediately below the MarkLine is hidden but contains rhythmic activity,
> > and if BOTH Y-offset and extra-spacing-width are overridden for
> > MetronomeMark, the first rhythmic column will stretch to the width of
> > the tempo mark.
>
> That sounds like a really special case: MarkLine context AND hidden
> Staff AND this staff contains notes (why is it hidden then?) AND
> Y-offset is set AND extra-spacing-width is set …
>
> >
> > Is this a bug?
>
> I’m not sure, maybe it’s expected behaviour in many cases and only your
> case is so special that it looks buggy even if it’s consistent.
>
> Using \markLengthOn instead of \override
> MetronomeMark.extra-spacing-width = #'(0 . 0) works for me. Would that
> help in your use case?
>
> ___
> 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: Possible bug with tempo mark spacing
Am 28.12.18 um 04:54 schrieb Saul Tobin: When using a context like MarkLine for tempo marks, if the staff immediately below the MarkLine is hidden but contains rhythmic activity, and if BOTH Y-offset and extra-spacing-width are overridden for MetronomeMark, the first rhythmic column will stretch to the width of the tempo mark. That sounds like a really special case: MarkLine context AND hidden Staff AND this staff contains notes (why is it hidden then?) AND Y-offset is set AND extra-spacing-width is set … Is this a bug? I’m not sure, maybe it’s expected behaviour in many cases and only your case is so special that it looks buggy even if it’s consistent. Using \markLengthOn instead of \override MetronomeMark.extra-spacing-width = #'(0 . 0) works for me. Would that help in your use case? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Possible bug with tempo mark spacing
Happy holidays all,
Below is a demonstration of an odd behavior I noticed.
When using a context like MarkLine for tempo marks, if the staff
immediately below the MarkLine is hidden but contains rhythmic activity,
and if BOTH Y-offset and extra-spacing-width are overridden for
MetronomeMark, the first rhythmic column will stretch to the width of the
tempo mark.
Is this a bug?
\version "2.19.82"
\layout {
\context {
\name "MarkLine"
\type "Engraver_group"
\consists Axis_group_engraver
\override VerticalAxisGroup.staff-affinity = #DOWN
\consists Metronome_mark_engraver
%% If either of the below lines is removed, the music spaces correctly
\override MetronomeMark.extra-spacing-width = #'(0 . 0)
\override MetronomeMark.Y-offset = #0
}
\context {
\Score
\remove Mark_engraver
\remove Metronome_mark_engraver
\accepts MarkLine
}
}
<<
\new MarkLine { \tempo "Testing testing" 4=123 }
\new Staff \with {
\override VerticalAxisGroup.remove-empty = ##t
\override VerticalAxisGroup.remove-first = ##t
keepAliveInterfaces = #'()
} {
c'8 8 8 8 8 8 8 8
}
\new Staff {
c'8 8 8 8 8 8 8 8
}
>>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
