Thanks to the help of four talented, generous Lilypond Users, I almost have
a working setup on my Mac for music engraving. (Additional input on the
Lilypond-on-MacOS-Monterrey 12.5 issue is still welcome.)
I withdraw my request for help in sourcing a Windows laptop. I don't want
to waste anyone's time.
What a great user-support community. Thank you!
On Sat, Feb 12, 2022 at 12:11 PM Valentin Petzel <valen...@petzel.at> wrote:
> Hello Jeremiah,
>
> this is definitely a pure Frescobaldi issue. It appears that Frescobaldi
> tries to concat a nonstring to a string when calling from macports, which
> python does not allow (basically you'd want to use string formatting
> instead).
>
> Bu considering this is python you can fix this yourself: Open
> /Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/lilypondinfo.py
> in a text editor, go to line 306. There should be something with a +
> between. So add a str(...) around each operand to make sure they are
> concerted to a string (unless they obviously are already strings).
>
> Regarding you initial message: The speed of Lilypond depends mainly on
> single core performance and disk IO, but Lilypond runs on pretty much
> anything. I've got it running on my phone. So you even could have it in
> some minimal kind of headless linux VM and add wrapper scripts for handling
> files and output.
>
> Cheers,
> Valentin
>
> 12.02.2022 11:19:49 Jeremiah Reilly <jeremiah.p.rei...@gmail.com>:
>
> Thank you all for your help.
>
> I have the development version of Lilypond 2.23.6 installed.
> I have Frescobaldi 3.1.3 installed.
> Frescobaldi launches fine.
> I ran the the following Lilypond test code (this used to be the original
> minimal input):
>
> {
> c' e' g' e'
> }
>
> Frescobaldi choked and returned an error message.
>
> I will take it up with Frescobaldi support. I reproduce the error message
> below my signature in case the Lilypond Development Team should know about
> it.
>
> Thank you all again for your detailed and helpful replies. I am looking
> forward to engraving with Lilypond again.
>
> Kind regards
>
> Jeremiah
>
> *Frescobaldi Error Report*
>
> Traceback (most recent call last):
>
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/engrave/__init__.py",
> line 141, in engraveRunner
>
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/engrave/__init__.py",
> line 145, in engravePreview
>
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/engrave/__init__.py",
> line 200, in engrave
>
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/engrave/__init__.py",
> line 252, in runJob
>
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/job/manager.py",
> line 61, in start_job
>
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/job/__init__.py",
> line 211, in start
>
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/job/lilypond.py",
> line 176, in configure_command
>
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/lilypondinfo.py",
> line 138, in wait
>
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/cachedproperty.py",
> line 253, in start
>
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/cachedproperty.py",
> line 261, in checkstart
>
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/cachedproperty.py",
> line 253, in start
>
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/cachedproperty.py",
> line 264, in checkstart
>
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/cachedproperty.py",
> line 278, in run
>
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/cachedproperty.py",
> line 189, in set
>
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/signals.py",
> line 191, in emit
>
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/signals.py",
> line 308, in call
>
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/cachedproperty.py",
> line 264, in checkstart
>
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/cachedproperty.py",
> line 276, in run
>
> File
> "/Applications/Frescobaldi.app/Contents/Resources/lib/python3.9/frescobaldi_app/lilypondinfo.py",
> line 306, in frommacports
>
> TypeError: unsupported operand type(s) for +: 'bool' and 'str'
>
>
>
>
> On Sat, Feb 12, 2022 at 11:10 AM Hans Åberg <haber...@telia.com> wrote:
>
>>
>> > On 12 Feb 2022, at 10:50, Lukas-Fabian Moser <l...@gmx.de> wrote:
>> >
>> >> I neglected to consider the development releases. I feel so
>> incompetent.
>> > No need to!
>> >
>> > The term "development" (as opposed to "stable") tends to scare users
>> away. And while it is basically true that
>> >
>> > - the development releases might have syntax changes (that might even
>> be changed again in later development releases)
>> > - the development releases reflect the current state of cutting-edge
>> development and therefore may contain changes that turn later out to be
>> less than ideal and have to be reverted,
>> >
>> > in practice, the development releases are absolutely suited for
>> everyday production work. The reason is that there's a pretty rigid
>> procedure for adding new changes (commits, merge requests) to LilyPond
>> which includes both a thorough review and automated tests against a very
>> extensive suite of regression tests.
>>
>> There is currently not so much difference, I would think, since you
>> recently have changed version, making the current regular release the old
>> development version.
>>
>> > So, I've always thought that the juxtaposition of "stable" vs.
>> "unstable" releases on the LilyPond home page is not really ideal, as
>> nobody wants to have "unstable" software. But these releases are routinelly
>> stable for use; they're just not guaranteed to be stable in the sense of
>> having frozen feature sets.
>>
>> I think the terms "development version" is better.
>>
>> > But: With the newly created binaries for current MacOS, we're actually
>> really at the point where we talk about "new infrastructure, please test
>> and report back if you encounter problems". If you're willing to do that -
>> and the lilypond-user list is a great place for reporting back -, you
>> should be good to go with the new 2.23.6 release. Happy engraving!
>>
>> The MacPorts version is though still using Guile 1.8, so there is not
>> much experimentation there.
>>
>>
