Davide,
First, much thanks for your very patient responses to my SIP API errors
with the Port version of Frescobaldi.
I'm happy to report that the app bundle, thus far, works flawlessly so no
further need for the Port install of Frescobaldi. I've opened some fairly
hairy scores which use book structure and all works as expected. I have
not, yet, tested the conversion apps. But for now all is working well.
Best regards,
Guy
On Tuesday, June 17, 2014 10:17:29 AM UTC-5, Davide Liessi wrote:
Dear FrescobaldiLilyPondMac users,
some months ago I published a DMG disk image containing an
experimental Frescobaldi.app bundle.
Some packaging problems were reported ([1]):
- lack of MIDI support (PortMIDI was not included),
- impossibility to run convert-ly and musicxml2ly (the wrong Python
interpreter was used for the scripts bundled in LilyPond.app).
During the last days I was able to fix these problems (at least on my
machine).
I uploaded a new version of Frescobaldi.app, based on the newly
released 2.0.16, at
https://www.dropbox.com/s/whu5qnn5pys81ix/Frescobaldi-2.0.16-devapp-20140616.dmg
The application contains some 64 bit code, so it won't run on machines
with 32 bit CPU (I'll try to solve this in the next iteration).
I would be very grateful if you could download the application, test
it and report any issues.
In particular you should test if MIDI output is working [2] and if you
are able to update a file with convert-ly and to import a MusicXML
file (example MusicXML files at [3]).
The test should be harmless: the only collateral effect is that any
change you'll make to the settings inside this application bundle will
be picked up by your usual installation of Frescobaldi, since they'll
share the same preferences file. [4]
The previous tests revealed only the mentioned problems, so the
application should be quite stable.
However this application bundle is still considered experimental, so I
don't recommend it for everyday use (although I really appreciate
people testing it in everyday use cases).
After the tests I advise you to delete the application bundle and wait
for the official release. [5]
Last but not least, I would like to thank once again the users who
tested the previous version of the application.
Best wishes.
Davide
[1] The splash screen bug
(https://github.com/wbsoft/frescobaldi/issues/428) and some very
critical usability problems (in particular compatibility with screen
readers) were also reported, but they are certainly unrelated to the
installation method, so I didn't address them.
[2] I remind you that in order to have MIDI support
FluidSynth/qsynth/SimpleSynth must be running and Frescobaldi must
recognize the MIDI ports (you should either start *synth before
Frescobaldi or refresh the MIDI ports in Frescobaldi's preferences).
[3] http://www.musicxml.com/wp-content/uploads/2012/11/xmlsamples.zip
[4] Actually, if your usual version of Frescobaldi is older than
October 2013, your settings will become inaccessible from that
version, while they will still be accessible from versions of the
program newer than that date.
But if you're running such an old version, you should seriously
consider updating to the newly released 2.0.16 (it will be available
through MacPorts in a few days): Frescobaldi has improved a whole lot
in the last months!
[5] To avoid messing with your current setup (except for the settings
changes mentioned in [4]) and forgetting to delete the application
bundle after the test, you can run the application directly from the
disk image, without copying it to the /Applications directory.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
