[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Globally disable transposition
From: |
Joseph Rushton Wakeling |
Subject: |
Re: Globally disable transposition |
Date: |
Mon, 04 Nov 2013 12:18:52 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 |
On 04/11/13 08:56, David Kastrup wrote:
Ugh. Why not
#(define-music-function (parser location p1 p2 m)
(ly:pitch? ly:pitch? ly:music?) m)
Thanks for the improved version! I'm not exactly fluent in Scheme -- combine
that with needing to work out which of Lilypond's variable types to use, and
it's not easy to just come up with something on the spot.
Better, but I'd use ly:pitch? instead of ly:music? here. And frankly: I
have my doubts the results will sound great in all cases.
I can see a number of potential issues -- e.g. if you have some parts that are
written (in Lilypond) in concert pitch with both \transposition and \transpose
statements, and some that are written in transposed pitch with a \transposition
statement, things could get nasty.
But for my current use case, it's satisfactory.
Re: Globally disable transposition, Jim Long, 2013/11/03