Too much drift in the duration of the Segments

[atseptember1]

Hi! I'm am currently using the DASH simulator (with my own VOD content) for testing purposes, however, am unable to generate the config file with the VOD analyzer tools.

The failure occurs when the VOD analyzer begins to analyze video content through the video segmenter when meeting the content limitation (as explained here: https://github.com/Dash-Industry-Forum/dash-live-source-simulator/wiki/Content-Limitations).
Does anyone have the same issue? Please let me know and thanks in advance for any advice/solutions!

[komar007]

I had the same (or similar) issue when using dash-live-source-simulator.
It is common for the final chunks of the VoD content to be shorter than all the others and I think dash-live-source-simulator does not handle this. In fact there might be no good way of handling it if you want to loop VoD content by looping just the chunk numbers, as you would have an occasional shorter chunk every time there is a rollback, which I don't even know whether it's ok by the spec.

I think your best bet is to make sure that the duration of the content you are working with is a multiple of your chunk duration. BTW trying to set a lower value of nr_segments_in_loop might not be a good idea, because in some codecs audio chunk boundaries will not be perfectly in sync with video chunk boundaries which can generate undesired effects each time the content loops.

I ended up removing the check from the source code completely, see around line 226 of dashlivesim/vodanalyzer/dashanalyer.py.