[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 586 in lilypond: Cross-staff slur causes a weird output
From: |
lilypond |
Subject: |
Re: Issue 586 in lilypond: Cross-staff slur causes a weird output |
Date: |
Fri, 30 Dec 2011 20:07:03 +0000 |
Updates:
Status: Verified
Comment #10 on issue 586 by address@hidden: Cross-staff slur causes a
weird output
http://code.google.com/p/lilypond/issues/detail?id=586
Verified with 2.15.23
No more notes left of time signature. Default slur is as reasonable as
possible, with the default shape, over these notes. (Setting 'eccentricity
helps but this is a user override, not automatic.) Tuplet bracket is
slanted to show that it includes the last note of the previous beam. The
problem in comment 5 looks like a copy/paste error that lost the notes in
the middle measure.
Attachments:
586.png 15.6 KB
- Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 2011/12/11
- Message not available
- Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 2011/12/16
- Message not available
- Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 2011/12/16
- Message not available
- Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 2011/12/16
- Message not available
- Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 2011/12/16
- Message not available
- Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 2011/12/18
- Message not available
- Re: Issue 586 in lilypond: Cross-staff slur causes a weird output,
lilypond <=
- Message not available
- Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 2011/12/30