GNOME Bugzilla – Bug 701191
rtsp-media: UTC ranges difficult to handle in element seeks
Last modified: 2014-02-25 22:28:30 UTC
Created attachment 245546 [details] [review] media: possibility to override range time conversion In gst_rtsp_media_seek, gst_rtsp_range_get_times is used for converting a GstRTSPTimeRange to GstClockTimes before seeking on the media pipeline. We have experienced problems with this for UTC ranges. For such ranges, gst_rtsp_range_get_times gives GstClockTimes that are nanoseconds since 1900. Such times are not meaningful in the element in the pipeline that handles our seeks. It is not clear to us how the seek function in the element could distinguish between such times and the times for other types of ranges, such as NPT. NPT ranges result in seeks between "normal" times such as 0:00:02.000000000 and 0:00:04.000000000. Our suggestion, in the attached patch, is to make it possible to override a method in GstRTSPMedia where the GstRTSPTimeRange is converted to GstClockTimes. In our GstRTSPMedia subclass, we would use knowledge about UTC times of the start and end of the media for computing useful GstClockTimes.
commit 7efa871c1f99b4a4e47a0d216bd76a09da89b731 Author: David Svensson Fors <davidsf@axis.com> Date: Wed May 29 13:45:00 2013 +0200 media: possibility to override range time conversion Make it possible to override the conversion from GstRTSPTimeRange to GstClockTimes, that is done before seeking on the media pipeline. Overriding can be useful for UTC ranges, where the default conversion gives nanoseconds since 1900. Fixes https://bugzilla.gnome.org/show_bug.cgi?id=701191