Many thanks! Your manual shape override did the trick. I am new to LP and
honestly amazed how often it makes "pretty good" or great decisions.
Problems like this stand out for their rarity.
On Tue, Oct 20, 2020 at 3:59 AM Jean Abou Samra wrote:
>
> Le 20/10/2020 à 01:08, Marc Shepherd a écrit :
Le 20/10/2020 à 01:08, Marc Shepherd a écrit :
The reason the tuplet is up, is that — in the actual music, there is a
lower voice, so the tuplet /has to be/ up. I left out the lower voice
in my example, because it is not relevant to the behavior I am asking
about.
In the real score, I have n
The reason the tuplet is up, is that — in the actual music, there is a
lower voice, so the tuplet *has to be* up. I left out the lower voice in my
example, because it is not relevant to the behavior I am asking about.
In the real score, I have not overridden the tuplet and slur direction.
With the
Le 19/10/2020 à 23:43, Marc Shepherd a écrit :
In the example shown below, notice that the slur is incorrectly
pointing upward, and "crashing" into the tuplet bracket. It only
happens with both the slur and the beam present. With slur only or
beam only, it engraves correctly.
Is this a known
In the example shown below, notice that the slur is incorrectly pointing
upward, and "crashing" into the tuplet bracket. It only happens with both
the slur and the beam present. With slur only or beam only, it engraves
correctly.
Is this a known issue? Should I be coding it differently? The code u
