[Bug 701191] New: rtsp-media: UTC ranges difficult to handle in element seeks
GStreamer (bugzilla.gnome.org)
bugzilla at gnome.org
Wed May 29 04:49:31 PDT 2013
https://bugzilla.gnome.org/show_bug.cgi?id=701191
GStreamer | gst-rtsp-server | git
Summary: rtsp-media: UTC ranges difficult to handle in element
seeks
Classification: Platform
Product: GStreamer
Version: git
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: gst-rtsp-server
AssignedTo: gstreamer-bugs at lists.freedesktop.org
ReportedBy: davidsf at axis.com
QAContact: gstreamer-bugs at lists.freedesktop.org
GNOME version: ---
Created an attachment (id=245546)
View: https://bugzilla.gnome.org/attachment.cgi?id=245546
Review: https://bugzilla.gnome.org/review?bug=701191&attachment=245546
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.
--
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the gstreamer-bugs
mailing list