RE: Too high measure numbers with ossia staff
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 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 measure numbers down? Below is a modified version of the example in
the documentation.
\version "2.18.2"
oss = \markup {\raise #1 "ossia" }
music = \relative c' {
<<
{ c4 b c2 }
\context Staff = "ossia" {
\stopStaff s1
}
>>
<<
{ e4 f e2 }
\context Staff = "ossia" {
\startStaff e4^\oss g8 f e2 \stopStaff
}
>>
g4 a g2 \break
c4 b c2
<<
{ g4 a g2 }
\context Staff = "ossia" {
\startStaff g4^\oss e8 f g2 \stopStaff
}
>>
e4 d c2
}
\score{
<<
\new Staff = "ossia" \with {
\remove "Time_signature_engraver"
\hide Clef
fontSize = #-3
\override StaffSymbol.staff-space = #(magstep -3)
\override StaffSymbol.thickness = #(magstep -3)
}
\new Staff <<\music>>
>>
}
Thanks in advance!
Erika
Frescobaldi and Python 3.11
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 Fedora package will be unusable soon on current Fedora versions. (The upstream Fedora issue is https://bugzilla.redhat.com/show_bug.cgi?id=2121995). Of course, over time, other distributions will start switching to Python 3.11 as well. I'm just raising this significant issue here for visibility, in case there are PyQt experts out there who have time and interest to track down this bug. Thanks, Jean
Re: Too high measure numbers with ossia staff
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 measure numbers down? Below is a modified version of the example
in the documentation.
Hello,
I'd suggest to remove "Bar_number_engraver" from the Score context and to
add it to your main Staff.
\layout {
\context {
\Score
\remove "Bar_number_engraver"
}
}
\new Staff \with {
\consists "Bar_number_engraver"
}
Cheers,
Xavier
--
Xavier Scheuer
Re: Too high measure numbers with ossia staff
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
fontSize = #-3
\override StaffSymbol.staff-space = #(magstep -3)
\override StaffSymbol.thickness = #(magstep -3)
}
\new Staff \with { \consists Bar_number_engraver } \music
>>
}
That being said: As long as you do not need multiple ossias in one system you
can use this much simple method:
\version "2.22"
oss = \markup {\raise #1 "ossia" }
ossiaStaff = \with {
\remove "Time_signature_engraver"
\omit Clef
fontSize = #-3
\override StaffSymbol.staff-space = #(magstep -3)
\override StaffSymbol.thickness = #(magstep -3)
}
music = \relative c' {
c4 b c2
<<
{ e4 f e2 }
\new Staff \with { alignAboveContext = "staff" \ossiaStaff } {
e4^\oss g8 f e2
}
>>
g4 a g2 \break
c4 b c2
<<
{ g4 a g2 }
\new Staff \with { alignAboveContext = "staff" \ossiaStaff } {
g4^\oss e8 f g2
}
>>
e4 d c2
}
\score{
\new Staff = "staff" \music
}
If you want to have multiple ossias in one system this will fail, as these
ossia staves would be put into different lines.
Cheers,
Valentin
Am Freitag, 21. Oktober 2022, 21:53:52 CEST schrieb Erika Pirnes:
> 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 measure numbers down? Below is a modified version of the example
> in the documentation.
>
> \version "2.18.2"
>
> oss = \markup {\raise #1 "ossia" }
>
> music = \relative c' {
> <<
> { c4 b c2 }
> \context Staff = "ossia" {
> \stopStaff s1
> }
>
>
> <<
> { e4 f e2 }
> \context Staff = "ossia" {
> \startStaff e4^\oss g8 f e2 \stopStaff
> }
>
> g4 a g2 \break
> c4 b c2
> <<
> { g4 a g2 }
> \context Staff = "ossia" {
> \startStaff g4^\oss e8 f g2 \stopStaff
> }
>
> e4 d c2
> }
>
> \score{
> <<
> \new Staff = "ossia" \with {
> \remove "Time_signature_engraver"
> \hide Clef
> fontSize = #-3
> \override StaffSymbol.staff-space = #(magstep -3)
> \override StaffSymbol.thickness = #(magstep -3)
> }
> \new Staff <<\music>>
>
> }
>
>
> Thanks in advance!
> Erika
signature.asc
Description: This is a digitally signed message part.
LilyPond 2.23.80
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 section in the Learning Manual for instructions how to set up the provided binaries: https://lilypond.org/doc/v2.23/Documentation/learning/installing signature.asc Description: This is a digitally signed message part
2.23.80 so far
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 noticed is in the documentation. In section 2.4.1 of the Notation reference it says that the moderntab clef for a tab staff supports 4 to 7 strings. I've been using it for the lap dulcimer tabs that only have 3 strings, and it seems to be working just fine. Don't know if that's just me getting lucky with that or what, but it does seem to work as expected. So far it's been an excellent experience. A bit of a learning curve to be sure, but well worth it. Much thanks and appreciation to all the devs and their hard work. Michael
