OpenLP is possible because of the commitment of individuals. If you would like to help there are several things that you can get involved with. Please see: Contributing for more information.
A variety of places!
OpenLP 2.0 is designed to be cross platform. Currently it has been known to run on Windows (XP, Vista, 7), Linux (Ubuntu/Kubuntu, Fedora), FreeBSD & Mac OSX. Please let us know if you’ve successfully run it on something else.
OpenLP 2.0 is written in Python and uses the Qt4 toolkit. Both are cross-platform which allows the software to run on different types of machine and so allow more people access to free worship software. Python is one of the easier programming languages to learn, so this helps us develop and find bugs quicker, and also allows more developers to contribute with the project.
OpenLP has support for multiple languages which can be seen on the Settings ‣Translate menu. However some of these translations are incomplete. If you would like to help complete or start to translate OpenLP into your language then see the Getting started page.
A beta release is a release which is almost feature complete and is fairly stable. However there may still be a few features to complete, and bugs we’ve not yet fixed. It is used by several people without serious problems. However there is a small possibility that it could still crash occasionally or do unexpected things. It is intended for those who want the latest version, and are prepared to give the program a good test before using it in a live situation to ensure they won’t encounter any unexpected problems. If you want to have a look at the latest beta release then just download it.
It is perfectly safe to install 2.0 on a system with 1.2. Both versions are installed in separate places, so you can still go back to 1.2. You can even run them at the same time!
2.0 stores its data in a separate folder to 1.2, so your data is perfectly safe, and whatever you do in 2.0 will not damage 1.2
No. However imports exist to transfer your data to the new version.
2.0 does require significantly more resources than v1.2. Therefore if your computer does not have much memory you may find 2.0 will struggle, especially when changing between slides.
This is an beta release, which means it is not finished and one of the things we haven’t completely finished yet is importing 1.2 data automatically. We plan to do this Version 1.9.6 (beta 2).
In OpenLP 2.0, go to the File ‣ Import ‣ Song menu. In the Wizard that appears, click Next and choose “openlp.org v1.x” from the Format list. Click the search button on the Filename prompt, and at the bottom of the dialog, copy the following into the File name prompt:
(This must be in the popup file chooser dialog. Don’t enter it directly into the wizard).
Click Open, then in the wizard just click Next and wait for the import to complete.
In OpenLP 2.0, go to the File ‣ Import ‣ Bible menu. In the Wizard that appears, click Next and choose “openlp.org v1.x” from the Format list. Click the search button on the Filename prompt, and at the bottom of the dialog, copy the following into the File name prompt:
(This must be in the popup file chooser dialog. Don’t enter it directly into the wizard).
Choose the Bible, Click Open, then in the wizard just click Next, enter the License details, and wait for the import to complete.
In openlp.org v1, export each theme by selecting it in the Theme Manager, and then clicking the picture of a blue folder with red arrow on the Theme Managers toolbox. This theme file can then be imported into V2 using the File ‣ Import ‣ Theme menu.
OpenLP 2.0 is a complete rewrite using a completely different programming language so it would work on different types of system. There are differences in how the old and new languages draw text on the screen, and therefore it is unlikely you’ll get an exact match.
When you installed OpenLP, the first time wizard would have asked which plugins you wanted, and songs and bibles should have been selected. If for some reason they were not, then you will need to activate them yourself. See How do I activate / deactivate a plugin for instructions.
Plugins can be turned on and off from the Plugin List Screen. Select the plugin you wish to start/stop and change it’s status. You should not need to restart OpenLP.
The plugins allow OpenLP to be extend easily. A number have been written (Songs, Bibles, Presentations) etc but it is possible for the application to be extended with functionality only you require. If this is the case then go for it but lets us know as we can help and it may be something someone else wants.
First of all ensure that the presentation plugin is enabled (see above). Then to enable a presentation application, go to the Settings dialog, switch to the Presentations tab and check one of the enabled checkboxes. OpenLP will automatically detect which of the three you have installed, and enable the appropriate checkbox(es). Check the applications you require, and then restart OpenLP for the change to be detected. Note, PowerPoint Viewer 2010 is not yet supported, use 2003 or 2007.
Currently the presentations plugin is not bundled with OpenLP on OS X. The reason for that is that the OpenOffice.org version on Mac OS X does not contain the (more exact: does only contain a broken) interoperability component (the so called pyuno bridge) which could be used by OpenLP. As soon as the interoperability component works on OS X we can re-enable the plugin and bundle it. We are really sorry for that.
The Bible plugin has a much improved Import Wizard which can import Bibles from a variety of sources. The following sources are supported:
An XML format for Bible. You can export Bibles from the Sword Project into OSIS using the mod2osis tool. After using the Sword software Media Manager (or other Sword frontend, like BibleTime or Xiphos) to download the required Bible, run the following command from the command line (works on Windows and Linux):
mod2osis <name> > <name>.osis
The <name> parameter is the name of your Bible, as you see it in Sword. Note that the <name> is case sensitive on all environments. Once you have exported your Bible to OSIS, the Bible import wizard will the read <name>.osis file and import your Bible.
OpenLP can download Bibles on demand from the following 3 sites:
In order to better conform to copyright law, the Web Download Bibles are not downloaded when you import them, but on the fly as you search for them. As a result, the search takes a little longer if you need to download those particular verses. Having said that, the Web Download Bibles cache downloaded verses so that you don’t need to download them again.
When you create and save a service, all the items in the service are saved with it. That means any images, presentations, songs and media items are saved. This is also true for bibles. What this means is you can create the service on your home computer, insert a Bible passage from the web, save it and then open the service using your church computer and voila, the Bible passage should be there! Note this can also be done with songs, etc!
If your distribution supports the XDG standard, you’ll find OpenLP’s configuration file in:
If that file and/or directory does not exist, look for:
<user> is your username.
You’ll find your configuration file here:
<user> is your username.
On Windows, OpenLP does not use a configuration file, it uses the Windows registry. You can find the settings here:
If you have found an error in the program (what we call a bug) you should report this to us so that OpenLP can be improved. Before reporting any bugs please first make sure that there isn’t already a bug report about your problem:
If there is already a bug report, you may be able to help by providing further information. However, if no one else has reported it yet, then please post a new bug report.
Since OpenLP 1.9.4, there is a bug report dialog which automatically opens when OpenLP hits a serious bug. However, this doesn’t appear all the time, and in some behavioural bugs, you’ll have to file a bug report yourself. The following items are information the developers need in order to reproduce the bug.
The more information you give us, the better we can help you.
We may need a debug log to help pin-point the issue. A new log file is created each time you start OpenLP so copy the file before you run the software a second time. On Windows a Debug option is available in the start menu. On other systems, you will need to run OpenLP from the command line, with the following option: `-l debug`. Please note, that is a lowercase L.
If you haven’t been given a specific email address to send it to, then please do not paste the log contents straight into a forum post. Instead, open the log file in a text editor (such as notepad on Windows) and copy and paste the contents into somewhere like pastebin.com. Then give us the link to the page that is created.
Find the OpenLP 2.0 folder in your Start menu. Choose the “OpenLP (Debug)” option.
OpenLP will start up. Go to the Tools ‣ Open Data Folder menu option, and an Explorer window will appear containing folders such as alerts, bibles, custom etc. Keep this Explorer window open.
Now repeat the steps you need to take in OpenLP to reproduce the problem you had, and then close down OpenLP.
In the Explorer window you left open, navigate up one level into the openlp folder. You will see the openlp.log file. This is the file to e-mail.
If you installed OpenLP from a package:
@:~$ openlp -l debug
Alternately, if you’re running OpenLP from source:
@:~$ ./openlp.pyw -l debug
If your Linux distribution supports the XDG standard, you’ll find the log in:
Otherwise, you’ll find the log file in:
Open Terminal.app and navigate to where you installed OpenLP, usually /Applications:
@:~$ cd /Applications
Then go into the OpenLP.app directory, down to the OpenLP executable:
@:~$ cd OpenLP.app/Contents/MacOS
And then run OpenLP in debug mode:
@:~$ ./openlp -l debug
Once you’ve done that, you need to get the log file. In your home directory, open the Library directory, and the Application Support directory within that. Then open the openlp directory, and you should find the openlp.log file in that directory:
<username> is your username.
Try installing the Visual C++ Runtime Redistributable.
When running OpenLP from the command line, you might get something like this:
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded WARNING: Phonon::createPath: Cannot connect Phonon::MediaObject ( no objectName ) to VideoDisplay ( no objectName ). WARNING: Phonon::createPath: Cannot connect Phonon::MediaObject ( no objectName ) to Phonon::AudioOutput ( no objectName ). WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded
These error messages indicate that you need to install an appropriate backend for Phonon.
If you’re using Gnome, you need to install the GStreamer backend for Phonon. On Ubuntu you would install the `phonon-backend-gstreamer` package:
@:~$ sudo aptitude install phonon-backend-gstreamer
If you’re using KDE, you need to install the Xine backend for Phonon. On Kubuntu you would install the `phonon-backend-xine` package:
@:~$ sudo aptitude install phonon-backend-xine
If you know which audiovisual system you’re using, then install the appropriate backend.
phonon-backend-vlc may also be worth trying on some systems.
Phonon should already be set up properly. If you’re still having issues, let the developers know.
You need to upgrade your song database. See this blog post for information on how to do this.
You need to run Tools ‣ Re-index Songs.
This is a known issue on some Mac OS X 10.5 systems, and has also been seen on Windows XP too. The solution is to convert the image into another format such as PNG.
This is a known issue on some systems, including some XP machines, and we have no solution at the moment.
If you are just playing videos from the Media plugin, try selecting the Use Phonon for Video playback option in the Media configuration, accessible by going to Settings ‣ Configure OpenLP ‣ Media. As for text over video, we have no solution for speeding this up. Reducing the monitor resolution and avoiding shadows and outline text will help. We are hoping a future release of the toolkit we are using (QtWebKit) will help improve this, but there is no timeframe at present.
Since 2.0 was a rewrite from the ground up, you won’t find a great deal of new features since initially we want to ensure all the 1.2 features are included. However the developers have managed to sneak a few in. Take a look at the complete list.
We made a decision to first implement 1.2 features, before going wild on new features. There are only a handful of developers working in their spare time. If we were to try and include everything we wanted to implement, then 2.0 would not likely ever get released.