I'm not top posting.
Tested on Lilypond 2.17.29 and latest release of 2.16.
Example 1:
% Wrong output in bar 1
\version 2.14.0
\relative c {
\key d \major
\time 6/8
g16*7 fis16*5
|
d2.
|
}
Example 2:
% Wrong output in bar 1
\version 2.14.0
\relative c {
\key f \major
\time
Neither am I :)
This output looks correct to me. In the first example you're asking for a
g16 to be displayed but for its duration to be 7/16 long followed by a fis16
with duration 5/16, so filling the bar. See
Hopefully, we're good!
On Mon, Oct 28, 2013 at 11:49 AM, Trevor Daniels t.dani...@treda.co.ukwrote:
Neither am I :)
This output looks correct to me. In the first example you're asking for a
g16 to be displayed but for its duration to be 7/16 long followed by a
fis16
with duration 5/16,
Paul Morris wrote:
Currently the function make-connected-path-stencil[1] does not allow you to
specify the starting point (origin) of the path, but arbitrarily hard-codes
it
as (0 0). This makes the function less flexible for no good reason.
Hello bug squad,
I'd like to withdraw this
Thanks for explaining. I've nearly forgot what Lilypond is :)
Actually, the 16*7 and 16*5 comes from the quantized output of midi2ly - I'm
using midi2ly to quantize raw midis and Lilypond to print readable scores in a
batch. Would that be more like a problem of midi2ly?
Jimmie
On 10/28/13 7:15 AM, Jimmie Felidae evolution.ji...@gmail.com wrote:
I'm not top posting.
Tested on Lilypond 2.17.29 and latest release of 2.16.
Example 1:
% Wrong output in bar 1
\version 2.14.0
\relative c {
\key d \major
\time 6/8
g16*7 fis16*5
|
d2.
|
}
I believe this does
