[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Different beaming for triplets
From: |
Richard Shann |
Subject: |
Re: Different beaming for triplets |
Date: |
Wed, 04 Dec 2013 18:46:26 +0000 |
On Wed, 2013-12-04 at 19:05 +0100, David Kastrup wrote:
> Richard Shann <address@hidden> writes:
>
> > Thank you David (and to the others that replied), I had a go at
> > getting my head round this before I asked, I find it a serious
> > challenge.
>
> Yes.
>
> > It would be nice to have a graphical way of selecting what you want
> > visually and letting the computer do the hard work...
>
> > Your new 2.19 syntax certainly looks an improvement!
>
> Note:
>
> >> \beamExceptions { 8[ 8 8] | \repeat unfold 3 \tuplet 3/2 { 16[ 16 16] } }
> rather than
> >> #'((end . (((1 . 8) . (3)) ((1 . 24) . (3 3 3)))))
>
> Well, you can also write
>
> \beamExceptions { c8[ c c] | \repeat unfold 3 \tuplet 3/2 { c16[ c c] } }
>
> which will look more familiar. But I am rather fond of the 2.19 way of
> being able to enter rhythms without the distraction of pitches.
Ha! I had just been mulling this over when you emailed. It looks like we
could offer a Denemo command to extract beam exceptions from the current
selection just by copying its LilyPond representation into a
\beamExceptions parameter. I was just trying to track down
\beamExceptions in the unstable documentation but that seems only to go
as far as 2.17 and you mentioned 2.19. I guess the documentation, such
as it is, is still in the devel-discussions (naturally). Well, all in
good time.
Richard
RE: Different beaming for triplets, Mark Stephen Mrotek, 2013/12/04
Message not available