lilypond-auto
[Top][All Lists]
Advanced

[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: Wed, 06 Mar 2013 03:08:02 +0000


Comment #3 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

I suggest it be normal text in NR1.1.3, rather than "known issues and warnings" because there is nothing troublesome or surprising about LilyPonds normal behavior in having the ottava indication apply to all voices on the staff. Only in exceptional cases can the ottava apply to just one voice without ambiguity. The \ottava shortcut does not handle those exceptional cases, but normal LilyPond commands can.

The workaround suggested in issue 1473 puts the octavation commands in the affected voice only:

%{If you have more than one voice on the staff, setting octavation in one 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 one voice,
the middleCPosition and ottava bracket may be set explicitly.  Below, the
treble clef usually has middleCPosition -6, six positions below the center
line, so in the 8va portion middleCPosition is 7 positions, one octave, lower
still. %}

  \new Staff << {
    r4

    \set Staff.ottavation = #"8va"
    \once \override Staff.OttavaBracket #'direction = #UP
    \set Voice.middleCPosition = #(+ -6 -7)  %  = #-13
    f''' r g''' |

    \unset Staff.ottavation
    \unset Voice.middleCPosition
    <e'' a''>1
  } \\ {
    <c' e'>1~ q
  } >>

--
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



reply via email to

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