dashdemux: incorrect use of period start

The period start information, calculated in gst_mpd_client_setup_media_presentation
function is stored in stream_period->start. The information read from
xml file and stored in stream_period->period->start is not changed.

If the xml file does not contain the period start information,
stream_period->period->start will be -1.

The function gst_mpd_client_get_next_segment_availability_end_time wants to
use period start time, but incorrectly uses stream_period->period->start
(value from xml file, which could be -1) instead of stream_period->start
(computed value)

https://bugzilla.gnome.org/show_bug.cgi?id=751465
This commit is contained in:
Florin Apostol 2015-06-24 21:42:32 +01:00 committed by Sebastian Dröge
parent 87a4d523b9
commit 93f08347de

View file

@ -4506,7 +4506,7 @@ gst_mpd_client_get_next_segment_availability_end_time (GstMpdClient * client,
if (stream_period && stream_period->period) {
GstDateTime *t =
gst_mpd_client_add_time_difference (availability_start_time,
stream_period->period->start * 1000);
stream_period->start * 1000);
gst_date_time_unref (availability_start_time);
availability_start_time = t;
}