What kind of input signal can the system handle?
Supported Input Formats, Resolutions, and Best Practices for Optimal Streaming
You can connect to the Deep Live Hub using either the WebRTC or RTMP protocol.
The input endpoint is designed to receive:
- audio or
- video signal.
| Protocol | Latency | Scalability | Security | Browser Support | Use Cases |
|
WebRTC |
sub-second | no P2P, not scalable | Encrypted | yes | Video calls interactive streaming |
| RTMP(S) | 1-3 seconds | Good for ingest | RTMPS encryption | no | Streaming to Youtube, Twitch |
| SRT | 1-2 seconds | Better scalability | AES encryption | no | Secure live broadcasting, unstable networks |
Resolutions:
The system can work with the following video resolution:
- 240P (SD): 426 x 240 Pixel
- 360P (SD): 640 x 360 Pixel
- 480P (SD): 854 x 480 Pixel
- 540P (SD): 960 x 540 Pixel
- 720P (HD): 1.280 x 720 Pixel
- 1.080P (HD): 1.920 x 1.080 Pixel
Frame Rates:
The system can work with the following frame rates:
- 25 fps (frames-per-second)
- 30 fps
- 50 fps
- 60 fps
FPS (Frames Per Second) Limits
For interlaced video, the frame rate can go up to 60 fps, while for progressive video, the limit is 30 fps.Information:
Please check the section "Input resolution and FPS" in the pricing table to see any restrictions in your package.
Input Signal
When selecting an input signal, keep the following in mind:
- The input video resolution determines the output video resolution, which is especially important when using Burned-In or Closed Caption settings.
- Audio quality directly affects the accuracy of transcripts and subtitles. For best results, ensure clear sound with minimal background noise. Avoid overlapping voices, background music, and distracting ambient sounds.