As changing them created choppy unreliable experiences
2- Are there other parameters to set in order to reduce the lag in DASH Live streams?
3- Am I understanding these properties right?
lag = mpegdashChunkDurationTarget * mpegdashMaxChunkCount
= 1000 ms * 5 = 5000ms = 5 seconds
3.1 - I should see a 5 second lag, instead of a 10 second lag, right?
I know we should take into account other possible lag sources that pile up, but how is it possible that, in the same conditions, if I switch to an RTSP to a flash video player the lag drops down to 3 seconds??
4 - Are MPEG DASH & HLS so much slower? (like 3 times at best?)
5 - what does mpegdashPlaylistChunkCount or cupertinoPlaylistChunkCount actually do?
Unfortunately with HTTP streams that are chunk based there is always going to be more latency than say with RTMP or RTSP. Having very small chunk duration targets is the way to go, but if you go too small then you may get choppy playback. Ensure that the keyframe is a factor of chunk duration target (which if set to 1 is obviously the case). The articles you linked to are really the best source for describing the various properties, and it really is a matter of experimenting with both the encoder and the chunk settings until you find a stable mix, but don't expect to get close to RTMP or RTSP latencies. This delay is not just at the Wowza level but also at the player level as the spec requires a minimum number of chunks before it begins the stream. The
HLS RFC is a good place to start if you wish to understand the internals of chunk based HTTP streaming delivery.