[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 #31 from Seungha Yang <sh.yang at lge.com> ---
Hello slomo, Thiago and Edward

Could you review this patches after GST1.12 code freeze? 
(it's quite a big change...)

Main concept is "trying to make new stream per moov OR per stream-start"
and compare the new stream with that of previous moov, in order to decide
whether re-exposing is required or not.

There seems to no regression on playbin/playbin3 usecase with gst-validate
and manually run some multi-period DASH-IF streams.

Note that, in my environment, following TCs are failed only in playbin3
regardless of my patch
[4 / 270] validate.dash.playback.reverse_playback.dash_exMPD_BIP_TC1: Timeout
(Application timed out: 240.0 secs)
[8 / 270] validate.dash.playback.seek_with_stop.dash_exMPD_BIP_TC1: Timeout
(Application timed out: 240.0 secs)

However, although my patches are applied, stream change does not work in
playbin3 because a bug in decodebin3. It was reported in bug #772230 (nobody
review it yet) and the patch in bug #772230 could fix stream change issue in
playbin3.

I hope this could fix the bug #781270 also.

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