Kdenlive/Manual/Installation: Difference between revisions

Revision as of 14:08, 24 December 2012

Other languages:

Installation

Install binary packages

Multimedia packages are made available on many alternative repositories, often because of distributions restrictions on available codecs due to patents in some countries (mainly US for the moment).

Everything would be perfect in a wonderful world if package builders would contribute to official distributions, and multimedia editors chose only free codecs to promote their use worldwide ... So try to stick to distributions deliveries?

Debian, Ubuntu and derivatives

Debian project ships Kdenlive packages since "squeeze" (6.0) release, however to benefit from recent updates and bugfixes you might consider upgrading to a "testing" release or even "sid".

Ubuntu also offers Kdenlive since "gutsy" (7.10), but for similar reasons it could be preferable to upgrade to the latest release.

In both cases a simple apt-get install kdenlive should then work.

Fedora, RedHat and derivatives

RPM packages are not yet maintained in official branch, so you must go through an unofficial repository such as RPM Fusion or packman. Follow the sites recommendations to make them available and end with yum install kdenlive

Gentoo, Arch, BSD ports

Building scripts are ready for up-to-date systems, so run respectively emerge kdenlive or pacman -S kdenlive or pkg_add kdenlive, etc.

Windows

There is no native Windows version of Kdenlive yet. However, you can use some virtualized Linux distribution to run Kdenlive on Windows. Some advices can be found on this page.

MacOS

Kdenlive and MLT can compile and run under Mac OS X. Packages are available from the MacPorts project.

MacPorts is a source-based system - there is not a binary app bundle for Kdenlive. Therefore, Kdenlive and all of its numerous dependencies including multimedia libraries, KDE, and Qt must be compiled. This can take a long time and much disk space! Furthermore, it is not unusual for something not to build correctly; it is definitely not something for the novice, impatient, or "faint of heart."

For more details see this

Installing from source

If you want to test latest committed code or your personal patches, you will have to build Kdenlive (and probably MLT) on your own.

You can use your distribution's package building procedure to use its software management system to install/upgrade/remove the binaries and data, and eventually share your builds (and even contribute to package maintainance - refer to the respective distribution manual).

If you prefer you can build & install Kdenlive to a local area (preferably not /usr, but rather /usr/local or $HOME/my_local_builds/kdenlive-last-release or similar). It is then recommanded to use the build script ^[1]

Installing from Sunabs PPA

Olivier Banus (AKA Sunab) provides a personal package archive (PPA) of the latest development trees of Frei0r-plugins, MLT and Kdenlive. For details on how to install Kdenlive using this source see launchpad.net

@@ Line 60: / Line 60: @@
 If you prefer you can build & install '''Kdenlive''' to a local area (preferably not <tt>/usr</tt>, but rather <tt>/usr/local</tt> or <tt>$HOME/my_local_builds/kdenlive-last-release</tt> or similar).
 It is then recommanded to use the [http://www.mltframework.org/twiki/bin/view/MLT/BuildScripts#Kdenlive build script] <ref>on distributions older than ''Debian 6'' or ''Ubuntu 10.04'' and derivatives, you need to set <code>ENABLE_SWFDEC=0</code> in the config variables of the script</ref>
+===Installing from Sunabs PPA ===
+Olivier Banus (AKA Sunab) provides a personal package archive (PPA) of the latest development trees of Frei0r-plugins, MLT and Kdenlive. For details on how to install Kdenlive using this source see [https://launchpad.net/~sunab/+archive/kdenlive-svn launchpad.net]
 <!--T:25-->