Please correct my understanding if any problem.
One chunk represents n * (data of one keyframe + data in key frame interval). The dvrChunkDurationMinimum property decides chunk minimum duration so it decides the n. Fixed duration does not mean fixed size because each (data of one keyframe + data in key frame interval) size is possible varying. Therefore the chunk size is varying in fixed dvrChunkDurationMinimum property.
If there is a stream named myStream it was disconnected and then restarted, and it continues to send upstream to Wowza, it is a live stream.
so myStream includes at least 2 stores right now, first is in [install-dir]/dvr/[applicationname]/myStream.0 , this is a 'recorded DVR store' , the second named myStream.1 and it is a 'live DVR store' if the live point is written into the myStream.1
If HLS player wants to play from the live point, uses
and it delays 3 chunks
If player wants to play a specific duration that crosses myStream.0 and myStream.1 , that also can be achieved by using dvrPlaylistRequestDelegate like
. What Wowza needs is to add dvrPlaylistRequestDelegate properties to Application/DVR/Properties
and it's optional to customize the getDvrPlaylistRequest methods
If there is a stream named myStream2 it was disconnected, restarted and then disconnected again, it is a recorded stream.
In this case both the myStream2.0 and myStream2.1 are recorded DVR stores