in the same sequence of sextuplets
1) the first time, the fingering 0 on the E collides with the slur
2) the second time, the fingering does not collide but the sextuplet number
is misplaced.
I have tested with 2.12, 2.14 and 2.15.30
http://old.nabble.com/file/p33354136/bug%2Bsextuplet.ly
{ a16 ( b cs cs-1 d e ) }
All this is pretty standard notation. What could be wrong here?
Marc M wrote:
in the same sequence of sextuplets
1) the first time, the fingering 0 on the E collides with the slur
2) the second time, the fingering does not collide but the sextuplet
number
Marc M wrote:
As you can see on this snippet the length of stems of sextuplets is too
short. The length of the stems extend for 32th but not for the 8th notes.
Is there anything i should do or is there something wrong is the default
values?
%% the sextuplets look compressed
Marc M wrote:
I am using the function looksSlower from the snippet
http://lsr.dsi.unimi.it/LSR/Item?id=305
and when i use it, it produces many warnings such as:
- warning: stem does not fit in beam
- warning: beam was started here
As a matter of fact, I get the same warnings
Nick Payne-3 wrote:
Look up \shiftOn \shiftOnn etc in the documentation. If you apply that
to the G in the middle voice it fixes the collision.
Nick
Thansk i tried them but it is really not easy to get it right. I was able to
get a decent layout with several \once \override NoteColumn
Graham Percival-3 wrote:
On Tue, Dec 14, 2010 at 7:27 PM, Marc Hohl m...@hohlart.de wrote:
and does it make the download size much much bigger.
How much is much much? Gonville is 3.5 MB, the Jazz font is 10 KB.
Downloading lilypond is 20 MB, so personally, I don't think this would
break
