[Bug 776200] dashdemux: Always parsing sidx for On-Demand profile

[GStreamer (GNOME Bugzilla)]

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

--- Comment #13 from Seungha Yang <sh.yang at lge.com> ---
(In reply to Sebastian Dröge (slomo) from comment #12)
> I don't think I can share my stream unfortunately, but if you can provide a
> patch that works for your content with SegmentTemplate then I can test it on
> mine and fix up anything that is missing.
Then, can you provide only MPD to me? (or only some part of it to figure out
hierarchy of xml doc.) 

> Also I think there's nothing that forbids for example something like my
> case, but the SIDX actually contains information about the previous, next
> and following segment. Or about the next and all previous segments. This has
> to be all considered when parsing the SIDX to get a coherent view.

I'm a little bit confused by the terminology "Segment". Although I need to
study the spec more, It does not seem to make sense that a SIDX has any
information about outside of the "Segment" which SIDX belongs to. But it should
include only the "Subsegment" information which SIDX belongs to, IMHO. In this
context, your stream makes sense because each SIDX contains "Subsegment" index
of which the SIDX belongs to.

In summary, it's still questionable that whether accumulating or searching
prev/next "Segment" is necessary when parsing SIDX...

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