CRS Ticket Tracker

The Ticket Tracker is a web platform tracking process of video recording and ingest sources and video encoding progress. It guides users through manual processes like editing and checking and provides an API for scripts doing post processing and encoding.

The tracker is a PHP web application and distributes tasks in form of 'tickets' to various workers. The worker scripts – written in Perl, Python, or PHP – advance the state and update the ticket's properties via tracker's XML RPC API.

The core system was initially written by FeM for 27C3 in 2010, and was released under the Apache License 2.0 end of 2017. Our instance is deployed at https://tracker.c3voc.de.

source code:

Further resources:

The C3 Ticket Tracker enables the (semi-)automated recording, editing & release of multilingual videos. In order to complete a release successfully, certain project settings must be configured and a few of the state transitions must be operated manually:

One of the really good features of the C3 tracker is that propertyies are inherited through the hierarchy:

  • Project settings (Conference or Series)
    • Meta ticket (Parent with Fahrplan-ID & -Metadata)
      • Recording ticket (Language, etc)
        1. Main encoding ticket (MP4)
        2. additional encoding tickets, e.g. WebM, MP3, Opus, SD formats, etc.

For each ticket type, the tracker has a predefined set of states, which can be enabled and disabled on an per project basis. Here is an example workflow with only one manual `checking` step:


see checking

Ticket types and states

  • Parent tickets for each Fahrplan entry
  • one recording ticket for each parent
  • several encoding tickets, one for each format – e.g. MP4 HD, MP4 SD, WebM, MP3, Opus
  • Create tracker project (you can also clone a matching project to have prefilled properties)
  • Import schedule.xml
  • Set all master tickets from staging to staged via mass-edit
  • Adjust project properties, recommendations: (full reference at the bottom of the page)
  • Compare project properties with previous instalment of the same event

see Project setup for more details

User accounts can have different roles depending on what the user should be able to do:

  • “User” - can cut and edit tickets
  • “Restricted” - can only use already defined actions and can't define new actions
  • “Superuser” - can edit profiles and (re)import fahrplan
  • “Admin”

more details on https://github.com/crs-tools/tracker/blob/master/src/Config/AccessControl.php

Files that should be handled by the tracker (input files) should be named as follows:


Files need to be placed in directories according to the room name

Note: Note that names are stripped from frab and combined with the word “saal” which means i.e. “startrampe 23” results in “saal23”. THIS WILL BE FIXED IN THE FUTURE.

Naming for intro and outro:

  • Intro <frab-id>.dv
  • Outro: outro.dv

The cutting process requires start and end marks. The tracker accepts frame numbers. If your player does not show frame numbers you can approximate with the formula

seconds * 25

assumed you have 25 frames per second. Note that this means you cut per second not per frame !!!

  • c3tracker/start.txt
  • Last modified: 2022/02/27 16:25
  • by andi