first bunch of content

docs/tracker/checking.md

@@ -0,0 +1,6 @@
+---
+title: "Tracker: Checking"
+order: 2
+---
+
+Please refer to [the wiki at c3tracker:checking](https://c3voc.de/wiki/c3tracker:checking) (for now).

docs/tracker/cutting.md

@@ -0,0 +1,6 @@
+---
+title: "Tracker: Cutting"
+order: 1
+---
+
+Please refer to [the wiki at c3tracker:cutting](https://c3voc.de/wiki/c3tracker:cutting) (for now).

docs/tracker/index.md

@@ -0,0 +1,38 @@
+---
+title: "Tracker: Overview"
+order: 0
+---
+
+The [CRS Ticket Trakcer](https://github.com/crs-tools/tracker) is the main tool which enables the c3voc to process so many videos during the duration of an event.
+It's a web-application at https://tracker.c3voc.de which is managing all tasks to record, cut, encode and release a talk based on the event's schedule in the [schedule.xml](https://c3voc.de/wiki/schedule) format.
+
+All automation at the c3voc is based on the schedule!
+
+## How to Help Us
+During an event, we may need help cutting and checking talks.
+How urgently help is needed depends on how many people from the team are present and how much help we get for operating the halls.
+
+There are two main kinds of help needed:
+
+- Help with normal cutting and checking: You need a laptop and some headphones
+- Help with broken talks: You need to know your way around in a video editor of your choice and ideally have experience in piecing together audio and video from different sources
+
+Usually only 0-10% of the recordings need manual editing becuase of a broken recording or becuase something was shown which shouldn't be released.
+As you may have guessed this work is quite labor-intensive and can take up to a few hours per talk to reach an state which can be released.
+
+## Tasks
+As mentioned before, we have a highly automated standard cutting workflow, but also a way to manually edit videos if needed.
+
+### Normal Cutting
+The normal process is mostly automated, but needs manual intervention to set the actual start and end of the talk.
+See the [cutting](cutting.md) and [checking](checking.md) pages for a detailed descrption what needs to be done.
+
+### Reparing Talks
+To repair a recording, you need to fetch the source files from where they are stored (depends on the event's specific setup) and do your magic in the video editor of your choice.
+Just make sure to render the output as 1920x1080px with 25 fps and no timecode track.
+
+Remove a timecode track with ffmpeg using:
+
+```shell
+ffmpeg -i inputfile.ext -c:a copy -c:v copy -write_tmcd 0 outfile.ext
+```

docs/tracker/setup.md

@@ -0,0 +1,5 @@
+---
+title: "Tracker: Setup"
+---
+
+Please refer to [the wiki at c3tracker:setup](https://c3voc.de/wiki/c3tracker:setup) (for now).