Re: no viable initial configuration found: may not find good beam slope

[TamuraJun]

Thanks Jean, for your prompt response.

Here is an example.

This is a part of the piece I’m type setting now - J. S. Bach’s Sonata for Flute and Harpsichord in B minor BWV 1030. Bar 13 of the harpsichord part of the second movement. I’m literally following Neue Bach Ausgabe (Bärenreiter) edition for the stem directions.

MWE.ly
Description: Binary data

MWE.pdf
Description: Adobe PDF document

2022/08/13 17:44、Jean Abou Samra <jean@abou-samra.fr>のメール:

Le 13/08/2022 à 10:27, TamuraJun a écrit :

Hello,

This could be a question that has been asked in the list for zillion times but I can’t find a good answer from the archive.

I see the subject warning message often when engraving keyboard music with cross-staff beaming. I believe that what i need to do is to widen the distance between two keyboard staves for a specific system causing the subject warning. What is the best way to direct Lilypond to do so? I’d like to keep all the default behaviors of staff distance calculation except for the system having the subject warning, if possible.

Thanks in advance.

Jun

In my experience, when this warning occurs, it is most frequently
because something is wrong with the stem directions, e.g.,

\version "2.22.2"

<<
  \new Staff = up { \voiceTwo c'8 \change Staff = down \voiceOne a''8 8 8 }
  \new Staff = down { s2 }
>>

For me, changing the directions (with \voiceXXX or \stemUp/\stemDown)
has allowed a good-looking beam without changing spacing in most cases.

Best,
Jean