cdn

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
cdn [2025/11/03 12:20] – ischluffcdn [2025/11/03 12:23] (current) – ischluff
Line 17: Line 17:
  
 === 1. Encoder === 1. Encoder
-The master stream encoding is created near the stage on the encoder PC running voctomix or on with other videoencoder for third party streams. +The initial stream encoding is created near the stage on the encoder PC running voctomix or any video-encoder for third party streams. 
-The master encoding contains a 1080p25 H264 video signal, the slides as 1080p5 and up to 3 tracks of audio encoded in AAC (Native, Translated, Translated-2).+The encoding usually contains a 1080p25 H264 video signal, the slides as 1080p5 and up to 3 tracks of audio encoded in AAC (Native, Translated, Translated-2).
 The translated audio tracks and the slide video track are optional. The translated audio tracks and the slide video track are optional.
  
-The master encoding is pushed as MPEG-TS via SRT to the ingest stage.+The origin encoding is pushed as MPEG-TS via SRT to the ingest stage.
  
 === 2. Ingest === 2. Ingest
-The ingest machines run both [[https://github.com/voc/srtrelay|srtrelay]] and nginx-rtmp to receive pushed streams from the master encoders. This also serves as the entry point for third party streams.+The ingest machines run both [[https://github.com/voc/srtrelay|srtrelay]] and nginx-rtmp to receive pushed streams from the encoders. This also serves as the entry point for third party streams.
  
 Additionally the ingest machines run a stream-api daemon which scrapes the local stream information from both srtrelay and nginx-rtmp and publishes it to consul KV. Additionally the ingest machines run a stream-api daemon which scrapes the local stream information from both srtrelay and nginx-rtmp and publishes it to consul KV.
Line 59: Line 59:
  
 === 5. Edge-Relays === 5. Edge-Relays
-The edge relays run nginx with caching proxy config and upstream set to the master relay.+The edge relays run nginx with caching proxy config and upstream set to the active origin relay.
  
 === 6. Loadbalancer === 6. Loadbalancer
Line 123: Line 123:
  * Building a live status dashboard which shows the current stream->ingest->transcoder pipelines  * Building a live status dashboard which shows the current stream->ingest->transcoder pipelines
  * To gracefully shutdown a relay it could be instructed via consul KV to redirect all clients back to a load balancer while taking it out of the haproxy redirects. That way all clients would be redistributed to different relays.  * To gracefully shutdown a relay it could be instructed via consul KV to redirect all clients back to a load balancer while taking it out of the haproxy redirects. That way all clients would be redistributed to different relays.
- * Build master relay redundancy using dynamic upload client and relay upstream configuration. (Relay upstreams need to be sticky, because the HLS playlists generated on the master relay are not deterministic)+ * Build origin relay redundancy using dynamic upload client and relay upstream configuration. (Relay upstreams need to be sticky, because the HLS playlists generated on the origin relay are not deterministic)
  * Use DNS rotation on ingest  * Use DNS rotation on ingest
  * Finalize srtrelay meshing to allow pushed streams to be pulled from any ingest machine.  * Finalize srtrelay meshing to allow pushed streams to be pulled from any ingest machine.
  • cdn.txt
  • Last modified: 2025/11/03 12:23
  • by ischluff