[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Lilypond-auto] Issue 2584 in lilypond: parcombine misplaces slurs
From: |
lilypond |
Subject: |
[Lilypond-auto] Issue 2584 in lilypond: parcombine misplaces slurs |
Date: |
Sun, 03 Jun 2012 02:39:09 +0000 |
Status: Accepted
Owner: ----
Labels: Type-Ugly Regression
New issue 2584 by address@hidden: parcombine misplaces slurs
http://code.google.com/p/lilypond/issues/detail?id=2584
Version 2.14 would warn about trying to start two slurs on the first beat,
but combined the slurs correctly. Version 2.15.39 starts two slurs and
lets one continue too long. Reverting the fix for issue 1967 restores
correct behavior.
I don't know if version 2.14 combined the slurs intentionally, or just
accidentally.
\version "2.15.39"
\partcombine
{e'2( f'4 g') g'2( f')}
{c'2( f'4 g') e'2( d')}
% Workarounds:
% Prevent the part-combiner from switching states during the slur
\partcombine
{\partcombineChords e'2( f'4 g') \partcombineAutomatic g'2( f')}
{c'2( f'4 g') e'2( d')}
% Use phrasing slurs
\partcombine
{e'2\( f'4 g'\) g'2\( f'\)}
{c'2\( f'4 g'\) e'2\( d'\)}
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Lilypond-auto] Issue 2584 in lilypond: parcombine misplaces slurs,
lilypond <=