[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

\partcombine interacts badly with \tag

From: H. S. Teoh
Subject: \partcombine interacts badly with \tag
Date: Sat, 18 Apr 2015 08:01:32 -0700
User-agent: Mutt/1.5.23 (2014-03-12)

% \partcombine should have produced a combined staff containing d'1 in
% the first bar, f'1 in the second and 3rd bars, and <f' d'>1 chords in
% the next 2 bars. However, it seems to interact badly with \tag, and
% the output has a missing f1' in the second bar, a stray rest in the
% 3rd bar, and a missing d'1 in the 4th bar. The first and last bars
% appear to be OK. (See attached .pdf file.)
% Removing the \removeWithTag line reveals that \partcombine has indeed
% combined the notes correctly, but apparently left the tags on the
% wrong notes, so that \removeWithTag deleted the wrong objects.
% Arguably, using \tag with \partcombine is a bad idea, since it can
% easily result in constructs that are probably not representable in a
% way that would make a subsequent \removeWithTag work correctly, but
% Lilypond should at least give a warning and/or reject such input
% instead of generating wrong output.

\version "2.18.2"

fluteIPart = {
    \tag #'layout { R1 }
    \tag #'midi { R1 }
    f'1 f' f' f'

fluteIIPart = {
    \tag #'layout { d'1 }
    \tag #'midi { d'1 }
    d'1 d'

\score {
    \removeWithTag #'midi {
        \partcombine \fluteIPart \fluteIIPart

Attachment: score.pdf
Description: Adobe PDF document

reply via email to

[Prev in Thread] Current Thread [Next in Thread]