[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 14:26:58 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
Kieren MacMillan <kieren@kierenmacmillan.info> writes:
> Hi all,
>
>>> convert-ly exists.
>> I actually thought I had tried this. Obviously I was too stupid to
>> do it correctly.
>
> Me, too, I guess…? At least in Frescobaldi, it didn't work at all [!!].
Running the given file through convert-ly changes the respective lines
in the example code (and bumps the version to 2.20.0 I think).
That's the entry part of this snippet. Whether the analysis part would
also be affected, I have no clue. If so, convert-ly would have no
chance of fixing it. But convert-ly appears to deal with the samples
Lukas discussed.
--
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