Solved. If one adds \voiceThree for the new voice for the tuplet 3/1, the
beaming all works as expected.
Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Here, if I use ordinary notes instead of grace notes, with proportional
notation enabled, the beaming produces notes in the wrong order. So, this
example, in which I have finally been able to prod the issue into appearing,
grace notes don’t actually come into it, they are all plain ordinary musi
Andrew Bernard writes:
> Hi Maite,
>
> Good suggestion. This is in fact exactly what I have been doing until
> now - including using the terrific slash function, thanks
> Ponderers!. But for some reason in my massively complex score which
> depends heavily on proportional notation, the beaming in
Hi Maite,
Good suggestion. This is in fact exactly what I have been doing until now -
including using the terrific slash function, thanks Ponderers!. But for some
reason in my massively complex score which depends heavily on proportional
notation, the beaming in this bar, at least under 2.19.25
Andrew Bernard writes:
> Hello Ponderers,
>
> My score has many places where a beamed set of grace notes start precisely on
> a note in a voice, and consequently overlap the first starting note. This is
> fine, and what the composer specifically intends (common notation in the New
> Complexity
Am 12.08.2015 um 08:13 schrieb Andrew Bernard:
In my example, I can’t get the start of the grace to sit on top of the note in
the other voice. Indeed, lilypond is being very excellent about avoiding a
collision, but I want to persuade it to align. I can achieve this with normal
notes, but no
Hello Ponderers,
My score has many places where a beamed set of grace notes start precisely on a
note in a voice, and consequently overlap the first starting note. This is
fine, and what the composer specifically intends (common notation in the New
Complexity School). The attached image shows a
