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
• Stream/Ingest Modes
  • MPEG Transport Stream
  • SRT
  • TRT
  • Teradek Cloud
  • RTSP
  • RTP Push
  • RTMP
  • RIST
  • Stream DASH & HLS (m4s segments)
  • WebRTC-HTTP Egress Protocol (WHEP)
  • WebRTC-HTTP Ingestion Protocol (WHIP)
  • Dolby.io WebRTC
  • PhenixRTS WebRTC
  • Streaming Platforms (Facebook, YouTube, Wowza)

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 be 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.

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 minimize the additional network overhead associated with 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): Choose between UDP, TCP, TCP Server, or Multicast:
  • TCP – This is the default setting and works well in most situations. TCP adds very little overhead beyond the video bitrate required for the bonding protocol, and TCP typically performs reliably across all connection types.
    • TCP Address - Enter the IP address of the decoder or server that will receive the MPEG-TS stream.
    • TCP Port - Specify the TCP port that receives the stream.
    • Adaptive Bitrate - Enable adjustment of video bitrate based on network conditions.
    • Max Buffer Length (Adaptive Bitrate enabled) - Adjust the amount of data the device buffers to manage network issues—longer buffers increase stability, while shorter buffers reduce latency.
    • Interface - Select the network interface the encoder uses to send the stream. Select'Auto'to let the device automatically pick the active interface.
  • TCP Server – The encoder waits for incoming decoder connections instead of initiating them. This mode works well when the encoder sits behind a firewall that restricts outgoing ports, and it still provides the same reliable delivery as standard TCP.
    • TCP Server Port - Specify the TCP server port that receives the stream.
    • Server Queue - Set how long the encoder holds incoming connection attempts before timing out.
    • Max Clients - Set the maximum number of decoders that can connect simultaneously.
    • Interface - Select the network interface the encoder uses to send the stream. Select'Auto'to let the device automatically pick the active interface.
  • UDP – Use UDP only when TCP doesn’t perform well. In high-traffic environments, some networks throttle TCP connections, making UDP a better choice. While UDP itself has no network overhead, the UDP bonding protocol adds roughly 30% above the configured bitrate.
    • RTP (Enable/Disable) - Enable to send the MPEG-TS stream inside RTP packets for receivers that require RTP.
    • UDP Address - Enter the IP address of the decoder or server that will receive the MPEG-TS stream.
    • UDP Port - Specify the destination port that receives the stream.
    • UDP Source Port - Set the port the encoder uses as its outgoing source port. Leave it at 0 to let the encoder assign one automatically.
    • Interface - Select the network interface the encoder uses to send the stream. Select Auto to let the device automatically pick the active interface.
  • Multicast – Use Multicast only on properly configured local networks that support multicast routing. Multicast sends a single stream that multiple receivers can join, reducing total bandwidth usage. This mode is not recommended for Internet streaming, as most wide-area networks do not pass multicast traffic.
    • RTP (Enable/Disable) - Enable to send the MPEG-TS stream inside RTP packets for receivers that require RTP.
    • Multicast Address - Enter the multicast IP address that receivers will join to access the stream.
    • Multicast Port - Specify the port number used for the multicast stream.
    • Multicast TTL - Set the Time-to-Live value, which controls the number of router hops the multicast stream can travel across a network. Higher values allow the stream to pass through more network segments.
    • Interface - Select the network interface the encoder uses to send the stream. Select Auto to let the device automatically pick the active interface.

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) are needed. For a direct connection (Caller mode), enter the correct destination IP address.

Configurable Settings

• Connection Type - Choose how the encoder establishes the SRT connection:
  • Caller - The encoder initiates the connection to the remote IP and port.
  • Listener - The encoder waits for the remote endpoint to connect.
  • Rendezvous - Both endpoints connect simultaneously, useful when both sides block inbound connections.
• Host (Caller/Rendezvous only) - Enter the IP address or hostname of the remote SRT endpoint.
• Port - Network port for receiving/sendingSRT data
• Source Port - Set the encoder’s outgoing source port. Leave at 0 to let the encoder assign one automatically.
• Stream ID - Enter a Stream ID when the receiving endpoint requires it to identify the stream.
• Encryption - Enable sending the stream securely in an encrypted form. When enabled, you will be prompted to create an Encryption Passphrase.
• Latency - Set the SRT latency buffer in milliseconds. Higher values improve reliability on unstable networks; lower values reduce end-to-end delay.
• Interface - Select the network interface the encoder uses to send the stream. Select Auto to  let the device automatically pick the active interface.

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 designed to meet the exacting demands of production managers seeking a reliable, 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) - The encoder initiates the connection to the remote IP and port.
  • Client (Listener) - The encoder waits for the remote endpoint to connect.

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): Choose between TCP or UDP
  • TCP – This is the default setting and works well in most situations. TCP adds very little overhead beyond the video bitrate required for the bonding protocol, and TCP typically performs reliably across all connection types.
  • UDP – Use UDP only when TCP doesn’t perform well. In high-traffic environments, some networks throttle TCP connections, making UDP a better choice. While UDP itself has no network overhead, the UDP bonding protocol adds roughly 30% above the configured bitrate.
• Host - Enter the server address where the device sends the stream.
• Port - Specify the server port that receives the stream.
• Session Password: Set a password to authenticate and secure the streaming session
• Buffer Length - Adjust the amount of data the device buffers to manage network issues—longer buffers increase stability, while shorter buffers reduce latency.
• Adaptive Bitrate: Enable adjustment of video bitrate based on network conditions.
• Encryption (Enable/Disable) - Enable to send the stream securely in an encrypted form. When enabled, you will be prompted to create an Encryption Passphrase.

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 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: Enter the destination IP address of the receiver (decoder or server).
• IP Address: Enter the destination IP address of the receiver (decoder or server).
• Port: Enter the port number the receiver uses to accept the RTP stream.
• TTL (Time to Live): Set how many hops the RTP packet can make across the network before being discarded. Lower values keep the stream contained to local segments.
• Interface (Wired 1, Wired 2, WiFi): Select the network interface the encoder uses to send the RTP stream.

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 (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.

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 (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 (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 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 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.

Prism features native integration with some of the most popular streaming platforms. Select a Stream Mode (Wowza, Facebook, Twitch, or YouTube Live), then follow the prompts to link your account.

1. Select Facebook, YouTube Live, Wowza, or Twitch, then clickLink your Account.
2. Copy the authentication code generated for your device, go to the link provided, then follow the instructions to authenticate your account.
3. Return to the Prism encoder’s web UI and clickContinue.
4. Enter the title, description and broadcast method, then adjust your privacy settings (if applicable).
5. ClickSave.