Dear all,
I’m vainly struggling with a weird spacing problem that I’ve never seen before:
the dot belonging to, for instance, c’2. is widely separated from the note
itself. (See screenshot).
In this section the horizontal note spacing is also rather capricious. ( \time
3/4 for the entire
On 6/3/20, Robert Blackstone wrote:
> I’m vainly struggling with a weird spacing problem
Hi Robert,
Unless you post some code, it’s gonna be difficult to help you. You
should first double check your source files in case there’s some
\override affecting the DotColumn object somewhere?
Che
Hi Valentin, Thanks for your interest in my problemThe piece, as you can see in the screenshot, is a piano score with two voices in each staff and occasionally a third voice by << { } \\ { } >> or \partcombine.I triple-checked my source code, first by hiding successively each voice, and see what
, 2020 10:27 AM
To: Valentin Villenave
Cc: Lilypond-User Mailing List
Subject: Re: A weird spacing problem
Hi Valentin,
Thanks for your interest in my problem
The piece, as you can see in the screenshot, is a piano score with two voices
in each staff and occasionally a third voice by
the previous bars.
>
> Thanks again for your interest.
>
> Best regards,
> Robert
>
>
>
> On 3 Jun 2020, at 14:14, Valentin Villenave wrote:
>
> On 6/3/20, Robert Blackstone wrote:
>
> I’m vainly struggling with a weird spacing problem
>
>
> Hi Robe
On 6/3/20, Robert Blackstone wrote:
> Overall there are several instances where I needed "\once \override
> NoteColumn #'force-hshift = #x" , and a few "\once\override
> NoteColumn.X-offset = #x”.
Ouch. That’s pretty brutal. May I ask why you felt the need to use
all these? This alters drastic
On 6/3/20, Mark Stephen Mrotek wrote:
> When I set piano four part I let Lilypond do all the work.
Hear hear! (Even for more than four parts, btw.)
> I have taken the liberty of recoding the section using four-part voicing.
Yeah, so did I! That sure was tempting wasn’t it? :-)
Cheers,
-- V.
hows the problem. It also shows that its origin
> does not ly in the previous bars.
> Thanks again for your interest.
> Best regards,
> Robert
>
>
> On 3 Jun 2020, at 14:14, Valentin Villenave
> wrote:
> On 6/3/20, Robert Blackstone wrote:
> Hi Robert,
> Unless you post some code, it’s gonna be difficult to help you. You
> should first double check your source files in case there’s some
> \override affecting the DotColumn object somewhere?
> Cheers,
> -- V.
I’m vainly struggling with a weird spacing problem
