Re: Lilypond/Frescobaldi on Mac Os 12

[Mark Mathias]

On Thu, Oct 6, 2022 at 2:56 PM Jean Abou Samra  wrote:

> Le 06/10/2022 à 14:27, Mark Mathias a écrit :
> > I am introducing an orchestra teacher friend to Lilypond/Frescobaldi.
> > We tried to install Lilypond on a Mac Os 12 notebook, but got an error
> > message saying Lilypond wasn't compatible with that version. Our next
> > step will be to install it on her home PC, but at some point it would
> > be nice to be able to use her Mac at work with Lilypond.
> >
> > Is there anything we can do besides wait? If that is the case, does
> > anyone have an idea of how long the wait will be?
>
>
>
>
> LilyPond 2.22, the latest stable version, does not have official
> 64-bit binaries, but as Thomas said, you can get around this by
> installing from MacPorts.
>
> Alternatively, you could use the latest unstable version, 2.23.13,
> for which 64-bit binaries are provided officially. See
> https://lilypond.org/development.html
>
> The next stable release, LilyPond 2.24, will have 64-bit official
> binaries and is planned to come around mid-December if all goes
> well.
>
> Best,
> Jean
>


Thank you so much, Jean and Thomas!

I'm embarrassed to say, I read that info on the website, but didn't really
"get it" since I'm not a Mac person and neither is she. We'll explore the
MacPorts solution together.

Blessings!
Mark

Beautiful music is God's love made audible.

Re: Lilypond/Frescobaldi on Mac Os 12

[Jean Abou Samra]

Le 06/10/2022 à 14:27, Mark Mathias a écrit :
I am introducing an orchestra teacher friend to Lilypond/Frescobaldi. 
We tried to install Lilypond on a Mac Os 12 notebook, but got an error 
message saying Lilypond wasn't compatible with that version. Our next 
step will be to install it on her home PC, but at some point it would 
be nice to be able to use her Mac at work with Lilypond.


Is there anything we can do besides wait? If that is the case, does 
anyone have an idea of how long the wait will be?





LilyPond 2.22, the latest stable version, does not have official
64-bit binaries, but as Thomas said, you can get around this by
installing from MacPorts.

Alternatively, you could use the latest unstable version, 2.23.13,
for which 64-bit binaries are provided officially. See
https://lilypond.org/development.html

The next stable release, LilyPond 2.24, will have 64-bit official
binaries and is planned to come around mid-December if all goes
well.

Best,
Jean

Re: Lilypond/Frescobaldi on Mac Os 12

[Thomas Scharkowski]

> Am 06.10.2022 um 14:27 schrieb Mark Mathias :
> 
> I am introducing an orchestra teacher friend to Lilypond/Frescobaldi. We 
> tried to install Lilypond on a Mac Os 12 notebook, but got an error message 
> saying Lilypond wasn't compatible with that version. Our next step will be to 
> install it on her home PC, but at some point it would be nice to be able to 
> use her Mac at work with Lilypond. 
> 
> Is there anything we can do besides wait? If that is the case, does anyone 
> have an idea of how long the wait will be?
> 
> As always, thank you!
> Mark

Hi Mark,

on my MacBook M1 / macOS 12.6 both LilyPond and Frescobaldi run fine; I 
installed with MacPorts though.

Thomas

Lilypond/Frescobaldi on Mac Os 12

[Mark Mathias]

I am introducing an orchestra teacher friend to Lilypond/Frescobaldi. We
tried to install Lilypond on a Mac Os 12 notebook, but got an error message
saying Lilypond wasn't compatible with that version. Our next step will be
to install it on her home PC, but at some point it would be nice to be able
to use her Mac at work with Lilypond.

Is there anything we can do besides wait? If that is the case, does anyone
have an idea of how long the wait will be?

As always, thank you!
Mark

Re: Frescobaldi on Mac Yosemite ?

[Omer Katzir]

Works great

On Sat, Feb 14, 2015 at 8:16 AM, Philippe Massart 
wrote:

> Yes it works fine.
>
> But if you prefer, there is now a compiled binary on a .DMG disk image
> available from the frescobaldi website:
>
> https://github.com/wbsoft/frescobaldi/releases
>
>
>
> > Le 14 févr. 2015 à 01:52, Steve Noland  a écrit :
> >
> > Dear all,
> >
> > Has Frescobaldi been successfully installed under Mac Yosemite via
> MacPorts?
> >
> > Thanks,
> >
> > Steve
> >
> > ___
> > lilypond-user mailing list
> > lilypond-user@gnu.org
> > https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>



-- 
Omer Katzir
The Silent Troubadour
http://omerkatzir.com
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Frescobaldi on Mac Yosemite ?

[Philippe Massart]

Yes it works fine.

But if you prefer, there is now a compiled binary on a .DMG disk image 
available from the frescobaldi website:

https://github.com/wbsoft/frescobaldi/releases



> Le 14 févr. 2015 à 01:52, Steve Noland  a écrit :
> 
> Dear all,
> 
> Has Frescobaldi been successfully installed under Mac Yosemite via MacPorts?
> 
> Thanks,
> 
> Steve
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Frescobaldi on Mac Yosemite ?

[Steve Noland]

Dear all,

Has Frescobaldi been successfully installed under Mac Yosemite via MacPorts?

Thanks,

Steve

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Installation instructions for Frescobaldi on Mac OS X

[Wilbert Berendsen]

Fantastic work. Thanks!
Wilbert

-- 
Wilbert Berendsen (www.wilbertberendsen.nl)

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Installation instructions for Frescobaldi on Mac OS X

[Davide Liessi]

Dear all,
the installation instructions for Frescobaldi on Mac OS X have been updated.
You can find them in the wiki of Frescobaldi's GitHub repository:
https://github.com/wbsoft/frescobaldi/wiki
(The French translation will hopefully be updated soon.)

The instructions have been reorganized and partially rewritten, and
they now present both the Homebrew- and the MacPorts-based
installation methods.

Best wishes.
Davide

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Frescobaldi on Mac installation instructions moved to Frescobaldi's wiki

[Davide Liessi]

Dear Paul,

2014-01-28 Paul Morris :
> The migration instructions worked well for me.

I'm glad to hear this.

> However, there was one line in them that was unclear to me:
>
> "You may delete the Portfile repository directory, even though it doesn’t
> interfere with the installation."
>
> Which directory is this?  (Not a big deal, since this is optional...)

My wording is actually unclear.

I meant the directory in which you cloned my Portfile repository
(https://github.com/dliessi/ports) when you first used it.
The line that you deleted in /opt/local/etc/macports/sources.conf
contained the path to that directory.
It could be a directory in your home folder (e.g. ~/github/ports), or
maybe /opt/dliessi.

I'll clarify and update the instructions later.

Best wishes.
Davide

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Frescobaldi on Mac installation instructions moved to Frescobaldi's wiki

[Paul Morris]

Davide Liessi-2 wrote
> the installation instructions for Frescobaldi on Mac OS X have been moved
> to Frescobaldi's wiki
> (https://github.com/wbsoft/frescobaldi/wiki).

Thanks Davide!  The migration instructions worked well for me.  However,
there was one line in them that was unclear to me:

"You may delete the Portfile repository directory, even though it doesn’t
interfere with the installation."  

Which directory is this?  (Not a big deal, since this is optional...)

Thanks again!
-Paul



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Frescobaldi-on-Mac-installation-instructions-moved-to-Frescobaldi-s-wiki-tp158539p158596.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac

[Davide Liessi]

2014-01-26 carltesta :
> Running Frescobaldi. When I try to run frescobaldi from the MacPorts
> directory, I get the following error: See the screenshot.
> 
>
> When I open the console, this is the error I get.
> 

Both of them are not very informative. :)

Can you please do what follows?
Open the Terminal and enter
/opt/local/bin/frescobaldi
Frescobaldi should start and (probably) give the same error, but this
time there will be some (hopefully more meaningful) messages in the
Terminal.
Close Frescobaldi and copy&paste here the full Terminal transcript
(starting from the line you entered).

Best wishes.
Davide

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Frescobaldi on Mac installation instructions moved to Frescobaldi's wiki

[Davide Liessi]

Dear Frescobaldi & Mac users,

the installation instructions for Frescobaldi on Mac OS X have been
moved to Frescobaldi's wiki
(https://github.com/wbsoft/frescobaldi/wiki).

They have also been updated, as a consequence of a recent
reorganization of the Portfile for Poppler, so it is no longer
necessary to install Poppler separately before Frescobaldi.

You can find them at
- 
https://github.com/wbsoft/frescobaldi/wiki/How-to-install-Frescobaldi-on-Mac-OS-X
(English)
- 
https://github.com/wbsoft/frescobaldi/wiki/Comment-installer-Frescobaldi-sous-Mac-OS-X
(français)
- 
https://github.com/wbsoft/frescobaldi/wiki/Come-installare-Frescobaldi-in-Mac-OS-X
(italiano)

Best wishes.
Davide

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac

[carltesta]

Running Frescobaldi. When I try to run frescobaldi from the MacPorts
directory, I get the following error: See the screenshot.
<http://lilypond.1069038.n5.nabble.com/file/n158466/screenshot.png> 

When I open the console, this is the error I get.
<http://lilypond.1069038.n5.nabble.com/file/n158466/screenshot2.png> 

Thank You
Carl



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/ANNOUNCE-New-Portfile-for-Frescobaldi-on-Mac-tp150564p158466.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac

[Davide Liessi]

Dear Carl,

2014/1/25 carltesta :
> But Frescobaldi still doesn't run on Mavericks.

Do you have problems installing or running Frescobaldi?
Can you explain exactly what happens?

Best wishes.
Davide

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac

[carltesta]

I have run selfupdate for Macports and run upgrade outdated as well. But
Frescobaldi still doesn't run on Mavericks. Is there something else that
needs to be done to get Frescobaldi running again?

Thanks,
Carl



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/ANNOUNCE-New-Portfile-for-Frescobaldi-on-Mac-tp150564p158454.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac

[Davide Liessi]

2013/10/30 Jean-Alexis Montignies :
> Don’t try to do update on Mavericks (MacOS 10.9) as QT is currently not 
> compiling.
> If installed before upgrading to 10.9, Frescobaldi continues to work.

The problem is now (apparently) solved:
https://trac.macports.org/ticket/40852
https://trac.macports.org/changeset/112811
https://trac.macports.org/changeset/112821

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac

[Henning Hraban Ramm]

Am 2013-10-31 um 10:23 schrieb Tim McNamara :

> It may be necessary to install the new version of the developer software and 
> the associated command line tools in order for MacPorts to update correctly.  
> It may also be that the new OS broke something that has to be fixed.  

Yep, as was written, QT doesn’t compile; I didn’t look into the error yet, that 
GUI stuff is mostly too complicated for me anyway...

> I do still find myself using Marc's LilyEditor as it's quicker to launch (I 
> apparently can't assign .ly and .ily files to go to Frescobaldi when double 
> clicked, for some reason unknown to me, so when I have to do something quick 
> LilyEditor gets the file).

Then probably there’s something missing in the setup.py; I use my own, that 
contains:

CFBundleDocumentTypes = [
{'CFBundleTypeExtensions': ['ly'],
 'CFBundleTypeName':'LilyPond File',
 'CFBundleTypeRole':'Editor'}
]

That sets Frescobaldi as editor for .ly files.


Greetlings, Hraban
---
fiëé visuëlle
Henning Hraban Ramm
http://www.fiee.net
http://angerweit.tikon.ch/lieder/
https://www.cacert.org (I'm an assurer)





___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac

[Tim McNamara]

On Oct 30, 2013, at 4:54 AM, Jean-Alexis Montignies  
wrote:

> Warning!
> 
> Don’t try to do update on Mavericks (MacOS 10.9) as QT is currently not 
> compiling.
> If installed before upgrading to 10.9, Frescobaldi continues to work.

Thanks for the heads-up.  

It may be necessary to install the new version of the developer software and 
the associated command line tools in order for MacPorts to update correctly.  
It may also be that the new OS broke something that has to be fixed.  

I hadn't updated to Mavericks yet and may put that off for a while due to this 
and another issue- I will also lose my favorite NNTP client as it requires Open 
Transport (a legacy item that's almost 20 years old, finally expunged after 
hanging around from System 7.5.2 through OS X 10.8.5).  Sad to see 
MT-NewsWatcher go.

OTOH, for the first time in many installation attempts, Frescobaldi does 
finally work on my Mac under 10.8.5 thanks to the latest portfile.  I was 
highly surprised when it worked!  Nice job, David L.

I do still find myself using Marc's LilyEditor as it's quicker to launch (I 
apparently can't assign .ly and .ily files to go to Frescobaldi when double 
clicked, for some reason unknown to me, so when I have to do something quick 
LilyEditor gets the file).
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac

[Derek]

Too late for me I had to do a fresh install of os x and totally borked me
Macports/frescobaldi install..



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/ANNOUNCE-New-Portfile-for-Frescobaldi-on-Mac-tp150564p153150.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac

[Jean-Alexis Montignies]

Warning!

Don’t try to do update on Mavericks (MacOS 10.9) as QT is currently not 
compiling.
If installed before upgrading to 10.9, Frescobaldi continues to work.

Jean-Alexis


On 18 oct. 2013, at 03:23, Paul Morris  wrote:

> Davide,  Thanks for the portfile and the easy to follow guide for it!  I
> successfully upgraded to the new Frescobaldi 2.0.11 using your portfile for
> the first time.  It all went smoothly.  A big improvement over doing it
> manually as I had done it before.  
> 
> The app bundle is a nice bonus.  I just realized that that was done by your
> portfile (rather than Frescobaldi itself...).  
> 
> Thanks!
> -Paul
> 
> 
> 
> --
> View this message in context: 
> http://lilypond.1069038.n5.nabble.com/ANNOUNCE-New-Portfile-for-Frescobaldi-on-Mac-tp150564p152528.html
> Sent from the User mailing list archive at Nabble.com.
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac

[Paul Morris]

Davide,  Thanks for the portfile and the easy to follow guide for it!  I
successfully upgraded to the new Frescobaldi 2.0.11 using your portfile for
the first time.  It all went smoothly.  A big improvement over doing it
manually as I had done it before.  

The app bundle is a nice bonus.  I just realized that that was done by your
portfile (rather than Frescobaldi itself...).  

Thanks!
-Paul



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/ANNOUNCE-New-Portfile-for-Frescobaldi-on-Mac-tp150564p152528.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Survey for users of Frescobaldi on Mac

[Davide Liessi]

Dear users of Frescobaldi on Mac,

if you installed Frescobaldi through MacPorts using the Portfiles
provided at https://github.com/dliessi/ports, I would be grateful if
you could answer some questions.

1. Did you install "frescobaldi" or "frescobaldi-devel"?

2. If you installed "frescobaldi-devel": why did you install it
instead of "frescobaldi"?
- to have the application bundle
- to have an installation closer to the development version
- other reasons

3. If you installed "frescobaldi-devel" because of the application
bundle: once Frescobaldi 2.0.11 will be out and the application bundle
will be created also for "frescobaldi", will you keep
"frescobaldi-devel" or will you install "frescobaldi" instead?

I don't want to clutter the mailing list, so please answer privately.
I will post the aggregate data to the list, in case somebody is interested.

Best wishes.
Davide

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

RE: [ANNOUNCE] New Portfile for Frescobaldi on Mac

[Steve Noland]

Dear David Liessi,

I used your procedure to install Frescobaldi on a MacBook Pro under Mountain 
Lion.  Went flawlessly!!  Took under an hour, mostly due to compile times.  
Works fine!  Thanks very much!!

Best regards,

Steve


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac (Wilbert Berendsen)

[Vaughan McAlley]

On 17 September 2013 19:55, Davide Liessi  wrote:

> Dear Guy,
>
> 2013/9/17 Guy Stalnaker :
> > 3. run "sudo port selfupdate" to get things up to date after the clean
> and
> > FileVault issues (this took well over SIX hours -- good gawd)
>
> Are you really saying that "sudo port selfupdate" took six hours? Or
> was it a "sudo port upgrade outdated" after the selfupdate?
> The latter could be OK, if there were large ports to be compiled from
> source; I would be very worried of the former.
>
> > 
> > [Lots of traceback calls]
> > import popplerqt4
> > RuntimeError: the sip module implements API v10.0 to v10.1 but the
> > popplerqt4 module requires API v9.1
> > 
>
> Usually this means that sip was updated but pyqt4 or
> python-poppler-qt4 still are not.
> The solution would be the one mentioned by Philippe: rebuild
> py27-pyqt4 and py27-python-poppler-qt4. [1]
>
> There actually was an update of sip port yesterday that I didn't
> notice until now, but...
>
> > "port installed" shows:
> >
> > 
> > Anorien% sudo port installed | grep sip
> >   py27-sip @4.13.3_0
> >   py27-sip @4.14.2_0
> >   py27-sip @4.15.1_0 (active)
> > Anorien [sudo port installed | grep sip] ~
> > 13-09-16 10:45PM
> > Anorien% sudo port installed | grep poppler
> >   poppler @0.20.5_0+qt4+quartz
> >   poppler @0.22.0_0+qt4+quartz
> >   poppler @0.24.1_0+qt4+quartz (active)
> >   poppler-data @0.4.6_0 (active)
> >   py27-python-poppler-qt4 @0.16.3_1 (active)
> > 
>
> ... you apparently have the same versions installed as me, and not the
> newer version of sip, and my installation doesn't have sip API
> problems.
>
> (Just a side note: you don't need to use "sudo" with port commands if
> you are only retrieving information about ports.)
>
> Anyway, I've just updated all ports ("sudo port sync", "sudo port
> upgrade outdated") without rebuilding python-poppler-qt4, and they are
> still working as expected.
>
> Maybe the outdated port is pyqt4: can you tell me the output of "port
> installed name:pyqt4"?
>
> > I cannot deactivate the active py27-sip or poppler. I get a dependency
> > errors.
>
> MacPorts doesn't let you deactivate ports that are dependencies of
> other ports: you must use the force ("-f") option if you really want
> to do that.
>
> > I installed the non-devel frescobaldi and get the exact same error on
> > running from terminal.
>
> OK. I don't think it is a problem with Frescobaldi.
>
> 2013/9/17 Guy Stalnaker :
> > I have a working frescobaldi. I had to  download the latest popplerqt4
> from
> > the poppler source. I did the bad thing and installed it over the old,
> but I
> > have a working frescobaldi and that's the important thing.
>
> Let me say this: yes, you did the bad thing.
> If you manually installed stuff inside MacPorts' tree (/opt/local),
> it's very likely that you are going to have similar problems in the
> future.
>
> Now you have a working Frescobaldi, but if you'll have problems in the
> future, I'll be happy to help.
>
> Best wishes.
> Davide
>
>
> [1] This is a task for Portfile writers: whenever a dependency x of
> port y is updated and rebuilding port y is required, the Portfile
> writer increases the "revision number" of port y, so MacPorts knows
> that there was an update, even if the version number does not change.
> This is usually done at the same time as the update in port x, but
> since my Portfiles aren't in the main repository, I need to notice the
> update of port sip and then update my ports.
> Anyway, the latest update of sip didn't change the API, so this is not
> what happened this time.
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
Davide, you are (as we say in Australia) an utter legend!

I was reluctant to touch my painfully installed, nearly working version of
Frescobaldi, but it broke when I tried to install something else. There was
a problem installing Poppler, but uninstalling and reinstalling the
dependencies fixed that. Now for the first time MIDI is working (I had
assumed Portmidi was permanently broken on Mac), and Poppler can now
display large documents properly.

Thank you!
Vaughan
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac (Wilbert Berendsen)

[pls]

On 18.09.2013, at 04:42, Guy Stalnaker  wrote:

> Davide, 
> 
> Success!! I followed your guide for uninstalling and reinstalling and it all 
> now works!
> 
> Thank you very much for your continued help and guidance. And for the 
> Frescobaldi port! 
+1
> 
> Best regards,
> 
> Guy
> 
> Guy Stalnaker
> jimmyg...@gmail.com
> 
> 
> On Tue, Sep 17, 2013 at 9:17 AM, Davide Liessi  
> wrote:
> Dear Guy,
> 
> 2013/9/17 Guy Stalnaker :
> > Thank you for this explanatory reply. I'm one of those people who actually 
> > appreciates them :-)
> 
> I'm glad to hear this.
> Also this message is a bit long... :)
> 
> > In your reply you mention rebuilding popplerqt4.  How is that done?
> 
> The easiest way to rebuild a port is "sudo port -f uninstall portname"
> followed by "sudo port install portname".
> The "-f" flag is necessary if the port is a dependency of another
> port, as in this case.
> If you want to rebuild all ports that may be involved in this issue, try this:
> 
> $ sudo port -f uninstall py27-python-poppler-qt4
> $ sudo port -f uninstall py27-pyqt4
> $ sudo port -f uninstall py27-sip
> $ sudo port -f uninstall poppler
> $ sudo port -f uninstall frescobaldi
> $ sudo port -f uninstall frescobaldi-devel
> 
> Maybe you have multiple versions of these ports installed (previous
> deactivated versions).
> In this case MacPorts will report an error, asking to specify exactly
> which port you want to uninstall.
> E.g. let's say that you have this situation:
> 
> $ port installed name:sip
> The following ports are currently installed:
>   py27-sip @4.15.1_0
>   py27-sip @4.15.2_0 (active)
> 
> MacPorts will report this:
> 
> $ sudo port -f uninstall py27-sip
> --->  The following versions of py27-sip are currently installed:
> --->  py27-sip @4.15.1_0
> --->  py27-sip @4.15.2_0 (active)
> Error: port uninstall failed: Registry error: Please specify the full
> version as recorded in the port registry.
> 
> In this case you actually want to uninstall only the active version,
> so you will reissue the uninstall command specifying the version:
> 
> $ sudo port -f uninstall py27-sip @4.15.2_0
> 
> Do this for each port that has multiple versions.
> 
> After you have successfully uninstalled all those ports, install
> poppler with the requested variants:
> 
> $ sudo port install poppler +qt4 +quartz
> 
> Then you can install Frescobaldi again with
> $ sudo port install frescobaldi
> or
> $ sudo port install frescobaldi-devel
> or
> $ sudo port install frescobaldi-devel +app
> This will make MacPorts reinstall also Frescobaldi's dependencies.
> 
> Technically it is not necessary to uninstall Frescobaldi and reinstall
> it, nor to uninstall each of these ports, but this is the simplest way
> to achieve what we want.
> 
> Let me know what happens.
> 
> Best wishes.
> Davide
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac (Wilbert Berendsen)

