[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 760 in lilypond: Feature request: polyphony shortcut could be bett
From: |
codesite-noreply |
Subject: |
Issue 760 in lilypond: Feature request: polyphony shortcut could be better |
Date: |
Fri, 06 Mar 2009 13:18:00 +0000 |
Updates:
Status: Accepted
Labels: Type-Enhancement Priority-Low
Comment #2 on issue 760 by v.villenave: Feature request: polyphony shortcut
could be better
http://code.google.com/p/lilypond/issues/detail?id=760
Now, a much better example from James:
\version "2.12.2"
musOne = \context Voice = upperOne \relative f' { \voiceOneStyle f4 <<{g
a}\\{e d}>>f }
musTwo = \context Voice = upperTwo \relative f' { \voiceOneStyle f4
<<{\voiceOne g
a}\context Voice = lowerTwo {\voiceTwo e d}>>\oneVoice f }
\score {
<<
\new Staff \musOne
>>
}
\score {
<<
\new Staff \musTwo
>>
}
% The goal is that <<{}\\{}>> doesn't create two new voice contexts, but
rather
% keeps the first one active, and just creates a second new voice context.
% The goal here is that one voice is consistent throughout.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings