Udp And Rtp Outputs - HELIX Broadcaster 100 User Manual

Helix Broadcaster 100 Touch Screen User Guide
Protocol
UDP with Low Latency TS
Helix Media Server

UDP and RTP Outputs

The following push output types use a transport stream wrapper similar to the output from an
MPEG-2 encoder used in television production. These options can be used to deliver the
encoded output to a satellite uplink, for example.
•
•
•
Purpose
Similar to the other UDP method, this output type is designed to
minimize the latency between the time the live stream is encoded and
when it is pushed to the network. See page 17 for instructions. You will
also need to set buffering values as described on page 18.
This method passes the stream to the embedded Helix Server for delivery
to media clients. You can also use this method if you want Helix Server to
forward the stream to other types of servers or content distribution
networks. See page 21.
For any output type, set
Note:
Broadcaster to encode the output.
UDP with TS envelope
This output delivers the encoded output using a transport stream and User Datagram
Protocol as the network transport layer protocol.
UDP Output Screen
UDP with Low Latency TS
This output format is similar to the preceding except that it enables the encoder to buffer
less of the transport stream before delivering the output. This results in lower end-to-end
latency, enabling the target to receive the event stream faster than with standard latency.
Low-latency encoding is designed for use with capture input rather than
Note:
network input.
RTP with TS envelope
This output delivers the encoded output as a transport stream using Real-Time Transport
Protocol for data packaging. Choose this only if you know that the target supports the
standards-based RTP packet format.
Output Protocols (continued)
to in the top field to enable Helix
Enabled
Yes
CHAPTER 3: Outputs
(Table Page 2 of 2)
17