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 667554 - [0.11] [h264] Reverse playback does not work anymore
[0.11] [h264] Reverse playback does not work anymore
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-libav
0.11.x
Other Linux
: Normal blocker
: 0.11.x
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks: 667560
 
 
Reported: 2012-01-09 13:55 UTC by Sebastian Dröge (slomo)
Modified: 2012-08-19 11:44 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastian Dröge (slomo) 2012-01-09 13:55:32 UTC
This sample file: http://samples.mplayerhq.hu/V-codecs/h264/cathedral-beta2-400extra-crop-avc.mp4
Comment 1 Tim-Philipp Müller 2012-08-19 11:44:30 UTC
This works fine now, probably fixed by:


commit 83870cf581128d94f6ae1a3062d6f59a36926a4a
Author: Tim-Philipp Müller <tim@centricular.net>
Date:   Fri Aug 10 22:58:56 2012 +0100

    baseparse: fix reverse playback with upstream demuxers that support it
    
    Don't just return FALSE for seek events with negative rates when
    operating in push mode. An upstream demuxer may support this just
    fine, so if we're not operating in pull mode always check upstream
    first if it can handle the seek event. This fixes reverse playback
    where the upstream demuxer supports it (e.g. with qtdemux). The
    same code would work fine in 0.10, because baseparse will just
    call the default pad event handler if FALSE was returned from the
    baseparse event handler, and the pad event handler will just
    forward it upstream. In 0.11 the baseclass or subclass is
    responsible for chaining up to the parent class or forwarding the
    event upstream in any case.
    
    Disable reverse playback in pull mode for now, there seems to
    be something going wrong with the segment configuration in that
    case.

possibly other commits elsewhere too.