117
edits
Changes
→Create transport file
Available options:
*'''--url''' (mandatory, string): URL of HLS playlist (m3u8). Note - only "live" HLS manifests is supported, not "VOD" (with #EXT-X-ENDLIST tag at the end of m3u8 file).
*'''--title''' (mandatory, string): Title of the broadcast
*'''--output-public''' (mandatory, string): Path of resulting public transport file
When you create transport file without <tt>--hide-hls-manifest</tt> option then HLS manifest URL is placed inside transport file and thus available to all clients.
In this case you can distribute transport file event even without special support nodes.
When you specify <tt>--hide-hls-manifest</tt> option engine outputs two transport files:
HLS support node is started with the same options as regular support node.
You must pass URL to of the transport file with <tt>--url</tt> option.
If you have created transport file with <tt>--hide-hls-manifest</tt> option then you should pass private transport file to support node.
There are some special flags for HLS broadcasts:
*'''--hide-hls-segments''': don't send info about HLS segments (chunks) URLs over into P2Pnetwork. With this flag clients will never access original HLS server (neither manifest nor chunks).
*'''--hls-skip-metadata-broadcast''': send info about HLS segments URLs to directly connected peers only and prevent sending this info into P2P pool. Use this flag if you want to limit number of clients who has direct access to your original HLS server.
*'''--hls-skip-data''': don't download HLS segments (chunks) on the support node. If you set this flag then support node will handle only HLS manifest. Chunks should be downloaded from original HLS server.
Be careful: specifying both <tt>--hide-hls-segments</tt> and <tt>--hls-skip-data</tt> options at the same time makes no sense.
