Prism encoders can encode and stream video to Prism decoders using several different protocols by configuring your decoder card to receive streams from the encoder. Choose the Stream Mode and Ingest Mode that are best for your application. Depending on the video’s destination, you can create and pick from various stream modes, each with its own set of configurable settings described here. Before streaming, ensure that the encoder and decoder are on the same network and using the same streaming method.
CREATING STREAM MODE PRESETS
1. Click one of the Stream options under the Streaming tab.
2. Select a stream mode, then configure the Stream mode settings.
3. Click the Save as Preset button to save the current settings under the Preset Menu list. You will prompted to create a unique name for the preset.
4. To load a stream preset, open the Preset window and make a selection from the Load Stream Presets dropdown menu.
5. Click Load Preset.
6. To stream to an RTMP-based platform like Facebook or YouTube Live, click Go Live at the top of the page.
7. To manage your Stream Presets, navigate to System Settings.
STREAM / INGEST MODES
NOTE: All streaming modes are compatible with H.264 encoders and decoders, although some configurable options will be different between H.264 and HEVC encoders.
MPEG TRANSPORT STREAM (MPEG-TS)
In MPEG Transport Stream Mode, Prism sends video via a TCP or UDP protocol to a specified unicast or multicast address. TCP is recommended when streaming over the Internet, while UDP is recommended when streaming over a local network to avoid the additional network overhead of TCP. Select the protocol best suited for your application needs, and ensure the Prism encoder is configured to stream to the Prism decoders corresponding IP address and port.
CONFIGURABLE SETTINGS
- Protocol (UDP/TCP/TCP Server/Multicast)
- TCP Server Port
- Server Queue
- Max Clients
- Local Stream Settings
- Password
ADVANCED SETTINGS
|
SRT
SRT is used to transmit high-quality, low-latency video over unreliable networks. SRT has two connection types: Listener and Caller. When the connection type is set to Listener, the encoder waits for the client to connect and pull the stream from it. When the connection type is set to Caller, the encoder pushes video to a single destination IP address on a specific port. For either mode, a port number and a passphrase (if encryption is enabled) is needed. For a direct connection (Caller mode), enter the correct destination IP address.
CONFIGURABLE SETTINGS
- Connection Type
- Host (Caller)
- Port
- Source Port
- Stream ID
- Encryption
- Latency
- Interface Name
ADVANCED SETTINGS
|
TRT
TRT facilitates both single-interface and multi-interface bonded transmission, achieving latency as low as 100 ms and 250 ms respectively. This UDP-based protocol is crafted to meet the exacting demands of production managers seeking a bonded, ultra-low latency point-to-point solution for live production environments. TRT has two connection modes: Server and Client. When the connection type is set to Server Mode, the encoder waits for the client to connect and pull the stream from it. When the connection type is set to Client Mode, the encoder pushes video to a single destination IP address on a specific port for a direct connection. A source or listening port number and a passphrase (if encryption is enabled) are needed for either mode.
CONFIGURABLE SETTINGS
- Name
- Connection Mode
- Server (Caller)
- Client (Listener)
SERVER SETTINGS
|
CLIENT SETTINGS
|
TERADEK CLOUD
Prism encoders and decoders can be remotely accessed, configured, and controlled using Teradek’s Core management and routing service. Select this mode to link your device to your Core account.
CONFIGURABLE SETTINGS
- Protocol (TCP/UDP)
- Host
- Port
- Session Password
- Buffer Length
- Adaptive Bitrate (Enable/Disable)
- Encryption (Enable/Disable)
RTSP
When RTP/RTSP mode is enabled, the decoder communicates whether to use the TCP or UDP protocol for the stream. Ensure you have the correct port and stream name (stream1 is the default).
CONFIGURABLE SETTINGS
- RTSP Server Port: The port used for RTSP communication and streaming (commonly 554).
- Stream Name: A unique identifier that specifies the stream on the server.
- Authentication (Enable/Disable): Toggles security for stream access. Note: When enabled, you must provide a username and password.
RTP Push - Encoder only
RTP Push actively transmits audio and video data from the sender (encoder) to a designated receiver (decoder or server) using the Real-time Transport Protocol (RTP). By directly pushing the stream to a specified IP address and port, RTP Push ensures a consistent and controlled delivery without requiring the receiver to initiate or request the stream.
CONFIGURABLE SETTINGS
- Session Name: A unique identifier for the RTP session, helping to differentiate streams in a system or network.
- IP Address: The destination IP address to which the RTP stream is sent, identifying the receiver (e.g., server or decoder).
- Port: The specific network port on the receiver's system used for receiving the RTP stream.
- TTL (Time to Live): Controls how many hops the RTP packet can make across the network before being discarded, limiting its reach to prevent unnecessary network load.
- Interface (Wired 1, Wired 2, WiFi): Specifies which network interface to use for transmitting the RTP stream, providing flexibility in network connectivity.
RTMP (H.264 only)
RTMP mode allows Prism to stream to other video platforms, CDNs, and streaming servers that are not one of the available Internet Streaming platforms (see below). RTMP is supported by most video streaming platforms, but you must first obtain a URL and stream key/name from the service you choose to stream to. Log into your account’s settings and retrieve the URL and stream key/name.
CONFIGURABLE SETTINGS
- Channel Name: Identifier for the streaming channel or session.
- Server URL: Address of the RTMP server receiving the stream (e.g., rtmp://server.com/app).
- Stream Key: Unique code to authenticate and route the stream to the desired channel.
- Username/Password: Credentials for server access, ensuring secure streaming.
- User Agent (FMLE/Teradek): Specifies the encoder type for compatibility (Flash Media Live Encoder or Teradek).
- Adaptive Bitrate: Adjusts stream quality dynamically based on network conditions.
- Auto Reconnect: Automatically attempts to reconnect if the stream is interrupted.
- Auto Start: Begins streaming automatically when the encoder powers on.
RIST
RIST (Reliable Internet Stream Transport) is a streaming protocol that ensures reliable video and audio transmission over unpredictable networks, including the Internet. RIST streaming mode suits professional video delivery by actively addressing issues like packet loss, jitter, and network congestion without reducing video quality.
CONFIGURABLE SETTINGS
- Connection Type (Client/Host): Defines if the device initiates (Client) or accepts (Host) the connection.
- Host (Client): IP address or hostname of the receiving device.
- Port: Specifies the network port for data transmission.
- Encryption: Secures the stream using protocols like AES.
- Canonical Name: Unique identifier for the device in a RIST session.
STREAM DASH & HLS (m4s segments) - Encoder only
DASH (Dynamic Adaptive Streaming over HTTP) and HLS (HTTP Live Streaming) are adaptive streaming protocols that adjust video quality based on network conditions, providing a smooth viewing experience. Combining both protocols ensures compatibility across a wide range of devices, allowing streaming platforms to deliver high-quality video to a broader audience.
WHEP
WHEP (WebRTC HTTP Egress Protocol) enables easy delivery of WebRTC streams over HTTP, making it simpler to distribute real-time video content. It works with WHIP (WebRTC HTTP Ingestion Protocol) to manage outgoing WebRTC streams, supporting ultra-low-latency streaming for live events and real-time applications without complex setups.
WHIP - Encoder only
WHIP (WebRTC HTTP Ingestion Protocol) simplifies sending real-time video streams to media servers via HTTP, supporting low-latency, live streaming applications like gaming and live events. Using the Publishing Token for secure authentication and an Endpoint URL to direct the stream, WHIP establishes an easy, HTTP-based method to deliver WebRTC streams, ensuring only authorized sources can connect to the correct server location.
Dolby.io WebRTC - Encoder only
Dolby.io WebRTC stream mode enables secure, real-time streaming with ultra-low latency. The Stream Name identifies specific sessions, while the Publishing Token provides authentication, ensuring only authorized sources can publish streams. Together, these settings support high-quality, live interactions for events and collaboration.
PhenixRTS WebRTC - Encoder only
PhenixRTS WebRTC stream mode enables ultra-low-latency, real-time streaming for large-scale, interactive events. Using WebRTC technology, it supports synchronized video delivery to millions of viewers with minimal delay, making it ideal for applications like live sports, auctions, and gaming. PhenixRTS provides tools for managing audience interaction, quality control, and secure streaming, ensuring a seamless experience for viewers and broadcasters alike.
STREAMING PLATFORMS - Encoder only
Prism features native integration with some of the most popular streaming platforms. Select a Stream Mode (Wowza, Facebook, or YouTube Live) then follow the prompts to link your account.
NOTE: Your device must be set to H.264 in order to stream to any streaming platform.
- Select Facebook, YouTube Live, or Twitch, then click Link your Account.
- Copy the authentication code generated for your device, go to the link provided, then follow the instructions to authenticate your account.
- Return to the Prism encoder’s web UI and click Continue.
- Enter the title, description and broadcast method, then adjust your privacy settings (if applicable).
- Click Save.