Image 01


wilbert berendsen , Netherlands
Audio Apps
KDE 3.x Splash Screens

Audio Apps 75 comments

Score 65.6%
Mar 08 2015
Just to let you know, there is a new Frescobaldi 2.0 beta-release available.

It's Frescobaldi 1.9.4, see

Frescobaldi 2 is a rewrite from scratch and does not depend on KDE anymore, so strictly I should move this entry to

It is built with Python and PyQt4 and it can run on Windows, Linux and Mac OS X.
Frescobaldi 1.2.x remains of course working on KDE but is developed in bugfix-mode only.

- Dec 06 2011
Changes in 1.1.2 -- July 8th, 2010

* New features:
- Segno bar line added (available in LilyPond 2.13.19 and higher)
- It is now possible to configure the path that is used to find
files that are included via the LilyPond \include command.
- New 'Close other' action to close all documents except the current
- Print and View icons in the toolbar to print music and open PDF and MIDI
files in their external helper applications
* Printing:
- Printing generated PDF files now uses a print dialog, instead of just
sending the PDF to the 'lpr' command.
* Run LilyPond:
- warn if the document contains a conflicting point and click setting
* General:
- print and email actions have moved to the File menu
- close button on document tabs (can be turned off in Settings->Editor Comp.)
- warnings and notifications have a "dont ask again" checkbox, and can be
turned back on in the settings
- progress indicator saves the build time in document metainfo
* Autocompletion:
- only popup completions from the expansion manager on blank lines
* Settings dialog:
- the settings have been organized in more logical groups
* Installation:
- building the icons from SVN or out-of-source requires LilyPond >= 2.13.19
* Translations:
- Dutch updated by Wilbert Berendsen
- French updated by Valentin Villenave
- Italian updated by Gianluca D'Orazio - Jul 07 2010
Hm, looking to the frescobaldi-data problem: It seems that frescobaldi-data-0.7.13 is conflicting with frescobaldi-1.0.1.

So yes, you must remove frescobaldi-data and then install frescobaldi-1.0.2 as soon as the package is available. - Feb 19 2010
First: the problems you're experiencing are due to a little bug in the interaction between Python-KDE 4.4 and SIP 4.10. Frescobaldi 1.0.2 contains a work-around for those problems and works well under KDE 4.4.

If your distribution splits Frescobaldi's application code from its data, it will automagically pull in frescobaldi-data for you.

Rumor is an external program that translates live MIDI input to LilyPond output. See for information about where to get Rumor. - Feb 19 2010
Please try to find out which Python PyKDE4 (and PyQt4) are installed for. (Maybe something got upgraded on your system? The CMake files didn't change for 1.0.1)

You can go to a terminal and type:

>>> import PyKDE4.kdecore

If this succeeds, you need to add -DPYTHON_EXECUTABLE=/usr/bin/python2.5 to the CMake command line.

If this fails (with ImportError, no module named PyKDE4.kdecore), try another Python, e.g. /usr/bin/python2.6

You can also try to look where PyKDE4 is installed using locate:

locate PyKDE4/

yields on my system:


So I must use /usr/bin/python2.6 (which is found automatically).

But yes, I could try to make the install procedure smarter, in that it tries to import the PyKDE4 modules and if some fail, just try the next Python...

- Jan 18 2010
Hi, read INSTALL about how to direct CMake to the correct Python :-)

use a command like:
cmake . -DPYTHON_EXECUTABLE=/usr/bin/python2.5

to use the correct Python interpreter version. - Dec 27 2009
I'm not sure if I understand the problem correctly. LilyPond requires its input to be in UTF-8 encoding. Frescobaldi always defaults to UTF-8. But if you check the option "Remember Cursor Position, Bookmarks etc." in Settings->Configure Frescobaldi, Frescobaldi will also remember the encoding files were saved with, and open them in the correct encoding again.

You can also enforce Frescobaldi to use another encoding in a document by writing a line like:

% kate: encoding UTF-8;

somewhere at the top or bottom of the file. This line is read by KatePart, the editor component of KDE that Frescobaldi uses. - Dec 10 2009
Thanks. There is something wrong in your installation, with versions of PyKDE, PyQt and maybe Python maybe not matching. It seems from your information that PyKDE4 is installed for Python 2.5 only.

Please make sure that sip and PyQt4 are also compiled for the same Python 2.5 and that Frescobaldi also uses the same Python.

Probably some parts of your installation need an update. Good luck!

W. - Dec 02 2009
Very strange, there must be something wrong in you KDE4, PyQt4 or PyKDE4 setup.

