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. Kevin On Thu, Aug 20, 2015 at 8:41 AM, Phil Holmes <m...@philholmes.net> wrote: > "Simon Albrecht" <simon.albre...@mail.de> wrote in message > news:55d51b39.2010...@mail.de... >> >> 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 > bug-lilypond@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-lilypond _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
