Output tab–hls – Cobalt Co9992-4ENC-4K-HEVC Software-Defined Broadcast Encoder User Manual
Page 60

60
Services Code Point). Note that setting this field will have no effect on the traffic QoS
unless the routers in the path are configured to honor the value.
Output Tab–HLS
In HLS mode, the encoder creates HLS segments and manifest files, and posts them to a server.
The server can be a local web server in the encoder itself, or it can be a remote server. If the
server is remote, multiple protocols can be used to transfer the segments and manifest files.
HLS Common Parameters
The picture below shows the HLS parameters that are common to all modes:
Server Location:
selecting
Remote
configures the encoder to upload the segment and
manifest files to a remote server. Selecting
Local
configures the encoder to place the
segments in its local web server, where they are directly-accessible to clients.
Segment (sec):
Number of seconds per segment. This defines the approximate size (in
seconds) for the above bitstream encoded files. The valid range is from 1 to 20 seconds.
Note that the clients will experience latency approximately equal to the segment size
times the number of segments.
Number of Segments:
This defines the number of bitstream segments advertised in the
playlist. The minimum number, as per the HLS specification, is 3. Some set-top boxes
require 4 segments. Apple devices (iPads, iPods, etc.) work well with 3 segments.
Program Name:
this is the program name that goes in the manifest. Most HLS clients
ignore this information.
HLS Local Server
No additional configuration options are required for HLS Local Server. The URL to access the
content is:
http://
encoder_ip_address
/HLS/encoder
X
.m3u8
Where
encoder_ip_address
is the IP address of either one of the Ethernet ports, and
X
is the
encoder channel number (1 to 4). For example, if the encoder is at 10.10.9.10, and Encoder 1 is
configured for HLS, the URL will be:
http://10.10.9.10/HLS/encoder1.m3u8