[Guy Stalnaker]

Davide,

Success!! I followed your guide for uninstalling and reinstalling and it
all now works!

Thank you very much for your continued help and guidance. And for the
Frescobaldi port!

Best regards,

Guy

Guy Stalnaker
jimmyg...@gmail.com


On Tue, Sep 17, 2013 at 9:17 AM, Davide Liessi wrote:

> Dear Guy,
>
> 2013/9/17 Guy Stalnaker :
> > Thank you for this explanatory reply. I'm one of those people who
> actually appreciates them :-)
>
> I'm glad to hear this.
> Also this message is a bit long... :)
>
> > In your reply you mention rebuilding popplerqt4.  How is that done?
>
> The easiest way to rebuild a port is "sudo port -f uninstall portname"
> followed by "sudo port install portname".
> The "-f" flag is necessary if the port is a dependency of another
> port, as in this case.
> If you want to rebuild all ports that may be involved in this issue, try
> this:
>
> $ sudo port -f uninstall py27-python-poppler-qt4
> $ sudo port -f uninstall py27-pyqt4
> $ sudo port -f uninstall py27-sip
> $ sudo port -f uninstall poppler
> $ sudo port -f uninstall frescobaldi
> $ sudo port -f uninstall frescobaldi-devel
>
> Maybe you have multiple versions of these ports installed (previous
> deactivated versions).
> In this case MacPorts will report an error, asking to specify exactly
> which port you want to uninstall.
> E.g. let's say that you have this situation:
>
> $ port installed name:sip
> The following ports are currently installed:
>   py27-sip @4.15.1_0
>   py27-sip @4.15.2_0 (active)
>
> MacPorts will report this:
>
> $ sudo port -f uninstall py27-sip
> --->  The following versions of py27-sip are currently installed:
> --->  py27-sip @4.15.1_0
> --->  py27-sip @4.15.2_0 (active)
> Error: port uninstall failed: Registry error: Please specify the full
> version as recorded in the port registry.
>
> In this case you actually want to uninstall only the active version,
> so you will reissue the uninstall command specifying the version:
>
> $ sudo port -f uninstall py27-sip @4.15.2_0
>
> Do this for each port that has multiple versions.
>
> After you have successfully uninstalled all those ports, install
> poppler with the requested variants:
>
> $ sudo port install poppler +qt4 +quartz
>
> Then you can install Frescobaldi again with
> $ sudo port install frescobaldi
> or
> $ sudo port install frescobaldi-devel
> or
> $ sudo port install frescobaldi-devel +app
> This will make MacPorts reinstall also Frescobaldi's dependencies.
>
> Technically it is not necessary to uninstall Frescobaldi and reinstall
> it, nor to uninstall each of these ports, but this is the simplest way
> to achieve what we want.
>
> Let me know what happens.
>
> Best wishes.
> Davide
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac (Wilbert Berendsen)

[Davide Liessi]

Dear Patrick,

2013/9/17 pls :
[...]
> Do I have to worry (or do anything) about it?

This is the same kind of error that you get if you manually placed
files in /opt/local, but it can happen also if for some reason there
is a corruption in MacPorts' database of files.
The successful forced activation should have solved the problem: all
needed files were placed where they belong, so the affected port
should work correctly.
Since your copy of Frescobaldi is working as expected, I wouldn't worry.

Best wishes.
Davide

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac (Wilbert Berendsen)

[pls]

Hi Davide,

thanks for your portfile and your detailed instructions!  Now I have 
frescobaldi-devel up and running!  I just wanted to mention that I got the 
following error:

Error: org.macports.activate for port py27-cx_Freeze returned: Image error: 
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/cxfreeze 
already exists and does not belong to a registered port.  Unable to activate 
port py27-cx_Freeze. Use 'port -f activate py27-cx_Freeze' to force the 
activation.
Error: Failed to install py27-cx_Freeze
Please see the log file for port py27-cx_Freeze for details:

/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-cx_Freeze/py27-cx_Freeze/main.log
Error: The following dependencies were not installed: py27-cx_Freeze py27-pyqt4 
py27-sip py27-python-poppler-qt4

I did sudo port -f activate py27-cx_Freeze to force the activation. I got quite 
a few warnings such as:
Warning: File 
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/cxfreeze 
already exists.  Moving to: 
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/cxfreeze.mp_1379430873.

Do I have to worry (or do anything) about it?

Thanks for your help!
patrick
On 17.09.2013, at 16:17, Davide Liessi  wrote:

> Dear Guy,
> 
> 2013/9/17 Guy Stalnaker :
>> Thank you for this explanatory reply. I'm one of those people who actually 
>> appreciates them :-)
> 
> I'm glad to hear this.
> Also this message is a bit long... :)
> 
>> In your reply you mention rebuilding popplerqt4.  How is that done?
> 
> The easiest way to rebuild a port is "sudo port -f uninstall portname"
> followed by "sudo port install portname".
> The "-f" flag is necessary if the port is a dependency of another
> port, as in this case.
> If you want to rebuild all ports that may be involved in this issue, try this:
> 
> $ sudo port -f uninstall py27-python-poppler-qt4
> $ sudo port -f uninstall py27-pyqt4
> $ sudo port -f uninstall py27-sip
> $ sudo port -f uninstall poppler
> $ sudo port -f uninstall frescobaldi
> $ sudo port -f uninstall frescobaldi-devel
> 
> Maybe you have multiple versions of these ports installed (previous
> deactivated versions).
> In this case MacPorts will report an error, asking to specify exactly
> which port you want to uninstall.
> E.g. let's say that you have this situation:
> 
> $ port installed name:sip
> The following ports are currently installed:
>  py27-sip @4.15.1_0
>  py27-sip @4.15.2_0 (active)
> 
> MacPorts will report this:
> 
> $ sudo port -f uninstall py27-sip
> --->  The following versions of py27-sip are currently installed:
> --->  py27-sip @4.15.1_0
> --->  py27-sip @4.15.2_0 (active)
> Error: port uninstall failed: Registry error: Please specify the full
> version as recorded in the port registry.
> 
> In this case you actually want to uninstall only the active version,
> so you will reissue the uninstall command specifying the version:
> 
> $ sudo port -f uninstall py27-sip @4.15.2_0
> 
> Do this for each port that has multiple versions.
> 
> After you have successfully uninstalled all those ports, install
> poppler with the requested variants:
> 
> $ sudo port install poppler +qt4 +quartz
> 
> Then you can install Frescobaldi again with
> $ sudo port install frescobaldi
> or
> $ sudo port install frescobaldi-devel
> or
> $ sudo port install frescobaldi-devel +app
> This will make MacPorts reinstall also Frescobaldi's dependencies.
> 
> Technically it is not necessary to uninstall Frescobaldi and reinstall
> it, nor to uninstall each of these ports, but this is the simplest way
> to achieve what we want.
> 
> Let me know what happens.
> 
> Best wishes.
> Davide
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac (Wilbert Berendsen)

[Davide Liessi]

Dear Guy,

2013/9/17 Guy Stalnaker :
> Thank you for this explanatory reply. I'm one of those people who actually 
> appreciates them :-)

I'm glad to hear this.
Also this message is a bit long... :)

> In your reply you mention rebuilding popplerqt4.  How is that done?

The easiest way to rebuild a port is "sudo port -f uninstall portname"
followed by "sudo port install portname".
The "-f" flag is necessary if the port is a dependency of another
port, as in this case.
If you want to rebuild all ports that may be involved in this issue, try this:

$ sudo port -f uninstall py27-python-poppler-qt4
$ sudo port -f uninstall py27-pyqt4
$ sudo port -f uninstall py27-sip
$ sudo port -f uninstall poppler
$ sudo port -f uninstall frescobaldi
$ sudo port -f uninstall frescobaldi-devel

Maybe you have multiple versions of these ports installed (previous
deactivated versions).
In this case MacPorts will report an error, asking to specify exactly
which port you want to uninstall.
E.g. let's say that you have this situation:

$ port installed name:sip
The following ports are currently installed:
  py27-sip @4.15.1_0
  py27-sip @4.15.2_0 (active)

MacPorts will report this:

$ sudo port -f uninstall py27-sip
--->  The following versions of py27-sip are currently installed:
--->  py27-sip @4.15.1_0
--->  py27-sip @4.15.2_0 (active)
Error: port uninstall failed: Registry error: Please specify the full
version as recorded in the port registry.

In this case you actually want to uninstall only the active version,
so you will reissue the uninstall command specifying the version:

$ sudo port -f uninstall py27-sip @4.15.2_0

Do this for each port that has multiple versions.

After you have successfully uninstalled all those ports, install
poppler with the requested variants:

$ sudo port install poppler +qt4 +quartz

Then you can install Frescobaldi again with
$ sudo port install frescobaldi
or
$ sudo port install frescobaldi-devel
or
$ sudo port install frescobaldi-devel +app
This will make MacPorts reinstall also Frescobaldi's dependencies.

Technically it is not necessary to uninstall Frescobaldi and reinstall
it, nor to uninstall each of these ports, but this is the simplest way
to achieve what we want.

Let me know what happens.

Best wishes.
Davide

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac (Wilbert Berendsen)

[Guy Stalnaker]

Davide,

Thank you for this explanatory reply. I'm one of those people who actually 
appreciates them :-)

