I’ve read everywhere trying to figure this out, so at this point, I thought I’d ask to see if anyone else has been down this road. I’m doing exclusively live adaptive bitrate streaming of sporting events and trying to get really clean dynamic switching throughout the quality levels. I’m using Wowza to transcode the incoming stream to 6 bitrates so extremely low latency is not really a concern, since the transcoder already creates a significant element of latency.
Here’s what I know from extensive reading, starting with Wowza (https://www.wowza.com/docs/how-to-configure-adobe-hds-packetization-sanjosestreaming)
-
Keyframe needs to be a factor of the chunk size (2/4, 3/9, etc) as a new chunk must start on a keyframe.
-
Apple (HLS) seems to recommend 9 second segments with 3 second keyframes. These take quite a while to switch over 6-8 quality levels in practice.
-
Adobe (HDS) can operate with smaller chunk sizes more efficiently according to all the comparisons/analysis I’ve read. This is one of the advantages of HDS for desktop Flash playback.
Adobe HDS: I’ve briefly tested using 4 second chunks with a 4 playlist chunk count and 10 chunk max. I used 2 second keyframes when encoding and transrating. It seems to work pretty well but this is an admittedly small sample of a test.
Has anyone had any experience with using HDS and manually lowering the sanjoseChunkDurationTarget (default is 10 seconds) and/or the PlaylistChunkCount and/or the sanjoseMaxChunkCount? Here are the properties in the Application.xml that you can change to for the LiveStreamPacketizer. Any help or experience would be greatly appreciated!
<Property>
<Name>sanjoseChunkDurationTarget</Name>
<Value>4000</Value>
<Type>Integer</Type>
</Property>
<Property>
<Name>sanjoseMaxChunkCount</Name>
<Value>10</Value>
<Type>Integer</Type>
</Property>
<Property>
<Name>sanjosePlaylistChunkCount</Name>
<Value>4</Value>
<Type>Integer</Type>
</Property>
<Property>
<Name>sanjoseRepeaterChunkCount</Name>
<Value>4</Value>
<Type>Integer</Type>
</Property>