[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 4108 in lilypond: Ossia is 'too long' if there
From: |
lilypond |
Subject: |
Re: [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:41:34 +0000 |
Comment #3 on 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 31/08/14 11:24, David Kastrup wrote:
Here is another:
\version "2.19"
\markup\italic "Ossia staff's too long at key change:"
\new Staff = "main" \relative c'' {
c4 b d c
<<
{ c4 b d c }
\new Staff \with {
\omit TimeSignature
alignAboveContext = #"main"
\magnifyStaff #2/3
firstClef = ##f
}
{ e4 d f e }
>>
\key a\major
c4 b c2
}
\markup\italic "This is almost a fix"
\new Staff = "main" \relative c'' {
c4 b d c
<<
{ c4 b d c }
\new Staff \with {
\omit TimeSignature
alignAboveContext = #"main"
\magnifyStaff #2/3
firstClef = ##f
}
{ e4 d f e \grace { \stopStaff s } }
>>
\key a\major
c4 b c2
}
However, it affects spacing somewhat curiously if you compare with the
original.
Maybe one should replace \magnifyStaff and check whether the artifacts
in either version have a longer history or not.
--
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