lilypond-auto
[Top][All Lists]
Advanced

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

Re: [Lilypond-auto] Issue 3475 in lilypond: Malformed tuplet bracket whe


From: lilypond
Subject: Re: [Lilypond-auto] Issue 3475 in lilypond: Malformed tuplet bracket when contents don't fit the duration
Date: Thu, 03 Apr 2014 18:21:32 +0000

Updates:
        Summary: Malformed tuplet bracket when contents don't fit the duration

Comment #1 on issue 3475 by address@hidden: Malformed tuplet bracket when contents don't fit the duration
http://code.google.com/p/lilypond/issues/detail?id=3475

The crash was a manifestation of issue 3551: crashing when the tuplet lacks a bound. It was fixed in 2.17.27:

commit 31cae8bae49aedd898210420cb5ccb10f34213f3
Author: Keith OHara <address@hidden>
Date:   Sun Sep 15 22:58:07 2013 -0700

    Tuplets: error-checking;  issue 3551

    lily/tuplet-engraver.cc
      do not create a TupletBracket if it would have no bounds
    lily/tuplet-bracket.cc
      defensive pointer check

However, the last bracket is still unterminated, which causes other problems, e.g. it can extend over subsequent notes:

\relative { \tuplet 3/2 4 { d'16 e f g a b c,16 d e f g a b, c d } e16 f g4 }

I'm not sure \tuplet should warn about incomplete groups when there's an explicit length. It's plausible to use that for a long series of tuplets with the last one incomplete, as in the example above (although it's easy to suppress the warning by splitting the \tuplet). It shouldn't warn with \tupletSpan, at least not when the tuplet is less than one group long, since that's common and harder to suppress.

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings



reply via email to

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