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
2014-05-20 14:46 GMT+02:00 Marnen Laibow-Koser :
> On Tuesday, May 20, 2014, Jeff Holland wrote:
>> 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 optio
2014-05-20 15:03 GMT+02:00 Urs Liska :
> I think directly bundling LilyPond wouldn't be that good because it
> definitely bloats the package even more, without being useful for _every_
> user.
I agree.
I believe that the best solution will be to keep the installers
separated and implement
https:/
2014-05-20 15:03 GMT+02:00 Urs Liska :
> We already had the idea of letting Frescobaldi handle the LilyPond
> installation in order to offer an easier entry path. On startup it would
> try to determine if a working LilyPond is installed, and if not, offer to
> download and install it. In the same
jeff235 wrote
> 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.)
+1, especially if MIDI playback that works "out-of
Am 20.05.2014 14:55, schrieb 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.
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
On Tuesday, May 20, 2014, Jeff Holland wrote:
>
> 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
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
2014-05-19 15:24 GMT+02:00 Marnen Laibow-Koser :
> Hear, hear! Is the standalone Mac app ready for real use yet? I thought it
> wasn't.
It is not, indeed.
The main problems are:
- PortMIDI is not included in the bundle, and even if it is included
(with the appropriate option of py2app) Frescobal
On Mon, May 19, 2014 at 2:38 AM, Jeff Holland wrote:
>
> 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 Fre
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
2014-05-10 16:49 GMT+02:00 :
> I had been using Frescobaldi successfully on OS X 10.9.2, installed via
> Homebrew. Everything was working well. A few days ago, the Music View (PDF
> viewer) stopped working, showing "Unable to load popplerqt4 module". I don't
> know what broke this. I recently inst
13 matches
Mail list logo