Re: Single Whole Measure Rest vs compressed MMR
On 28 February 2013 01:05, Thomas Morley thomasmorle...@googlemail.com wrote:
Hi Xavier,
do you think of sth like this:
(snip)
Hi Thomas,
Thank you for your answer.
I did not use the 'bound-padding property but I was overriding MMR
'minimum-length to different values corresponding to my needs.
Your 'bound-padding solution is interesting. I'm not used to
'before-line-breaking (and 'after-line-breaking) overrides and its
rather cryptic scheme expressions as values.
I'll keep that in mind for my future codes, thanks.
On 28 February 2013 01:37, Thomas Morley thomasmorle...@googlemail.com wrote:
BTW, you could print the MultiMeasureRestNumber on a single Whole
Measure Rest, too:
{ \set restNumberThreshold = #0 R1 }
Yes I knew that (and already used it).
One point in favor of the fact that single Whole Measure Rest and
compressed MMR are usually treated similarly.
Cheers,
Xavier
--
Xavier Scheuer x.sche...@gmail.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Single Whole Measure Rest vs compressed MMR
On 28 February 2013 05:25, Werner LEMBERG w...@gnu.org wrote: As far as I know, they are treated similarly. OK, thanks. Why should there be a difference? The idea of having compressed MMRs is to save horizontal space, isn't it? I did not claim there should be a difference, I was asking the question. IIRC I increased the horizontal space of compressed MMR in order to prevent overlapping of tempo indications in a piece for an instrument part with many MMR (similar to what Kieren is also asking/fighting AFAIK). I also used it as a workaround because full measure rests take too little horizontal space compared to notes (issue 1798, still open as issue 3135). http://code.google.com/p/lilypond/issues/detail?id=3135 Can you show us some literature scans which supports your claim? I can't, that's why I was asking the question (but instrument parts with lots of MMR and tempo indications still needs careful thinking). Since it seems single Whole Measure Rest and compressed MMR are usually treated similarly, sorry for the noise. Thank you for your consideration. Cheers, Xavier -- Xavier Scheuer x.sche...@gmail.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Single Whole Measure Rest vs compressed MMR
IIRC I increased the horizontal space of compressed MMR in order to prevent overlapping of tempo indications in a piece for an instrument part with many MMR (similar to what Kieren is also asking/fighting AFAIK). Aah, but this is a different problem (which can be very annoying, I know). Werner ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Single Whole Measure Rest vs compressed MMR
2013/3/4 Xavier Scheuer x.sche...@gmail.com:
On 28 February 2013 01:05, Thomas Morley thomasmorle...@googlemail.com
wrote:
Hi Xavier,
do you think of sth like this:
(snip)
Hi Thomas,
Thank you for your answer.
I did not use the 'bound-padding property but I was overriding MMR
'minimum-length to different values corresponding to my needs.
Your 'bound-padding solution is interesting. I'm not used to
'before-line-breaking (and 'after-line-breaking) overrides and its
rather cryptic scheme expressions as values.
Hi Xavier,
'bound-padding and 'minimum-length are not the same, but seem to work
similiar here. Good to know both.
Actually there is no need to use 'before-line-breaking here. Setting
the 'minimum-length diectly works (see code below).
I'm used to start such coding by using the 'before-line-breaking or
'after-line-breaking-properties, because these properties offer a
wider range of possibilities.
And I don't think it's very cryptic.
The example from the Extending-manual has nearly the same structure.
http://lilypond.org/doc/v2.16/Documentation/extending/callback-functions
Well, ok, I know there are several scheme-haters ...
Here a modified, commented code:
\version 2.16.2
mmrLngth =
\override MultiMeasureRest #'minimum-length =
#(lambda (grob) ;; 'minimum-length is set to a scheme-procedure,
starting here.
;; Defining some local variables.
(let* (;; Read-out the 'measure-count-property.
;; Call it measure-count
(measure-count (ly:grob-property grob 'measure-count))
;; Choose different numbers depending on measure-count.
;; Call it lngth
(lngth (if ( measure-count 1)
30;; bound-padding for compressed MMR
15))) ;; bound-padding for single MMR
;; Set the 'minimum-length-property to lngth
;; via the predefined `ly:grob-set-property!`
(ly:grob-set-property! grob 'minimum-length lngth)))
\relative c' {
\mmrLngth
\compressFullBarRests
R1*20
R1
}
Regards,
Harm
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Single Whole Measure Rest vs compressed MMR (WAS: Issue 3208 Wrong MultiMeasureRest glyph)
2013/2/28 Xavier Scheuer x.sche...@gmail.com:
On 27 February 2013 18:13, lilyp...@googlecode.com wrote:
Comment #1 on issue 3208 by philehol...@googlemail.com: Wrong
MultiMeasureRest glyph
http://code.google.com/p/lilypond/issues/detail?id=3208
OK - let's just be clear about what the bug is. Lilypond does the right
thing (TM) for single Whole Measure Rests - breve rests and longa rests are
correct. It does the wrong thing for multimeasure rests, where what it uses
for 2 breve bar rests (staff system 2 above) it uses the symbol for a 4 bar
church rest. That's wrong, agreed, and needs fixing.
This reminds me of a question/issue I never asked here.
I sometimes wanted different horizontal space settings for single Whole
Measure Rest and real multimeasure rests a.k.a compressed MMR
(with a number above).
Hi Xavier,
do you think of sth like this:
\version 2.17.12
boundPadding =
\override MultiMeasureRest #'before-line-breaking =
#(lambda (grob)
(let* ((measure-count (ly:grob-property grob 'measure-count))
(b-p (if ( measure-count 1)
20;; bound-padding for single MMR
15))) ;; bound-padding for compressed MMR
(ly:grob-set-property! grob 'bound-padding b-p)))
{
\boundPadding
R1
\repeat unfold 20 { c'' }
}
{
\boundPadding
\compressFullBarRests
R1*5
\repeat unfold 20 { c'' }
}
Cheers,
Harm
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Single Whole Measure Rest vs compressed MMR (WAS: Issue 3208 Wrong MultiMeasureRest glyph)
2013/2/28 Xavier Scheuer x.sche...@gmail.com:
I sometimes wanted different horizontal space settings for single Whole
Measure Rest and real multimeasure rests a.k.a compressed MMR
(with a number above).
Hi again.
BTW, you could print the MultiMeasureRestNumber on a single Whole
Measure Rest, too:
{ \set restNumberThreshold = #0 R1 }
-Harm
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Single Whole Measure Rest vs compressed MMR
1. Are single Whole Measure Rest and compressed MMR two different things, and treated as such, with specific rules, etc. in references like Ross, Read, Gould? As far as I know, they are treated similarly. Why should there be a difference? The idea of having compressed MMRs is to save horizontal space, isn't it? Can you show us some literature scans which supports your claim? Werner ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
