I just tried the example again with the latest git version and
the beam is slanted upwards (not much but still clearly visible
if you look carefully).
I have attached a png with debug-beam-scoring and another one
where I also set inspect-quants. The corresponding input file is repeated
here for c
I must have dreamt that I tried it. Anyway, it seems that the unit of the
argument is not the same as for global-set-staff-size. If you try
#(layout-set-staff-size (* 14.0 pt))
you will get the correct size. Still, the staff line spacing isn't adjusted
as long as the function is called within a \l
Mats Bengtsson escreveu:
> I just tried the example again with the latest git version and
> the beam is slanted upwards (not much but still clearly visible
> if you look carefully).
>
> I have attached a png with debug-beam-scoring and another one
> where I also set inspect-quants. The correspondi
Han-Wen Nienhuys wrote:
Mats Bengtsson escreveu:
I just tried the example again with the latest git version and
the beam is slanted upwards (not much but still clearly visible
if you look carefully).
I have attached a png with debug-beam-scoring and another one
where I also set inspect-qua
Issue 190: Unexpected beam slanting in the opposite direction
http://code.google.com/p/lilypond/issues/detail?id=190
Comment #2 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
Labels: fixed_2_10_8 fixed_2_11_8
--
You received this me
Issue 203: Bus error: afterGrace, rest, break and strict-grace-spacing
http://code.google.com/p/lilypond/issues/detail?id=203
Comment #3 by trevorbaca:
Cofirmed that the fix works correctly in 2.11.7.
--
You received this message because you are listed in the owner
or CC fields of this issue,
Issue 207: Rhythm moves afterGrace to incorrect measure
http://code.google.com/p/lilypond/issues/detail?id=207
Comment #3 by trevorbaca:
Cofirmed that fix works correctly in 2.11.7.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you star
Issue 204: afterGrace eats up skip duration under strict-grace-spacing
http://code.google.com/p/lilypond/issues/detail?id=204
Comment #2 by trevorbaca:
OK, workaround will work now due to the presence of \override NoteColumn
#'ignore-colision = ##t. Prior to addition of this NoteColumn attribute,
Issue 127: Dead contexts keep making an influence to the end of the line
http://code.google.com/p/lilypond/issues/detail?id=127
Comment #1 by hanwenn:
fixed with 2.11 skyline changes.
Issue attribute updates:
Status: Fixed
--
You received this message because you are listed in the owne
Issue 212: Context-initial afterGrace generates programming error
http://code.google.com/p/lilypond/issues/detail?id=212
New issue report by trevorbaca:
Example 1 begins with an afterGrace and generates a programming error.
%%% BEGIN EX 1 %%%
\version "2.11.7"
\new Score \with {
\override Sp
10 matches
Mail list logo