If even 'frescobaldi -- version' segfaults, it crashes somewhere in the KDE code, because that option is handled by KDE.

Are you sure that Frescobaldi is using the same Python version PyKDE4 and PyQt4 was compiled for?

What happens if you manually start the Python interpreter with /usr/bin/python2.x (the first line of the frescobaldi script installed in /usr/bin or /usr/local/bin) and then type on the python prompt (which looks like >>>):

import PyKDE4.kdecore
import PyKDE4.kdeui

(It's difficult for me to debug this situation as there is no crash log)

Thanks for your time!

- Dec 02 2009
Can you run Frescobaldi from a terminal window and post the console output here?

e.g. open a terminal and type:


of course, must exist.

Also: please post the output of:

frescobaldi --version

And by the way: does it crash as soon as a file is opened, or direcly when started with no file (i.e. via the menu) or only when started by clicking a .ly file in the file manager?

thanks! - Dec 01 2009
Which version of Frescobaldi are you using? And what are the versions of KDE, PyQt4 (python-qt4), PyKDE4 (python-kde4) and SIP (python-sip4)?

Also: can you provide me with the crash log from the dialog after the segfault?

thanks, - Dec 01 2009
Frescobaldi can easily be had from svn:

A new release is due out in about two weeks, but the gui texts etc. are just finished. So you could start updating the po file from svn!
- Oct 28 2009
You can join the frescobaldi mailing list.
(first link on
There are also many feeds, see - Oct 28 2009
Your best bet is to save your music from Finale in the MusicXML format. LilyPond 2.12 has very good MusicXML import. Frescobaldi has not yet a specialized import GUI but you can use the musicxml2ly tool distributed with LilyPond to convert the MusicXML file to the LilyPond input format. Then of course you can use Frescobaldi to edit the file! - Aug 17 2009
I haven't searched a lot, but how can I fetch the svn tree and commit it when the fr.po file is updated ?
svn checkout

To commit just send me the output of svn diff po/fr.po or mail the file.

Was the use of lokalize a good idea ?
Yes, I use it as well for the Dutch translations.
- Jun 22 2009

Added to Frescobaldi SVN. I noticed that some translated texts were still marked fuzzy, while the translation were perfect (afaics). In that cases I removed the 'fuzzy' tag. - Jun 22 2009
The MIDI and PDF can be opened in external applications (if they are up-to-date) via the menu: LilyPond->Generated files. There is also a command in the file menu to open the document directory, for access to all (possibly) related files. But a quick button for MIDI would indeed be nicer!

Yes, the quick insert bar is slated to grow :-) tied notes are a good example, but I've not yet got my head around the exact user interface to use :)

Regarding the French translation: Valentin Villenave made the first French translation, but you're welcome to update it. (See the file fr.po in the po/ directory.) - Jun 10 2009
There seems to be something wrong with your LilyPond installation (i.e. LilyPond and Guile not matching). Try updating both LilyPond and (Lib)Guile! - May 31 2009
in SVN r 1302.

The icons take the default foreground text color. - May 19 2009
Yes, to connect notes in the PDF to positions in the MIDI requires changes to LilyPond, but an embedded MIDI-player with a memory for positions would already be very nice. (I.e. it remembers the starting position time of small fragments and is able to restart there, even if the file has been updated and has to be re-read.

I'll fix the button colors! - May 19 2009
First let me say: Thank you for this great little app! It "just works"!

I have some suggestions to improve it though:

- Symbols with transparent background (like articulation symbols which can be quick inserted) are unusable with dark desktop themes, as you can't see them!
I'm aware, yes! They should get the current text color, but I don't know how to do that ... :-)

- If multiple documents are opened, a tab below this quick insert tab with the opened documents would be nice, though not terribly necessary

- A tab with quick insert a note would be nice (for usual notes this is not necessary, of course, but think about double-cross notes etc). For experienced lilypond coders this won't be necessary of course, but they could simply leave this tab closed. Probably also other things to quick insert, I don't know.
Yes the quick insert toolbox could use more tabs, am also thinking on some markup helpers, etc.

- I experienced some crashes, don't know why.
Yes: same here, they started somewhere in between KDE 4.2.1 and 4.2.2. There is a bug somewhere in KDE, Qt or PyKDE which causes Frescobaldi to crash when calling perfectly legal functions. Sometimes a crash occurs when Frescobaldi gets a "smart" cursor position from KatePart (the embedded editor) but most times not.

I'm trying to circumvent that, but did not yet succeed.... You could use Frescobaldi 0.7.7 or 0.7.6 that does not have "smart" point and click support.

- It's annoying to always have to save the document before lilypond can be run. Can't it be saved automatically to a temporary file? Probably also keep it inside some $HOME/.frescobaldi directory, so it can be used to recover after a crash?
You can check a box in the settings to have Frescobaldi autosave the document when you call LilyPond.

- Autosaving feature, see above
Yes, would be nice.

- Probably unwanted feature: automatically run lilypond, if user stopped typing for some seconds or so?
I'm thinking on things like this. Even an automatic preview mode that just typesets the voice currently being edited, with a few measures before and after (using LilyPond skip typesetting feature).

- When clicking "play midi", it asks for a midi player instead of simply using "timidity ..." command from settings dialog
Yes, but the timidity command from the settings dialog is the command to start a MIDI player as an ALSA client, for use with the Rumor plugin. You can confingure the playback MIDI player using KDE's File Associations dialog.

- Would it be possible to select a note inside pdf document, and start midi playback from that place? I know, this might be a difficult task, but probably some midi player allows seeking?
That is theoretically possible. But Frescobaldi then should be able to "unserstand" where a certain position in the source file is in the time, and that would require Frescobaldi to have a perfect LilyPond parser, i.e. almost become LilyPond itself ;-)

