Differences

This shows you the differences between two versions of the page.

--- doc:appunti:linux:video:olive_editor_ovexml [2023/09/28 14:59] – created niccolo
+++ doc:appunti:linux:video:olive_editor_ovexml [2023/09/28 18:03] (current) – [Proof of concept program] niccolo
@@ Line 1: / Line 1: @@
-====== Olive Video Editor OVEXML file format ======
+====== Olive Video Editor: an insight of the OVEXML file format ======
 **[[https://www.olivevideoeditor.org/|Olive Video Editor]]** is the most open video editor in the world. From its completely configurable render pipeline to its open source codebase, every aspect of it is designed to provide users with as much control as possible over both their work and their workflow.
+===== The project can be saved as an XML file =====
 A feature that I really apreciated is the ability to save the project file into an XML file (with the **.ovexml** extension). Being addicted to the **GNU/Linux command** line and **ffmpeg** I immediately tried to convert an Olive project into an ffmpeg script.
+===== A walk inside the OVEXML =====
+Here I explain some findings on an **OVEXML** file created with **Olive v.0.2**.
 Beware that the project I worked on is a **really simple** one! Only two tracks (one video and one audio), video is always locked with the audio, **the clips are just concatenated** without transition effects, gaps, etc. Parsing the OVEXML of such a project is feasible, any extra feature could make the job too challenging.
-My goal was to build **the sequence of clips** used into a project, printing for each clip the footage filename, the start frame and the length. The aim is to make a list of unused footages do trash, and perhaps to build a timeline script to make a rendering using ffmpeg on the Linux command line.
+My goal was to print **the sequence of clips** used into a project, showing for each clip the footage filename, the start frame and the length. The aim is to make a list of unused footages to trash, and perhaps to build a timeline script to make a rendering using ffmpeg on the Linux command line.
-The first challenge was to find the link from the top level node of the project (the **org.olivevideoeditor.Olive.sequence**) down to the lower level node **org.olivevideoeditor.Olive.footage** (e.g. the media files on the computer disk). In this walk I had to figure out how to get the clip starting frame and its length.
+The first challenge was to find the link from the top level node of the project (the **org.olivevideoeditor.Olive.sequence**) down to the lower level nodes **org.olivevideoeditor.Olive.footage** (e.g. the media files on the computer disk). In this walk I had to figure out how to get the clip starting frame and its length.
 The nodes to walk into the XML structure are the following:
@@ Line 29: / Line 35: @@
 </code>
-When foolowing an audio track, you have to search for a **volume** node instead of the **transform**. Starting frame and length of the clip is into the **clip** node, something like this:
+When following an audio track, you have to search for a **volume** node instead of the **transform**. Starting frame and length of the clip is into the **clip** node, something like this:
 <code xml>
@@ Line 49: / Line 55: @@
 </code>
-As you can see the frame numbers are represented as rationales. Being my framerate 29.97 (i.e. 30000/1001) the math is as follow **1001 / 200 * 30000 / 1001 = 150** (i.e. 150 frames clip length). Beare to perform always the multiplication before the divisions, so that you surely get a whole number, without approximation.
+As you can see the frame numbers are represented as rational numbers. Being my footages shot at 29.97 FPS (i.e. 30000/1001) the math is as follow: **1001 / 200 * 30000 / 1001 = 150** (i.e. 150 frames clip length). Beware to perform always the multiplications before the divisions, so that you surely get a whole number, without approximation.
+The most challenging part was to understand how the clips are ordered into the timeline. Unfortunately the **%%<content>%%** nodes into the track are listed rougly in the order they are added to the project, the order does not correspond to the timeline order.
+We have instead to look at the **%%<input id="arraymap_in">%%** tag of the track:
+<code xml>
+<node version="1" id="org.olivevideoeditor.Olive.track" ptr="139716158571008">
+    <input id="arraymap_in">
+        <primary>
+             <standard>
+                 <track>AwAAAAgAAAAFAAAABwAAAAYAAAA=</track>
+             </standard>
+         </primary>
+     </input>
+</code>
+The ASCII string **%%AwAAAAgAAAAFAAAABwAAAAYAAAA=%%** is actually a base64 encoded binary string that you can decode on the command line into a binary file:
+<code bash>
+echo 'AwAAAAgAAAAFAAAABwAAAAYAAAA='  | base64 -d > arraymap_in
+</code>
+And then open it with an hex editor:
+<file>
+00 00 00 │ 08 00 00 00 │ 05 00 00 00 │ 07 00 00 00 │ 06 00 00 00
+</file>
+Hence the timeline sequence of clip elements: #3, #8, #5, #7 and #6 (32 bit unsigned integers, little endian).
+===== Proof of concept program =====
+Here you can find my Python script that I used to parse an Olive Editor project file, the output is the ordered list of all the clips used, with the **footage filename**, the **start frame** and the **length** of the clip (in frames).
+**{{.:olive:olive-ovexml-list-clips-in-project.py.txt|olive-ovexml-list-clips-in-project.py}}**