In your reply you mention rebuilding popplerqt4.  How is that done? I took the 
course to install the latest version from source thinking I had exhausted my 
options with MacPorts. I did misspeak--the six hours was likely following the 
outdated command and not self update.

Guy Stalnaker
jstal...@wisc.edu
jimmyg...@gmail.com

On Sep 17, 2013, at 4:55 AM, Davide Liessi  wrote:

> Dear Guy,
> 
> 2013/9/17 Guy Stalnaker :
>> 3. run "sudo port selfupdate" to get things up to date after the clean and
>> FileVault issues (this took well over SIX hours -- good gawd)
> 
> Are you really saying that "sudo port selfupdate" took six hours? Or
> was it a "sudo port upgrade outdated" after the selfupdate?
> The latter could be OK, if there were large ports to be compiled from
> source; I would be very worried of the former.
> 
>> 
>> [Lots of traceback calls]
>>import popplerqt4
>> RuntimeError: the sip module implements API v10.0 to v10.1 but the
>> popplerqt4 module requires API v9.1
>> 
> 
> Usually this means that sip was updated but pyqt4 or
> python-poppler-qt4 still are not.
> The solution would be the one mentioned by Philippe: rebuild
> py27-pyqt4 and py27-python-poppler-qt4. [1]
> 
> There actually was an update of sip port yesterday that I didn't
> notice until now, but...
> 
>> "port installed" shows:
>> 
>> 
>> Anorien% sudo port installed | grep sip
>>  py27-sip @4.13.3_0
>>  py27-sip @4.14.2_0
>>  py27-sip @4.15.1_0 (active)
>> Anorien [sudo port installed | grep sip] ~
>> 13-09-16 10:45PM
>> Anorien% sudo port installed | grep poppler
>>  poppler @0.20.5_0+qt4+quartz
>>  poppler @0.22.0_0+qt4+quartz
>>  poppler @0.24.1_0+qt4+quartz (active)
>>  poppler-data @0.4.6_0 (active)
>>  py27-python-poppler-qt4 @0.16.3_1 (active)
>> 
> 
> ... you apparently have the same versions installed as me, and not the
> newer version of sip, and my installation doesn't have sip API
> problems.
> 
> (Just a side note: you don't need to use "sudo" with port commands if
> you are only retrieving information about ports.)
> 
> Anyway, I've just updated all ports ("sudo port sync", "sudo port
> upgrade outdated") without rebuilding python-poppler-qt4, and they are
> still working as expected.
> 
> Maybe the outdated port is pyqt4: can you tell me the output of "port
> installed name:pyqt4"?
> 
>> I cannot deactivate the active py27-sip or poppler. I get a dependency
>> errors.
> 
> MacPorts doesn't let you deactivate ports that are dependencies of
> other ports: you must use the force ("-f") option if you really want
> to do that.
> 
>> I installed the non-devel frescobaldi and get the exact same error on
>> running from terminal.
> 
> OK. I don't think it is a problem with Frescobaldi.
> 
> 2013/9/17 Guy Stalnaker :
>> I have a working frescobaldi. I had to  download the latest popplerqt4 from
>> the poppler source. I did the bad thing and installed it over the old, but I
>> have a working frescobaldi and that's the important thing.
> 
> Let me say this: yes, you did the bad thing.
> If you manually installed stuff inside MacPorts' tree (/opt/local),
> it's very likely that you are going to have similar problems in the
> future.
> 
> Now you have a working Frescobaldi, but if you'll have problems in the
> future, I'll be happy to help.
> 
> Best wishes.
> Davide
> 
> 
> [1] This is a task for Portfile writers: whenever a dependency x of
> port y is updated and rebuilding port y is required, the Portfile
> writer increases the "revision number" of port y, so MacPorts knows
> that there was an update, even if the version number does not change.
> This is usually done at the same time as the update in port x, but
> since my Portfiles aren't in the main repository, I need to notice the
> update of port sip and then update my ports.
> Anyway, the latest update of sip didn't change the API, so this is not
> what happened this time.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac (Wilbert Berendsen)

[Davide Liessi]

Dear Guy,

2013/9/17 Guy Stalnaker :
> 3. run "sudo port selfupdate" to get things up to date after the clean and
> FileVault issues (this took well over SIX hours -- good gawd)

Are you really saying that "sudo port selfupdate" took six hours? Or
was it a "sudo port upgrade outdated" after the selfupdate?
The latter could be OK, if there were large ports to be compiled from
source; I would be very worried of the former.

> 
> [Lots of traceback calls]
> import popplerqt4
> RuntimeError: the sip module implements API v10.0 to v10.1 but the
> popplerqt4 module requires API v9.1
> 

Usually this means that sip was updated but pyqt4 or
python-poppler-qt4 still are not.
The solution would be the one mentioned by Philippe: rebuild
py27-pyqt4 and py27-python-poppler-qt4. [1]

There actually was an update of sip port yesterday that I didn't
notice until now, but...

> "port installed" shows:
>
> 
> Anorien% sudo port installed | grep sip
>   py27-sip @4.13.3_0
>   py27-sip @4.14.2_0
>   py27-sip @4.15.1_0 (active)
> Anorien [sudo port installed | grep sip] ~
> 13-09-16 10:45PM
> Anorien% sudo port installed | grep poppler
>   poppler @0.20.5_0+qt4+quartz
>   poppler @0.22.0_0+qt4+quartz
>   poppler @0.24.1_0+qt4+quartz (active)
>   poppler-data @0.4.6_0 (active)
>   py27-python-poppler-qt4 @0.16.3_1 (active)
> 

... you apparently have the same versions installed as me, and not the
newer version of sip, and my installation doesn't have sip API
problems.

(Just a side note: you don't need to use "sudo" with port commands if
you are only retrieving information about ports.)

Anyway, I've just updated all ports ("sudo port sync", "sudo port
upgrade outdated") without rebuilding python-poppler-qt4, and they are
still working as expected.

Maybe the outdated port is pyqt4: can you tell me the output of "port
installed name:pyqt4"?

> I cannot deactivate the active py27-sip or poppler. I get a dependency
> errors.

MacPorts doesn't let you deactivate ports that are dependencies of
other ports: you must use the force ("-f") option if you really want
to do that.

> I installed the non-devel frescobaldi and get the exact same error on
> running from terminal.

OK. I don't think it is a problem with Frescobaldi.

2013/9/17 Guy Stalnaker :
> I have a working frescobaldi. I had to  download the latest popplerqt4 from
> the poppler source. I did the bad thing and installed it over the old, but I
> have a working frescobaldi and that's the important thing.

Let me say this: yes, you did the bad thing.
If you manually installed stuff inside MacPorts' tree (/opt/local),
it's very likely that you are going to have similar problems in the
future.

Now you have a working Frescobaldi, but if you'll have problems in the
future, I'll be happy to help.

Best wishes.
Davide


[1] This is a task for Portfile writers: whenever a dependency x of
port y is updated and rebuilding port y is required, the Portfile
writer increases the "revision number" of port y, so MacPorts knows
that there was an update, even if the version number does not change.
This is usually done at the same time as the update in port x, but
since my Portfiles aren't in the main repository, I need to notice the
update of port sip and then update my ports.
Anyway, the latest update of sip didn't change the API, so this is not
what happened this time.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac (Wilbert Berendsen)

[Guy Stalnaker]

All,

Being the stupid can't-let-it-go idiot I am :-)

I have a working frescobaldi. I had to  download the latest popplerqt4 from
the poppler source. I did the bad thing and installed it over the old, but
I have a working frescobaldi and that's the important thing.

Thanks to all three of you for taking the time to look through my problem.
I *greatly* appreciate it.

Guy Stalnaker
jimmyg...@gmail.com


On Tue, Sep 17, 2013 at 12:26 AM, Philippe Massart  wrote:

> I had the same error a few weeks ago, before trying the frescobaldi port
> file. But, it occurred with the "manually installed" version of frescobaldi
> (more precisely: the "manually installed" version of python-poppler-qt4).
>
> The python-poppler-qt4 I had manually installed had been compiled a long
> time ago and didn't recognize the new versions of the Sip API (installed by
> macport). The solution was tho rebuild and re-install the "manually
> installed" python-poppler-qt4, but since your python-poppler-qt4 was
> successfully installed by macport, I guess the problem lies elsewhere.
>
> I'll continue to look at it.
>
> Philippe
>
> Le 17 sept. 2013 à 07:04, Guy Stalnaker  a écrit :
>
> Well, this is certainly been an adventure. Sorry for the delay in
> acknowledging your and Davide's replies, but I've had to jettison using
> FileVault to regain space on the local harddrive. Somehow FileVault was
> holding 30Gb of space and refusing to release it, causing me no end of
> grief in downloading MacPort source and then compiling.
>
> So, finally, I have had to restart this from scratch. I'm afraid I was a
> bit rash in trying to troubleshoot the situation so your proffered solution
> cannot help (but you do describe what I did a year ago when I first
> installed Frescobaldi "python setup.py install"). What I've now done:
>
> 1. remove all traces (port uninstall/rm -rf) of poppler and frescobaldi
> 2. run "sudo port clean" to remove temp files, etc.
> 3. run "sudo port selfupdate" to get things up to date after the clean and
> FileVault issues (this took well over SIX hours -- good gawd)
> 4. run "sudo port install poppler +qt4 +quartz" which completed
> successfully
> 5. run "sudo port install frescobaldi-devel +app" which completed
> succefully
>
> But ...
>
> Frescobaldi crashes on startup:
>
> 
> [Lots of traceback calls]
> import popplerqt4
> RuntimeError: the sip module implements API v10.0 to v10.1 but the
> popplerqt4 module requires API v9.1
> 
>
> "port installed" shows:
>
> 
> Anorien% sudo port installed | grep sip
>   py27-sip @4.13.3_0
>   py27-sip @4.14.2_0
>   py27-sip @4.15.1_0 (active)
> Anorien [sudo port installed | grep sip] ~
>  13-09-16 10:45PM
> Anorien% sudo port installed | grep poppler
>   poppler @0.20.5_0+qt4+quartz
>   poppler @0.22.0_0+qt4+quartz
>   poppler @0.24.1_0+qt4+quartz (active)
>   poppler-data @0.4.6_0 (active)
>   py27-python-poppler-qt4 @0.16.3_1 (active)
> 
>
> I cannot deactivate the active py27-sip or poppler. I get a dependency
> errors.
>
> 
> Anorien% sudo port deactivate py27-sip @4.15.1_0
> Password:
> --->  Deactivating py27-sip @4.15.1_0
> --->  Unable to deactivate py27-sip @4.15.1_0, the following ports depend
> on it:
> --->py27-pyqt4 @4.10.3_1
> --->py27-python-poppler-qt4 @0.16.3_1
> ...
> Anorien% sudo port deactivate poppler @0.24.1_0+qt4+quartz
> --->  Deactivating poppler @0.24.1_0+qt4+quartz
> --->  Unable to deactivate poppler @0.24.1_0+qt4+quartz, the following
> ports depend on it:
> --->py27-python-poppler-qt4 @0.16.3_1
> --->texlive-bin @2013_2+x11
> 
>
> I installed the non-devel frescobaldi and get the exact same error on
> running from terminal.
>
> I "port uninstalled" all old sip/poppler ports and both frescobaldi ports
> and reinstalled, but the API error persists. So I cannot remove it due to
> dependencies (the texlive dependency is especially weighty - there are
> *many* that arise if I try to remove texlive as well).
>
> Any ideas?
>
> 
>
> It's always frustrating when folks post at how it just works for them LOL
> This stuff never just works for me.
>
> Guy Stalnaker
> jimmyg...@gmail.com
>
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac (Wilbert Berendsen)

[Philippe Massart]

I had the same error a few weeks ago, before trying the frescobaldi port file. 
But, it occurred with the "manually installed" version of frescobaldi (more 
precisely: the "manually installed" version of python-poppler-qt4). 

The python-poppler-qt4 I had manually installed had been compiled a long time 
ago and didn't recognize the new versions of the Sip API (installed by 
macport). The solution was tho rebuild and re-install the "manually installed" 
python-poppler-qt4, but since your python-poppler-qt4 was successfully 
installed by macport, I guess the problem lies elsewhere.

I'll continue to look at it.

Philippe

Le 17 sept. 2013 à 07:04, Guy Stalnaker  a écrit :

> Well, this is certainly been an adventure. Sorry for the delay in 
> acknowledging your and Davide's replies, but I've had to jettison using 
> FileVault to regain space on the local harddrive. Somehow FileVault was 
> holding 30Gb of space and refusing to release it, causing me no end of grief 
> in downloading MacPort source and then compiling.
> 
> So, finally, I have had to restart this from scratch. I'm afraid I was a bit 
> rash in trying to troubleshoot the situation so your proffered solution 
> cannot help (but you do describe what I did a year ago when I first installed 
> Frescobaldi "python setup.py install"). What I've now done:
> 
> 1. remove all traces (port uninstall/rm -rf) of poppler and frescobaldi
> 2. run "sudo port clean" to remove temp files, etc.
> 3. run "sudo port selfupdate" to get things up to date after the clean and 
> FileVault issues (this took well over SIX hours -- good gawd)
> 4. run "sudo port install poppler +qt4 +quartz" which completed successfully
> 5. run "sudo port install frescobaldi-devel +app" which completed succefully
>  
> But ...
> 
> Frescobaldi crashes on startup:
> 
> 
> [Lots of traceback calls]
> import popplerqt4
> RuntimeError: the sip module implements API v10.0 to v10.1 but the popplerqt4 
> module requires API v9.1
> 
> 
> "port installed" shows:
> 
> 
> Anorien% sudo port installed | grep sip  
>   py27-sip @4.13.3_0
>   py27-sip @4.14.2_0
>   py27-sip @4.15.1_0 (active)
> Anorien [sudo port installed | grep sip] ~
>   13-09-16 10:45PM
> Anorien% sudo port installed | grep poppler
>   poppler @0.20.5_0+qt4+quartz
>   poppler @0.22.0_0+qt4+quartz
>   poppler @0.24.1_0+qt4+quartz (active)
>   poppler-data @0.4.6_0 (active)
>   py27-python-poppler-qt4 @0.16.3_1 (active)
> 
> 
> I cannot deactivate the active py27-sip or poppler. I get a dependency 
> errors. 
> 
> 
> Anorien% sudo port deactivate py27-sip @4.15.1_0
> Password:
> --->  Deactivating py27-sip @4.15.1_0
> --->  Unable to deactivate py27-sip @4.15.1_0, the following ports depend on 
> it:
> --->py27-pyqt4 @4.10.3_1
> --->py27-python-poppler-qt4 @0.16.3_1
> ...
> Anorien% sudo port deactivate poppler @0.24.1_0+qt4+quartz 
> --->  Deactivating poppler @0.24.1_0+qt4+quartz
> --->  Unable to deactivate poppler @0.24.1_0+qt4+quartz, the following ports 
> depend on it:
> --->py27-python-poppler-qt4 @0.16.3_1
> --->texlive-bin @2013_2+x11
> 
> 
> I installed the non-devel frescobaldi and get the exact same error on running 
> from terminal.
> 
> I "port uninstalled" all old sip/poppler ports and both frescobaldi ports and 
> reinstalled, but the API error persists. So I cannot remove it due to 
> dependencies (the texlive dependency is especially weighty - there are *many* 
> that arise if I try to remove texlive as well).
> 
> Any ideas?
> 
> 
> 
> It's always frustrating when folks post at how it just works for them LOL 
> This stuff never just works for me.
> 
> Guy Stalnaker
> jimmyg...@gmail.com

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac (Wilbert Berendsen)

[Guy Stalnaker]

Well, this is certainly been an adventure. Sorry for the delay in
acknowledging your and Davide's replies, but I've had to jettison using
FileVault to regain space on the local harddrive. Somehow FileVault was
holding 30Gb of space and refusing to release it, causing me no end of
grief in downloading MacPort source and then compiling.

