snippet multi-measure-rest-markup.ly and use of s1*0
Hi
I have two different questions (quite related to each other)
1) In NR 1.2.2, Full measure rests
The snippet multi-measure-rest-markup.ly says:
Markups attached to a multi-measure rest will be centered above or
below it. Long markups attached to multi-measure rests do not cause the
measure to expand. To expand a multi-measure rest to fit the markup, use
a spacer rest with an attached markup before the multi-measure rest.
Note that the spacer rest causes a bar line to be inserted.
I cannot understand the last sentence.
I cannot see any change in the bar lines if I comment the spacer rests.
2) Should s1*0 be replaced by (see issue 2522)?
Two snippets still use s1*0
$ cd Documentation/snippets
$ git grep 's1\*0'
multi-measure-rest-markup.ly: s1*0^\markup { [MAJOR GENERAL] }
multi-measure-rest-markup.ly: s1*0_\markup { \italic { Cue: ... it is
yours } }
multi-measure-rest-markup.ly: s1*0^\markup { A }
positioning-segno-and-coda-with-line-break.ly:% | s1*0^\markup {
D.S. al
positioning-segno-and-coda-with-line-break.ly:% | s1*0^\markup {
\center
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: snippet multi-measure-rest-markup.ly and use of s1*0
Federico Bruni wrote Sunday, December 30, 2012 11:35 AM I have two different questions (quite related to each other) 1) In NR 1.2.2, Full measure rests The snippet multi-measure-rest-markup.ly says: Markups attached to a multi-measure rest will be centered above or below it. Long markups attached to multi-measure rests do not cause the measure to expand. To expand a multi-measure rest to fit the markup, use a spacer rest with an attached markup before the multi-measure rest. Note that the spacer rest causes a bar line to be inserted. I cannot understand the last sentence. I cannot see any change in the bar lines if I comment the spacer rests. Neither can I. I can't remember what I meant by this. I guess that sentence should be deleted. 2) Should s1*0 be replaced by (see issue 2522)? Two snippets still use s1*0 Yes. Will you submit a revised snippet, or shall I? Trevor ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: snippet multi-measure-rest-markup.ly and use of s1*0
On Sun, Dec 30, 2012 at 6:35 AM, Federico Bruni fedel...@gmail.com wrote: Hi I have two different questions (quite related to each other) 1) In NR 1.2.2, Full measure rests The snippet multi-measure-rest-markup.ly says: Markups attached to a multi-measure rest will be centered above or below it. Long markups attached to multi-measure rests do not cause the measure to expand. To expand a multi-measure rest to fit the markup, use a spacer rest with an attached markup before the multi-measure rest. Note that the spacer rest causes a bar line to be inserted. I cannot understand the last sentence. I cannot see any change in the bar lines if I comment the spacer rests. Greetings, Federico and other LilyPonders - Please forgive me, but I cannot see how I can comment out the spacer rests without either commenting out the \markup s or replacing the spacer rests with . Am I missing something? Ralph ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: snippet multi-measure-rest-markup.ly and use of s1*0
On Sun, Dec 30, 2012 at 6:35 AM, Federico Bruni fedel...@gmail.com wrote:
2) Should s1*0 be replaced by (see issue 2522)?
Two snippets still use s1*0
$ cd Documentation/snippets
$ git grep 's1\*0'
multi-measure-rest-markup.ly: s1*0^\markup { [MAJOR GENERAL] }
multi-measure-rest-markup.ly: s1*0_\markup { \italic { Cue: ... it is
yours } }
multi-measure-rest-markup.ly: s1*0^\markup { A }
positioning-segno-and-coda-**with-line-break.lyhttp://positioning-segno-and-coda-with-line-break.ly:
% | s1*0^\markup { D.S. al
positioning-segno-and-coda-**with-line-break.lyhttp://positioning-segno-and-coda-with-line-break.ly:
% | s1*0^\markup { \center
Greetings, Federico and other LilyPonders -
I agree that it looks like these are candidates for , but I don't believe
they belong on the Bug List. Would you like to write new snippets,
Federico? The same goes for anyone else out there who's ambitious.
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: snippet multi-measure-rest-markup.ly and use of s1*0
Il 30/12/2012 14:06, Trevor Daniels ha scritto: Note that the spacer rest causes a bar line to be inserted. I cannot understand the last sentence. I cannot see any change in the bar lines if I comment the spacer rests. Neither can I. I can't remember what I meant by this. I guess that sentence should be deleted. 2) Should s1*0 be replaced by (see issue 2522)? Two snippets still use s1*0 Yes. Will you submit a revised snippet, or shall I? Please go ahead. I've logged in the LSR website but I cannot modify the snippets. Who said that web interfaces are easier than git? :) -- Federico ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: snippet multi-measure-rest-markup.ly and use of s1*0
Federico Bruni wrote Sunday, December 30, 2012 3:00 PM Il 30/12/2012 14:06, Trevor Daniels ha scritto: Will you submit a revised snippet, or shall I? Please go ahead. I've logged in the LSR website but I cannot modify the snippets. Who said that web interfaces are easier than git? :) It's not :( You have to copy out the snippet, edit it and resubmit. However, as it was mine originally I may be able to modify it. I'll try. Trevor ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: snippet multi-measure-rest-markup.ly and use of s1*0
2012/12/30 Federico Bruni fedel...@gmail.com: Il 30/12/2012 14:06, Trevor Daniels ha scritto: Note that the spacer rest causes a bar line to be inserted. I cannot understand the last sentence. I cannot see any change in the bar lines if I comment the spacer rests. Neither can I. I can't remember what I meant by this. I guess that sentence should be deleted. 2) Should s1*0 be replaced by (see issue 2522)? Two snippets still use s1*0 Yes. Will you submit a revised snippet, or shall I? Please go ahead. I've logged in the LSR website but I cannot modify the snippets. Who said that web interfaces are easier than git? :) -- Federico ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond Hi Federico, I followed this discussion only cursorily. If there's need to alter a LSR-snippet I could do it for you. Please send me revised version. BTW, you can alter LSR-snippets yourself, only if you have the permission to do so. -Harm ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: snippet multi-measure-rest-markup.ly and use of s1*0
Il 30/12/2012 16:21, Thomas Morley ha scritto:
Hi Federico,
I followed this discussion only cursorily.
If there's need to alter a LSR-snippet I could do it for you. Please
send me revised version.
Maybe Trevor is already working on it.
Anyway, find files attached
BTW, you can alter LSR-snippets yourself, only if you have the
permission to do so.
I read here:
http://lsr.di.unimi.it/LSR/html/contributing.html
that you can only edit your own snippets.
Creating a new snippet to propose a revision looks like a waste of time...
--
Federico
\version 2.14.2
\header {
texidoc =
Markups attached to a multi-measure rest will be centered above or
below it. Long markups attached to multi-measure rests do not cause
the measure to expand. To expand a multi-measure rest to fit the
markup, use an empty chord with an attached markup before the
multi-measure rest.
Text attached to an empty chord in this way is left-aligned to the position
where the note would be placed in the measure, but if the measure
length is determined by the length of the text, the text will appear to
be centered.
doctitle = Multi-measure rest markup
}
\relative c' {
\compressFullBarRests
\textLengthOn
^\markup { [MAJOR GENERAL] }
R1*19
_\markup { \italic { Cue: ... it is yours } }
^\markup { A }
R1*30^\markup { [MABEL] }
\textLengthOff
c4^\markup { CHORUS } d f c
}
\version 2.14.2
\header {
texidoc =
If you want to place an exiting segno sign and add text like @qq{D.S.
al Coda} next to it where usually the staff lines are you can use this
snippet. The coda will resume in a new line. There is a variation
documented in this snippet, where the coda will remain on the same
line.
doctitle = Positioning segno and coda (with line break)
}
{
\clef treble
\key g \major
\time 4/4
\relative c'' {
\repeat unfold 4 {
c4 c c c
}
% Set segno sign as rehearsal mark and adjust size if needed
% \once \override Score.RehearsalMark #'font-size = #3
\mark \markup { \musicglyph #scripts.segno }
\repeat unfold 2 {
c4 c c c
}
% Set coda sign as rehearsal mark and adjust size if needed
\once \override Score.RehearsalMark #'font-size = #4
\mark \markup { \musicglyph #scripts.coda }
\repeat unfold 2 {
c4 c c c
}
% Should Coda be on anew line?
% Coda NOT on new line: use \nobreak
% Coda on new line: DON'T use \nobreak
% \noBreak
\bar ||
% Set segno sign as rehearsal mark and adjust size if needed
\once \override Score.RehearsalMark #'break-visibility = #begin-of-line-invisible
% \once \override Score.RehearsalMark #'font-size = #3
\mark \markup { \musicglyph #scripts.segno }
% Here begins the trickery!
% \cadenzaOn will suppress the bar count and \stopStaff removes the staff lines.
\cadenzaOn
\stopStaff
% Some examples of possible text-displays
% text line-aligned
% ==
% Move text to the desired position
% \once \override TextScript #'extra-offset = #'( 2 . -3.5 )
% | ^\markup { D.S. al Coda } }
% text center-aligned
%
% Move text to the desired position
% \once \override TextScript #'extra-offset = #'( 6 . -5.0 )
% | ^\markup { \center-column { D.S. al Coda } }
% text and symbols center-aligned
% ===
% Move text to the desired position and tweak spacing for optimum text alignment
\repeat unfold 1 {
s1
\bar
}
\once \override TextScript #'extra-offset = #'( 0 . -3.0 )
\once \override TextScript #'word-space = #1.5
^\markup { \center-column { D.S. al Coda \line { \musicglyph #scripts.coda \musicglyph #scripts.tenuto \musicglyph #scripts.coda} } }
% Increasing the unfold counter will expand the staff-free space
\repeat unfold 3 {
s1
\bar
}
% Resume bar count and show staff lines again
\startStaff
\cadenzaOff
% Should Coda be on new line?
% Coda NOT on new line: DON'T use \break
% Coda on new line: use \break
\break
% Show up, you clef and key!
\once \override Staff.KeySignature #'break-visibility = #end-of-line-invisible
\once \override Staff.Clef #'break-visibility = #end-of-line-invisible
% Set coda sign as rehearsal mark and adjust size and position
% Put the coda sign ontop of the (treble-)clef dependend on coda's line-position
% Coda NOT on new line, use this:
% \once \override Score.RehearsalMark #'extra-offset = #'( -2 . 1.75 )
% Coda on new line, use this:
\once \override Score.RehearsalMark #'extra-offset = #'( -4.5 . 0 )
\once \override Score.RehearsalMark #'font-size = #5
\mark \markup { \musicglyph #scripts.coda }
% The coda
\repeat unfold 5 {
Re: snippet multi-measure-rest-markup.ly and use of s1*0
Thomas Morley wrote Sunday, December 30, 2012 3:21 PM If there's need to alter a LSR-snippet I could do it for you. Please send me revised version. BTW, you can alter LSR-snippets yourself, only if you have the permission to do so. Thanks, Harm, but I've already done it. It was my snippet, so I could change it easily. Trevor ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: snippet multi-measure-rest-markup.ly and use of s1*0
2012/12/30 Federico Bruni fedel...@gmail.com: Il 30/12/2012 16:21, Thomas Morley ha scritto: Hi Federico, I followed this discussion only cursorily. If there's need to alter a LSR-snippet I could do it for you. Please send me revised version. Maybe Trevor is already working on it. Anyway, find files attached BTW, you can alter LSR-snippets yourself, only if you have the permission to do so. I read here: http://lsr.di.unimi.it/LSR/html/contributing.html that you can only edit your own snippets. Not sure if you can edit your own snippet after it's approved. Creating a new snippet to propose a revision looks like a waste of time... -- Federico I changed Positioning segno and coda (with line break) http://lsr.dsi.unimi.it/LSR/Item?id=190 Multi-measure rest markup http://lsr.dsi.unimi.it/LSR/Item?id=587 was altered already. Maybe Trevor was faster. :) -Harm ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
