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 658305 - [souphttpsrc] can’t seek during double speed playback
[souphttpsrc] can’t seek during double speed playback
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
0.10.36
Other Linux
: Normal normal
: 0.10.31
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-09-06 00:17 UTC by Davy
Modified: 2011-09-06 08:36 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Davy 2011-09-06 00:17:41 UTC
Problem: it’s not possible to seek file position during 2X speed playback.
Related function: gst_soup_http_src_do_seek(…)

Actually, this problem is caused by below routine,
if (segment->rate != 1.0 || segment->format != GST_FORMAT_BYTES) {
+    GST_WARNING_OBJECT (src, "Invalid seek segment");
     return FALSE;
+  }
As you can see, the do_seek is allowed only when “rate” is 1.0.

I’ve reviewed both commit log and bug report but I don’t know why you prohibit the seek condition in double speed playback.
Commit log: http://cgit.freedesktop.org/gstreamer/gst-plugins-good/commit/ext/soup?id=6a9372529222300c7b6eacfcf8b9a844b96021c9
Related bug: https://bugzilla.gnome.org/show_bug.cgi?id=632977

So I’d like to know, what happened will be occurred, if I removed the condition regarding playback speed.

BR,
Davy
Comment 1 Sebastian Dröge (slomo) 2011-09-06 08:36:23 UTC
commit 7b592ff1265210cf3d74e2181664d269df7064e0
Author: Sebastian Dröge <sebastian.droege@collabora.co.uk>
Date:   Tue Sep 6 10:33:21 2011 +0200

    souphttpsrc: Allow positive, non-1.0 segment rates
    
    Only negative rates are not supported. Fixes bug #658305.