[Bug 684790] isomp4/qtdemux: Whenever a moov atom is found, restart the demuxer

[GStreamer (GNOME Bugzilla)]

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

--- Comment #11 from Seungha Yang <sh.yang at lge.com> ---
(In reply to Thiago Sousa Santos from comment #9)
> Review of attachment 340289 [details] [review]:
> Besides DASH track_Id changes, what other cases would be covered here? What
> should we do with pull-mode?
I expect this will cover all push-mode fragmented format cases. And pull-mode
does not considered. Because ISOBMFF spec is saying that only one moov box is
allowed, does it makes sense that multi-moov on pull-mode?

> Should we also test that it works by sending sequentially 2 independent moov
> files? Just checking what should we add together with this to validate media
> tests.
In my opinion, any DASH mpd (multi-Representation, Bitrate switching cases)
with playbin3 can be a test case for this, because playbin3 reuses demuxer.

> This change looks simple enough that we could do it without GstStreams API
> (as it should work anyway) and do the porting on a separate patch to make
> reviewing and spotting regressions easier.
I'll split patch :)

> Reconfigure has a certain meaning in gstreamer related to the RECONFIGURE
> event, maybe we want something like "has_new_headers" or "has_new_moov"?
Because my intention for the boolean variable was to indicate "exposing new
srcpad or removing any oldpads is needed", but not "new moov", I will consider
new naming excluding "reconfigure"

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