After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 761583 - Getting gst_element_query_position to return NTP time
Getting gst_element_query_position to return NTP time
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
1.6.3
Other Linux
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-02-05 09:28 UTC by Sergio Torres Soldado (zenx)
Modified: 2018-05-06 12:18 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Example (5.22 KB, text/x-c++src)
2016-02-19 15:53 UTC, Sergio Torres Soldado (zenx) 		Details

Description Sergio Torres Soldado (zenx) 2016-02-05 09:28:19 UTC 
As discussed here http://lists.freedesktop.org/archives/gstreamer-devel/2016-February/056516.html

The idea it to support play time synchronization with the NTP timestamps from the RTCP SR packets.
Comment 1 Sebastian Dröge (slomo) 2016-02-16 07:45:46 UTC 
You want to do synchronization based on the NTP timestamps of the RTCP SRs? (That is already implemented and works well).

Or report the NTP time as the stream time, e.g. from gst_element_query_position() as the title of this bug suggests?


Any progress on this already?
Comment 2 Sergio Torres Soldado (zenx) 2016-02-19 09:37:53 UTC 
The latter. 

I have made some progress yes, I am firing an event from rtpbin when the rtcp packet is received. On the rtpjitterbuffer I will probably need to add a property to choose between responding with the PTS or the stream time to a position query.
Comment 3 Sergio Torres Soldado (zenx) 2016-02-19 15:53:34 UTC 
Created attachment 321668 [details]
Example

Usage example of previous patch
Comment 4 Sebastian Dröge (slomo) 2018-05-06 12:18:11 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!