[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: autoBeaming and \set measurePosition

From: Kevin Barry
Subject: Re: autoBeaming and \set measurePosition
Date: Thu, 20 Aug 2015 08:51:28 +0100

Tinkering with your example seems to suggest that any value that is
larger than the time signature will produce the unwanted behaviour.

That is, if you set the Timing.measurePosition to anything bigger than
the normal size of a bar in the current time signature, the beam
before the override is broken. It's odd for sure, but perhaps
understandable: you're effectively telling LilyPond that a 2/4 bar has
3 beats left, or that a 3/4 bar has 4 beats left. I'm not sure if I
would consider it a bug or not, but it's definitely undesirable.


On Thu, Aug 20, 2015 at 8:41 AM, Phil Holmes <address@hidden> wrote:
> "Simon Albrecht" <address@hidden> wrote in message
> news:address@hidden
>> I don’t quite know what I’m supposed to think of this: With 3/4, there
>> is no beam between the third and fourth quavers. It doesn’t happen with
>> -1/4, 0, 1/4, or 2/4. Doesn’t seem like this is going to appear in any
>> realistic scenario. Just ignore it?
>> Yours, Simon
> --------------------------------------------------------------------------------
> Simon,
> What are you trying to do with this example?
> Also, for trivially small examples (like this is) I think most people find
> it far easier to comment if you post the code in line, rather than as an
> attachment.  I certainly do.
> --
> Phil Holmes
> _______________________________________________
> bug-lilypond mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/bug-lilypond

reply via email to

[Prev in Thread] Current Thread [Next in Thread]