Hi Michael, TL;DR: It's intended.
As the name implies, "FULL measure rests" are supposed to span full measures. In particular, they are always rendered as if they do, so your input should be virtually indistinguishable from R1. And it's also indistinguishable from R1. in 3/2 time, or R1*2 in 4/2 time, and so on.
Hence, to avoid confusion for the reader, FULL measure rests really need to span FULL measures:
"The duration in a multi-measure rest must always be an integral number of measure-lengths [...]"
http://lilypond.org/doc/v2.18/Documentation/notation/writing-rests#full-measure-restsWhile this page does not explicitly state that bar checks are implicitly added around full measure rests, the last line of the section gives a hint to that effect:
"When a multi-measure rest immediately follows a \partial setting, resulting bar-check warnings may not be displayed."
HTH, Alex On 21.05.19 12:51, Michael Gerdau wrote:
Hi list,
the following MWE triggers a barcheck failure. Is that intended or a bug?
And if it is intended I'd like to understand the rationale.
%%%%%%%%%%%%%
\version "2.21.0"
{ R1*3/4 s4 | }
%%%%%%%%%%%%%
Kind regards,
Michael
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
