Operation Manual

-51-
the server as a receiver in a splitting arrangement. Please refer to Helix Server
documentation for details.
• Push, Multicast (Helix Server)
o In a multicast, Niagara Pro can deliver the same broadcast stream to any number of
Helix Servers without increasing its outgoing bandwidth. The Helix Servers will need
to be pre-configured for a multicast from Niagara Pro. Refer to your Helix Server
documentation for details.
• Pull (Helix Server)
o In pull broadcasting, Niagara Pro begins to generate broadcast packets as soon as you
start the encoding. However, it does not deliver the broadcast stream until Helix
Server requests the stream, which occurs when the first RealPlayer
®
user requests the
broadcast. In that way, Pull broadcasting saves bandwidth between Niagara Pro and
Helix Server when no one is viewing the broadcast. This broadcast method allows
you to send a stream to Helix Server version 9 or later.
• Legacy Push (8.x, 7.x, G2)
o The legacy push method is similar to the account-based push method. However, the
legacy push does not use a monitoring connection to provide server feedback and
statistics and is not as robust a broadcast method as an account-based push. Use this
broadcasting method only when sending a broadcast stream to a server that predates
Helix Server version 9, such as RealSystem
®
Server G2, 7, or 8.
Transport Protocol: When you use a push broadcast method, you specify whether to use UDP or
TCP upon delivering the broadcast stream to Helix Server. UDP is the preferred protocol due to the
lower network overhead. But you may want to use TCP when delivering the broadcast over a lossy
environment.
In the Stream Name field, enter a name for the broadcast stream. This name resembles a clip name
and should use the appropriate extension, either .rm for a constant bit rate stream or .rmvb for a
variable bit rate stream. This name appears in the broadcast URL.
For the Server Address field, enter the IP address or DNS name of the Helix Server used for the
broadcast, such as 207.188.7.176 or helixserver.example.com.
If using a Multicast Address, enter the multicast address for the broadcast stream in the Multicast
Address field. The Multicast Address must be in the range 224.0.0.0 to 239.255.255.255.
The Path (optional) field specifies a virtual path, which can be used for archiving or splitting on
Helix Server. Use a simple name followed by a forward slash, such as news/.
For the Port/Port Range field, specify the HTTP port on Helix Server. The default value is port 80,
which is the server's default HTTP port. If multicasting, indicate the range of ports on the Helix