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 512774 - [rtpjitterbuffer] does not accept clock rate from caps
[rtpjitterbuffer] does not accept clock rate from caps
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
git master
Other Linux
: Normal normal
: 0.10.6
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-29 11:40 UTC by Thijs Vermeir
Modified: 2008-01-29 18:57 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
get clock-rate from buffer (733 bytes, patch)
2008-01-29 11:41 UTC, Thijs Vermeir 		committed Details | Review

Description Thijs Vermeir 2008-01-29 11:40:17 UTC 
When the clock-rate is only provided by the caps of the buffers and not via the emit signal rtpjitterbuffer dump's all packets with:
"No clock-rate in caps!"

This is caused by changing the payload type of the packets ( or just the first payload type). Then the clock-rate read from the caps is reset to -1 and only tried to reset with the emit signal.
Comment 1 Thijs Vermeir 2008-01-29 11:41:07 UTC 
Created attachment 103952 [details] [review]
get clock-rate from buffer

recheck the caps of the buffer for the clock-rate.
Comment 2 Wim Taymans 2008-01-29 18:57:31 UTC 
        Patch by: Thijs Vermeir  <thijsvermeir at gmail dot com>

        * gst/rtpmanager/gstrtpjitterbuffer.c:
        (gst_rtp_jitter_buffer_chain):
        Try to get the new clock-rate from the buffer caps when we receive a new
        payload type instead of always firing the signal. Fixes #512774.