π₯ Input Streams
Input Streams are the foundation of your streaming workflow, representing live video sources from encoders.
Overview
Input Streams represent live video sources ingested from hardware or software encoders. The platform supports both UDP multicast and RTMP protocols for video ingestion. Each input stream is uniquely identified by a Content ID that must match across the entire streaming pipeline.
Key Concepts
- Content ID: Unique identifier for the stream (case-sensitive)
- Source URL: Location of the input stream (UDP or RTMP)
- Protocol Support: UDP multicast and RTMP
- Encoder Integration: Compatible with standard broadcast encoders
The Content ID is case-sensitive and must match exactly across all components (transcoders, packagers, etc.).
In This Section
- Configuration Guide - How to add and configure input streams
- Protocol Support - UDP and RTMP protocol details
- Testing & Validation - Verify your input streams work correctly
- Best Practices - Optimization and naming conventions
Quick Start
Adding Your First Input Stream
- Navigate to Input Streams from the left sidebar
- Click Add Input Stream button
- Fill in the required fields:
- Name: Descriptive channel name
- Content ID: Unique identifier (case-sensitive)
- Source URL: Complete encoder URL
- Click Save
View detailed configuration guide β
Common Use Cases
Live TV Broadcast
Name: "News Channel HD"
Content ID: "news_hd_01"
Source URL: udp://@239.1.1.1:5000
Event Streaming
Name: "Concert Event Main"
Content ID: "concert_2024_main"
Source URL: rtmp://encoder.example.com:1935/live/event01
Multi-Camera Production
Name: "Sports Camera 1"
Content ID: "sports_cam1_hd"
Source URL: udp://@239.1.1.10:5000
Protocol Support
The platform supports two primary ingestion protocols:
UDP Multicast
- Format:
udp://@[multicast-address]:[port] - Best for: Traditional broadcast workflows
- Requires: Network multicast routing
- Learn more about UDP β
RTMP
- Format:
rtmp://[server]:[port]/[app]/[stream-key] - Best for: Internet-based encoders, OBS, Wirecast
- Requires: RTMP server configuration
- Learn more about RTMP β
Configuration Fields
| Field | Required | Description | Example |
|---|---|---|---|
| Name | β | Human-readable channel name | βSports Channel HDβ |
| Content ID | β | Unique stream identifier | βsports_hd_01β |
| Source URL | β | Encoder stream location | udp://@239.1.1.1:5000 |
| Server | β | Server receiving the input | server-01 |
| Status | β | Enable/Disable toggle | ENABLED |
Workflow Integration
Input streams connect to the rest of your streaming pipeline:
π₯ Input Stream β βοΈ Transcoder β π¦ Packager β π Origin β π₯ Viewers
Next Steps After Configuration
- Create a Transcoder - Transcoders Documentation
- Set up Packagers - Packagers Documentation
- Deploy Origin - Origin Servers Documentation
Related Documentation
- Configuration Guide - Detailed setup instructions
- Testing Guide - Verification methods
- Best Practices - Optimization tips
- Troubleshooting - Common issues