[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:40:14 +0000 |
Comment #2 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
another solution would have been to put the ossia as a markup, e.g. :
\version "2.18.2"
ossia =
\tweak self-alignment-X #RIGHT
\tweak padding #3
\mark\markup\score {
\new Staff
\with {
alignAboveContext = #"myStaff"
\omit Clef
\omit TimeSignature
fontSize = #-3
\override StaffSymbol.staff-space = #(magstep -3)
\override StaffSymbol.thickness = #(magstep -3)
}
\relative c' {
\stopStaff\partial 8 s8
\startStaff
<<
{ e4 g8 f e2 }
{
% here's how to enlarge the ossia
\hide MultiMeasureRest
\override MultiMeasureRest.minimum-length = #31
R1
}
>>
\stopStaff
}
\layout { }
}
\new Staff \relative c' {
c4 b c2
e4 f e2
\ossia
\key a \major
g4 a g2
\break
c4 b c2
}
Cheers,
Pierre
--
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