Contents

Thread titleRepliesLast modified
Additional Kubuntu 15.10 Packages020:41, 18 January 2016
Following a Specific Branch017:40, 31 December 2015
Make sure to set env variables correctly for home dir-based setups020:13, 22 December 2015
Following Kdenlive Patches Early019:08, 15 November 2015
make -j#015:51, 9 October 2015
Kubuntu: Installing a recent git version of FFmpeg for Kdenlive (optional) 013:19, 6 October 2015

Additional Kubuntu 15.10 Packages

On Kubuntu 15.10, more additional packages need to be installed first.

MLT[edit]

Also install the (optional) libsamplerate.

$sudo apt-get install libsamplerate-dev

Kdenlive[edit]

While not strictly related to compiling your own Kdenlive, you may later experience that a lot of transitions may be missing. In fact, many transitions are not built into MLT, but instead come from the frei0r plugins. So you need to make sure that those plugins are installed, unless you know for sure that they have been installed as part of another package.

$ sudo apt-get install frei0r-plugins

In addition, you must install also the following KF5 dev packages in order to be able to compile Kdenlive.

$ sudo apt-get install libkf5crash-dev libkf5filemetadata-dev

Edit: added libkf5crash-dev, libkf5filemetadata-dev

Ffmpeg[edit]

$sudo apt-get install yasm
17:43, 15 November 2015

Following a Specific Branch

Say you don't want to follow the main development but instead a particular branch. In particular, Kdenlive developers currently work in a main branch as well as a maintenance branch and a upcoming release branch: for instance, MAIN, Applications/15.08, and Applications/15.12. Here, Applications/15.08 may be the maintenance branch for the current recent releases. In contrast, Applications/15.12 is to soon to be recent development branch that may be under beta testing right now.

So you want to live on that beta development branch? After you've cloned the Kdenlive git repository, switch to the appropriate branch:

git checkout Applications/15.12 origin/Applications/15.12

You are now following that specific development branch. Using

git pull origin

you can pull upstream changes made by the Kdenlive developers in the meantime. This assumes that you are not doing any development on your local Kdenlive git repo and instead only want to get the source code as fresh as possible.

If you want to switch back to the master branch, simply use:

git checkout master

Edit: removed -b option to git-checkout. Edit: added example for switching back to master branch.

16:29, 6 December 2015

Make sure to set env variables correctly for home dir-based setups

It is important to have especially the environment variable XDG_DATA_DIRS correctly set to point to the share dir inside the Kdenlive installation directories. The given standard paths for XDG_DATA_DIRS are typically /usr/share as well as /usr/local/share. So if you install Kdenlive to some other place, such as within your own home directory, make sure to add the path to your home-based share dir to XDG_DATA_DIRS before attempting to start Kdenlive. Failing to do so causes Kdenlive to crash in unexpected situations, such as when trying to select a transition in the timeline.

Here's a nifty little script that sets up the environment variables automatically, then fires up Kdenlive; place this script next to your kdenlive executable. And don't forget to make it executable (chmod u+x kdenlive.sh).

#!/bin/bash
SCRIPT_NAME=$(readlink -f "$0")
SCRIPT_PATH=$(dirname "$SCRIPT_NAME")
export INSTALL_PREFIX=$(dirname "$SCRIPT_PATH")
export LD_LIBRARY_PATH=$INSTALL_PREFIX/lib
export XDG_DATA_DIRS=$INSTALL_PREFIX/share:$XDG_DATA_DIRS:/usr/share
export XDG_CONFIG_DIRS=$INSTALL_PREFIX/etc/xdg:$XDG_CONFIG_DIRS
echo "Environment set up for $INSTALL_PREFIX"
$INSTALL_PREFIX/bin/kdenlive

Edit: added missing LD_LIBRARY_PATH setting.
Edit: added setting XDG_CONFIG_DIRS to properly access .knsrc config files.

16:24, 21 October 2015

Following Kdenlive Patches Early

So we video editing people may not be exactly git rocket scientists. So when the Kdenlive developers put in new patches fixing bugs (what's that?) after you've retrieved the Kdenlive source code, how do you keep up with changes?

Fortunately, that's easy. Change into the directory into which you originally clones the Kdenlive git repository. This should be often named "kdenlive" and is the parent directory to the "build" dir. Then fast forward your sources to the current state of affairs:

$git pull origin

Next, make sure that you've set INSTALL_PREFIX and XDG_DATA_DIRS correctly (as you did the first time you'd compiled Kdenlive sources).

$export INSTALL_DIR=...
$export XDG_DATA_DIRS=...

Change into the proper build directory, clean, and compile.

$cd build
$make clean; make -j4

If that succeeded, install again.

$make install
19:07, 15 November 2015

Maybe the compilation instructions should explain the meaning of make -j#: this controls the number of parallel compilation jobs. -j4 is fine for a Core i3/i5, while it bores a Core i7 to death. On a Core i7 thus better use -j8 as it speeds up compilation a lot and makes use of all available real cores...

15:51, 9 October 2015

Kubuntu: Installing a recent git version of FFmpeg for Kdenlive (optional)

In order to be able to successfully compile ffmpeg, several library development packages need to be installed. I think it would be convenient to such user if they can install the missing packages in a single run instead of having to run configure over and over again just to find what is next missing.

$sudo apt-get install libfaac-dev libgsm1-dev libmp3lame-dev libopencore-amrnb-dev libopencore-amrwb-dev libschroedinger-dev libtheora-dev libvorbis-dev libvpx-dev libx264-dev libx265-dev libxvidcore-dev libdc1394-22-dev
13:19, 6 October 2015

This page was last edited on 6 October 2015, at 13:19. Content is available under Creative Commons License SA 4.0 unless otherwise noted.