So, finally, I have had to restart this from scratch. I'm afraid I was a
bit rash in trying to troubleshoot the situation so your proffered solution
cannot help (but you do describe what I did a year ago when I first
installed Frescobaldi "python setup.py install"). What I've now done:

1. remove all traces (port uninstall/rm -rf) of poppler and frescobaldi
2. run "sudo port clean" to remove temp files, etc.
3. run "sudo port selfupdate" to get things up to date after the clean and
FileVault issues (this took well over SIX hours -- good gawd)
4. run "sudo port install poppler +qt4 +quartz" which completed successfully
5. run "sudo port install frescobaldi-devel +app" which completed succefully

But ...

Frescobaldi crashes on startup:


[Lots of traceback calls]
import popplerqt4
RuntimeError: the sip module implements API v10.0 to v10.1 but the
popplerqt4 module requires API v9.1


"port installed" shows:


Anorien% sudo port installed | grep sip
  py27-sip @4.13.3_0
  py27-sip @4.14.2_0
  py27-sip @4.15.1_0 (active)
Anorien [sudo port installed | grep sip] ~
 13-09-16 10:45PM
Anorien% sudo port installed | grep poppler
  poppler @0.20.5_0+qt4+quartz
  poppler @0.22.0_0+qt4+quartz
  poppler @0.24.1_0+qt4+quartz (active)
  poppler-data @0.4.6_0 (active)
  py27-python-poppler-qt4 @0.16.3_1 (active)


I cannot deactivate the active py27-sip or poppler. I get a dependency
errors.


Anorien% sudo port deactivate py27-sip @4.15.1_0
Password:
--->  Deactivating py27-sip @4.15.1_0
--->  Unable to deactivate py27-sip @4.15.1_0, the following ports depend
on it:
--->py27-pyqt4 @4.10.3_1
--->py27-python-poppler-qt4 @0.16.3_1
...
Anorien% sudo port deactivate poppler @0.24.1_0+qt4+quartz
--->  Deactivating poppler @0.24.1_0+qt4+quartz
--->  Unable to deactivate poppler @0.24.1_0+qt4+quartz, the following
ports depend on it:
--->py27-python-poppler-qt4 @0.16.3_1
--->texlive-bin @2013_2+x11


I installed the non-devel frescobaldi and get the exact same error on
running from terminal.

I "port uninstalled" all old sip/poppler ports and both frescobaldi ports
and reinstalled, but the API error persists. So I cannot remove it due to
dependencies (the texlive dependency is especially weighty - there are
*many* that arise if I try to remove texlive as well).

Any ideas?



It's always frustrating when folks post at how it just works for them LOL
This stuff never just works for me.

Guy Stalnaker
jimmyg...@gmail.com
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac (Wilbert Berendsen)

[Davide Liessi]

Dear Guy,

2013/9/16 Guy Stalnaker :
> Tonight I tried to use your new port. The port compiles with no errors. The
> macport install process failed when attempting to activate your
> Frescobaldi+devel saying that previous files exist.

I'm sorry I didn't notice this problem on my machine before the
publication of my Portfiles.
I had manually installed Frescobaldi and python-poppler-qt4 but not
with Philippe's guide: I had installed them explicitly setting the
prefix to something different from /opt/local, so they didn't interact
with MacPorts' directory hierarchy.

This problem occurs because when you do "python setup.py install" for
python-poppler-qt4 and Frescobaldi, they are installed inside the
directory tree of the Python version you used (in this case the
MacPorts' one).
So their files are copied inside MacPorts' tree.

When you then install them with my Portfiles, MacPorts tries to copy
the same files in the same locations, but it finds the manually
installed files and refuses to continue.
This is because manually installed files can be user data files (e.g.
databases) or user settings files (like the ones in /opt/local/etc),
so by default MacPorts cannot overwrite files that weren't written by
itself.

Philippe is right when he says that
2013/9/16 Philippe Massart :
> The idea is to really avoid touching manually the macport tree.

The solution, that Philippe mentions, should be simply to force the
activation with '-f' option.
This allows MacPorts to overwrite existing files.

2013/9/16 Guy Stalnaker :
> I did a check by
> attempting to deactivate Frescobaldi, but macports said there was not an
> activated Frescobaldi port.

MacPorts was right: there wasn't an active Frescobaldi or
python-poppler-qt4 port, but it couldn't activate them because there
were already files in place.

2013/9/16 Philippe Massart :
> Now, the errors you have when trying to open files come probably from the
> folders you moved.

Probably.
The best thing to do, in my opinion, is to uninstall
frescobaldi(-devel) and py27-python-poppler-qt4 ports, move back the
folders and files in their original location and then force install
frescobaldi(-devel).
This way all other ports should work correctly and the force install
should take care of overwriting the manually installed files.

2013/9/16 Philippe Massart :
> Like you, I had a manually installed frescobaldi version; since "forcing"
> the activation of the portfile, my both frescobaldi install are now working:
> the one from macport, the other manually installed (and sync via github).

As long as you don't "python setup.py install" Frescobaldi (with the
default prefix) there shouldn't be interaction problems between
MacPorts and manually installed versions.
My advice is to avoid "python setup.py install" for Frescobaldi at all
and run it from its directory.
You can rely on MacPorts for all dependencies (including
python-poppler-qt4) and then have MacPorts' Frescobaldi and, e.g. in
your home directory, multiple directories each with a different
version of Frescobaldi (or a Git repository in which you can switch
versions).

Dear Guy, let us know if you need further assistance and if the "undo
move / force install" solution works for you.
I think I should put a notice on my repository's home page about this
problem, but I'll wait and see if the proposed solution works for you.

Best wishes.
Davide

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac (Wilbert Berendsen)

[Philippe Massart]

Hello,

Before trying to find a solution to your situation (it will take some time to 
investigate), I think interesting to point some possible explanations about 
what occurred.

I think that to problem comes from the coexistence of macport installed 
frescobaldi, and manually installed (even with with macport dependencies): some 
libraries (python-poppler-qt4, mainly) make a link between frescobaldi and 
other dependencies. If these are installed by macports, a file is created in 
the macport install tree. That's why it says that a file already exists when 
trying to activate the "macport frescobaldi". The problem is not frescobaldi 
itself, but the link with the dependencies.

Usually, a macport message error mentions a solution: "force the activation" 
(something like "sudo port -f activate frescobaldi-devel). Macport then makes a 
copy of the former link file and allows the link between the dependencies and 
the "macport installed" frescobaldi (I sent a message to the list about that).

Now, the errors you have when trying to open files come probably from the 
folders you moved. I don't remember if there is a feature like "rebuild" in 
macport, but the first things I would do in this case would be:
- repair authorisation
- re-install macport :/ (or at least remove frescobaldi (the macport version) 
and the dependencies you don't use (to uninstall frescobaldi and its 
dependencies without removing the dependencies used by other ports, I think the 
command looks like sudo port -fellow-dependencies frescobaldi-devel Double 
check in the help of macport)

The idea is to really avoid touching manually the macport tree.

Like you, I had a manually installed frescobaldi version; since "forcing" the 
activation of the portfile, my both frescobaldi install are now working: the 
one from macport, the other manually installed (and sync via github).

Hope this could help (at least for further investigations)

Philippe

Le 16 sept. 2013 à 04:17, Guy Stalnaker  a écrit :

> Davide,
> 
> Prior to using your new port, I had a working Frescobaldi that I installed 
> many months ago using a very cryptic and painful process that required a lot 
> of manual work to get poppler, frescobaldi, etc installed. But, it did work.
> 
> Tonight I tried to use your new port. The port compiles with no errors. The 
> macport install process failed when attempting to activate your 
> Frescobaldi+devel saying that previous files exist. I did a check by 
> attempting to deactivate Frescobaldi, but macports said there was not an 
> activated Frescobaldi port. So I systematically renamed each file/folder 
> using the mv comment as the port activate process for your new Frescobaldi 
> port kept throwing up the errors. Eventually your port successfully activated.
> 
> And, it runs. But any attempt to open a file results in a cascade of errors. 
> First set seem related to code-folding. Then there are more and eventually 
> Frescobaldi crashes.
> 
> Now quite sure how to fix this. If macports said that there was no previous 
> port I don't know how it could remove/clean it to make way for your port. Nor 
> do I know enough to use a terminal (which I do know how to use) to remove 
> things manually. Easy enough to use 'mv path path.old' as the port install 
> was tossing out errors. Not so much to ferret out all the possible things 
> that may be hindering your new port.
> 
> Any suggestions welcome.
> 
> Guy Stalnaker
> jimmyg...@gmail.com
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

[ANNOUNCE] New Portfile for Frescobaldi on Mac (Wilbert Berendsen)

[Guy Stalnaker]

Davide,

Prior to using your new port, I had a working Frescobaldi that I installed
many months ago using a very cryptic and painful process that required a
lot of manual work to get poppler, frescobaldi, etc installed. But, it did
work.

Tonight I tried to use your new port. The port compiles with no errors. The
macport install process failed when attempting to activate your
Frescobaldi+devel saying that previous files exist. I did a check by
attempting to deactivate Frescobaldi, but macports said there was not an
activated Frescobaldi port. So I systematically renamed each file/folder
using the mv comment as the port activate process for your new Frescobaldi
port kept throwing up the errors. Eventually your port successfully
activated.

And, it runs. But any attempt to open a file results in a cascade of
errors. First set seem related to code-folding. Then there are more and
eventually Frescobaldi crashes.

Now quite sure how to fix this. If macports said that there was no previous
port I don't know how it could remove/clean it to make way for your port.
Nor do I know enough to use a terminal (which I do know how to use) to
remove things manually. Easy enough to use 'mv path path.old' as the port
install was tossing out errors. Not so much to ferret out all the possible
things that may be hindering your new port.

Any suggestions welcome.

Guy Stalnaker
jimmyg...@gmail.com
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Jacques Menu]

Hello Davide,

Le 13 sept. 2013 à 16:57, Davide Liessi  a écrit :

> Dear Jacques,
> 
> 2013/9/13 Jacques Menu :
>> - the About menu is in english;
> 
> Are you referring to the "About Frescobaldi" menu entry in the menu
> named "Frescobaldi"

Yes.

> or to the "About Frescobaldi" window that pops up
> when you click on that menu entry?
> All menu entries in the "Frescobaldi" menu are always in English, I
> have yet to understand how to make them switch language; on the other
> hand, the "About..." window should be in French, and if this is not
> the case, it is a new bug.

It's in french alright.

> 
>> - same for the first item in the "Outils" menu to setup a new score.
> 
> This is expected, because (some of) the translation files need to be updated.

OK, same for "
• Configuring the Outline View" 
in the help's table of contents.

A nice w-e!

JM

PS> Didn't find yet how to switch a passage from relative to absolute mode.

--

Jacques Menu
Ch. de la Pierre 12
1023 Crissier

mailto:jacques.m...@tvtmail.ch





___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Davide Liessi]

Dear Jacques,

2013/9/13 Jacques Menu :
> - the About menu is in english;

Are you referring to the "About Frescobaldi" menu entry in the menu
named "Frescobaldi" or to the "About Frescobaldi" window that pops up
when you click on that menu entry?
All menu entries in the "Frescobaldi" menu are always in English, I
have yet to understand how to make them switch language; on the other
hand, the "About..." window should be in French, and if this is not
the case, it is a new bug.

> - same for the first item in the "Outils" menu to setup a new score.

This is expected, because (some of) the translation files need to be updated.

Best wishes.
Davide

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Jacques Menu]

Hello Davide,

After looking around, found two glitches in the french version of 
frescobaldi-devel 2.0.11:

- the About menu is in english;
- same for the first item in the "Outils" menu to setup a new score.

I've switched by default to the Menlo font, designed by Apple to replace Monaco 
as a fixed size font. It's been optimized for various displays, among them the 
Retina ones.

Great app, thanks a lot!

JM

--

Jacques Menu
Ch. de la Pierre 12
1023 Crissier

mailto:jacques.m...@tvtmail.ch




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac

[Stan Sanderson]

Thanks goes also to Wilbert Berendsen for creating Frescobaldi. 

As a Frescobaldi learning exercise, I encoded two pieces by J. F. Froberger - 
Ricereare I and Capriccio XV - a total of 20,018 keystrokes. Frescobaldi cut 
the time required at least by half, and I'm sure there are many shortcuts which 
I have yet to discover.

Stan

On Sep 12, 2013, at 8:02 AM, Wilbert Berendsen  wrote:

