Re: Mac testers needed for Frescobaldi! (again)

2014-06-19 Thread Jeff Holland
Davide Liessi (17.06.2014) : 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 t

Re: [Frescobaldi] Re: Mac testers needed for Frescobaldi!

2014-05-20 Thread Jeff Holland
On Tuesday, May 20, 2014 4:19:34 PM UTC+2, Davide Liessi wrote: > I did not say that it is impossible to bundle a working PortMIDI with > Frescobaldi > I know. My suggestions were only a related tangent. Your current predicament got me thinking is all. I didn't mean to add any distractions fr

Re: [Frescobaldi] Re: Mac testers needed for Frescobaldi!

2014-05-20 Thread Jeff Holland
On Tuesday, May 20, 2014 2:46:08 PM UTC+2, Marnen Laibow-Koser wrote: Or just communicating with the QuickTime synthesizer directly? > Sure, whatever works. (I just thought the combination I mentioned sounded better.) > That may not be a bad idea. But then how would you handle Lilypond > u

Re: [Frescobaldi] Re: Mac testers needed for Frescobaldi!

2014-05-20 Thread Jeff Holland
On Monday, May 19, 2014 6:50:31 PM UTC+2, Davide Liessi wrote: > The main problems are: > - PortMIDI is not included in the bundle, and even if it is included > (with the appropriate option of py2app) Frescobaldi cannot see the > MIDI ports provided by SimpleSynth or FluidSynth; > What about

Re: [Frescobaldi] Re: Mac testers needed for Frescobaldi!

2014-05-18 Thread Jeff Holland
On Monday, May 12, 2014 12:44:14 AM UTC+2, Davide Liessi wrote: > > 2014-05-10 16:49 GMT+02:00 >: > > Did you uninstall and reinstall only Frescobaldi? > You should try to uninstall Frescobaldi, Poppler and Qt and then > reinstall Frescobaldi > I uninstalled and reinstalled all of those (and