[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cross staff notes collide

From: Evan Laforge
Subject: Re: cross staff notes collide
Date: Tue, 9 Apr 2013 15:15:41 -0700

On Tue, Apr 9, 2013 at 1:54 PM, Phil Holmes <address@hidden> wrote:
> "Evan Laforge" <address@hidden> wrote in message
> news:address@hidden
>>>>> It's not automatic - you have control.  Try using voices, and
>>>>> checking the output for error messages:
>>>> Right, it's easy to fix manually, \stemUp works too.  But that goes
>>>> for all collision / ugliness bugs.  The ideal is that it automatically
>>>> finds the prettiest possible way to lay things out, yes?
>>> That is consistent with the instructions it has been given.
>> Indeed, but I didn't give it any stem direction instructions, it picks
>> the colliding direction on its own.
> Using standard stem direction methods.
> We've told you how to correct your error.  What's your issue?

This is not my error, it's lilypond's error.  Additionally, the point
is not that it's possible to manually fix the problem.  It's possible
to manually fix all placement problems.

If the problem is that it's too hard to figure out stem direction
automatically, that's one thing. "Hard to fix" is not a reason to not
file a bug, but it might influence my motivation to go try and fix it
myself.  If the problem is that there's a policy of basing stem
direction only on pitch and not potential collisions, that's another
thing, and would be an interesting thing to talk about.

C'mon guys, there's no need to be defensive.  What other software does
and how much it costs is not relevant.

On Tue, Apr 9, 2013 at 2:51 PM, Janek Warchoł <address@hidden> wrote:
> However, i agree that in case of voices crossing staves, it might be
> not possible to reliably decide how they should be laid out.

Well, it's not possible in general to get all layout perfect from a
human's point of view.  But the closer to the ideal the better.

> In other words, i don't expect this to be solved anytime soon.

Perhaps not, but that's not a reason to not file a bug, and not a
reason to not look into a fix, though it might be a reason to
eventually give up on a fix.

Although your example looks fine to me, since nothing is actually
colliding with anything else.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]