> Op Wed, 11 Sep 2013 17:16:21 +0200
> Jacques Menu  schreef:
> 
>> Thanks for everything, both frescobaldi and frescobaldi-devel work
>> fine now!
> 
> Thanks to all people involved to make Frescobaldi on Mac OS X working!
> 
> Best!
> Wilbert
> 
> -- 
> Wilbert Berendsen
> (http://www.wilbertberendsen.nl)
> 
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac

[Wilbert Berendsen]

Op Wed, 11 Sep 2013 17:16:21 +0200
Jacques Menu  schreef:

> Thanks for everything, both frescobaldi and frescobaldi-devel work
> fine now!

Thanks to all people involved to make Frescobaldi on Mac OS X working!

Best!
Wilbert

-- 
Wilbert Berendsen
(http://www.wilbertberendsen.nl)


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac

[Tim McNamara]

On Sep 11, 2013, at 7:50 AM, Jacques Menu  wrote:

> Building python-poppler-qt4-0.16.3 fails on Mac OS X 10.8.4, though, you'll 
> find the trace below.

The choice of Poppler is highly problematic on the Mac for some reason.  I 
wonder if it is possible to rejigger this to use Preview as the engine for 
displaying PDFs.  I would have no idea how to do that...
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac

[Davide Liessi]

Dear Tim,

2013/9/11 Tim McNamara :
> The choice of Poppler is highly problematic on the Mac for some reason.

Why do you think so?

Yes, manually installing all dependencies of Poppler and
python-poppler-qt4 can be a pain.
But MacPorts provides Poppler since long time, and now, with my
Portfiles, also python-poppler-qt4 and frescobaldi can be installed
through MacPorts with just a couple of commands.

> I wonder if it is possible to rejigger this to use Preview as the engine for 
> displaying PDFs.  I would have no idea how to do that...

Neither would I.
But I don't think it is worth the effort (also because it would mean a
lot more platform-specific code).

Best wishes.
Davide

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac

[Jacques Menu]

Hello Davide,

Oops, I missed the fact that popple was implicitly installed.

Thanks for everything, both frescobaldi and frescobaldi-devel work fine now!

JM

Le 11 sept. 2013 à 16:28:49, Davide Liessi  a écrit :

> Dear Jacques,
> 
> 2013/9/11 Jacques Menu :
>> I've followed your recommended steps, synthesized in the script below, and 
>> that works fine.
>> 
>> Building python-poppler-qt4-0.16.3 fails on Mac OS X 10.8.4, though, you'll 
>> find the trace below.
> [...]
> 
> If the command `sudo port install frescobaldi` completed successfully,
> there is no need to install python-poppler-qt4 manually, since it is
> already installed by MacPorts as a dependency of frescobaldi.
> 
> Just try `/opt/local/bin/frescobaldi-2.7` in the Terminal (or simply
> `frescobaldi-2.7` if you have MacPorts' bin directory in your $PATH)
> and see if Frescobaldi launches correctly.
> 
> Best wishes.
> Davide
> 
> 
> P.S: You may want to try the application bundle, since it includes
> some useful patches when working with Frescobaldi on Mac OS X.
> You can give it a try doing the following in the Terminal:
> sudo port deactivate frescobaldi
> sudo port install frescobaldi-devel +app
> You'll find the application bundle inside /Applications/MacPorts/.
> 
> If you then want to switch between the two versions, you just need to do:
> sudo port deactivate frescobaldi-devel
> sudo port activate frescobaldi
> or the other way round, depending on which port is currently active.


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac

[Davide Liessi]

Dear Jacques,

2013/9/11 Jacques Menu :
[...]
> both frescobaldi and frescobaldi-devel work fine now!

Nice to know.

Best wishes.
Davide

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac

[Davide Liessi]

Dear Jacques,

2013/9/11 Jacques Menu :
> I've followed your recommended steps, synthesized in the script below, and 
> that works fine.
>
> Building python-poppler-qt4-0.16.3 fails on Mac OS X 10.8.4, though, you'll 
> find the trace below.
[...]

If the command `sudo port install frescobaldi` completed successfully,
there is no need to install python-poppler-qt4 manually, since it is
already installed by MacPorts as a dependency of frescobaldi.

Just try `/opt/local/bin/frescobaldi-2.7` in the Terminal (or simply
`frescobaldi-2.7` if you have MacPorts' bin directory in your $PATH)
and see if Frescobaldi launches correctly.

Best wishes.
Davide


P.S: You may want to try the application bundle, since it includes
some useful patches when working with Frescobaldi on Mac OS X.
You can give it a try doing the following in the Terminal:
sudo port deactivate frescobaldi
sudo port install frescobaldi-devel +app
You'll find the application bundle inside /Applications/MacPorts/.

If you then want to switch between the two versions, you just need to do:
sudo port deactivate frescobaldi-devel
sudo port activate frescobaldi
or the other way round, depending on which port is currently active.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac

[Jacques Menu]

Hello Davide,

I've followed your recommended steps, synthesized in the script below, and that 
works fine.

Building python-poppler-qt4-0.16.3 fails on Mac OS X 10.8.4, though, you'll 
find the trace below.

JM

--

m...@semac1.epfl.ch > python --version
Python 2.7.2


m...@semac1.epfl.ch > cat InstallFrescobaldiMacPort.sh 
#!/bin/bash

#set -x

echo "--> Gitting dliessi ports"
sudo mkdir /opt/dliessi
echo

cd /opt/dliessi
sudo git clone https://github.com/dliessi/ports.git
echo

echo "--> Contents of /opt/dliessi:"
ls -sal
echo

echo "--> Add the following before the 'rsync://' lines:"
echo "file:///opt/dliessi/ports/"
echo "then type Ctrl-O to save and Ctrl-X to exit."
echo
echo "Type any key to go ahead..."
read VAR

sudo nano /opt/local/etc/macports/sources.conf
echo

echo "--> Indexing port files"
cd /opt/dliessi/ports
sudo portindex
echo

echo "Update MacPorts stuff"
sudo port selfupdate
sudo port sync
sudo port upgrade outdated
echo

echo "--> Installing poppler:"
sudo port install poppler +qt4 +quartz
echo

echo "--> Installing Frescobaldi:"
sudo port install frescobaldi
echo

echo "--> Installing fluidsynth:"
sudo port install fluidsynth
echo


--

m...@semac1.epfl.ch:~/Downloads/python-poppler-qt4-0.16.3 > sudo python 
setup.py install
dyld: DYLD_ environment variables being ignored because main executable 
(/usr/bin/sudo) is setuid or setgid
running install
running bdist_egg
running egg_info
writing python_poppler_qt4.egg-info/PKG-INFO
writing top-level names to python_poppler_qt4.egg-info/top_level.txt
writing dependency_links to python_poppler_qt4.egg-info/dependency_links.txt
reading manifest file 'python_poppler_qt4.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'python_poppler_qt4.egg-info/SOURCES.txt'
installing library code to build/bdist.macosx-10.8-intel/egg
running install_lib
running build_ext
building 'popplerqt4' extension
clang -fno-strict-aliasing -fno-common -dynamic -g -Os -pipe -fno-common 
-fno-strict-aliasing -fwrapv -mno-fused-madd -DENABLE_DTRACE -DMACOSX -DNDEBUG 
-Wall -Wstrict-prototypes -Wshorten-64-to-32 -DNDEBUG -g -Os -Wall 
-Wstrict-prototypes -DENABLE_DTRACE -arch i386 -arch x86_64 -pipe 
-I/usr/local/Cellar/qt/4.8.4/include 
-I/usr/local/Cellar/qt/4.8.4/include/QtCore 
-I/usr/local/Cellar/qt/4.8.4/include/QtGui 
-I/usr/local/Cellar/qt/4.8.4/include/QtXml -I/opt/local/include/poppler/qt4 
-I/opt/local/include/poppler 
-I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 
-I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c 
build/temp.macosx-10.8-intel-2.7/sippopplerqt4cmodule.cpp -o 
build/temp.macosx-10.8-intel-2.7/build/temp.macosx-10.8-intel-2.7/sippopplerqt4cmodule.o

… … …

clang: warning: argument unused during compilation: '-mno-fused-madd'
clang -fno-strict-aliasing -fno-common -dynamic -g -Os -pipe -fno-common 
-fno-strict-aliasing -fwrapv -mno-fused-madd -DENABLE_DTRACE -DMACOSX -DNDEBUG 
-Wall -Wstrict-prototypes -Wshorten-64-to-32 -DNDEBUG -g -Os -Wall 
-Wstrict-prototypes -DENABLE_DTRACE -arch i386 -arch x86_64 -pipe 
-I/usr/local/Cellar/qt/4.8.4/include 
-I/usr/local/Cellar/qt/4.8.4/include/QtCore 
-I/usr/local/Cellar/qt/4.8.4/include/QtGui 
-I/usr/local/Cellar/qt/4.8.4/include/QtXml -I/opt/local/include/poppler/qt4 
-I/opt/local/include/poppler 
-I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 
-I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c 
build/temp.macosx-10.8-intel-2.7/sippopplerqt4QLinkedList0100PopplerAnnotationRevision.cpp
 -o 
build/temp.macosx-10.8-intel-2.7/build/temp.macosx-10.8-intel-2.7/sippopplerqt4QLinkedList0100PopplerAnnotationRevision.o
clang: warning: argument unused during compilation: '-mno-fused-madd'
build/temp.macosx-10.8-intel-2.7/sippopplerqt4QLinkedList0100PopplerAnnotationRevision.cpp:22:55:
 error: 
  no member named 'Revision' in 'Poppler::Annotation'; did you mean 
'revisions'?
reinterpret_cast 
*>(sipDst)[sipDstIdx] =...
 ~^~~~
  revisions
/opt/local/include/poppler/qt4/poppler-annotation.h:392:24: note: 'revisions' 
declared here
QList revisions() const;
   ^
build/temp.macosx-10.8-intel-2.7/sippopplerqt4QLinkedList0100PopplerAnnotationRevision.cpp:22:55:
 error: 
  call to non-static member function without an object argument
reinterpret_cast 
*>(sipDst)[sipDstIdx] =...
 ~^~~~
build/temp.macosx-10.8-intel-2.7/sippopplerqt4QLinkedList0100PopplerAnnotationRevision.cpp:22:75:
 error: 
  subscript of pointer to incomplete type 'void'
reinterpret_cast 
*>(sipDst)[sipDstIdx] =...
   ~~ ^
build/temp.macosx-10.8-intel-2.7/sippopplerqt4QLinkedList0100PopplerAnnotationRevision.cpp:22:146:
 e

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac

[Stan Sanderson]

Installation was very easy and almost everything is working. However, in order 
to use MIDI, I still have to manually start Qsynth to provide Frescobaldi with 
a fluidsynth output port. Is there a simple way to bypass this step or automate 
it from within Frescobaldi?

Stan

On Sep 10, 2013, at 6:09 AM, Davide Liessi  wrote:

> Dear Mac OS X Frescobaldi users,
> 
> [from http://lists.gnu.org/archive/html/lilypond-user/2013-09/msg00030.html]
>> I am currently fine tuning a new version of the Portfile that
>> automatically creates also the application bundle.
>> I just need to test it on 10.7 and 10.8 machines (I run 10.6 and have
>> occasional access to those machines) and then I'll publish it into the
>> master branch of my repository.
>> I'll announce to the list when this will happen (in a couple of days, I 
>> hope).
> 
> I am pleased to announce that a new version of my Portfiles for
> Frescobaldi installation through MacPorts is publicly available in my
> GitHub repository (https://github.com/dliessi/ports).
> 
> New features include the possibility to build a clickable application
> bundle and the inclusion of some useful patches for system language
> handling and automatic detection of default LilyPond installation.
> 
> You'll find instructions on how to install/upgrade in my repository's home 
> page.
> If you need further instructions or if you run into any problems,
> don't hesitate to contact me, either sending me an email message or
> opening an issue on GitHub (https://github.com/dliessi/ports/issues).
> 
> I would like to publicly thank Stefan Vollmar for his help in testing
> my Portfiles.
> 
> Best wishes.
> Davide
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [ANNOUNCE] New Portfile for Frescobaldi on Mac

[Derek]

That is freaking awesome and a breeze to install. Thanks!



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/ANNOUNCE-New-Portfile-for-Frescobaldi-on-Mac-tp150564p150596.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

[ANNOUNCE] New Portfile for Frescobaldi on Mac

[Davide Liessi]

Dear Mac OS X Frescobaldi users,

[from http://lists.gnu.org/archive/html/lilypond-user/2013-09/msg00030.html]
> I am currently fine tuning a new version of the Portfile that
> automatically creates also the application bundle.
> I just need to test it on 10.7 and 10.8 machines (I run 10.6 and have
> occasional access to those machines) and then I'll publish it into the
> master branch of my repository.
> I'll announce to the list when this will happen (in a couple of days, I hope).

I am pleased to announce that a new version of my Portfiles for
Frescobaldi installation through MacPorts is publicly available in my
GitHub repository (https://github.com/dliessi/ports).

New features include the possibility to build a clickable application
bundle and the inclusion of some useful patches for system language
handling and automatic detection of default LilyPond installation.

You'll find instructions on how to install/upgrade in my repository's home page.
If you need further instructions or if you run into any problems,
don't hesitate to contact me, either sending me an email message or
opening an issue on GitHub (https://github.com/dliessi/ports/issues).

I would like to publicly thank Stefan Vollmar for his help in testing
my Portfiles.

Best wishes.
Davide

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Davide Liessi]

2013/9/2 flup2 :
> First of all, thanks for your work, Davide :-)

I'm glad that my work is helpful.

> I installed the portfile and it works without problem.

This is nice to hear!
Just for information, what version of Mac OS are you running?

> For those who already installed Frescobaldi and want to update next versions
> this way, macports detects that python-poppler-qt4 is already installed. We
> need thus to force the installation by macports:
>
> port -f activate py27-python-poppler-qt4
>
> On my setup, the same occurred with frescobaldi itself.

This happens because with your instructions python-poppler-qt4 is
installed inside MacPorts' directory tree.
But MacPorts knows only about files you write inside its tree through
the port command, and it shouldn't overwrite unknown files unless
forced (because they could be user settings, like in etc, or
user-installed packages, like in this case).

> Note: I doesn't break the former setup. I have now a macports installed
> stable version, and the github synced "hand-made" installation. Both are
> running well (for me, the github synced version is easier to work on the
> French translation).

As long as one does not install frescobaldi with 'python setup.py
install', but runs it without installing it, there shouldn't be any
conflicts.

Another solution, which I adopted in my setup prior to writing the
Portfiles, is to install with the --prefix option in a custom
directory tree (other than the MacPorts one).
This requires to set the PYTHONPATH environment variable to a suitable
path (Python itself should tell the exact path in the error message
when installing with PYTHONPATH not correctly set).
Also this kind of setup should not conflict with MacPorts.

I am currently fine tuning a new version of the Portfile that
automatically creates also the application bundle.
I just need to test it on 10.7 and 10.8 machines (I run 10.6 and have
occasional access to those machines) and then I'll publish it into the
master branch of my repository.
I'll announce to the list when this will happen (in a couple of days, I hope).

Best wishes.
Davide

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[flup2]

Hello,

First of all, thanks for your work, Davide :-)

I installed the portfile and it works without problem.

For those who already installed Frescobaldi and want to update next versions
this way, macports detects that python-poppler-qt4 is already installed. We
need thus to force the installation by macports:

port -f activate py27-python-poppler-qt4

On my setup, the same occurred with frescobaldi itself.

Note: I doesn't break the former setup. I have now a macports installed
stable version, and the github synced "hand-made" installation. Both are
running well (for me, the github synced version is easier to work on the
French translation).

Philippe



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p150077.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Derek]

That is awesome and perfectly clear thank you!



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p150075.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Davide Liessi]

2013/9/1 Davide Liessi :
> git clone git clone https://github.com/dliessi/ports.git

Typo: replace with
git clone https://github.com/dliessi/ports.git

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Davide Liessi]

2013/8/20 Derek :
> Installing now

Dear Derek,
I noticed today, while I was reading this thread on Nabble, that the
message you sent to the list on 2013/08/20 was cut at the first line
(see http://lists.gnu.org/archive/html/lilypond-user/2013-08/msg00508.html
and 
http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-td139401i40.html#a149513).

This is the part that was cut away:

> Ok I am clueless at this I don't think I am performing:
>
> insert the line file:///path/to/repository (where /path/to/repository is the 
> full path to the repository) in /opt/local/etc/macports/sources.conf;
> (MacPorts finds Portfiles in the order specified in sources.conf, so you may 
> want to insert the line before other repositories.)
> in Terminal, cd to the repository and execute portindex.
>
>
> Just to be clear the files in step 2 are we inserting the path of where the 
> ports-master folder is currently into the sources.config file in the 
> /opt/local/etc/macports folder? I am not too clear on this step

I'll give an example.

==

Let's suppose that your username is derek, that your home directory
(~) is /Users/derek and that you want to keep my repository in a
subdirectory of ~/github (that you have already created).
Then open the Terminal and do

cd ~/github
git clone git clone https://github.com/dliessi/ports.git

Now you have a subdirectory called ports that contains my repository.
The next step is to open the sources.conf file in your favorite
editor, for example nano.
In the Terminal

sudo nano /opt/local/etc/macports/sources.conf

Go after the comment lines (those that begin with #) and before the
line(s) that begin with 'rsync://' and add the following line

file:///Users/derek/github/ports/

Then save the file and exit the editor (if you use nano: ctrl-O to
save, enter to confirm the file name, ctrl-X to exit).
Now again in the Terminal

cd ~/github/ports
portindex

Now your MacPorts installation should be able to see my Portfiles.
To test this, try in the Terminal

port info py-python-poppler-qt4
port info frescobaldi

==

I'll reword the instructions in the home page of my repository.
Let me know if you need help.

Best wishes.
Davide

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Stan Sanderson]

Davide-

As far as I know, I have a working Frescobaldi install (OS 10.8.4) after 
following Philippe's instructions, except that lyric hyphenation generates an 
error message. I am curious as to whether it works in your installation.

Thank you for the work you have done to make this valuable tool more readily 
accessible for Mac users. I'm planning to retry installing it on my 1st-gen 
intel iMac, which has had extensive Fink use, and has been exposed to HomeBrew 
and MacPorts. It is a very "dirty" machine.

I will report the results when I have a chance.

Stan

On Aug 20, 2013, at 2:17 AM, Davide Liessi  wrote:

> 2013/8/16 Davide Liessi :
>> Yesterday I submitted to MacPorts new Portfiles for frescobaldi and
>> python-poppler-qt4.
> [...]
>> I will announce on this list when the Portfiles will be approved and
>> available to all users.
> 
> Not yet approved by MacPorts project, but if you want to try them, you
> can find them at https://github.com/dliessi/ports.
> In that page you'll find instructions on how to use my Portfile
> repository and what changes with respect to the Frescobaldi Mac OS X
> install guide by Philippe Massart
> (https://github.com/wbsoft/frescobaldi/wiki/Frescobaldi-Mac-OS-X-install-guide).
> If you need any clarification, information or assistance, do not
> hesitate to ask.
> 
> I would be very grateful if MacPorts users could try my Portfiles and
> report problems (either by email or as GitHub issues).
> 
> To the ones who had pkgconfig issues (Robin Newman, Derek,
> chiffonMyst) : I would really appreciate if you could install and
> uninstall py-python-poppler-qt4 both with and without the
> PKG_CONFIG_PATH environment variable and let me know what happens.
> 
> Davide
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Derek]

Installing now



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p149513.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Davide Liessi]

2013/8/16 Davide Liessi :
> Yesterday I submitted to MacPorts new Portfiles for frescobaldi and
> python-poppler-qt4.
[...]
> I will announce on this list when the Portfiles will be approved and
> available to all users.

Not yet approved by MacPorts project, but if you want to try them, you
can find them at https://github.com/dliessi/ports.
In that page you'll find instructions on how to use my Portfile
repository and what changes with respect to the Frescobaldi Mac OS X
install guide by Philippe Massart
(https://github.com/wbsoft/frescobaldi/wiki/Frescobaldi-Mac-OS-X-install-guide).
If you need any clarification, information or assistance, do not
hesitate to ask.

I would be very grateful if MacPorts users could try my Portfiles and
report problems (either by email or as GitHub issues).

To the ones who had pkgconfig issues (Robin Newman, Derek,
chiffonMyst) : I would really appreciate if you could install and
uninstall py-python-poppler-qt4 both with and without the
PKG_CONFIG_PATH environment variable and let me know what happens.

Davide

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Davide Liessi]

2013/3/27 Derek :
> Package poppler-qt4 was not found in the pkg-config search path.
> Perhaps you should add the directory containing `poppler-qt4.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'poppler-qt4' found

2013/8/16 chiffonMyst :
> Package poppler-qt4 was not found in the pkg-config search path.
> Perhaps you should add the directory containing `poppler-qt4.pc'

In the email I sent on Friday I overlooked these lines.

Apparently you are having the same problem as Robin Newman's, i.e.
MacPorts' pkgconfig for some reason cannot see
/opt/local/lib/pkgconfig.
This should not happen, since MacPorts' pkgconfig is compiled with
'--with-pc-path=/opt/local/lib/pkgconfig:/opt/local/share/pkgconfig',
so it should always search these paths as a last resort.

I cannot reproduce this behaviour on either of the Macs I can use.
I suggest that you report the problem on the user mailing list of
MacPorts (see https://trac.macports.org/wiki/MailingLists) or file a
bug report at https://trac.macports.org/newticket (read the
guidelines).

As a workaround you can try to set the environment variable
PKG_CONFIG_PATH, then clean the build directory and build again: in
Terminal, cd to the build directory and write

export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/opt/local/lib/pkgconfig
/opt/local/bin/python2.7 setup.py clean
/opt/local/bin/python2.7 setup.py build

(In a working MacPorts installation of Python 2.7,
/opt/local/bin/python2.7 is a symlink to
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7
.)

This worked for Robin Newman; please, let me know if it works also for you.

Davide

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[rbn]

Thanks Robert
That sorted it!

Robin

On 17 Aug 2013, at 15:10, Robert Schmaus  wrote:

> Hi robin, 
> 
> I just had the exact same problems. Solved them by going into the preference 
> folder of my system and ditching all frescobaldi related prefs & plists. Some 
> could not be deleted though. 
> 
> After that, no problems anymore. Of course you need to set all preferences 
> new, but 
> 
> Best, Robert 
> 
> -
> Von meinem Fliewatüüt gesendet.
> 
> On 17 Aug 2013, at 15:15, Robin Newman  wrote:
> 
>> I too am trying to get Frescobadi working on my Mac. I have reached the stage
>> of of managing to compile and install the python-poppler-qt4 library, so I
>> now have lilypond compilation and dfp display working in Frescobaldi.
>> 
>> I have followed the installation instructions of Philippe Massart as regards
>> getting midi support going:
>> Installed via macports fluidsynth and portmidi
>> Installed and configured qsynth
>> 
>> When I start Frescobaldi I see the fluidsynth virtual port selected, but I
>> get errors from Frescobaldi. in three areas, although they are probably
>> related to the same cause.
>> 1) When selecting the Midi-Setting preference panel
>> 
>> Traceback (most recent call last):
>> File
>> "/Applications/frescobaldi-2.0.10/frescobaldi_app/preferences/__init__.py",
>> line 143, in slotCurrentItemChanged
>>   item.activate()
>> File
>> "/Applications/frescobaldi-2.0.10/frescobaldi_app/preferences/__init__.py",
>> line 163, in activate
>>   w.loadSettings()
>> File
>> "/Applications/frescobaldi-2.0.10/frescobaldi_app/preferences/__init__.py",
>> line 296, in loadSettings
>>   group.loadSettings()
>> File
>> "/Applications/frescobaldi-2.0.10/frescobaldi_app/preferences/midi.py", line
>> 113, in loadSettings
>>   self._playerPort.setEditText(s.value("player/output_port", port))
>> TypeError: QComboBox.setEditText(QString): argument 1 has unexpected type
>> 'QPyNullVariant'
>> ==
>> It doesn't switch to the panel, but if I click midi-settigs a second time it
>> does, showing the fluidsynth virtual port selected
>> 
>> If I then click refresh-midi ports I get the error
>> 
>> Traceback (most recent call last):
>> File
>> "/Applications/frescobaldi-2.0.10/frescobaldi_app/preferences/midi.py", line
>> 107, in refreshMidiPorts
>>   self.loadSettings()
>> File
>> "/Applications/frescobaldi-2.0.10/frescobaldi_app/preferences/midi.py", line
>> 113, in loadSettings
>>   self._playerPort.setEditText(s.value("player/output_port", port))
>> TypeError: QComboBox.setEditText(QString): argument 1 has unexpected type
>> 'QPyNullVariant'
>> ===
>> 
>> 2: when clicking the play button on the midi-player 
>> 
>> Traceback (most recent call last):
>> File
>> "/Applications/frescobaldi-2.0.10/frescobaldi_app/miditool/__init__.py",
>> line 64, in slotPlay
>>   self.widget().play()
>> File
>> "/Applications/frescobaldi-2.0.10/frescobaldi_app/miditool/widget.py", line
>> 155, in play
>>   self.openOutput()
>> File
>> "/Applications/frescobaldi-2.0.10/frescobaldi_app/miditool/widget.py", line
>> 124, in openOutput
>>   o = midihub.output_by_name(p)
>> File "/Applications/frescobaldi-2.0.10/frescobaldi_app/midihub.py", line
>> 97, in output_by_name
>>   if i.isoutput and i.name.startswith(name) and not i.isopen:
>> TypeError: startswith first arg must be str, unicode, or tuple, not
>> QPyNullVariant
>> 
>> Needless to say it doesn't play any midi. The midifile is show correctly
>> loaded in the midi player.
>> 
>> Any suggestions how I proceed?
>> 
>> Robin
>> 
>> 
>> 
>> 
>> 
>> --
>> View this message in context: 
>> http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p149344.html
>> Sent from the User mailing list archive at Nabble.com.
>> 
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Robert Schmaus]

