lilypond-auto
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Lilypond-auto] Issue 4338 in lilypond: Octavecheck - unexpected behavio


From: lilypond
Subject: [Lilypond-auto] Issue 4338 in lilypond: Octavecheck - unexpected behavior
Date: Fri, 03 Apr 2015 11:40:36 +0000

Status: Accepted
Owner: ----
Labels: Type-Documentation

New issue 4338 by address@hidden: Octavecheck - unexpected behavior
https://code.google.com/p/lilypond/issues/detail?id=4338

Nik Repka, Abraham Lee, Joram, and Trevor Daniels wrote :

\relative c'' {
   c4 f g f

   c4
   \octaveCheck c'
   f
   \octaveCheck c'
   g
   \octaveCheck c'
   f
}

I understand why the first and third octave checks fail... but I am
uncertain why the last f (which appears in the output as the f below c') is
chosen instead of f'.  According to the manual (
http://lilypond.org/doc/v2.18/Documentation/notation/changing-multiple-pitches),
"If this [octave] check fails, a warning is printed, but the previous note
is not changed. Future notes are relative to the controlpitch." However, f below c' is not "relative" to c' since it is a fifth away from c'. Or have
I misunderstood what is meant by "relative"?

Basically, my question is... why do we get f not f'?

-and-

Here is a guess what happens (even if that contradicts the docs):
The following pitches are perhaps not relative to the octave check but
to the previous pitch corrected by the octave check.
I am commenting inside your example:

     \relative c'' {
       c4 f g f

       c4
       \octaveCheck c'
The c4 is a c'' -> check resets to c' -> following note is f'
       f
       \octaveCheck c'
Check passed -> continue relative to f' -> next note is g'
       g
       \octaveCheck c'
The g is a g' closer to a c'' -> check resets to g -> next note is f
       f
     }

This would explain it, but the docs would have to be corrected.

Btw, the other way to do octave checks seems more intuitive to me:

\relative c'' {
  c4 f g f
  c='4 f=' g='' f
}

-and-

Yes, it's a doc issue.  But is it really useful in this form?
Does anyone use it?

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