On Sun 19 Jan 2025 at 16:05:00 (-0500), Saul Tobin wrote:
> convert-ly should work fine when run from its default location within the
> Lilypond installation. If after reinstalling Lilypond you still get this
> type of issue, likely it is due to your PATH including
> only lilypond-2.24.4\bin. I would try changing that to the entire lilypond
> install directory, not just \bin.
You can settle that issue by seeing whether "lilypond -v" prints
something like:
GNU LilyPond 2.24.0
Copyright (c) 1996--2022 by
Han-Wen Nienhuys <han...@xs4all.nl>
Jan Nieuwenhuizen <jann...@gnu.org>
and others.
depending on whether the final \bin is included in the PATH string.
(Also "convert-ly --version" likewise.)
BTW,
On Sun 19 Jan 2025 at 12:20:06 (+0000), Jenifer Tribe wrote:
> I also have the python310.dll in lilypond\usr\bin,
What is lilypond\usr\bin? Or, perhaps, where is it contained?
What makes me suspicious is that here on linux I happen to have:
~/lilypond-2.18.2-1.linux-64/lilypond/usr/bin/
which is part of the old-fashioned (≤2.23.6) LP tree (but _not_ in
the PATH). Hopefully yours is not loitering around in your PATH
or the new unpacked archive.
Cheers,
David.
