[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Possible bug with \oneVoice involving rests
From: |
Urs Liska |
Subject: |
Re: Possible bug with \oneVoice involving rests |
Date: |
Mon, 02 Jun 2014 18:13:51 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 |
Am 02.06.2014 09:51, schrieb Brian Eve:
\version "2.18.2-1"
{
\clef bass
\compressFullBarRests
\override Rest #'staff-position = #0
R1*6
<< g4. e >> << f d >> <<e4 d >>
a1
R1*6
<< b8 e8 >>
r8 r4 r2
R1*6
R1
r
R
}
No, that's very wrong code.
With these << >> you are actually telling LilyPond to print independent
voices while you want to write chords.
This may work in your example but you would definitely run into problems
very soon.
\version "2.18.2-1"
{
\clef bass
\compressFullBarRests
R1*6
<g e >4. < f d > <e d >4
a1
R1*6
<b e >8
r8 r4 r2
R1*6
R1
r
R
}
Is the correct way to write your example.
But I assume this is not what you _want_ - you will want to have the
polyphonic part with independent stems.
This is the smartest way to write what you want because it makes the
voicing right automatically:
\version "2.18.2-1"
{
\clef bass
\compressFullBarRests
R1*6
<<
{
g4. f e4
} \\
{
e4. d d4
}
>>
a1
R1*6
<<
{
b8
} \\
{
e8
}
>>
r8 r4 r2
R1*6
R1
r
R
}
This construct (with the "\\") creates \voiceOne, \voiceTwo etc. implicitly.
Read
http://lilypondblog.org/2013/07/voice-contexts-in-temporary-polyphonic-sections/
and particularly the chapter from the Notation Reference that is linked
in that article.
HTH
Urs
- Possible bug with \oneVoice involving rests, Brian Eve, 2014/06/02
- Re: Possible bug with \oneVoice involving rests, Brian Eve, 2014/06/02
- Re: Possible bug with \oneVoice involving rests, Urs Liska, 2014/06/02
- Re: Possible bug with \oneVoice involving rests, Phil Holmes, 2014/06/02
- Re: Possible bug with \oneVoice involving rests, Brian Eve, 2014/06/02
- Re: Possible bug with \oneVoice involving rests,
Urs Liska <=
- Re: Possible bug with \oneVoice involving rests, David Kastrup, 2014/06/02
- Re: Possible bug with \oneVoice involving rests, James, 2014/06/14
- Re: Possible bug with \oneVoice involving rests, David Kastrup, 2014/06/14