Re: Length-1 tuplets crash LilyPond (with strict-note-spacing & tupletFullLength)

Thanks for the confirmation of version, Simon. For what it's worth, the bad output is no problem in actual scores because other layout settings will be used to space everything correct, move time signatures around and so on. It's only the crashing of the system that is a problem. Also, the

Re: Length-1 tuplets crash LilyPond (with strict-note-spacing & tupletFullLength)

On 20.09.2015 19:07, Trevor Bača wrote: Thanks for the confirmation of version, Simon. For what it's worth, the bad output is no problem in actual scores because other layout settings will be used to space everything correct, move time signatures around and so on. It's only the crashing of

Re: Length-1 tuplets crash LilyPond (with strict-note-spacing & tupletFullLength)

Simon Albrecht writes: > On 16.09.2015 23:04, Trevor Bača wrote: >> \version "2.19.27" >> >> \layout { >> \context { >> \Score >> \override SpacingSpanner #'strict-note-spacing = ##t >> tupletFullLength = ##t >> } >> } >> >> \new Staff

Length-1 tuplets crash LilyPond (with strict-note-spacing & tupletFullLength)

Hi, I've been using length-1 tuplets in my music recently. (Length-1 tuplets being tuplets with only a single note or rest.) It's quite wonderful that Lily handles these things correctly (just like how the system handles unusual time signatures like 1/12 and 5/14, too). But I've now uncovered a

Re: Length-1 tuplets crash LilyPond (with strict-note-spacing & tupletFullLength)

On 16.09.2015 23:04, Trevor Bača wrote: \version "2.19.27" \layout { \context { \Score \override SpacingSpanner #'strict-note-spacing = ##t tupletFullLength = ##t } } \new Staff { \time 1/8 \times 2/3 { c'8. } \time 5/8