[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 586 in lilypond: Cross-staff slur causes a weird output
From: |
codesite-noreply |
Subject: |
Issue 586 in lilypond: Cross-staff slur causes a weird output |
Date: |
Tue, 04 Mar 2008 14:38:59 -0800 |
Issue 586: Cross-staff slur causes a weird output
http://code.google.com/p/lilypond/issues/detail?id=586
New issue report by v.villenave:
% this example shows an extremely ugly slur
% (which can be much improved by setting #'positions
% to almost any value) but above all puts the first notes to the
% left of the time signature.
% Admittedly, the slur is very difficult
% to typeset nicely whatever you do, but you shouldn't get
% notes to the left of the time signature.
% (By chance, the same example also illustrates another bug in
% version 2.10 that has been fixed in 2.11.)
\version "2.11.41"
<<
\new Staff = up { s1*2 }
\new Staff = down \relative c,{\clef bass \stemDown
% Commenting out the next line gives a much nicer slur shape
% almost no matter what values I specify for the positions.
% \once \override Slur #'positions = #'(5 . 5)
f4. ( a8 d f \change Staff = "up" \stemUp \times 2/3 {a[ d f} |
a16] d,[ f a \times 4/5 {d16] f[ a d32. f64 ~ f16] ~} f4 ) r | \noBreak
d4 a f d ||
}
>>
\layout{ ragged-right = ##t }
Issue attributes:
Status: Accepted
Owner: v.villenave
Labels: Type-Collision Priority-Medium
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
- Issue 586 in lilypond: Cross-staff slur causes a weird output,
codesite-noreply <=