Yes, it is indeed the same problem, except that I added yet another layer
of complication to it - I am NOT using \new FiguredBass, but only
\figuremode, because I don't want the figures to be horizontally aligned.
But maybe there is a possibility of achieving the same effect in \new
FiguredBass, does anyone know? If yes, let me know! But in either case, the
figures are not centered over the notes and the workarounds Werner found
don't seem to work as intended (with them the figures are too far to the
right). Here's a snippet to show the problem:
\version "2.24.4"
% this is the "official" solution
\new Staff <<
{ \clef "bass" c8 f g b d' d b4 }
\new FiguredBass \figuremode {
<5>8 <6> <7> <6 5> <3 4>8 <6> <6>
}
>>
% this is what I prefer - the figures follow the bass line, instead of
being all on the same level
\new Staff <<
{ \clef "bass" c8 f g b d' d b4 }
\figuremode {
<5>8 <6> <7> <6 5> <3 4>8 <6> <6>
}
>>
% with the workarounds, it's too far to the right
\new Staff <<
{ \clef "bass" c1 d c }
\new FiguredBass \figuremode {
\override BassFigure.X-offset =
#ly:self-alignment-interface::aligned-on-x-parent
\override BassFigure.parent-alignment-X = #CENTER
%\override BassFigure.X-align-on-main-noteheads = ##t
<5>1 <6 4+ 2\+> <6>
}
>>
On Thu, Dec 18, 2025 at 5:18 AM Werner LEMBERG <[email protected]> wrote:
>
> >> Apparently at some point the font for figured bass has been changed
> >> to smaller one -
>
> Yes, and this has been documented:
>
> https://lilypond.org/doc/v2.24/Documentation/changes/index.html
>
> >> I think in the process the horizontal position of the figures
> >> hasn't been adjusted and they appear slightly off-center (too much
> >> to the left), which is not really aesthetically satisfying. I
> >> wonder if there's a way of fixing this?
>
> I guess this is issue
>
> https://gitlab.com/lilypond/lilypond/-/issues/3172
>
> Some workrounds are given there, but the fundamental problem in the
> code is not fixed yet.
>
> > For those of us who are not Figured Bass experts, but are pretty
> > good at LilyPond, it would be nice to have a small example that
> > showed the problem. Then we could modify the code to try to fix it,
> > instead of having to write the code first, then try to fix it.
>
> Yeah, especially to check whether the problem is not the same as issue
> #3172.
>
>
> Werner
>
