[Bug 780589] dashdemux: Don't try mpd update if minimumUpdatePeriod is not present

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=780589

--- Comment #14 from Seungha Yang <sh.yang at lge.com> ---
(In reply to Edward Hervey from comment #13)
> Here's a trick question: What do you do if minimumUpdatePeriod is present
> ... but it's set to 0s ?
This patch does not consider that condition. I'm planning to report now bug as
I mentioned in bug #783028 if you ok. Abstract my idea for this zero
minimumUpdatePeriod is,
- Disable periodic mpd update for zero minimumUpdatePeriod case.
- Update manifest only if the current manifest is expired
Note that, if inbandstream scheme (I'm working on bug#775803) is used, zero
minimumUpdatePeriod is recommended. This is another usecase of zero
minimumUpdatePeriod

> 
> My understanding is that:
> * it only implies that everything in the manifest is for everything
> available until "now"
That's my understanding. When I saw spec, it's still tricky for me, but DASHIF
implementation guide is saying that
4.4.2.3.Some Special Cases
"If the MPD @minimumUpdatePeriod is set to 0, then the MPD documents all
available  segments on the server."

> * Whenever we go beyond the last segment present in the manifest we need to
> request an updated manifest
Right. we should update at this moment or before.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.