Erika,
Is the \break necessary?
Mark
From: lilypond-user [mailto:lilypond-user-boun...@gnu.org] On Behalf Of
Erika Pirnes
Sent: Friday, October 21, 2022 12:54 PM
To: lilypond-user@gnu.org
Subject: Too high measure numbers with ossia staff
Hi,
I just learned how to use the ossia
Hi,
Frescobaldi is facing an issue that prevents it from launching
under Python 3.11 beta.
https://github.com/frescobaldi/frescobaldi/issues/1453
Python 3.11.0 will be released tomorrow, and it's a matter
of weeks until Fedora 37 is also released, with Python 3.11.0.
Thus the Frescobaldi
On Sat, 22 Oct 2022 at 00:55, Erika Pirnes wrote:
>
> Hi,
>
> I just learned how to use the ossia staff. And I'm quite happy with the
results, except it seems that the measure numbers follow the hidden ossia
staff instead of the first visible staff. Can anyone think of a nice way to
move the
Hi Erika,
a very simple method would be to simply move the Bar_number_engraver from
Score to the top Staff like this:
\layout {
\context {
\Score
\remove Bar_number_engraver
}
}
\score{
<<
\new Staff = "ossia" \with {
\remove "Time_signature_engraver"
\hide Clef
We are happy to announce the release of LilyPond 2.23.80. This is the
first release candidate towards the next stable version 2.24.0 expected
in December. Please test your scores with this version and report back
the experience as well as any problems you encounter. Please refer to
the Installing
So far I've only tried 2.23.80 on a few simple scores, but so far
everything is working as expected. These are simple lap dulcimer and
tin whistle scores that I initially made with 2.22.0, then 2.22.1,
thru 2.22.2, transitioned to 2.23.14, and then to 2.23.80.
The only (very slight) issue I've