Hi robin, 

I just had the exact same problems. Solved them by going into the preference 
folder of my system and ditching all frescobaldi related prefs & plists. Some 
could not be deleted though. 

After that, no problems anymore. Of course you need to set all preferences new, 
but 

Best, Robert 

-
Von meinem Fliewatüüt gesendet.

On 17 Aug 2013, at 15:15, Robin Newman  wrote:

> I too am trying to get Frescobadi working on my Mac. I have reached the stage
> of of managing to compile and install the python-poppler-qt4 library, so I
> now have lilypond compilation and dfp display working in Frescobaldi.
> 
> I have followed the installation instructions of Philippe Massart as regards
> getting midi support going:
> Installed via macports fluidsynth and portmidi
> Installed and configured qsynth
> 
> When I start Frescobaldi I see the fluidsynth virtual port selected, but I
> get errors from Frescobaldi. in three areas, although they are probably
> related to the same cause.
> 1) When selecting the Midi-Setting preference panel
> 
> Traceback (most recent call last):
>  File
> "/Applications/frescobaldi-2.0.10/frescobaldi_app/preferences/__init__.py",
> line 143, in slotCurrentItemChanged
>item.activate()
>  File
> "/Applications/frescobaldi-2.0.10/frescobaldi_app/preferences/__init__.py",
> line 163, in activate
>w.loadSettings()
>  File
> "/Applications/frescobaldi-2.0.10/frescobaldi_app/preferences/__init__.py",
> line 296, in loadSettings
>group.loadSettings()
>  File
> "/Applications/frescobaldi-2.0.10/frescobaldi_app/preferences/midi.py", line
> 113, in loadSettings
>self._playerPort.setEditText(s.value("player/output_port", port))
> TypeError: QComboBox.setEditText(QString): argument 1 has unexpected type
> 'QPyNullVariant'
> ==
> It doesn't switch to the panel, but if I click midi-settigs a second time it
> does, showing the fluidsynth virtual port selected
> 
> If I then click refresh-midi ports I get the error
> 
> Traceback (most recent call last):
>  File
> "/Applications/frescobaldi-2.0.10/frescobaldi_app/preferences/midi.py", line
> 107, in refreshMidiPorts
>self.loadSettings()
>  File
> "/Applications/frescobaldi-2.0.10/frescobaldi_app/preferences/midi.py", line
> 113, in loadSettings
>self._playerPort.setEditText(s.value("player/output_port", port))
> TypeError: QComboBox.setEditText(QString): argument 1 has unexpected type
> 'QPyNullVariant'
> ===
> 
> 2: when clicking the play button on the midi-player 
> 
> Traceback (most recent call last):
>  File
> "/Applications/frescobaldi-2.0.10/frescobaldi_app/miditool/__init__.py",
> line 64, in slotPlay
>self.widget().play()
>  File
> "/Applications/frescobaldi-2.0.10/frescobaldi_app/miditool/widget.py", line
> 155, in play
>self.openOutput()
>  File
> "/Applications/frescobaldi-2.0.10/frescobaldi_app/miditool/widget.py", line
> 124, in openOutput
>o = midihub.output_by_name(p)
>  File "/Applications/frescobaldi-2.0.10/frescobaldi_app/midihub.py", line
> 97, in output_by_name
>if i.isoutput and i.name.startswith(name) and not i.isopen:
> TypeError: startswith first arg must be str, unicode, or tuple, not
> QPyNullVariant
> 
> Needless to say it doesn't play any midi. The midifile is show correctly
> loaded in the midi player.
> 
> Any suggestions how I proceed?
> 
> Robin
> 
> 
> 
> 
> 
> --
> View this message in context: 
> http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p149344.html
> Sent from the User mailing list archive at Nabble.com.
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Robin Newman]

I too am trying to get Frescobadi working on my Mac. I have reached the stage
of of managing to compile and install the python-poppler-qt4 library, so I
now have lilypond compilation and dfp display working in Frescobaldi.

I have followed the installation instructions of Philippe Massart as regards
getting midi support going:
Installed via macports fluidsynth and portmidi
Installed and configured qsynth

When I start Frescobaldi I see the fluidsynth virtual port selected, but I
get errors from Frescobaldi. in three areas, although they are probably
related to the same cause.
1) When selecting the Midi-Setting preference panel

Traceback (most recent call last):
  File
"/Applications/frescobaldi-2.0.10/frescobaldi_app/preferences/__init__.py",
line 143, in slotCurrentItemChanged
item.activate()
  File
"/Applications/frescobaldi-2.0.10/frescobaldi_app/preferences/__init__.py",
line 163, in activate
w.loadSettings()
  File
"/Applications/frescobaldi-2.0.10/frescobaldi_app/preferences/__init__.py",
line 296, in loadSettings
group.loadSettings()
  File
"/Applications/frescobaldi-2.0.10/frescobaldi_app/preferences/midi.py", line
113, in loadSettings
self._playerPort.setEditText(s.value("player/output_port", port))
TypeError: QComboBox.setEditText(QString): argument 1 has unexpected type
'QPyNullVariant'
==
It doesn't switch to the panel, but if I click midi-settigs a second time it
does, showing the fluidsynth virtual port selected

If I then click refresh-midi ports I get the error

Traceback (most recent call last):
  File
"/Applications/frescobaldi-2.0.10/frescobaldi_app/preferences/midi.py", line
107, in refreshMidiPorts
self.loadSettings()
  File
"/Applications/frescobaldi-2.0.10/frescobaldi_app/preferences/midi.py", line
113, in loadSettings
self._playerPort.setEditText(s.value("player/output_port", port))
TypeError: QComboBox.setEditText(QString): argument 1 has unexpected type
'QPyNullVariant'
===

2: when clicking the play button on the midi-player 

Traceback (most recent call last):
  File
"/Applications/frescobaldi-2.0.10/frescobaldi_app/miditool/__init__.py",
line 64, in slotPlay
self.widget().play()
  File
"/Applications/frescobaldi-2.0.10/frescobaldi_app/miditool/widget.py", line
155, in play
self.openOutput()
  File
"/Applications/frescobaldi-2.0.10/frescobaldi_app/miditool/widget.py", line
124, in openOutput
o = midihub.output_by_name(p)
  File "/Applications/frescobaldi-2.0.10/frescobaldi_app/midihub.py", line
97, in output_by_name
if i.isoutput and i.name.startswith(name) and not i.isopen:
TypeError: startswith first arg must be str, unicode, or tuple, not
QPyNullVariant

Needless to say it doesn't play any midi. The midifile is show correctly
loaded in the midi player.

Any suggestions how I proceed?

Robin





--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p149344.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[flup2]

@chiffonMyst

Usually, that kind of dependencies need to be installed from the same
source: a "manually" installed SIP will be difficult to find by other
installations via macports or homebrew.

So, if your SIP installation via macports doesn't work, a manual
installation won't be a help for further steps: the problem lies before.

Could you send me the result of the following command:
port installed

Philippe



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p149333.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Stan Sanderson]

Update- Re: fresh install on OS 10.8.4 following the recipe linked to the 
Frescobaldi page on a "clean" machine. XQuartz previously installed but no 
previous MacPorts, Fink or HomeBrew installs. 

Frescobaldi is working well, but I was having problems with MIDI. I now believe 
it was due to the sound font I had set in qsynth (a very large font- 1.6GB). I 
extracted the sound font from Musescore, as Philippe suggests and with synth 
running the MIDI is now working.

The instructions could mention the importance of either setting path variables 
or providing full path links e.g., to the  lilypond binary.

Stan

On Aug 16, 2013, at 6:02 PM, chiffonMyst  wrote:

> Robert,
> 
> I have been trying to install frescobaldi for the past couple days and I ran
> into that problem as well. What I did to solve it was download the
> sip-4.14.7 tarball at
> http://www.riverbankcomputing.com/software/sip/download
> 
> I then proceeded to run configure.py, then run make, and make install (all
> within the expanded sip-4.14.7 directory, of course...). This solved the
> same problem you are having but eventually led to more problems when trying
> to build python-poppler-qt4.
> 
> 
> 
> 
> 
> --
> View this message in context: 
> http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p149328.html
> Sent from the User mailing list archive at Nabble.com.
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[chiffonMyst]

Robert,

I have been trying to install frescobaldi for the past couple days and I ran
into that problem as well. What I did to solve it was download the
sip-4.14.7 tarball at
http://www.riverbankcomputing.com/software/sip/download

I then proceeded to run configure.py, then run make, and make install (all
within the expanded sip-4.14.7 directory, of course...). This solved the
same problem you are having but eventually led to more problems when trying
to build python-poppler-qt4.





--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p149328.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[David Rogers]

Robert Schmaus  writes:

> That brings me to my question: I've worked through Phillippe's
> "recipe" faithfully (I think). Now, when I try to launch frescobaldi
> on the Terminal, I get an error message
>
> ImportError: No module named sip
>
> Does anyone know what's the problem there?

According to the person who packaged it for Arch Linux, sip is "A tool
that makes it easy to create Python bindings for C and C++ libraries".

On my system, the dependencies relating to sip go as follows:

frescobaldi needs python2-poppler-qt;

python2-poppler-qt needs python2-pyqt4;

python2-pyqt4 needs python2-sip;

