[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: What is this warning? “no viable initial configuration found: may no
From: |
Harold Hausman |
Subject: |
Re: What is this warning? “no viable initial configuration found: may not find good beam slope” |
Date: |
Tue, 12 Jun 2018 19:57:33 -0600 |
On Sun, Jun 10, 2018 at 3:12 AM, Andrew Bernard
<address@hidden> wrote:
>
> Hi Harold,
>
> Welcome to the Pond.
>
Andrew, thank you, and thank you for this informative reply. I learned a lot.
> Lilypond does a pretty good job (actually, not just pretty good, but amazing)
> left to it's own devices, but music scoring is so rich that there are
> situations where you may need to help it out a bit. The virtue of lilypond is
> that there are tweaks and adjustments available from very simple to really
> advanced using Scheme, the lilypond extension language.
>
I am actually a LISP programmer by trade, so this sounds like good
news to me. Where can I find documentation for things like
`Beam.positions`?
> It's a good idea to always use bar checks at the end of a measure. Saves many
> headaches.
>
Good to know. I will make a habit of this, then.
> As always I really recommend using the new development versions, they are
> very stable and it is only the conventional open source tradition of self
> deprecation that labels them as 'unstable' (but even this view is
> controversial on the list). There's so many more features and I hammer
> 2.19.81 professionally all day and have not been able to crash it.
>
I did not realize that the latest stable version is from 2014 (!).
I have upgraded. The latest version I could find was 2.19.80
(http://download.linuxaudio.org/lilypond/binaries/linux-64/), where
did you get 2.19.81 from?
> As a final point, all the beam slopes here I find personally quite ugly and
> ragged. There are techniques to address this, but for another email.
>
When this becomes my biggest problem, I'll be sure to ask!
Kind thanks again for your time and insight,
-Harold