Well, that approach won't handle G to C#. I still get Db with no
alternative.
J
On 3/12/24 19:02, John Helly wrote:
M.
Prompted by your idea, I could do the equivalent with a short bash
script to edit selected chords to be the appropriate enharmonic form
anticipating the transpose.
Mahalo.
On 3/12/24 18:48, John Helly wrote:
Mahalo, that's an interesting approach. Maybe something in that vein
would do it. I'll experiment.
However, I have a whole song that has a lot of chromatic chord
changes and I suspect it'll be a 'fix one, break one' situation. I'd
like to find a general solution or some way to make a specialized
chord library for a song.
If there's no LP solution then I'll have to figure out plan B.
J.
On 3/12/24 18:22, Michael Werner wrote:
Hi John,
On Tue, Mar 12, 2024 at 11:51 PM John Helly <hel...@ucsd.edu> wrote:
Aloha.
Here's an MWE to exhibit the issue.
I have a flat note (bes) that I want to transpose down 4
half-tones to F#. However, when the transpose is applied, the
result is Gb. I understand that a flat note was the initial
value so maybe LP is preserving that specification?
Nonetheless, short of re-writing the whole piece in A rather
than C#, is there a way to specify the enharmonic representation
for an F# rather than Gb, for example?
It's maybe a bit hackish, but what about first transposing from B
flat to A sharp. *then* transposing C sharp to A? Something like:
\version "2.25.13"
bflat = \chordmode { bes1 }
{
\transpose cis' a {
\new ChordNames {
\bflat
\transpose bes ais { \bflat }
}
}
}
--
Michael
--
John Helly / San Diego Supercomputer Center / Scripps Institution of
Oceanography
https://www.sdsc.edu/~hellyj / 808 205 9882 / 760 8408660
--
John Helly / San Diego Supercomputer Center / Scripps Institution of
Oceanography
https://www.sdsc.edu/~hellyj / 808 205 9882 / 760 8408660
--
John Helly / San Diego Supercomputer Center / Scripps Institution of
Oceanography
https://www.sdsc.edu/~hellyj / 808 205 9882 / 760 8408660
