[prev in list] [next in list] [prev in thread] [next in thread]
List: lilypond-user
Subject: Re: RehearsalMark and MetronomeMark =?utf-8?b?dG9nZXRoZXLigKY=?= =?utf-8?b?YWdhaW7igKY=?=
From: Keith OHara <k-ohara5a5a () oco ! net>
Date: 2013-11-28 3:22:25
Message-ID: loom.20131128T041644-322 () post ! gmane ! org
[Download RAW message or body]
Kieren MacMillan <kieren_macmillan <at> sympatico.ca> writes:
> To be clear, \markLengthOn does not solve the problem.
>
Just for anybody searching the archives, what \markLengthOn *does* do
is space the music out to give room for the marks. So it helps when
the RehearsalMark and tempo are on different notes, barlines, etc:
\version "2.17.19"
{ \markLengthOn
\mark\default
\tempo "This is a really long tempo mark"
c''4 d'' e'' f''
\mark\default \tempo 4=60
g'' 1 }
A lot of people writing score-and-parts use Shevek's MarkLine context,
in which case it makes sense to include the essential bit of
\markLengthOn in the definition of MarkLine context:
\score { <<
\new MarkLine {
\mark \default
\tempo \markup "This is a really long tempo mark"
s1
\mark \default
\tempo 4=60
s1 }
\new Staff {
c''4 d'' e'' f''
g'' 1
} >>
\layout {
\context {
\name "MarkLine"
\type "Engraver_group"
\consists Axis_group_engraver
\consists Output_property_engraver
\consists Mark_engraver
\consists Metronome_mark_engraver
\consists Text_spanner_engraver
\consists Time_signature_engraver
\override TimeSignature #'stencil = #point-stencil
\override MetronomeMark #'Y-offset = #0
\override RehearsalMark #'Y-offset = #0
\override RehearsalMark #'extra-spacing-width = #'(0 . 0.5)
\override MetronomeMark #'extra-spacing-width = #'(0 . 1.5)
\override VerticalAxisGroup #'staff-staff-spacing = #'((padding . 1))
}
\context {
\Score
\remove Metronome_mark_engraver
\remove Mark_engraver
\accepts MarkLine } } }
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic