[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Lilypond-auto] Issue 4108 in lilypond: Ossia is 'too long' if there is
From: |
lilypond |
Subject: |
[Lilypond-auto] Issue 4108 in lilypond: Ossia is 'too long' if there is a key change in the other Staffs |
Date: |
Wed, 17 Sep 2014 07:38:13 +0000 |
Status: Accepted
Owner: ----
Labels: Type-Ugly
New issue 4108 by address@hidden: Ossia is 'too long' if there is a key
change in the other Staffs
https://code.google.com/p/lilypond/issues/detail?id=4108
On 30/08/14 17:42, Peter Van Kranenburg wrote:
If right after an ossia there is a key change in the other parts, the
staff of the ossia extends with the length of the key signature. See
below for an example.
I tried to do \set Staff.explicitKeySignatureVisibility = #all-invisible
in the ossia staff, but that didn't work.
\version "2.18"
<<
\new Staff = "ossia" \with {
\remove "Time_signature_engraver"
\hide Clef
fontSize = #-3
\override StaffSymbol.staff-space = #(magstep -3)
\override StaffSymbol.thickness = #(magstep -3)
}
{ \stopStaff s1*6 }
\new Staff \relative c' {
c4 b c2
<<
{ e4 f e2 }
\context Staff = "ossia" {
\startStaff e4 g8 f e2 \stopStaff
}
>>
\key a \major g4 a g2 \break
c4 b c2
}
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
- [Lilypond-auto] Issue 4108 in lilypond: Ossia is 'too long' if there is a key change in the other Staffs,
lilypond <=