Hi, this seems like the same issue in your other thread
I assume this is the guide you are referring to for HDS
This is the same principle as with HLS streaming, you modify sanjoseChunkDurationTarget, but it has to correspond to the key frame frequency of the stream. If you are able to encode to 1 second key frame frequency by making the key frame interval (or gop) the same as the FPS setting (e.g. FPS 24 and GOP 24) you will have 1 second key frame frequency; then if you set sanjoseChunkDurationTarget and cupertinoChunkDurationTarget to “1000” ms (1 second), the chunks will all be 1 second in duration with one key frame. This will improve playback start time and live stream latency.
When Wowza starts packetizing a live stream you will see the 1st 10 chunks being logged in the access log, and it that includes a/v/k (audio/video/key frames) and duration data for each chunk. It is ideal when eachc chunk is the same duration and has the same number of key frames.
So, to be clear, just setting these chunk targets is not enough, that setting should be a factor of key frame frequency.
Richard