GNOME Bugzilla – Bug 746038
dashdemux: fetch wrong segment at the end of Period
Last modified: 2015-03-15 12:23:35 UTC
For MPD file like this: <Period duration="PT5M0S" start="PT0.00S"> ... <SegmentTemplate startNumber="0" duration="3000" timescale="1000" ... /> ... Currently(1.4.5), segemnt-100 will be fetched, but it's not specification complied. According to specification, segemnt-[0-99] are valid segments. Yet for segemnt-100, it's out of range and invalid, and it should not be requested by dashdemux.
Created attachment 299105 [details] [review] a candidate patch a candidate patch is attached. Under this scenario, gst_mpdparser_get_chunk_by_index will return false to indicate EOS, rather than continue to download a out-of-range invalid segment
commit 5a1ed14c3c56e24d1dbe716b41dc089d9cf19ea7 Author: xixi <xixi10111011@gmail.com> Date: Wed Mar 11 23:03:24 2015 +0800 dashdemux: fetch wrong segment at the end of Period Fix check for end of Period time to avoid trying to fetch a segment that doesn't exist https://bugzilla.gnome.org/show_bug.cgi?id=746038 Merged to 1.4 commit 18da30a929401e5c7478297445b50907b2940b54 Author: xixi <xixi10111011@gmail.com> Date: Wed Mar 11 23:03:24 2015 +0800 dashdemux: fetch wrong segment at the end of Period Fix check for end of Period time to avoid trying to fetch a segment that doesn't exist https://bugzilla.gnome.org/show_bug.cgi?id=746038