[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the s
From: |
lilypond |
Subject: |
Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning |
Date: |
Mon, 13 Feb 2012 14:41:46 +0000 |
Comment #14 on issue 1967 by address@hidden: Concurrent slurs that
start and end at the same moment should not produce a warning
http://code.google.com/p/lilypond/issues/detail?id=1967
The partcombiner does not modify the events at all. It simply uses four
voices and decides to which voice to dispatch each event. Iit does not
really create a chord, but simply places the notes into the same voice and
let lilypond handle this situation as a chor, i.e. it produces something
similar to << c e >> rather than <c e>.
In effect, partcombining the example in the original report, i.e.
\partcombine \relative c'' { c2( a ~ a1) } \relative a' { a2( f ~ f1) }
everything is placed into the same voice. It is exactly the same as in my
simplified example:
<< \relative c'' { c2( a ~ a1) } \relative a' { a2( f ~ f1) } >>
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/13
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/13
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/13
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/13
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning,
lilypond <=
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/13
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end atthe same moment should not produce a warning, Trevor Daniels, 2012/02/13
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/13
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15