[gstreamer-bugs] [Bug 482541] New: Broken RTP timestamps
GStreamer (bugzilla.gnome.org)
bugzilla-daemon at bugzilla.gnome.org
Tue Oct 2 04:35:17 PDT 2007
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=482541
GStreamer | gst-plugins-base | Ver: HEAD CVS
Summary: Broken RTP timestamps
Product: GStreamer
Version: HEAD CVS
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: gst-plugins-base
AssignedTo: gstreamer-bugs at lists.sourceforge.net
ReportedBy: spglegle at yahoo.fr
QAContact: gstreamer-bugs at lists.sourceforge.net
GNOME version: Unspecified
GNOME milestone: Unspecified
Hi,
In current gstbasertpdepayload.c there is the following comment ::
/* we pass rtptime as backward compatibility, in reality, the incomming
* buffer timestamp is always applied to the outgoing packet. */
The last function called is gst_base_rtp_depayload_push_full() and does not
use incoming rtp timestamp.
So the temporal reference seems to be the creation time of the incoming buffer
and not the RTP timestamp.
If some buffers come in in the same millisecond (for ex.), due to network
congestion, all the buffers will be created with a similar timestamp, rtp
timestamp information is lost, so the following pipeline outputs erroneous rtp
timestamps :
udpsrc ! rtpamrdepay ! rtpamrpay ! udpsink
Regards.
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=482541.
More information about the Gstreamer-bugs
mailing list