Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Nächste Überarbeitung | Vorhergehende Überarbeitung | ||
public:projekte:c3:start [2012/12/30 15:30] – angelegt pegro | public:projekte:c3:start [2013/01/03 17:44] (aktuell) – [Marking] atze | ||
---|---|---|---|
Zeile 1: | Zeile 1: | ||
====== FeM C3 Streaming and Recording Setup Documentation ====== | ====== FeM C3 Streaming and Recording Setup Documentation ====== | ||
- | ** Under construction ** | + | ** __!!!! |
+ | |||
+ | Questions go to [[cccongress@fem.tu-ilmenau.de]] | ||
===== Encoding Pipeline ===== | ===== Encoding Pipeline ===== | ||
+ | ==== Recording ==== | ||
* Recording using [[http:// | * Recording using [[http:// | ||
* Recording is done in fixed length segments for continous capturing (and not missing any lecture starts) without reaching file system limits | * Recording is done in fixed length segments for continous capturing (and not missing any lecture starts) without reaching file system limits | ||
+ | |||
+ | ==== Marking ==== | ||
+ | |||
+ | The main goal of the marking process is to avoid the massive I/O that was necessary in earlier encoding setups. So the core concept is to use a custom [[http:// | ||
+ | |||
+ | In 2012 there was a remake of the recording pipeline, especially in this process to support multiple audio tracks for 29C3 and maybe higher resolutions in the future. The pipeline used before 29C3 will be referenced as " | ||
+ | |||
+ | === Marking v1 workflow (< 29C3) === | ||
+ | |||
+ | * recording format: rawDV 720x576 (if source is 16:9 then it is recorded anamorph) with 1x stereo PCM 16bit 48ks/s | ||
+ | * files containing 4500 frames each, split by simple perl script | ||
+ | * custom FUSE file system: **[[http:// | ||
+ | * fuse-vdv provides a generated **kdenlive project file** | ||
+ | * this file is opened by an operator on her workstation directly via the glusterFS network share. | ||
+ | * in the provided kdenlive project the virtually concatenated recording is trimmed and the project is saved | ||
+ | * on save, fuse-vdv parses the written project file and extracts the trim marks | ||
+ | * using the trim marks and the knowledge of constant frame sizes in raw DV fuse-dvd provides three additional virtual files | ||
+ | * a file '' | ||
+ | * a file '' | ||
+ | * a file '' | ||
+ | * subsequent processes (e.g. encoding the final files) just use '' | ||
+ | |||
+ | |||
+ | === Marking v2 workflow (>= 29C3) === | ||
+ | |||
+ | (only the differences between v1 and v2 are shown here) | ||
+ | |||
+ | * recording format: [[http:// | ||
+ | * files are split by the ffmpeg segmenter every 3 minutes | ||
+ | * custom FUSE file system: **[[http:// | ||
+ | * fuse-ts also provides a kdenlive project file | ||
+ | * operator trims like in workflow v1 | ||
+ | * after saving the kdenlive project file, fuse-ts **does not** provide trimmed versions of the virtual files, since it doesn' | ||
+ | * it just extracts the trim marks from the project file, converts them from frame numbers to fractioned seconds and stores them for later use | ||
+ | * subsequent processes (e.g. encoding the final files) use the untrimmed '' | ||
+ | |||
+ | |||
==== Ticket Tracker ==== | ==== Ticket Tracker ==== | ||
Zeile 27: | Zeile 67: | ||
* each room one WMV encoder | * each room one WMV encoder | ||
* sdi card, windows media encoder 9 | * sdi card, windows media encoder 9 | ||
- | |||
* each room one slide only encoder | * each room one slide only encoder | ||
- | * sdi card, capture tool providing | + | * sdi card, capture tool providing |
* Code: [[http:// | * Code: [[http:// | ||
+ | * [[http:// | ||
==== Relay ==== | ==== Relay ==== | ||
* RTMP and HTTP Relay using Nginx | * RTMP and HTTP Relay using Nginx | ||
Zeile 37: | Zeile 76: | ||
* Code: [[https:// | * Code: [[https:// | ||
* WMV relay using Windows Server 200X with Media Services | * WMV relay using Windows Server 200X with Media Services | ||
+ | * CDN Controll software and config files | ||
+ | * [[http:// | ||
+ | |||