lilypond-user
[Top][All Lists]
Advanced

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

Re: programming error: no solution found for Bezier intersection


From: Reinhold Kainhofer
Subject: Re: programming error: no solution found for Bezier intersection
Date: Wed, 14 Sep 2011 11:59:03 +0200
User-agent: KMail/1.13.6 (Linux/2.6.38-11-generic; KDE/4.7.0; i686; ; )

Am Wednesday, 14. September 2011, 06:47:50 schrieb Colin Campbell:
> On 11-09-13 09:29 PM, Nick Payne wrote:
> > Ok, the following small example reproduces the error on my system with
> > 2.15.11:

The minimal example is (the normal fingering "-1" does not have any influence, 
so it should be removed, too, and the language is also not relevant):
%======================================
\version "2.15.11"

\relative c'' {
  \set strokeFingerOrientations = #'(up)
  \override StrokeFinger #'avoid-slur = #'outside
  <a-\rightHandFinger #2 >16( b)
}
%======================================

This example shows clearly that StrokeFinger is to blame here.

The warning appears only with #'avoid-slur=#'outside, not with 'inside. 
However, the actual value of strokeFingerOrientations is not relevant (as long 
as you set it to some value), the warning appears both with #'(up) and with 
#'(down).

> > If I get rid of the right hand fingering then the error goes away, and
> > if I comment out the override for StrokeFinger #'avoid-slur then the
> > error also goes away but the log contains the warning:
> > 
> > /home/nick/lilypond/examples/test.ly:14:13: warning: Ignoring grob for
> > slur: StrokeFinger. avoid-slur not set?
> > <as-1
> > 
> >              -\rightHandFinger #2 >16( b)

That's definitely a bug. The StrokeFinger seems to be missing the avoid-slur 
property (and there seems to be a regtest missing for StrokeFinger).

> Nick, one of our developers is working on Bezier range calculations:
> there is an open tracker item
> (http://code.google.com/p/lilypond/issues/detail?id=1784
> <http://code.google.com/p/lilypond/issues/detail?id=1784>) which sounds
> like your problem.

I guess only Mike Solomon can answer that question, since he didn't describe 
which problem he tries to solve with the patch...

Cheers,
Reinhold
-- 
------------------------------------------------------------------
Reinhold Kainhofer, address@hidden, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org



reply via email to

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