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 676242 - [metabug] Verify that elements handle seqnum for seeks correctly
[metabug] Verify that elements handle seqnum for seeks correctly
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.10.x
Other All
: Normal normal
: 1.1.3
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-05-17 14:13 UTC by Thiago Sousa Santos
Modified: 2013-07-25 18:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
matroskademux: properly handle seqnums of events related to a seek (9.97 KB, patch)
2012-05-18 19:02 UTC, Thiago Sousa Santos
needs-work Details | Review

Description Thiago Sousa Santos 2012-05-17 14:13:21 UTC
Verify that elements involved in seek handling properly set seqnum to the events that they push when performing a seek (flushes and newsegments).
Comment 1 Thiago Sousa Santos 2012-05-18 19:02:40 UTC
Created attachment 214395 [details] [review]
matroskademux: properly handle seqnums of events related to a seek

Events that are consequence of a seek event should have the
same seqnum as the seek event.

This patch fixes the seqnum handling for seeks for matroska demux, I have
similar patches for qtdemux, asfdemux, avidemux and I'm still fixing others, the
idea of the patch is the same for all of them: store the seqnum of the seek
event and set flushes and newsegments to use the same seqnum. In push mode,
keep the converted event that goes upstream with the same seqnum of the
received seek.

If this patch is ok, the others should be, too. So I'll push all them
together.
Comment 2 Sebastian Dröge (slomo) 2013-07-24 08:58:25 UTC
Comment on attachment 214395 [details] [review]
matroskademux: properly handle seqnums of events related to a seek

Please rebase against latest git master. Also *all* events and messages following a seek should have the seek sequence number. (And remove the "newsegment" notion there, no newsegment event in 1.0 :) )
Comment 3 Thiago Sousa Santos 2013-07-25 18:28:57 UTC
commit aa5ea6d80e21a3876d81878c0837a28f8842252c
Author: Thiago Santos <thiago.sousa.santos@collabora.com>
Date:   Thu Jul 25 12:20:14 2013 -0300

    baseparse: fix seqnum handling for seeks


commit 7eac4c7c030568b99540082f52ec4cf2f35f003d
Author: Thiago Santos <thiago.sousa.santos@collabora.com>
Date:   Thu Jul 25 11:13:01 2013 -0300

    avidemux: fix seqnum handling for seeks
    
commit 8bd12e12b38eab3496955265e38c031db39d262a
Author: Thiago Santos <thiago.sousa.santos@collabora.com>
Date:   Thu Jul 25 01:39:58 2013 -0300

    matroskademux: fix seqnum handling for seeks
    

commit e49b6e7c353dbe366add0e19c20692cff6343b38
Author: Thiago Santos <thiago.sousa.santos@collabora.com>
Date:   Thu Jul 25 01:11:31 2013 -0300

    qtdemux: correctly handle seqnum for seeks and segments
    

commit c2eb7118beb6d2eb456f275ef7b597855c721e1b
Author: Thiago Santos <thiago.sousa.santos@collabora.com>
Date:   Thu Jul 25 11:28:54 2013 -0300

    asfdemux: fix seqnum handling for seeks


oggdemux was already ok.