Carl Sorensen writes:
> On 7/2/18, 6:32 AM, "David Kastrup" wrote:
>
>
> I'll take a thorough look at this code. Looks like it could benefit
> from a more graphic approach to intersections than converting everything
> into zero-based polynomials and then doing root finding.
>
On 7/2/18, 6:32 AM, "David Kastrup" wrote:
I'll take a thorough look at this code. Looks like it could benefit
from a more graphic approach to intersections than converting everything
into zero-based polynomials and then doing root finding.
I probably have a link to som
Thomas Morley writes:
> Hi,
>
> the code below returns
> programming error: no solution found for Bezier intersection
> for 2.19.82 as well as for current master. 2.18.2 is ok.
Ok, as far as I can see that is just the consequence of massively
numerically naive coding.
Basica
> Starting program: /usr/local/tmp/lilypond/out/bin/lilypond /tmp/harm.ly
>> [Thread debugging using libthread_db enabled]
>> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
>> GNU LilyPond 2.21.0
>> Processing `/tmp/harm.ly'
&
lypond /tmp/harm.ly
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> GNU LilyPond 2.21.0
> Processing `/tmp/harm.ly'
> Parsing...
> Interpreting music...[8][16]
> Preprocessing graphical ob
arting program: /usr/local/tmp/lilypond/out/bin/lilypond /tmp/harm.ly
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
GNU LilyPond 2.21.0
Processing `/tmp/harm.ly'
Parsing...
Interpreting music...[8][16]
Preprocess
2018-07-01 21:13 GMT+02:00 David Kastrup :
> Colin Campbell writes:
>
>> On 2018-07-01 11:47 AM, Thomas Morley wrote:
>>> Hi,
>>>
>>> the code below returns
>>> programming error: no solution found for Bezier intersection
>>>
Colin Campbell writes:
> On 2018-07-01 11:47 AM, Thomas Morley wrote:
>> Hi,
>>
>> the code below returns
>> programming error: no solution found for Bezier intersection
>> for 2.19.82 as well as for current master. 2.18.2 is ok.
>>
>>
>>
On 2018-07-01 11:47 AM, Thomas Morley wrote:
Hi,
the code below returns
programming error: no solution found for Bezier intersection
for 2.19.82 as well as for current master. 2.18.2 is ok.
It's a heavily boiled down version of the original file (thus the
strange octaves).
Though I&
2018-07-01 19:47 GMT+02:00 Thomas Morley :
> Hi,
>
> the code below returns
> programming error: no solution found for Bezier intersection
> for 2.19.82 as well as for current master. 2.18.2 is ok.
>
> \version "2.19.82"
I was wrong with 2.18.2.
At least the strippe
Hi,
the code below returns
programming error: no solution found for Bezier intersection
for 2.19.82 as well as for current master. 2.18.2 is ok.
\version "2.19.82"
oneUp = \relative c' {
%\time 3/4
\voiceOne
1
q
q
q
q
r8
\times 2/3 { 16 q q }
q8 q q r8
r8
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 remov
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:
%==
\version "2.15.11"
\language "english"
fingering = {
\set fingeringOrientations = #'(left)
\set strokeFingerOrientations = #'
On 14/09/11 08:34, Trevor Daniels wrote:
Nick Payne wrote Tuesday, September 13, 2011 11:25 PM
The problem is that the score is quite large, and the log gives no
indication at all about where the error is coming from. I guess I can
try commenting out different sections to see if I can isolate
14 matches
Mail list logo
