= c3voc in a nutshell

{{ ::docs_architecture-overview-apis.png?500|}}

This page aims to give you an overview how our setup works.
The links below are a good start to get an impression on what we are doing and how:

 * Voctoweb: [[https://media.ccc.de/v/c4.openchaos.2019.09.media | lecture recording from OpenChaos 2019 (deu)]]
 * Voctomix: [[https://media.ccc.de/v/froscon2016-1696-voctomix | lecture recording from FrOSCon 2016 (eng)]]
    * [[http://slides.com/mazdermind/froscon12-voctomix|slides]]
 * Overview about our infrastructure / technology stack as of 2015:
   * [[https://c3voc.de/share/MiniDebConf-VOC-slides.pdf | slides from a MiniDebConf 15 talk (eng)]]
   * [[https://media.ccc.de/v/froscon2015-1520-conference_recording_und_streaming#embedshare | lecture recoding from FrOSCon 2015 (deu)]]

Below you find the overview images which together with the talk / slides should be a good introduction. When you are done with this go back to the startpage and have a look at the more detailed documentation linked there.

* [[:voctomix]]
* [[:cdn]]
* [[:ansible]]
* [[:c3tracker]]
* [[:schedule]]
* [[:api]]



~~CLEARFLOAT~~



== Signal path
The image below shows the signal way from the recording of the image by the camera over to capturing of the signal and encoding it to different formats for streaming of the event.

{{:signalpath.png?direct|}}

== Postprocessing
This image shows different building blogs of the post processing chain. The process goes from recording of the event over to cutting followed by encoding and publishing.

{{:postpros.png?direct|}}