python2-sip needs sip and python2.


... there are other dependencies for some of these things of course, but
I think those are the relevant ones in the situation. Hopefully the
situation is at least analogous for you...

-- 
David R

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Stan Sanderson]

Success report.

OK, I have installed Frescobaldi and apart from the midi, it appears to be 
working as advertised.

I started with a "fresh" MacBook Air running OS 10.8.4, i.e., no previous Fink, 
HomeBrew or MacPort installs. I followed the instructions on the Frescobaldi 
Mac OSX install guide page to the best of my ability in the order presented.

I did not previously have lilypond in my $PATH so I had to specify the complete 
path to the lilypond binary in the Frescocbaldi preferences. Everything I've 
tried so far has worked except for Midi. It did start working once, but so far 
it claims there is no output. I have reset the Qsynth preferences but no luck.

Anyway, all the steps worked when the recipe was followed. 

Stan


On Aug 16, 2013, at 3:08 PM, flup2  wrote:

> Hello (and thanks for the flowers ;-) )
> 
> 
> Robert Schmaus wrote
>> That brings me to my question: I've worked through Phillippe's "recipe" 
>> faithfully (I think). Now, when I try to launch frescobaldi on the 
>> Terminal, I get an error message
>> 
>> ImportError: No module named sip
>> 
>> Does anyone know what's the problem there?
>> 
>> Best,
>> Robert
> 
> Could you tell us exactly which command you use to run frescobaldi?
> I had the same problem using "python frescobaldi". I use instead the
> complete path of the macport-installed version:
> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7
> frescobaldi
> 
> 
> David Kastrup wrote
>> Actually, this works fine with Emacs and a number of PDF viewers as
>> well.
> 
> Regarding the use of others editors with point-and-click, it doesn't work
> out of the box with emacs or vi (and skim a previewer) on a mac (even if I
> tried to...): clicking on a pdf launches the lilypad editor. At this time
> frescobaldi and lilypondtool are the only working for me. Yet another thing
> to investigate on my schedule.
> 
> Philippe
> 
> 
> 
> --
> View this message in context: 
> http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p149317.html
> Sent from the User mailing list archive at Nabble.com.
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Robert Schmaus]

Am 8/16/13 10:08 PM, schrieb flup2:

That brings me to my question: I've worked through Phillippe's "recipe"
faithfully (I think). Now, when I try to launch frescobaldi on the
Terminal, I get an error message

ImportError: No module named sip

Does anyone know what's the problem there?


Could you tell us exactly which command you use to run frescobaldi?
I had the same problem using "python frescobaldi". I use instead the
complete path of the macport-installed version:
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7
frescobaldi


Ah - I should have remembered - you said so at another place in your guide.
Yes, using the full python2.7 path instead of just python indeed does 
the trick! Oh, I'm excited now !


Thank you once more!



Regarding the use of others editors with point-and-click, it doesn't work
out of the box with emacs or vi (and skim a previewer) on a mac (even if I
tried to...): clicking on a pdf launches the lilypad editor. At this time
frescobaldi and lilypondtool are the only working for me. Yet another thing
to investigate on my schedule.


I can add Eclipse with Elysium here - point & click works fine!
And I may add, I really worked fine with this for a couple of years, and 
I really like the way, Eclipse keeps individual projects together 
(something Elysium inherits from Eclipse being a native Java IDE). So 
except for some oddities with Elysium and the slowness, I actually like 
Elysium.


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[flup2]

Hello (and thanks for the flowers ;-) )


Robert Schmaus wrote
> That brings me to my question: I've worked through Phillippe's "recipe" 
> faithfully (I think). Now, when I try to launch frescobaldi on the 
> Terminal, I get an error message
> 
> ImportError: No module named sip
> 
> Does anyone know what's the problem there?
> 
> Best,
> Robert

Could you tell us exactly which command you use to run frescobaldi?
I had the same problem using "python frescobaldi". I use instead the
complete path of the macport-installed version:
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7
frescobaldi


David Kastrup wrote
> Actually, this works fine with Emacs and a number of PDF viewers as
> well.

Regarding the use of others editors with point-and-click, it doesn't work
out of the box with emacs or vi (and skim a previewer) on a mac (even if I
tried to...): clicking on a pdf launches the lilypad editor. At this time
frescobaldi and lilypondtool are the only working for me. Yet another thing
to investigate on my schedule.

Philippe



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p149317.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[David Kastrup]

Evan Driscoll  writes:

[...]

> As someone who is only a very hobbyist musician but *very* comfortable
> with the command line and Emacs and compilers and Latex and etc.,

[...]

> The LilyPondTool description on the "Easier Editing" page *does* mention
> point-and-click support, but doesn't actually say what point-and-click
> *is*. For people like me who are dense (and likely only somewhat
> skimming the page), I think you should even say explicitly something
> like "It's features include ... an embedded PDF viewer with advanced
> point-and-click support that allows you to click notes and other
> graphical items in the score and automatically move the cursor to the
> corresponding source location."

Actually, this works fine with Emacs and a number of PDF viewers as
well.

-- 
David Kastrup


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Robert Schmaus]

May I contribute to this thread some comments as well as a question?

Well then: I use a Mac at home, and I have been using LilyPond on the 
Mac without any problem (mac-specific ones, I mean) since v2.14. I don't 
know if I misunderstood David K.'s comment ("we have pretty few vocal 
Mac users here") but I think in most of the discussions it's rather 
unimportant which system one uses (except in cases where technical or 
installer-related problems are discussed - a clear minority). that could 
be interpreted as "lilypond runs just fine on macs" - and that would 
indeed match my experience.


another issue is frescobaldi. it runs on a Mac but is hard to install. 
over the last two year I tried several times to install it. the reason 
it didn't work was always something to do with the python installation 
or poppler or some file that was missing in the end. I'm a programmer 
myself, but I could not solve those problems for a simple reason: I knew 
that, to solve them, I would need to dig deep into the system. It'd take 
weeks to understand what's going on. That I'm a programmer doesn't imply 
that I want to do that, or indeed (as Tim pointed out) actually have the 
time to do this, and that's precisely the reason I use a non-free (or, 
to cite a rather nasty discussion from some months back, 
"freedom-denying") OS. I just don't want to bother with the system, I 
just would like a tool that works in general. I don't have to know the 
details of beer-brewing either to enjoy a bottle once in a while ...


don't misunderstand me: I'm not saying Frescobaldi is deficient in any 
way. It just doesn't target Macs, that's all. If I'd take the time to 
write such a program, I probably would not go to the trouble of writing 
a Windows installer as well.


Luckily, there are people like Philippe Massart who figure out how to 
get frescobaldi running on a Mac and don't keep it to themselves. Thank you!
With his help I'm now almost there to use frescobaldi, too, which I'm 
really looking forward to! (Up to now, I use Eclipse/Elysium which works 
fine but is rather slow.)


That brings me to my question: I've worked through Phillippe's "recipe" 
faithfully (I think). Now, when I try to launch frescobaldi on the 
Terminal, I get an error message


ImportError: No module named sip

Does anyone know what's the problem there?

Best,
Robert

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Re: frescobaldi on mac

[Evan Driscoll]

On 08/16/2013 05:00 AM, Christian Andersson wrote:
> I work most efficiently
> with quite large orchestral scores using Lilypond, vi(1), sed(1), Bourne
> shell and GNU make (and a PDF viewer). ... [I]n my
> experience it is quite hard to get MacOS users well accustomed to
> working in the terminal.

Don't forget: it's not just comfort with the terminal, it's also textual
editing of an almost entirely non-textual document (at least the way I
see it).

As someone who is only a very hobbyist musician but *very* comfortable
with the command line and Emacs and compilers and Latex and etc.,
finding out that Frescobaldi has its point-and-click thing and
highlighting of the item under the cursor is what got me to actually
start using Lilypond directly (as opposed to through Denemo).

Even for me, a typical text editor plus the command line and Lilypond
executable is too... intimidating in terms of how long I'm worried it
would take to go from "this note is wrong" to finding the corresponding
point in the source, considering how often that happens. It doesn't seem
to me like searching the document for a particular occurrence of a note
would be nearly as easy & fast as finding the place in a Latex document
that's wrong. With Frescobaldi, I just click on the wrong note and
that's that.

(Of course, Frescabaldi isn't the only thing that supports
point-and-click, probably not even on Macs.)


Actually, if you want to appeal to people like me who are more
interested in "I want to write this quickly" than "I want the output to
look really good", it may be worthwhile to see if there's anything you
can do to draw more attention to the point-and-click feature.

For example, the "Easier Editing" page on lilypond.org describes the
right-hand pane of Frescabaldi as "a built-in PDF viewer" with no
mention of the point-and-click feature. I passed over Frescabaldi in
favor of Denemo for a while in part because I didn't know about that.

The LilyPondTool description on the "Easier Editing" page *does* mention
point-and-click support, but doesn't actually say what point-and-click
*is*. For people like me who are dense (and likely only somewhat
skimming the page), I think you should even say explicitly something
like "It's features include ... an embedded PDF viewer with advanced
point-and-click support that allows you to click notes and other
graphical items in the score and automatically move the cursor to the
corresponding source location."

(I had good experiences with Denemo too, but switched to "raw" Lilypond
using Frescabaldi for... well, reasons.)

Evan




signature.asc
Description: OpenPGP digital signature
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Tim McNamara]

On Aug 16, 2013, at 3:40 AM, Davide Liessi  wrote:

> 2013/8/16 Christian Andersson :
>> This issue with running Frescobaldi on MacOS X must be one of the most
>> long-running among threads of this list. Why can't some of you Mac users
>> please take your responsibility for the community, and see to that a working
>> distribution gets created, from which everybody (with Macs) can benefit,
>> with all the tweaks and dependencies, and then donate this for download from
>> the official Frescobaldi-site. I'd love to be able to recommend a number of
>> friends of mine, sadly (for them) with Apple boxes, to take a look at
>> Frescobaldi, but given the state of affairs here this is simply not possible
>> at the moment. Of course it is easier to do this in, e.g., a Linux platform,
>> but I just can't imagine that it would be that impossible for Macs as is
>> suggested by all these howtos, neither of which seems to work for everybody.
> 
> Yesterday I submitted to MacPorts new Portfiles for frescobaldi and
> python-poppler-qt4.
> There's a couple of small changes that are needed, but I hope they
> will be approved soon.
> After they are in MacPorts' repository, frescobaldi should be easier to 
> install.
> It will essentially be a matter of two/three MacPorts commands (plus
> maybe install Qsynth as a fluidsynth GUI and a soundfont for MIDI
> support): no more manually compiling the software.
> (I know, Mac users are more used to single packages you can download
> and copy in /Application/ folder. MacPorts is not that simple, but I
> would still say it is easy to use.)
> 
> I will announce on this list when the Portfiles will be approved and
> available...

Very nice, David, and a huge thank you.  While MacPorts takes a few steps to 
use, it borders on trivial when the portfiles are correct.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Tim McNamara]

On Aug 16, 2013, at 3:22 AM, Christian Andersson 
 wrote:

> This issue with running Frescobaldi on MacOS X must be one of the most 
> long-running among threads of this list. Why can't some of you Mac users 
> please take your responsibility for the community, and see to that a working 
> distribution gets created, from which everybody (with Macs) can benefit, with 
> all the tweaks and dependencies, and then donate this for download from the 
> official Frescobaldi-site. I'd love to be able to recommend a number of 
> friends of mine, sadly (for them) with Apple boxes, to take a look at 
> Frescobaldi, but given the state of affairs here this is simply not possible 
> at the moment. Of course it is easier to do this in, e.g., a Linux platform, 
> but I just can't imagine that it would be that impossible for Macs as is 
> suggested by all these howtos, neither of which seems to work for everybody.

One problem is that most Mac users, like myself, don't have those skills.  For 
the most part it is not something we have to know when installing apps.  The 
Mac application design philosophy is much different than Linux when it comes to 
dependencies and the like.  We never have to install dependencies to install a 
Mac app, for example.  If there is something needed by the app that is not 
already part of the operating system, the developer includes it in the app 
package and the app is delivered precompiled.  Drop it somewhere on your hard 
drive, double click it, and it works.  That is what Mac users are used to.  We 
don't troubleshoot installs.  If an app doesn't work, word gets around and we 
use an alternative app.

And, like many people, I just don't have time to learn those things.  I have a 
full time-plus career that has nothing to do with computers, plus a marriage, 
plus aging parents in ill health, plus a band, plus other hobbies and 
interests, a house and yard to take care of, etc.  For better and for worse, 
like most Mac users I am reliant on developers.  My one computer class was in 
1978 and involved punch cards and Fortran IV; all I remember from that is that 
my comprehension of program design sucked and I barely passed the class.

The issue with Frescobaldi is simply that the developer is not a Mac developer, 
he is obviously a very talented and dedicated Linux developer.  And even though 
the Mac OS is based on Unix (mostly OpenBSD using the Mach kernel) and 
technically POSIX compliant, Apple has not made it particularly easy to just 
run Linux apps on the Mac.  Especially when that app is written in Python (the 
majority of Mac apps are written in Objective-C, which is more or less the 
"native" programming language for the Apple Mac SDK).

The sticking point for my attempts to install Frescobaldi is its dependence on 
Poppler to see the PDF output.  There is a bit of software necessary that also 
has to be installed, the Python-Poppler-Qt library; for me this seems to be 
broken by something.

The best hopes are for someone to make an .app package or to use the MacPorts 
repository to set up installation of all the necessary bits and bobs.  I don't 
have the know-how, but I would be happy to toss in some cash for someone who 
does have the skills to make either of those happen.  That's the best I can do.

In the meantime I continue to use Marc's LilyEditor which does what I need and 
is the best current Mac option for editing Lilypond files.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Stan Sanderson]

I've been trying to get up enough  courage to attempt it again on a new (Mac) 
machine running OS 10.8.4, using Mike's instructions. Previously I attempted to 
install on an OS 10.6 machine using homebrew, followed by MadPorts, but I 
believe my long-time use of fink and an incomplete removal of homebrew messed 
things up. 

 When it happens, I will report.

Stan

On Aug 16, 2013, at 7:57 AM, flup2  wrote:

> Mike Solomon wrote
>> I got it working (don't remember how) but I recall that a large chunk of
>> it had to do with using brew and not other package managers (fink,
>> macports for example).
> 
> Probably. That's why the installation instructions I posted here ( 
> https://github.com/wbsoft/frescobaldi/wiki/Frescobaldi-Mac-OS-X-install-guide
> <https://github.com/wbsoft/frescobaldi/wiki/Frescobaldi-Mac-OS-X-install-guide>
>   
> ) are using a macport installation (I was never able to install all the
> dependencies using homebrew).
> 
> Philippe
> 
> 
> 
> --
> View this message in context: 
> http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p149294.html
> Sent from the User mailing list archive at Nabble.com.
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[flup2]

Mike Solomon wrote
> I got it working (don't remember how) but I recall that a large chunk of
> it had to do with using brew and not other package managers (fink,
> macports for example).

Probably. That's why the installation instructions I posted here ( 
https://github.com/wbsoft/frescobaldi/wiki/Frescobaldi-Mac-OS-X-install-guide
<https://github.com/wbsoft/frescobaldi/wiki/Frescobaldi-Mac-OS-X-install-guide> 
 
) are using a macport installation (I was never able to install all the
dependencies using homebrew).

Philippe



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p149294.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Mike Solomon]

On 16 août 2013, at 11:04, chiffonMyst  wrote:

> Philippe,
> 
> I  tried using the complete path and thats what was giving me that error.
> 
> I did a sudo port select --set python python 27 and it said it switched to
> python27.
> 
> I tried running the complete path on the setup.py and still received the
> same error.
> 

I got it working (don't remember how) but I recall that a large chunk of it had 
to do with using brew and not other package managers (fink, macports for 
example).

Good luck!

Cheers,
MS
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Derek]

But you expect others to have the time and acquire the skill set.  And 
probably also buy themselves the same sort of computer that you want to 
use.  Why?

