lilypond-auto
[Top][All Lists]
Advanced

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

Re: [Lilypond-auto] Issue 1278 in lilypond: Enhancement: arrow notation


From: lilypond
Subject: Re: [Lilypond-auto] Issue 1278 in lilypond: Enhancement: arrow notation for quarter-tones
Date: Sun, 14 Jul 2013 05:10:35 +0000

Updates:
        Labels: Needs-design

Comment #8 on issue 1278 by address@hidden: Enhancement: arrow notation for quarter-tones
http://code.google.com/p/lilypond/issues/detail?id=1278

Well, it succeeds for B-flat-lowered Clarinet, and fails for B-half-flat Clarinet in a very friendly way:
  warning: Could not find glyph-name for alteration 3/5
And the snippet has a very friendly comment showing the resolution
  % Transposition could generate pitches with alterations
  %  double-sharp-lower (8/10) or double-flat-raise (-8/10)
  %  but there are no such symbols in the font, so we substituted
  %  the most appropriate symbols.
  % If some pitch in your score has no symbol, LilyPond gives a warning.

Fundamentally, if you want quarter-tone pitches to sometimes maintain a distinction
  "C-sharp-lower distinct from C-natural-raise"
but ignore other distinctions
"F-sharp-lower transposed by a sharp-lower would be E-double-sharp-double-lower,
   but just use F-sharp for that"
then you need a way to describe your notation system to LilyPond.

The current way to describe such a system is to make the pitches numerically distinct, and tell LilyPond which glyphs to use for the numerical pitches that could arise in practice.

Note that the patch in comment #1 stores a quarter sharp, transposed up by a quarter tone, as 2/4, which is kept distinct from 1/2. In that system, similarly, one needs to tell LilyPond whether 2/4 should be printed with a sharp, or alternatively a user-defined double-up-arrow.

Attachments:
        1278.png  53.7 KB

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