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 537609 - RTSP - rtspsrc module support for Scale header
RTSP - rtspsrc module support for Scale header
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
git master
Other Linux
: Normal enhancement
: 0.10.15
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-10 14:44 UTC by John Hurt
Modified: 2009-05-04 14:19 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Proposed patch (3.04 KB, patch)
2008-06-10 14:45 UTC, John Hurt
none Details | Review

Description John Hurt 2008-06-10 14:44:30 UTC
The rtspsrc module doesn't make use of the RTSP Scale header. Header and function is defined in the RTSP RFC 2326 section 12.34.

I propose the following patch to add a new "scale" property to the rtspsrc module in order to allow the use of the Scale header.
Comment 1 John Hurt 2008-06-10 14:45:50 UTC
Created attachment 112477 [details] [review]
Proposed patch
Comment 2 Wim Taymans 2008-06-11 09:04:39 UTC
I would not do it that way, GStreamer uses the seek events to control the playback speed of elements, not properties. I would like to see a patch where a property is added to rtspsrc to control the usage of Scale or Speed when performing a rate adjustment with a seek event.
Comment 3 Wim Taymans 2009-04-15 17:03:48 UTC
We have the SKIP seek flag now to trigger the scale header.
Comment 4 Wim Taymans 2009-05-04 14:19:32 UTC
commit 56656dd03d28f4882bb99c4abcb2035ff880f8c5
Author: Wim Taymans <wim.taymans@collabora.co.uk>
Date:   Mon May 4 16:16:54 2009 +0200

    rtspsrc: use SKIP flag to use SCALE headers
    
    We can use the SKIP seek flag to instruct the server to send data faster then
    normal but with the same bandwidth.
    Fixes #537609