I was also wondering : shall we add another exception for half rests ? I ...
12 years, 10 months ago
(2011-05-17 22:10:29 UTC)
#3
I was also wondering : shall we add another exception for half rests ?
I always found this disturbing to have a whole rest in 2/4.
I know this is what traditional editors do, but...
If we do so, then it would be better and cleaner to make an alist of durations
instead of this mess.
And add a user-settable property "approximate-to-superior-rest".
This would be easier to understand than the current system.
On 5/17/11 4:10 PM, "bordage.bertrand@gmail.com" <bordage.bertrand@gmail.com> wrote: > I was also wondering : shall we ...
12 years, 10 months ago
(2011-05-17 22:32:58 UTC)
#4
On 5/17/11 4:10 PM, "bordage.bertrand@gmail.com"
<bordage.bertrand@gmail.com> wrote:
> I was also wondering : shall we add another exception for half rests ?
I do not think we should. A whole measure rest should be a whole rest,
regardless of the measure length, unless the measure is longer than 4/2.
Quoting Stone, p. 136 "Whole rests are used for a full-measure rest
regardless of the measure's actual duration... If, however, the total value
of a measure reaches eight quarters (4/2 measures), a double whole-rest
should be used."
Also, page 135 "Whole rests are used as full measure rests for all meters
less than 4/2 (see page 136)."
Footnote on page 135 "A number of composers have tried during recent years
to replace the "universal" whole-measure rests with rests that represent the
measures' acutal values, but these efforts have thus far failed to gain
widespread acceptance".
> I always found this disturbing to have a whole rest in 2/4.
> I know this is what traditional editors do, but...
>
> If we do so, then it would be better and cleaner to make an alist of
> durations instead of this mess.
>
> And add a user-settable property "approximate-to-superior-rest".
> This would be easier to understand than the current system.
If we want to create a non-standard capability, it would seem to me that the
user-settable property should be some kind of alist, rather than a boolean.
If you feel strongly enough about having this capability to code it, I'm
certainly willing to review patches, as long as the current behavior is
concerned.
Thanks,
Carl
I know these rules. They will always be LilyPond's default behavior. What I meant is ...
12 years, 10 months ago
(2011-05-17 23:51:27 UTC)
#5
I know these rules. They will always be LilyPond's default behavior.
What I meant is "if someone want to change this (for contemporary music or
anything else), it doesn't have to be difficult to do".
> If we want to create a non-standard capability, it would seem to me that the
> user-settable property should be some kind of alist, rather than a boolean.
Yes, that's what I meant : an alist of durations (or duration-logs) and a
boolean.
Because for now, when one sets use-breve-rest in a measure longer than a whole
and shorter than a breve, a breve is engraved.
It's only for this purpose that I suggested to add a boolean.
> If you feel strongly enough about having this capability to code it, I'm
> certainly willing to review patches, as long as the current behavior is
> concerned.
If you agree with what I just said, I'll start to implement it.
Issue 4543055: Handles longa in MultiMeasureRest
(Closed)
Created 12 years, 10 months ago by Bertrand Bordage
Modified 12 years, 9 months ago
Reviewers: Graham Percival (old account), c_sorensen
Base URL:
Comments: 0