[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Proposed Doc Changes in Polyphonic music
From: |
Mats Bengtsson |
Subject: |
Re: Proposed Doc Changes in Polyphonic music |
Date: |
Fri, 26 Jan 2007 09:18:56 +0100 |
User-agent: |
Thunderbird 1.5.0.9 (X11/20061206) |
I hope you are aware of the fact that the only difference between \voiceOne
and \voiceThree is that the latter includes a \shiftOn. Similararly for
\voiceTwo versus \voiceFour. Therefore, two other methods to get the
same result as your second measure is
<< {d=''2 \voiceThree g2 } \\
{\oneVoice d=''8 c8 r4 e,8 c'8 r4 } \\
{ \voiceFour e,,2 e'2}
>>
<< {\oneVoice d=''8 c8 r4 e,8 c'8 r4 } \\ {} \\
{d=''2 g2 } \\
{ e,,2 e'2}
>>
Note also that it's probably better to write \oneVoice instead of
\stemNeutral,
if that voice also involves ties, slurs, articulations and so on.
/Mats
Carl D. Sorensen wrote:
Here is a proposed doc addition to section 6.3.5 Collision Resolution
Just befor the heading Predefined Commands, I'd recommend the following
---
If three or more notes line up in the same column,
merge-differently-headed can't
successfully complete the merge of the two notes that should be merged.
To allow the merge to work properly, apply a \shift to the note that
should not be merged.
In the first measure of the example below, merge-differently-headed
doesn't work (the half-note head is solid). In the second measure,
\shiftOn is applied to move the top g out of the column, and
merge-differently-headed works properly.
%%%% Begin .ly snippet
% \shiftXxx can be used to avoid "warning: too many clashing note
columns"
\version "2.10.5" %Windows XP
\paper {indent = 0\mm ragged-right = ##t}
\relative c' {
\override Staff.NoteCollision #'merge-differently-headed = ##t
<< {d=''2 g2 } \\
{\stemNeutral d=''8 c8 r4 e,8 c'8 r4 } \\
{ \voiceFour e,,2 e'2}
>>
<< {d=''2 \shiftOn g2 } \\
{\stemNeutral d=''8 c8 r4 e,8 c'8 r4 } \\
{ \voiceFour e,,2 e'2}
>>
}
%%%% end of .ly snippet.
---
Also, in the Predefined Commands part of section 6.3.5 Collision
resolution, the first sentence should read "these commands specify the
degree to which chords of the current voice should be shifted." ISO
"these commands specify in what chords of the current voice should be
shifted."
--
Immediately before 6.3.5 Collision Resolution, the following text could
be added:
In some instances of complex polyphonic music, you may need additional
voices to avoid collisions between notes. Additional voices are added
by defining an identifier, as shown below
voiceFive = #(context-spec-music (make-voice-props-set 4) 'Voice)
<< { \voiceOne g''4 ~ \stemDown g32[ f( es d c b a b64 )g] } \\ {
\voiceThree b4} \\ { \voiceFive d,} \\ { \voiceTwo g,}\\>>
---
Graham, I've greatly admired your work on the docs. Now I'm even more
impressed, given that you can work on the docs during momentary pauses
in FFT lectures!
Carl Sorensen
Carl D. Sorensen
Associate Professor
Department of Mechanical Engineering
Brigham Young University
Provo, UT 84602
801-422-6397 Fax 801-422-0516
_______________________________________________
lilypond-devel mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
=============================================
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: address@hidden
WWW: http://www.s3.kth.se/~mabe
=============================================