Confidential
Page 11
Give the output a friendly name. Keep in mind that this name will be used as the description if/when
you generate an m3u playlist. Next select UDP vs. RTP. UDP is raw UDP. The RTP protocol, which is also
transmitted using UDP, is more robust because the packets are numbered. Additional robustness can be
added using SMPTE2022 FEC, but this is only beneficial if the receiving device can utilize the FEC data.
The IP addresses and port fields are self-explanatory. Multicast addresses are supported. Specify the
interface you wish to bind this output to (N1, N2, N3 or N4). If you aren’t sure of the routing, check the
“System>Settings” page of this WebUI. The Data Rate used must be sufficient to contain the multiplex
transport that is being assigned to this output. If insufficient, clipping will occur and an error will be
shown on the Overview page. Nul stripping reduces the network traffic and is recommended for non
CBR applications. MPEG transport streams require signaling that is compatible with the transport and
targeting receiving devices. For example, if the IP output is feeding an edge QAM modulator for the US
market, select US Cable for signaling.
A playlist.m3u file that describes all of the multicast outputs can be downloaded
by clicking on the playlist icon. For IPTV networks, session announcement
protocol (SAP
RFC 2974
) is supported and included in the stream when enabled.
ASI
ASI inputs are automatically detected and populated if available. These entries may be edited to change
the name or enable/disable as necessary.
Modulated RF Output
The modulator hardware is automatically detected and a list of available modulators is shown on the
Output page of the WebUI. All modulators are expected to transmit over the same cable network, as
such it is not necessary to identify how a modulator maps to a particular F connector.
