#EXT-X-SERVER-CONTROL:CAN-BLOCK-RELOAD=YES,PART-HOLD-BACK=1.536 #EXT-X-MAP:URI="audio.fmp4?nimblesessionid=1" Here is an example of such chunk list (obtained via video.m3u8). The main playlist will have proper chunklists which will have a content according to LL-HLS spec. Now as the set up has been made, you can use the player to consume the stream using the usual playback URL. Once LL HLS is enabled, you need to re-start the input stream so Nimble Streamer could start producing LL HLS output stream. Nimble Live Transcoder allows setting it as well. Key frame interval can be set on your encoder side.For same chunk size and part duration of 2000, the valid key frame intervals will be 1, 2, 3, 6 seconds. for 6 seconds chunk and 1000ms part duration the valid key frame intervals would be 1, 2, 3 seconds. You may align key frame interval with chunk size.Even though Nimble is able to produce smaller parts, we just don't want our customers to deal with potential bottlenecks in other areas. Part size smaller than 500ms does not make any practical sense because of the overhead in delivery and processing chain.Use it only if you have a managed network and latency is crucial for your case. This duration gives very low playback buffer, severe bandwidth consumption and server resources' usage. The latency will be around 2 seconds in this case.
This duration gives better latency but less playback buffer and more bandwidth consumption as well as server resources' usage. The expected latency will be about 4-5 seconds in this case. The minimum recommended part duration of 1000ms.This duration provides optimal bandwidth and latency as well as good playback buffer. The expected latency will be about 6 seconds in this case. We recommend using part duration of 2000ms with chunk duration of 6 seconds.
0 kommentar(er)
