On 8/11/2019 3:55 PM, Víctor Manuel Ares Piñeiro via lilypond-user wrote:
Thank you all very much for your answers and comments.
First of all, the code that Andrew Bernard very kindly gave me:
{
\clef bass
\stemUp
b,8
\stemDown
b8 b b b
}
This code was one of my first attempts to make that fragment. However, in my
version of LilyPond, which is 2.19.82, the compiler shows me this warning:
"warning: no viable initial configuration found: may not find good beam slope
Although the score is compiled correctly, in each fragment of the score in
which I use it, the compiler shows me the corresponding warning, and the
Frescobaldi program marks the lines in red.
Maybe it's just a simple warning, no more complications, but I'd like to know if there's
any other way to make that fragment without the LilyPond compiler "protesting".
On the other hand, Pierre Perol-Schneider, thank you very much for your
warning. I am aware that this mode of writing is obsolete and not currently
used. My intention is to copy Beethoven's Symphonies to review my musical
knowledge and learn complex and unusual LilyPond techniques to improve my
knowledge of the program.
Many thanks again to all of you for your answers.
Víctor Manuel Ares Piñeiro
victormanue...@protonmail.com
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
El sábado, 10 de agosto de 2019 14:38, Andrew Bernard
<andrew.bern...@gmail.com> escribió:
Use stem up and stem down.
{
\clef bass
\stemUp
b,8
\stemDown
b8 b b
}
I leave it as an exercise for you to check the NR (Notation Reference)
for how to make the beam flat.
Andrew
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi Victor,
It seems like you're having problems understanding the next step and how
to discover the answer. Here is one way of looking at solving your problem.
{
\clef bass
\once \override Beam.positions = #'(1 . 1)
\stemUp
b,8
\stemDown
b8 b b
\override Beam.damping = #2
b b g g
}
Quick summary: by using the override and setting both to the same value,
you essentially create a flat beam. And since your attached photo shows
the beam going across the F line, the pair 1 . 1 seems to work fine in
this case. (see attached)
Do you follow? :)
In several different sections of the comprehensive documentation you'll
find code that concerns beams, slopes, and overrides. Check out the
sections that talk about "manually controlling beam positions etc." or
something similar.
Hope that helps you narrow it down, and by reverse engineering code to
see how we arrive at solutions you learn to look at things from a
different angle. Everyone learns differently. Forwards or backwards,
it's all the same.
LilyPond has a lot of power, and you'll find what works for you!
Good luck!
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
