[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: polychords: what's the current state-of-the-art?
From: |
David Kastrup |
Subject: |
Re: polychords: what's the current state-of-the-art? |
Date: |
Tue, 09 Aug 2022 13:05:44 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
Lukas-Fabian Moser <lfm@gmx.de> writes:
> Hi Kieren,
>
> What's the current best snippet for rendering polychords? I know the GSoC
> chord stuff is still in air traffic control, but the snippet found at
> <https://lists.gnu.org/archive/html/lilypond-user/2012-02/txtmAr2kxZ1Uy.txt>
> definitely doesn't work, and is likely far from optimal given the
> decade-plus of advances in the codebase.
>
> I don't have much time at the moment, but as a first pointer:
>
> The snippet worked as late as 2.18.2. What broke it after that is that the
> meaning of
> c1:5.9-.11.13- in chordmode has changed:
>
> \version "2.18.2"
>
> \chordmode {
> c1:5.9-.11.13-
> }
>
> yields
>
> *
>
> in 2.18.2, whereas in 2.19.83, it yields
>
> *
>
> The culprit seems to be the added support for power chords: In 2.18.2, c1:5
> generated a c major chord; now it only generates a power chord fifth. My guess
> would be that Valentin V.'s chord name cleanup in 78225bc1b386e12dc was the
> point when this changed.
convert-ly exists.
Sounds more like issue 4614 to me.
--
David Kastrup
Re: polychords: what's the current state-of-the-art?, Valentin Petzel, 2022/08/09
Re: polychords: what's the current state-of-the-art?, Lukas-Fabian Moser, 2022/08/09
Re: polychords: what's the current state-of-the-art?, Thomas Morley, 2022/08/14