howto:3rdparty_ingest

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
howto:3rdparty_ingest [2026/02/24 22:07] – ischluffhowto:3rdparty_ingest [2026/07/26 22:17] (current) – external edit 127.0.0.1
Line 1: Line 1:
-====== HowTo: Third-Party Stream Ingest ======+###### HowTo: Third-Party Stream Ingest
 You want your live content to be streamed over the C3VOC infrastructure during CCCongress or another large event? Here's how. You want your live content to be streamed over the C3VOC infrastructure during CCCongress or another large event? Here's how.
  
 (Recordings have to be dealt with separately) (Recordings have to be dealt with separately)
  
-===== Get in Touch ======+##### Get in Touch
 To make sure your stream works on day 1 of the event we need to know of it beforehand so we can: To make sure your stream works on day 1 of the event we need to know of it beforehand so we can:
   - configure your ingest endpoint   - configure your ingest endpoint
Line 12: Line 12:
 When we have provided you with an ingest endpoint name to use you need to configure your encoder for one of the formats below. When we have provided you with an ingest endpoint name to use you need to configure your encoder for one of the formats below.
  
-===== Ingest Formats ===== +##### Ingest Formats 
-==== SRT Ingest  ====+#### SRT Ingest
 SRT is our preferred method of ingest, because it performs well even over flaky networks. SRT is our preferred method of ingest, because it performs well even over flaky networks.
 Please note however that SRT won't prevent you from saturating your uplink, so choose a streaming bitrate appropriate for your ISPs bandwidth. Please note however that SRT won't prevent you from saturating your uplink, so choose a streaming bitrate appropriate for your ISPs bandwidth.
  
-=== Stream-Format ===+### Stream-Format
  * Transport: SRT  * Transport: SRT
  * Container: MPEG-TS  * Container: MPEG-TS
Line 28: Line 28:
  
  
-=== URLs ===+### URLs
  
  * Hosts:  * Hosts:
Line 38: Line 38:
    * `srt://{host}:1337?streamid=play/{your_endpoint}/{auth_key}`    * `srt://{host}:1337?streamid=play/{your_endpoint}/{auth_key}`
  
-=== OBS ===+### OBS
  
 Same settings as with [[howto:3rdparty_ingest#obs-studio_example|RTMP]], but use the following in **Settings -> Stream**: Same settings as with [[howto:3rdparty_ingest#obs-studio_example|RTMP]], but use the following in **Settings -> Stream**:
Line 46: Line 46:
  
 **Audio:** Use [[https://github.com/lukas2511/obs-studio|this OBS Fork]] ([[https://cloud.cccv.de/s/bczAqcWHXX8EkL6|compiled version]]) to be able to stream multiple audio Streams (for translations). **Audio:** Use [[https://github.com/lukas2511/obs-studio|this OBS Fork]] ([[https://cloud.cccv.de/s/bczAqcWHXX8EkL6|compiled version]]) to be able to stream multiple audio Streams (for translations).
-=== ffmpeg example ===+### ffmpeg example
 <code> <code>
 ffmpeg -y -re -nostdin -hide_banner \ ffmpeg -y -re -nostdin -hide_banner \
Line 63: Line 63:
 </code> </code>
  
-=== How to test ===+### How to test
 You can play back your stream at the same endpoint you pushed to, e.g.: You can play back your stream at the same endpoint you pushed to, e.g.:
 <code> <code>
Line 74: Line 74:
 </code> </code>
  
-==== RTMP Ingest  ====+#### RTMP Ingest
 RTMP is the most widely used format for origin streams and is supported by many hardware/software-encoders. It is however limited to H264 video and Stereo MP3/AAC audio. RTMP is the most widely used format for origin streams and is supported by many hardware/software-encoders. It is however limited to H264 video and Stereo MP3/AAC audio.
  
-=== Stream-Format ===+### Stream-Format
  * Transport: RTMP  * Transport: RTMP
  * Container: FLV  * Container: FLV
Line 87: Line 87:
  
  
-=== URLs ===+### URLs
  * Hosts:  * Hosts:
    * `ingest.c3voc.de`    * `ingest.c3voc.de`
Line 95: Line 95:
    * Note: Play is currently always possible without auth    * Note: Play is currently always possible without auth
  
-=== ffmpeg example ===+### ffmpeg example
 <code> <code>
 ffmpeg -y -re -nostdin -hide_banner \ ffmpeg -y -re -nostdin -hide_banner \
Line 112: Line 112:
 </code> </code>
  
-=== OBS-studio example ===+### OBS-studio example
   * Settings   * Settings
     * Stream     * Stream
Line 131: Line 131:
       * Integer FPS Value: 25       * Integer FPS Value: 25
  
-=== How to test ===+### How to test
 You can play back your stream at the same endpoint you pushed to, e.g.: You can play back your stream at the same endpoint you pushed to, e.g.:
 <code> <code>
Line 138: Line 138:
  
  
-==== Direct Upload ====+#### Direct Upload
 If you have agreed with us on directly uploading muxed stream to our CDN-master we will provide you with HTTP-credentials and a base-URL to upload to. You will have to provide the following formats: If you have agreed with us on directly uploading muxed stream to our CDN-master we will provide you with HTTP-credentials and a base-URL to upload to. You will have to provide the following formats:
   * A HLS master playlist at http://baseurl/hls/native_hd.m3u8   * A HLS master playlist at http://baseurl/hls/native_hd.m3u8
Line 155: Line 155:
 The baseurl is currently assembled as follows: <code>host/upload/yourname/</code> The baseurl is currently assembled as follows: <code>host/upload/yourname/</code>
  
-===== Output Formats =====+##### Output Formats
 Per default we transcode uploaded streams into an SD and a HD stream (+ potentially a slide only stream). Per default we transcode uploaded streams into an SD and a HD stream (+ potentially a slide only stream).
  
 They are served over different protocols as documented here: [[:cdn#stream-urls]] They are served over different protocols as documented here: [[:cdn#stream-urls]]
  
-===== Recommended encoder settings =====+##### Recommended encoder settings
  
   * H.264:   * H.264:
  • howto/3rdparty_ingest.1771970822.txt.gz
  • Last modified: 2026/02/24 22:07
  • by ischluff