Kdenlive/Development/File format

Kdenlive's project files (.kdenlive files) use an XML format, based on MLT's format (see also MLT’s DTD/document type definition) to describe the source media used in a project, as well as the use of that media as in the timeline. For most media, such as video, audio, and images, Kdenlive stores only a reference in a project, but not the media itself. Only some media gets stored directly inside Kdenlive’s project files, most notably Kdenlive title and color clips.

Important aspects of this file format decision are:

  • MLT is able to directly render Kdenlive project files. MLT simply ignores all the additional Kdenlive-specific project data and just sticks to its rendering information. The Kdenlive-specific data is the additional icing on top that makes working with projects much easier than editing at the (lower) rendering level.
  • Kdenlive can directly include and work with MLT rendering files, just the same way it works with other media. In fact, Kdenlive’s library clips are simply MLT rendering files, and nothing more.

There are different file format generations depending on the version of Kdenlive you're using.

Generation 1

Generation 1 (gen-1) projects were created and edited the last time using Kdenlive up to 0.9.10. These are the Kdenlive versions developed for KDE 4.x. (While this isn’t strictly true, we won’t go into discussions about the early KDE 3.x versions of Kdenlive.)

The gen-1 projects contain a lot of project data that needs to be duplicated into the outer MLT XML data in order to MLT understanding what it needs to do. As an unfortunate consequence of this data duplicity, gen-1 projects had the habit of getting the outer MLT data out of sync with the inner Kdenlive project data. For instance, sometimes the effects as rendered got out of sync with the effect parameters as set in the Kdenlive user interface. As the proper remedy for this situation, the Kdenlive developers switched to Generation 2 as part of their porting Kdenlive to the KDE Frameworks 5 (or “KF5” for short).

Generation 2: KF5

Generation 2 projects are those created or last edited using Kdenlive 15.04 or later, up to 17.08 stable.

With the KF5/Qt5 version of Kdenlive, we now store all Kdenlive data through MLT's xml module to remove the data duplicity from the Kdenlive project file structure. This fixed project data model results in much more stable Kdenlive project behavior. As another positive side effect, it’s now much easier to manually edit or create Kdenlive XML project files from outside Kdenlive.

Project XML Structure

The overall structure of the XML data inside Kdenlive project files is roughly as illustrated next:

 1 <mlt producer="main bin">
 2   <!-- definition of rendering profile -->
 3   <profile/>
 4 
 5   <!-- definition of master clips, as well as derived producers -->
 6   <producer id="#"/>
 7   <producer id="#_video"/>
 8   <producer id="#_playlist"/>
 9   <producer id="slowmotion:#:#:#"/>
10   ...
11 
12   <!-- project settings, and more -->
13   <playlist id="main bin">
14 
15   <property name="kdenlive:...">...</property>
16     ...
17   </playlist>
18 
19   <producer id="black"/>
20 
21   <!-- the individual timeline tracks -->
22   <playlist id="playlist#"/>
23   ...
24 
25   <!-- the main tractor is the last producer in the document,
26        so MLT takes it as the default for playout -->
27   <tractor id="maintractor">
28     <track producer="..."/>
29     ...
30 
31     <!-- all transitions -->
32     <transition id="transition#"/> <!-- user transitions -->
33     <transition id="transition#"> <!-- internally added trans -->
34       <property name="internal_added">237</property>
35     </transition>
36 
37   </tractor>
38 </mlt>

We avoid storing any inner Kdenlive project data that’s already present in the outer MLT data layer, this means that all information must be stored in MLT objects like Tractor, Playlist, Producer, etc.

To separate these properties from other MLT properties, we prefix them with "kdenlive:". This page lists the properties that we use in this new file format.

Properties applied to project clips (MLT Producer object)

  • kdenlive:clipname
    Stores the name that will be displayed for this clip in the Project Bin
  • kdenlive:folderid
    Stores a string containing the id of the folder where this clip is (empty if clip is in the root folder).
  • kdenlive:zone_in
    Stores the "in" point for the play zone defined for this clip
  • kdenlive:zone_out
    Stores the "out" point for the play zone defined for this clip
  • kdenlive:originalurl
    Stores the clip's original url. Useful to retrieve original url when a clip was proxied.
  • kdenlive:proxy
    Stores the url for the proxy clip, or "-" if no proxy should be used for this clip.

Project Bin

The (project) bin is represented by an MLT <playlist> element with the well-known id “main bin”. This element holds project-specific (meta) data, the bin folders as well as their hierarchy, clip groups, and some more stuff.

Note
While Kdenlive now mainly uses the term “bin” when talking about what formerly was the “project bin”, the early internal name “name bin” has stuck since the early days of Kdenlive.


Properties applied to the Bin Playlist (MLT Playlist object "main bin"):

  • kdenlive:folder.xxx.yyy
    This property stores the names of folders created in the Project Bin. xxx is the id of the parent folder (-1 for root) and yyy is the id for this folder. The value of this property is the name of the folder.

Timeline Tracks

The setup of the timeline tracks is represented by an MLT <tractor> element with the well-known id “maintractor“. The elements inside are the individual timeline tracks: these are referenced, with the actual tracks then being MLT producers (see next).

The indivdual Kdenlive timeline tracks can be found in form of MLT <playlist> elements. They can also easily be identfied according to their “playlist#” id naming scheme; here, “#” is a number internally maintained by Kdenlive. The tracks feature additional properties that describe their title, locking state, and some more.

There is one semi-internal track here, the built-in “black” track. As you can see here, while it is built into Kdenlive, it isn’t so into MLT. Instead, to MLT this is just another track that happen to be created by Kdenlive. Kdenlive never shows this background track in the timeline as an individual track. But you can reference it from transitions (the composite ones, that is).

Transitions (Compositions)

Transitions come in two (three) flavors, but always represented by MLT <transition> elements:

  • user transitions are the ones added by, you’ve guessed it … users. These are the transitions currently shown slightly moved down and overlaying timeline tracks and their clips.
  • internally added transitions are basically a convenience to make the timeline do automatic audio mixing across multiple tracks, and (with more recent Kdenlive versions) transparent tracks.

Not Shown

  • bin clip producers
  • proxy clips

Slightly Invalid XML?

When you need to process Kdenlive project files using XML tools, there’s a gotcha to be aware in case of gen-2 project files. As soon as a project makes use of track-wide effects, the project XML as written by Kdenlive becomes invalid. You won’t notice this when editing Kdenlive project files just inside Kdenlive, and render them using MLT. You will only notice when editing them using standard XML tools.

The reason is that Kdenlive uses (or has used) its own attributes inside a separate “kdenlive” namespace. Unfortunately, Kdenlive forgets to declare this additional namespace it uses at the beginning of every XML project document. As a simple fix, you’ll need to add the missing namespace yourself before processing the Kdenlive project file with XML tools:

1 <?xml version='1.0' encoding='utf-8'?>
2 <mlt xmlns:kdenlive="http://www.kdenlive.org/project" ...>
3   ...
4 </mlt>


Generation 3: Timeline 2

Generation 3 projects are those projects created or edited using Kdenlive versions with the new Timeline 2 engine.

Generation 4: Comma / Point

With version 20.08.0 a major refactoring of the project file fixed a long standing issue with the decimal separator (comma/point) conflict causing many crashes. Projects created with 20.08 forward are not backwards compatible.

Further Reading


This page was last edited on 3 May 2021, at 14:47. Content is available under Creative Commons License SA 4.0 unless otherwise noted.