From 93f08347de7b725f568b74e972c7d4a59773bb6f Mon Sep 17 00:00:00 2001 From: Florin Apostol Date: Wed, 24 Jun 2015 21:42:32 +0100 Subject: [PATCH] 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 --- ext/dash/gstmpdparser.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ext/dash/gstmpdparser.c b/ext/dash/gstmpdparser.c index 003e1d5db7..6b94a9e9c6 100644 --- a/ext/dash/gstmpdparser.c +++ b/ext/dash/gstmpdparser.c @@ -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; }