Hi Andrew,
sorry that I was confused by your example (which actually was *not*
"minimal", with the excess information being actively misleading. The
keyword "breakable" in combination with the explicit beams made me
think you were after a broken beam, not also about the line break.)
OK: You can
On 2020-08-01 9:03 pm, Andrew Bernard wrote:
Ah, is it to do with the tuplet not being breakable?
Nope. It's because there was no barline to break at.
Try: \bar "" \break
Remember that your \tuplet 7/8 is scaling note durations.
You could do this instead and see that you do not need to
Ah, is it to do with the tuplet not being breakable?
On Sun, 2 Aug 2020 at 14:00, Andrew Bernard wrote:
>
> Sorry, but if you remove the explicit beam the same issue remains. I
> am stumped. I am unable to understand your comment about 'at note
> heads. Surely the break can only occur between
Sorry, but if you remove the explicit beam the same issue remains. I
am stumped. I am unable to understand your comment about 'at note
heads. Surely the break can only occur between notes?
On Sun, 2 Aug 2020 at 13:37, Urs Liska wrote:
>
> Ah no, much simpler: If you ask LilyPond to print an
Ah no, much simpler: If you ask LilyPond to print an explicit beam it
will print an explicit beam ;-)
Am Sonntag, den 02.08.2020, 05:35 +0200 schrieb Urs Liska:
> Am Sonntag, den 02.08.2020, 13:32 +1000 schrieb Andrew Bernard:
> > \version "2.21.4"
> >
> >
> >
> > {
> >
> > \time 7/8
> >
>
Am Sonntag, den 02.08.2020, 13:32 +1000 schrieb Andrew Bernard:
> \version "2.21.4"
>
>
>
> {
>
> \time 7/8
>
> \set Timing.measureLength = #(ly:make-moment 1/4)
>
> \override Beam.breakable = ##t
>
> \tuplet 7/8 {
>
> b'16[ b' b' b'
>
> \break
>
> c'' c'' c'']
>
>
Why won't this let me break the beam?
Andrew
%
\version "2.21.4"
{
\time 7/8
\set Timing.measureLength = #(ly:make-moment 1/4)
\override Beam.breakable = ##t
\tuplet 7/8 {
b'16[ b' b' b'
\break
c'' c'' c'']
} |
}
%
David Kastrup writes:
> Thomas Morley writes:
>
>> Hi,
>>
>> the following code generates outlined nested pdf-marks, see attached.
>>
>> \version "2.21.4"
>>
>> \book {
>> \markuplist \table-of-contents
>> \tocItem x #"foo"
>> \tocItem x.y #"foo-1"
>> { R1 }
>> }
>>
>> Though, if I
Thomas Morley writes:
> Hi,
>
> the following code generates outlined nested pdf-marks, see attached.
>
> \version "2.21.4"
>
> \book {
> \markuplist \table-of-contents
> \tocItem x #"foo"
> \tocItem x.y #"foo-1"
> { R1 }
> }
>
> Though, if I switch from \book to \bookpart pdf-marks are
Hi,
the following code generates outlined nested pdf-marks, see attached.
\version "2.21.4"
\book {
\markuplist \table-of-contents
\tocItem x #"foo"
\tocItem x.y #"foo-1"
{ R1 }
}
Though, if I switch from \book to \bookpart pdf-marks are gone (while
the table-of-content is still
10 matches
Mail list logo