[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 1009 in lilypond: \transpose causes crash (std
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 1009 in lilypond: \transpose causes crash (std::logic_error) |
Date: |
Thu, 07 Nov 2013 05:59:55 +0000 |
Updates:
Status: Started
Labels: -fixed_2_13_14 Patch-new
Comment #9 on issue 1009 by address@hidden: \transpose causes crash
(std::logic_error)
http://code.google.com/p/lilypond/issues/detail?id=1009
The fix for this issue may have gone too far. It warns if transposing
creates a triple-sharp, but then also replaces the pitch with the triple
sharp.
With the warning alone, the user can /choose/ to reduce the triple sharp
with
{ \naturalizeMusic \transpose disis,, c { a b c d } }
using the definition of \naturalizeMusic in the manual.
If someone is working with music where triple-sharps arise, he might define
a glyph to represent them, but cannot use it if \transpose automatically
converts the pitches (destroying information in the process).
This question came up in the context of just intonation <> . A minimized
example is below where a fisis is generated by a \transpose, which in
Pythagorean tuning is actually slightly higher than g, so generates the
warning, but we would like to be able to print f-doublesharp in this case.
% Pythagorean tuning
#(ly:set-default-scale (ly:make-scale
#(0/200 204/200 408/200 498/200 702/200 906/200 1110/200)))
#(define-public COMMA 24/200)
#(define-public SHARP 114/200)
#(define-public DOUBLE-SHARP (* 2 SHARP))
#(define-public FLAT (- SHARP))
#(define-public standard-alteration-glyph-name-alist
`(( 0 . "accidentals.natural")
(,COMMA . "scripts.stopped")
(,FLAT . "accidentals.flat")
(,SHARP . "accidentals.sharp")
(,DOUBLE-SHARP . "accidentals.doublesharp")))
#(ly:load "define-note-names.scm")
\language "nederlands"
\new Voice \with {
\override Accidental #'glyph-name-alist =
\standard-alteration-glyph-name-alist }
{ \transpose c cis' { c4 d e fis } }
A realistic example is found if we transpose
<http://lsr.dsi.unimi.it/LSR/Item?id=786> from B minor to C-sharp minor.
Avoid the crash, but preserve the pitch:
http://codereview.appspot.com/22710043
--
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
- Re: [Lilypond-auto] Issue 1009 in lilypond: \transpose causes crash (std::logic_error),
lilypond <=
- Re: [Lilypond-auto] Issue 1009 in lilypond: \transpose causes crash (std::logic_error), lilypond, 2013/11/07
- Message not available
- Re: [Lilypond-auto] Issue 1009 in lilypond: \transpose causes crash (std::logic_error), lilypond, 2013/11/10
- Message not available
- Re: [Lilypond-auto] Issue 1009 in lilypond: \transpose causes crash (std::logic_error), lilypond, 2013/11/12
- Message not available
- Re: [Lilypond-auto] Issue 1009 in lilypond: \transpose causes crash (std::logic_error), lilypond, 2013/11/13
- Message not available
- Re: [Lilypond-auto] Issue 1009 in lilypond: \transpose causes crash (std::logic_error), lilypond, 2013/11/13
- Message not available
- Re: [Lilypond-auto] Issue 1009 in lilypond: \transpose causes crash (std::logic_error), lilypond, 2013/11/16
- Message not available
- Re: [Lilypond-auto] Issue 1009 in lilypond: \transpose causes crash (std::logic_error), lilypond, 2013/11/19
- Message not available
- Re: [Lilypond-auto] Issue 1009 in lilypond: \transpose causes crash (std::logic_error), lilypond, 2013/11/19