[gstreamer-bugs] [Bug 338810] [matroskademux] blocks on segmenting seek (and other seek/segment glitches)

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=338810
 GStreamer | gst-plugins-good | Ver: 0.10.2


Tim-Philipp Müller changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #63732|accepted-commit_now         |committed
               Flag|                            |
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|HEAD                        |0.10.3




------- Comment #5 from Tim-Philipp Müller  2006-04-20 13:29 UTC -------
Committed the segment-seek related part of the patch:

 2006-04-20  Tim-Philipp Müller  <tim at centricular dot net>

        Patch by: Mark Nauwelaerts  <manauw at skynet dot be>

        * gst/matroska/matroska-demux.c:
        (gst_matroska_demux_handle_seek_event), (gst_matroska_demux_loop):
          Handle end of segment properly when set; don't dead-lock when
          posting start of segment message when doing a segment seek.
          Fixes #338810.


The key unit stuff should also be fixed in CVS now.


The issue I meant was indeed ffdec_* complaining about not receiving a keyframe
as first frame. What startled me was that I didn't seem to remember there being
such an issue before when we'd used entry->time for segment start
unconditionally.

Any improvements to GStreamer's matroska muxer would be very welcome of course,
so feel free to fix this :)

I've seen these issues with the sample videos from the matroska.org as well
though, and I'm fairly sure those haven't been produced by GStreamer.


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.