live sample, start issue

[nicosang]

with sample http://vm2.dashif.org/livesim-dev/segtimeline_1/testpic_2s/Manifest.mpd, streaming doesn't start.
There are always problems when the user wants to seek. :-(

[LloydW93]

Related to #1729

[nicosang]

seek problem occurs when a refresh manifest is done just after the first seek command. In this kind of sample, minimumUpdatePeriod = 'PT0S', so the refresh is done each second. When a seek command occurs, the requested time is defined for video type for instance (DVR metric information is used, in the webApp to define the time to seek). Manifest informations are updated, calcSegmentAvailabiltyRange is also updated, consequently the DVR information. Then, the requested time for audio is defined in the webApp : this new time is of course different from requested video time. Finally, the playback does not restart.
In my opinion, it could be interesting to stop refreshing manifest between the first seek command and the seeked event. Is it correct according to dash specifications?

[dsparacio]

We are putting out a 2.4.1 point release. This seems like something that should be a part of that.

[dsparacio]

I assume we are still not supporting minimumUpdatePeriod = 'PT0S', properly. Instead of every second it should become chained with each fragment request. So instead of timer based update, we need ondemand update followed by a single chunk download, rinse and repeat.

[davemevans]

This is no longer needed after #1758, right?

[nicosang]

For me, the issue is still there.

[nicosang]

@bbcrddave , Yes, you're right this PR is no longer needed. it has been done with #1758 . However, the problem of seeking on this sample is still there. One reason of this issue was the manifest update call too often.