C3 Ticket Tracker [c3voc]

Diese Seite ist nicht editierbar. Sie können den Quelltext sehen, jedoch nicht verändern. Kontaktieren Sie den Administrator, wenn Sie glauben, dass hier ein Fehler vorliegt.
FIXME **Diese Seite wurde noch nicht vollständig übersetzt. Bitte helfen Sie bei der Übersetzung.**\\ //(diesen Absatz entfernen, wenn die Übersetzung abgeschlossen wurde)//

= C3 Ticket Tracker

The C3 Ticket Tracker is the central managing component in our [[docu:overview#postprocessing|postprocessing]] pipeline, releasing the final recordings. The tracker is a PHP web application and distributes tasks in form of '//tickets//' to various //workers//. The workers – 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:
* https://github.com/crs-tools/tracker
* workers
  * https://github.com/crs-tools/crs-scripts (Perl)
  * https://github.com/voc/publishing (Python)
  * https://github.com/crs-tools/tracker-lib-php (PHP)
* [[projects:fuse-ts | custom fuse filesystem driver used by tracker workers]]
* (VOC) encoding profiles: TODO FIXME

Further resources:
* [[https://wiki.fem.tu-ilmenau.de/public/projekte/c3/start | FeM tracker Beschreibung / FeM *C3 Doku]]
* [[https://repository.fem.tu-ilmenau.de/trac/c3tt/wiki | FeM tracker doku]]
* [[https://wiki.fem.tu-ilmenau.de/streaming/projekte/c3/28c3/crs/pipeline | old FeM tracker doku (probably outdated but still usefull]]


== Concepts

The C3 Ticket Tracker ermöglich die (teil-)automatisierten Aufzeichnung, Schnitt & Release von mehrsprachigen Videos. Um ein Release erfolgreich abzuschließen, müssen bestimmte Projekt-Einstellungen  konfiguriert werden und einige wenige Status-Übergänge bedient von Hand bedient werden:

=== Ticket types and hierarchy

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

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

=== Ticket states

{{drawio>c3tracker:states}}


== Usage during event


=== Task: Cut

see [[operation:cutting]]

{{c3_tracker_-_schnitt_mit_kdenlive.mp4}}
* [[https://www.youtube.com/watch?v=K-KHbAcTo9I|Usage video YT link]] (german)


* TODO: [[events:cccamp15:pp]] integrieren

=== Task: Check 

see [[operation:checking]]


Ticket types and states

* Parent tickets for each [[:schedule|Fahrplan]] entry
* one recording ticket for each parent
* several encoding tickets, one for each format – e.g. MP4 HD, MP4 SD, WebM, MP3, Opus


== Project setup

  * 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 [[c3tracker:setup]] for more details

=== User Roles
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


== Recording
Files that should be handled by the tracker (input files) should be named as follows:
<code>
  <room>-YYYY-MM-DD_HH-MM-SS.<extension>
</code>

Files need to be placed in directories according to the room name
<bootnote>
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.
</bootnote>

Naming for intro and outro:
  * Intro <frab-id>.dv 
  * Outro: outro.dv

== Postprocessing

=== Cut
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
<code>
seconds * 25
</code>
assumed you have 25 frames per second. Note that this means you cut per second not per frame !!!

== Trackerfahrer Scripts

see [[scripts]]

== Ticket Properties

see [[properties]]