Once again where are you getting that from? I basically said the same thing
as Christian A. 
" I wish I could somehow find the time needed to contribute better."

but for some reason you took my comment as some sort of spoilt child asking
everyone to do everything for him type thing which it wasn't.

"So what steps did you take to make sure that others will have it easier 
and benefit from your experience?"

If anything I discovered wasn't in the particular thread I was reading I
posted it to help anyone else who might have the same issue. What else could
I do?

"Using LilyPond" is neutral (apart from incurring hosting/download 
costs).  Contributing back to a community involves more than just using 
the software.  Complaining about the software is a feedback, but without 
the investment of time and care required to make that complaint specific 
and addressable, it does not help the community or ultimately the 
software." 

Am I complaining about the software?? No I think it fantastic.

"Attitudes and PR will not make a difference regarding how hard it is to 
use LilyPond on a Mac.  LilyPond is supported by an active and 
incredibly helpful community (which happens to pay my bills as well in 
order to keep myself working on the project).  But there are limits to 
what it can do.  If no actual users of a platform can be bothered to get 
involved in deployment (which requires a lot of cooperation and detailed 
feedback), then there will be no support or the existing support will 
eventually break down."

Once again when was I complaining about the software or how hard it was to
use? I wasn't. I merely commented on the attitudes towards mac users their
seems to be around here. I never asked you to come to my house and fix
anything. I just said I wish I knew more so I could contribute and you
started patronising me. 

"And that is not something that can be resolved by complaining about it, 
and by complaining in general that it is the responsibility of some 
mystical higher class of humans known as "programmers" who are bound to 
work on the problems of all others because everyone knows that they 
don't have a life of their own. 

Even the "programmers" need something substantial to work with."

Once again did I complain about a technical issue? And if one were to
comment on a technical issue who but those with the programming abilities
can fix it? For some reason you have an issue with my comment even though
those same sentiments were posted by others. What gives?



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p149283.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[David Kastrup]

Derek  writes:

> Blah Blah and when I was a kid I had to walk five miles uphill in the
> snow to school both ways...

Except that I still do things like find problems with GCC code
generation.  And stuff like that tends to take days.  Longer than
digging through a set of half-working recipes and figuring out the
correct course would for someone actually having a Mac.

> Whatever it sounds like to you you are wrong. My point was that with
> my programming skills I wouldn't be of much use to anyone else ie I
> can't make an installer package and contribute as I don't have the
> time or the skill set.

But you expect others to have the time and acquire the skill set.  And
probably also buy themselves the same sort of computer that you want to
use.  Why?

> I finally got it running just reading this forum, nobody came and held
> my hand or did it for me so enough with patronising bollocks, it seems
> to be a pattern around here.

So what steps did you take to make sure that others will have it easier
and benefit from your experience?

> If I didn't like the program so much I would have bailed long ago.

How would we have noticed?

> Do you actually want people to use lilypond or do you want to send
> them on their way because they don't use linux or aren't as
> technically minded as others?

"Using LilyPond" is neutral (apart from incurring hosting/download
costs).  Contributing back to a community involves more than just using
the software.  Complaining about the software is a feedback, but without
the investment of time and care required to make that complaint specific
and addressable, it does not help the community or ultimately the
software.

> People bagging out mac users or spamming the Steinberger blog with
> Lilypond evangelism, the program is fantastic but the attitudes and pr
> around here need some work.

Attitudes and PR will not make a difference regarding how hard it is to
use LilyPond on a Mac.  LilyPond is supported by an active and
incredibly helpful community (which happens to pay my bills as well in
order to keep myself working on the project).  But there are limits to
what it can do.  If no actual users of a platform can be bothered to get
involved in deployment (which requires a lot of cooperation and detailed
feedback), then there will be no support or the existing support will
eventually break down.

And that is not something that can be resolved by complaining about it,
and by complaining in general that it is the responsibility of some
mystical higher class of humans known as "programmers" who are bound to
work on the problems of all others because everyone knows that they
don't have a life of their own.

Even the "programmers" need something substantial to work with.

-- 
David Kastrup


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Derek]

Blah Blah and when I was a kid I had to walk five miles uphill in the snow to
school both ways... 

Whatever it sounds like to you you are wrong. My point was that with my
programming skills  I wouldn't be of much use to anyone else ie I can't make
an installer package and contribute as I don't have the time or the skill
set. I finally got it running just reading this forum, nobody came and held
my hand or did it for me so enough with patronising bollocks, it seems to be
a pattern around here. If I didn't like the program so much I would have
bailed long ago. Do you actually want people to use lilypond or do you want
to send them on their way because they don't use linux or aren't as
technically minded as others? People bagging out mac users or spamming the
Steinberger blog with Lilypond evangelism, the program is fantastic but the
attitudes and pr around here need some work.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p149279.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Christian Andersson]

On Fri, Aug 16, 2013 at 10:45 AM, David Kastrup  wrote:

> Derek  writes:
>
> > Believe me if I were a programmer I would and I am sure many are in
> > the same boat.
>
> The boat of the passive-aggressive passenger?  There are a number of
> recipes around which are apparently working only sometimes and for some
> people.  Why?  That requires the will for experimentation and
> perseverence.  Sure, programmers might have that, but it's not exclusive
> to them.
>

Personally, since I don't pay s**t for IDEs, I work most efficiently with
quite large orchestral scores using Lilypond, vi(1), sed(1), Bourne shell
and GNU make (and a PDF viewer). Some day I intend to share my "scripts"
and configurations somehow, but as usual they need to stablize a bit. I
suppose Lilypond itself should be easier (than Frescobaldi) to keep working
in the MacOS environment, as long as there is at least one user who could
imagine paying with her time to test, but in my experience it is quite hard
to get MacOS users well accustomed to working in the terminal. That is why
I hope to be able to recommend Frescobaldi, which I think is quite a decent
IDE for this task, compared to most of the others.

Vielen Dank, David Kastrup, for all your hard work with an absolutely
excellent software! I wish I could somehow find the time needed to
contribute better.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Davide Liessi]

2013/8/16 Davide Liessi :
> Have you installed poppler with qt4 variant? (port install poppler +qt4)
>
> I would suggest also quartz variant. (port install poppler +qt4 +quartz)

OK, the '+quartz' suggestion is actually a very strong recommendation,
and if you are on Mac OS 10.6 or later it is necessary, since qt4-x11
is broken on those platforms (https://trac.macports.org/ticket/20309).

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[David Kastrup]

Derek  writes:

> Believe me if I were a programmer I would and I am sure many are in
> the same boat.

The boat of the passive-aggressive passenger?  There are a number of
recipes around which are apparently working only sometimes and for some
people.  Why?  That requires the will for experimentation and
perseverence.  Sure, programmers might have that, but it's not exclusive
to them.

The above sounds like "Believe me if I were a hero I would sign a
petition against overboarding surveillance" to me.  Things are not as
bad as that.  Yet.  If people are willing to do what they can.  Which
may be more or less, but that's not an excuse for those able to
contribute less to demand that the others bear the load alone.

In my youth, I had to solder my computer together, write my own BIOS
(not to be confused with the existing monitor ROM) and bootstrap loader,
write my own arcade games.  No, I wasn't born a programmer.  It was just
what was necessary to move ahead.  "If only someone else did things for
me" was not really an option.  Of course I was young and had plenty of
time.

But working out the bad kinks from existing recipes and streamlining
them into a workable process that, perhaps, someone else might cast into
a program or script eventually is not on the same level of difficulty.

Yes, it's very likely an exercise in frustration.  That's life.

-- 
David Kastrup


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Davide Liessi]

2013/8/16 Christian Andersson :
> This issue with running Frescobaldi on MacOS X must be one of the most
> long-running among threads of this list. Why can't some of you Mac users
> please take your responsibility for the community, and see to that a working
> distribution gets created, from which everybody (with Macs) can benefit,
> with all the tweaks and dependencies, and then donate this for download from
> the official Frescobaldi-site. I'd love to be able to recommend a number of
> friends of mine, sadly (for them) with Apple boxes, to take a look at
> Frescobaldi, but given the state of affairs here this is simply not possible
> at the moment. Of course it is easier to do this in, e.g., a Linux platform,
> but I just can't imagine that it would be that impossible for Macs as is
> suggested by all these howtos, neither of which seems to work for everybody.

Yesterday I submitted to MacPorts new Portfiles for frescobaldi and
python-poppler-qt4.
There's a couple of small changes that are needed, but I hope they
will be approved soon.
After they are in MacPorts' repository, frescobaldi should be easier to install.
It will essentially be a matter of two/three MacPorts commands (plus
maybe install Qsynth as a fluidsynth GUI and a soundfont for MIDI
support): no more manually compiling the software.
(I know, Mac users are more used to single packages you can download
and copy in /Application/ folder. MacPorts is not that simple, but I
would still say it is easy to use.)

I will announce on this list when the Portfiles will be approved and
available to all users.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Davide Liessi]

2013/3/27 Derek :
> In file included from
> build/temp.macosx-10.8-intel-2.7/sippopplerqt4cmodule.cpp:7:
> poppler-qt4.sip:22:10: fatal error: 'qt4/poppler-qt4.h' file not found
> #include 
>  ^
> 1 error generated.
> error: command 'clang' failed with exit status 1

2013/8/16 chiffonMyst :
> I'm having the exact same problem as Derek
>
> this part looks of interest... :
>
> Package poppler-qt4 was not found in the pkg-config search path.
> Perhaps you should add the directory containing `poppler-qt4.pc'

Have you installed poppler with qt4 variant? (port install poppler +qt4)

I would suggest also quartz variant. (port install poppler +qt4 +quartz)

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[David Kastrup]

Christian Andersson  writes:

> This issue with running Frescobaldi on MacOS X must be one of the most
> long-running among threads of this list. Why can't some of you Mac users
> please take your responsibility for the community,

Are Mac users allowed to have a community?  More seriously, you'll find
that we have pretty few vocal Mac users here.  Even the core
distribution of LilyPond was unusable for months at a time due to the
difficulty of finding people willing and/or able to work on Mac support.
If you check for Opsys-MacOs issues in our issue tracker, the history of
some of those issues just isn't pretty.

-- 
David Kastrup


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Derek]

Believe me if I were a programmer I would and I am sure many are in the same
boat.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p149270.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Christian Andersson]

This issue with running Frescobaldi on MacOS X must be one of the most
long-running among threads of this list. Why can't some of you Mac users
please take your responsibility for the community, and see to that a
working distribution gets created, from which everybody (with Macs) can
benefit, with all the tweaks and dependencies, and then donate this for
download from the official Frescobaldi-site. I'd love to be able to
recommend a number of friends of mine, sadly (for them) with Apple boxes,
to take a look at Frescobaldi, but given the state of affairs here this is
simply not possible at the moment. Of course it is easier to do this in,
e.g., a Linux platform, but I just can't imagine that it would be that
impossible for Macs as is suggested by all these howtos, neither of which
seems to work for everybody.

Kind regards /Christian
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[chiffonMyst]

Philippe,

I  tried using the complete path and thats what was giving me that error.

I did a sudo port select --set python python 27 and it said it switched to
python27.

I tried running the complete path on the setup.py and still received the
same error.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p149267.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[flup2]

Hello,

I think it's related to the python command: could you try to run it using
the complete path of the python command installed by macports? (something
like
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 )

I think Derek's problem was caused by using the python command shipped with
OS X.

To avoid that, there is a command to make sure that the python command using
the terminal is the one installed by macports: sudo port select --set python
python27

Hope this helps,

Philippe



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p149263.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[chiffonMyst]

I'm having the exact same problem as Derek

this part looks of interest... :

Package poppler-qt4 was not found in the pkg-config search path.
Perhaps you should add the directory containing `poppler-qt4.pc'

Not sure what to make of it but its been driving me crazy all night... can't
seem to get this thing working.





--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p149262.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Derek]

I don't now if this helps


localhost:python-poppler-qt4-0.16.2 shmk$ python setup.py install --user
Package poppler-qt4 was not found in the pkg-config search path.
Perhaps you should add the directory containing `poppler-qt4.pc'
to the PKG_CONFIG_PATH environment variable
No package 'poppler-qt4' found
running install
running build
running build_ext
building 'popplerqt4' extension
clang -fno-strict-aliasing -fno-common -dynamic -g -Os -pipe -fno-common
-fno-strict-aliasing -fwrapv -mno-fused-madd -DENABLE_DTRACE -DMACOSX
-DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32 -DNDEBUG -g -Os -Wall
-Wstrict-prototypes -DENABLE_DTRACE -arch i386 -arch x86_64 -pipe
-I/opt/local/include -I/opt/local/include/QtCore -I/opt/local/include/QtGui
-I/opt/local/include/QtXml
-I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7
-I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7
-c build/temp.macosx-10.8-intel-2.7/sippopplerqt4cmodule.cpp -o
build/temp.macosx-10.8-intel-2.7/build/temp.macosx-10.8-intel-2.7/sippopplerqt4cmodule.o
clang: warning: argument unused during compilation: '-mno-fused-madd'
In file included from
build/temp.macosx-10.8-intel-2.7/sippopplerqt4cmodule.cpp:7:
poppler-qt4.sip:22:10: fatal error: 'qt4/poppler-qt4.h' file not found
#include 
 ^
1 error generated.
error: command 'clang' failed with exit status 1
localhost:python-poppler-qt4-0.16.2 shmk$ 




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p143514.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[flup2]

Perhaps the reason is elsewhere, but your kind of error is what occurs when
the python command use the built-in version of python, not the one installed
by macports (or homebrew).

If you installed python via macports, you could use this (always from
python-poppler-st4 folder):

/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7
setup.py build
sudo
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7
setup.py install

If it doesn't work, could you copy the text from the terminal ?



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p143414.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Derek]

Thanks for that. Yes it shows up in the module window. I have tried to
install using the commands you have posted but I always get a fatal error,
sorry not in from of my computer but it is something to do with #include
 not being at the correct path. It happens with the first
command you listed. Thanks for that help, it is appreciated.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p143413.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[flup2]

Hello,

Did you install all the dependencies? If that message shows in the "Preview"
window of frescobaldi, it seems that the "python-poppler-qt4" module is not
installed.

Unlike other dependencies, it's not available via macports or homebrew. You
have to download it here and fellow the instructions to install it: 
https://code.google.com/p/python-poppler-qt4/
<https://code.google.com/p/python-poppler-qt4/>   (choose the 0.16.3
version)

Once unpacked on your computer, you'll have to use the Terminal to go to the
python-poppler-qt4 folder and type those 2 commands:
python setup.py build
sudo python setup.py install

Philippe



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p143396.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: frescobaldi on mac

[Derek]

I am trying to get frescobaldi to run. I have it installed and it loads
except I get the "could not load poplarqt4 module" Anyone know of a fix for
this?

Thank you




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p143394.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Mac MIDI synthesizer (was frescobaldi on mac)

[Paul Morris]

On Jan 15, 2013, at 4:47 AM, flup2  wrote:

> Each time Qsynth is launched, it uses a different port, obvisously; if you
> had to restart it, you need to click "Refresh MIDI ports" and choose another
> Fluidsynth occurrence (the port number is shown between parenthesis).

Thank you.  That's got it working for me again.

(I had tried clicking "refresh MIDI ports" before, but did not click the 
pull-down menu to realize that another option had been added to it that needed 
to be chosen.  If it was not a pull down menu, but an always-visible list of 
options, then I wouldn't have missed it.  I think I assumed that the refresh 
button would remove the old no-longer-working instance and go ahead and replace 
it with a new one, but that was not the case.)

-Paul
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Mac MIDI synthesizer (was frescobaldi on mac)

[flup2]

Each time Qsynth is launched, it uses a different port, obvisously; if you
had to restart it, you need to click "Refresh MIDI ports" and choose another
Fluidsynth occurrence (the port number is shown between parenthesis).



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/frescobaldi-on-mac-tp139401p139580.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user