- For midi playback: Embedding Dragon Player would be cool (if it's able to play midi files, not sure about that), and a step to cross platform compatibility.
Embedding a MIDI player is planned.

- Stop button for midi playback (for longer music files...)
See above ;-)

- I tried to complete German translation, but the English messages seem to be a little bit of a mess: with or without trailing ".", ...
Are the current messages somehow in a "final" state? Probably they need some clean-up...
Actually they are quite final. Menu commands etc don't end with a period, but tooltips do. Menu commands that open a dialog end with ... That's the standard I use. So you can quite safely assume that strings will not change often. Completion of the German translation is very welcome!

- Templates: Could you provide template file support? Probably even deliver good templates with frescobaldi? I think this would help beginners a lot!
Planned! The Score Wizard can help already, and the Expansion Manager has some nice constructs prefilled. But a real template manager would be nice, or a possibility to have presets in the score wizard.

That's all for the moment. Don't be shocked by the number of requests, I think frescobaldi is a great app already! :-)
Many thanks for your very useful feedback! It quite enlarged my TODO list :-D
- May 17 2009
replying to your latest comment: thanks :-) and yes: currently Frescobaldi can only simply call the default MIDI player on the file generated by LilyPond. Input via MIDI is possible using Rumor. Rumor is a command line tool to convert MIDI input in LilyPond notes. Frescobaldi's Rumor plugin is actually quite advanced and uses all features that Rumor provides, many of them automagically (e.g. key/time signature, pitch name language, etc.).

But more advanced MIDI support (input AND playing/output) is a future goal for Frescobaldi.

playing: an embedded MIDI player that can optionally autostart or start where the cursor is etc. etc.

input: a replacement for the current Rumor support, enabling entering multiple voices at the same time etc.

But I want the MIDI support to be cross-platform, so I'm currently looking at good Python MIDI libraries that work in GNU/Linux, Mac OS X and Windoze.

Thanks again for your comments and if you have any suggestions, let me know! - Mar 07 2009
you can already do this: add a \midi {} line in your score section (see the LIlypond docs on how to do that or read the Frescobaldi user guide on creating MIDI output)

then you should get a MIDI file. After LilyPond run, you see an icon to play the MIDI file. Use any MIDI player and configure that as the default application for MIDI files. - Mar 06 2009
There are now (K)Ubuntu packages at - Mar 06 2009
I finally got around creating a Gentoo ebuild:

Put it in your overlay in the media-sound category and name it frescobaldi-0.7.7.ebuild

then ebuild frescobaldi-0.7.7.ebuild digest and then emerge frescobaldi.
- Mar 06 2009
I created a clean Gentoo chroot environment and installed KDE, and I've updated the Frescobaldi ebuild and it installs Frescobaldi fine. So please try it :-)

The ebuild is at:

- Mar 06 2009
I created an ebuild without testing it yet. Please try it. Put it in your overlay (read the Gentoo docs how to do that) in the media-sound category.

The ebuild is here: - Mar 05 2009
Regarding GNOME: Frescobaldi should run under GNOME, it just needs kdelibs, kdebase and kdegraphics (for Okular, the PDF widget) installed and PyKDE4 (the Python bindings for KDE4, because it is written in Python). - Mar 04 2009
meinproc4 builds the help file cache.

Try to determine which package is needed by apt-file search meinproc4 and install that package OR just use the ubuntu package by Chris Snyder at

