mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2024-12-25 01:30:38 +00:00
Code Issues 1 Projects Releases Wiki Activity

mpdparser: Fix unit test that assumed that fragment timestamps should include the period start timestamp

Browse source 
https://bugzilla.gnome.org/show_bug.cgi?id=754222
This commit is contained in:
Sebastian Dröge 2015-09-03 10:26:03 +03:00
parent 0d0455e346
commit d9c45e918f
1 changed files with 8 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
tests/check/elements/dash_mpd.c
View file

@ -4082,7 +4082,14 @@ GST_START_TEST (dash_mpdparser_segment_template)
* We expect it to not be limited to period duration. * We expect it to not be limited to period duration.
*/ */
expectedDuration = duration_to_ms (0, 0, 0, 0, 0, 12000, 0); expectedDuration = duration_to_ms (0, 0, 0, 0, 0, 12000, 0);
expectedTimestamp = duration_to_ms (0, 0, 0, 0, 0, 10, 0);
/* while the period starts at 10ms, the fragment timestamp is supposed to be
* 0ms. timestamps are starting from 0 at every period, and only the overall
* composition of periods should consider the period start timestamp. In
* dashdemux this is done by mapping the 0 fragment timestamp to a stream
* time equal to the period start time.
*/
expectedTimestamp = duration_to_ms (0, 0, 0, 0, 0, 0, 0);
ret = gst_mpd_client_get_next_fragment (mpdclient, 0, &fragment); ret = gst_mpd_client_get_next_fragment (mpdclient, 0, &fragment);
assert_equals_int (ret, TRUE); assert_equals_int (ret, TRUE);