[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 3223 in lilypond: Document known issue with Ot
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 3223 in lilypond: Document known issue with Ottava bracket in one voice |
Date: |
Tue, 05 Mar 2013 09:08:57 +0000 |
Comment #1 on issue 3223 by address@hidden: Document known issue with
Ottava bracket in one voice
http://code.google.com/p/lilypond/issues/detail?id=3223
Nick sent in a documentation suggestion here:
http://lists.gnu.org/archive/html/bug-lilypond/2013-03/msg00033.html
as follows:
Colin
Is the suggested text and example below clear or not? I grabbed the example
notes from a question on the lilypond user list a couple of years ago,
which seemed to demonstrate more clearly than anything else the problem and
how to solve it:
http://comments.gmane.org/gmane.comp.gnu.lilypond.general/61276. I guess
that any work done on issue 1473 would affect this as well.
This is for a "Known issues and warnings" paragraph to be placed at the end
of the subsection on ottava brackets in NR 1.1.3 Displaying Pitches.
"If you have more than one voice on the staff, setting ottavation in any
voice will transpose the position of notes in all voices for the duration
of the ottava bracket. If the ottavation is only intended to apply to that
one voice, you can set the middleCPosition in the other voice(s) to stop
them being transposed. For instance, in this example, set
Voice.middleCPosition in the upper voice for the duration of the ottava
bracket in the lower voice in order to prevent the tied chord in the upper
voice from appearing an octave higher than it should. Note that the value
you need to assign to middleCPosition will vary depending on the both the
ottavation and clef being used.
\relative c {
\clef bass
<<
{
<fis cis' g'>1~
\set Voice.middleCPosition = #6
<fis cis' g'>4
\unset Voice.middleCPosition
}
\\
{ r2. \ottava #-1 <b,,,~ bes'^~>4 <b bes'>4 \ottava #0 }
>>
}
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings