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 700820 - tsdemux: doesn't seek because of 2 commits
tsdemux: doesn't seek because of 2 commits
Status: RESOLVED DUPLICATE of bug 698050
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
git master
Other Linux
: Normal normal
: git master
Assigned To: Josep Torra Valles
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-05-22 02:39 UTC by David Schleef
Modified: 2013-05-22 07:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description David Schleef 2013-05-22 02:39:57 UTC 
These two commits broke seeking for me:

commit 3d012665f06797cd2cd3c7c2f4df7144319b44ce
Author: Josep Torra <n770galaxy@gmail.com>
Date:   Tue Nov 13 22:40:25 2012 +0100

    tsdemux: forward upstream time segments after flushes
    
    Also reset segment info and drop the segment event when demuxer is
    flushed.
    Restore demuxer segment with the info stored in base when demuxer is
    going to push data again if needed.
    Drop code to recover the segment info from base in the initial program
    becauses it's superseded by the new code.

commit 150376efe476f4b9ea6c6cef54af1399cf6f478e
Author: Josep Torra <n770galaxy@gmail.com>
Date:   Sun Nov 11 12:45:03 2012 +0100

    mpegtspacketizer: flush observations too
    
    Flush the previous observations when the packetizer is flushed.
    Also don't leak them in the dispose.


I haven't tested if this is just on the one file I'm looking at.  I cannot make the file available.
Comment 1 Tim-Philipp Müller 2013-05-22 05:57:10 UTC 
there's already a (blocker) bug for that, with some more info.

But i think these commits should just be reverted for now.
Comment 2 Sebastian Dröge (slomo) 2013-05-22 07:31:00 UTC 
Yeah, that's bug #698050

And I agree that this should be reverted, or even better be fixed properly :)

*** This bug has been marked as a duplicate of bug 698050 ***