Chris Snyder created (K)Ubuntu packages for both Intrepid (8.10) and Jaunty (9.04). - Mar 04 2009
I used to use Gentoo but unfortunately I have no Gentoo machine currently, so I can't test an ebuild. You could create a crude ebuild that just performs the commands in the INSTALL file, but then dependencies are not correctly resolved.... - Mar 04 2009
Frescobaldi will be in KUbuntu Jaunty (9.04) - Feb 01 2009
Fixed in SVN. Now Frescobaldi should save user's settings. Thanks again for reporting. - Jan 17 2009
Thank you for your compliments.

The saving of the settings you describe are indeed not implemented yet. Some are settings that are not global to Frescobaldi, but unique for every opened document.

I have not yet figured out how to save those settings.

But also it seems some settings in the editor component config pages are not saved. That would be a bug on Frescobaldi's part. Thanks again for your report! - Jan 17 2009
Unfortunately, after many years I just switched my home system from Gentoo to Kubuntu. But I'll try to create one! - Jan 14 2009
So, next release (0.7.3 or 0.8.0 don't know yet) will be easier to install (no need to build the Lily icons, those will be prebuilt in the release tarballs). - Jan 07 2009
but LilyPond 2.10.33 should work. It probably has something todo with the 64bit compiled version you use. And that could have been fixed in the recent stable 2.12 releases. - Jan 07 2009
Your best bet would probably be upgrade LilyPond to 2.12.0

But I should really release a package with the LilyPond-generated icons prebuilt! I will try in the short future. - Jan 07 2009
Please update SIP (python-sip4) to the most recent version (I believe 4.7.7). And also PyQt4 and PyKDE4 should be recent versions. - Jan 07 2009
If there would be an utility that exports LilyPond to MusixTex, Frescobaldi could provide an easy to use GUI for it.

But you can already use LilyPond from within LaTeX, using lilypond-book. See the lilypond documentation. - Dec 29 2008

Music Production 54 comments

by plcl
Score 58.0%
Aug 15 2010
Hi, thanks for kmid(2) which is very nice and easy to use. I'm the author of Frescobaldi, a LilyPond text editor. Frescobaldi needs a feature to playback the MIDI files generated by LilyPond. Currently it just launches whichever MIDI player the user configures in the settings. But it would be nice if KMid2 could be embedded somehow (in a small player widget) inside another KDE application. Is this already possible? - Jun 07 2010

Audio Apps 51 comments

Score 50.0%
Nov 21 2008
Thanks for your comment!

Regarding KDE4: Yes, sure!

As soon as Pate (the Kate Python plugin framework by Paul Giannaros) becomes available for KDE4, LilyKDE will be ported to KDE4. But if not, it could also be possible to turn LilyKDE into a standalone application for KDE4 (using the Katepart text editing component). - Oct 23 2008
Hmm. I call KApplication.kApplication().dcopClient() instead of KApplication.dcopClient(). It works on my system. If you want to try, change line 54 of $HOME/.kde/share/apps/lilykde/lilykde/ from:

c = KApplication.kApplication().dcopClient()


c = KApplication.dcopClient()

this should work, next release (0.6.6) will contain this fix.

Thank you for your report! - Oct 08 2008
... with some changes that should hopefully fix LilyKDE's behaviour when there are non-ascii characters in filenames. - Oct 08 2008
it seems this works: line 30:

url = sys.argv[1].decode(sys.getfilesystemencoding()).encode('latin1')

Please let me know if it works in your system as well. - Oct 07 2008
Could you please try opening /home/jakob/.kde/share/apps/lilykde/ and changing line 30 into:

url = sys.argv[1]

so just remove the call to unicode() ?

Next release will contain this fix, if it works. - Oct 07 2008
What exactly is the full pathname of the file you are editing? - Oct 07 2008
thanks for your feedback. I will try to investigate. - Oct 07 2008
Thank you! So I guessed right, that referencing KDEDIRS while it is not set on your system was the problem. I fixed it already. You can get the svn version or just wait for 0.6.0 which will be released shortly. - Jun 09 2008
Well, I guess you have no KDEDIRS in your environment (the hyphen module just expected it to be set, so it bailed out when it is not set).

I made more robust in commit 484, so that it just uses some default search paths if KDEDIRS is not set.

0.6 will contain this improvement, that will hopefully fix hyphenation on your system! - Jun 09 2008
Thanks for your report. It seems there occurs an error on your system while building the config dialog.

Could you please run kate from the commandline (e.g. Konsole), and post the exact output here, after you open the config page?

The error message will point me in the right direction for a fix (I hope :-)

Thanks in advance! - Jun 08 2008

Music Production
by plcl

Score 58.0%
Aug 22 2010