> It seems my previous reply failed to deliver bug-lilypond. Here's the
content:
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
2013/10/29 Carl Sorensen <c_soren...@byu.edu>
> 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 exactly what is supposed to do: print a sixteenth note
> that takes up the duration of 7 sixteenth notes, followed by a sixteenth
> note that takes up the duration of 5 sixteenth notes for a total of 12/16
> or 6/8, thus filling the bar.
>
> What do you believe it should do?
>
> Thanks,
>
> Carl
>
>
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
