bug-lilypond
[Top][All Lists]
Advanced

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

Re: Serious bugs in figured bass in Lilypond 2.7.17


From: Erik Sandberg
Subject: Re: Serious bugs in figured bass in Lilypond 2.7.17
Date: Thu, 24 Nov 2005 11:01:44 +0100
User-agent: KMail/1.8.3

On Tuesday 22 November 2005 16.58, liang seng wrote:
> Hi, I've been using Lilypond 2.7.17 for Windows to take advantage of its
> support for figured bass. However, I discovered several problems and bugs
> which I hope can be fixed.
> Here is the file for your reference:\version "2.7.17"
>
> 1. The first problem concerns multiple extender lines that are stacked
> vertically. Normally, when we want more than one extender line, we use the
> method as outlined in the manual.
> However, there seems to be some serious bugs. In bars 32, 35 and 115, there
> are supposed to be two extender lines extending from each of the figured
> bass numbers. But as you can see, there is only one extender line.
> Plus, the extender line extends from the midway point between the two
> figures.

Can you please isolate this to a short example? (something like 1 bar)

> 2. In instances where two or more extender lines are in place, sometimes
> their horizontal positions are not aligned to one another. This can be seen
> in bars 40, 42, 61 and 115.
> Here, the extender lines are misaligned even though their lengths are the
> same. This is of course not a bug because the misalignment is caused by the
> addition of figured bass accidentals beside the numbers which shifted the
> horizontal position of the extender lines.

I think it's a bug; at least the right edges of the extender lines should be 
aligned.

This can easily be reduced to the following example:

\version "2.7.18"
\layout {raggedright=##t}
\new FiguredBass \figuremode { 
  \set useBassFigureExtenders = ##t 
  \set figuredBassAlterationDirection = #1
  \set figuredBassPlusDirection = #1
  <3+ 5> <3+ 5>
}

The reason why we prefer short examples is not only because we're lazy. It 
happens that the bugs actually aren't bugs, but rather errors made by the bug 
reporter. Such errors are often easily detected while reducing the bug 
reports.

-- 
Erik




reply via email to

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