Differences

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

--- c3tracker:start [2022/02/27 16:25] – andi
+++ c3tracker:start [2025/06/19 11:37] (current) – andi
@@ Line 19: / Line 19: @@
 * [[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]]
+== Ticket Properties
-== Concepts
+see [[properties]]
-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:
-=== Ticket types and hierarchy
-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)
-           - Main encoding ticket (MP4)
-           - additional encoding tickets, e.g. WebM, MP3, Opus, SD formats, etc.
-=== Ticket states
-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:
-{{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
@@ Line 117: / Line 28: @@
 see [[scripts]]
-== Ticket Properties
-see [[properties]]