[gstreamer-bugs] [Bug 544509] [qtdemux] Regression in segment.stop
GStreamer (bugzilla.gnome.org)
bugzilla-daemon at bugzilla.gnome.org
Sun Jul 27 05:17:30 PDT 2008
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=544509
GStreamer | gst-plugins-good | Ver: 0.10.9
Edward Hervey changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |FIXED
------- Comment #9 from Edward Hervey 2008-07-27 12:17 UTC -------
my bad, this isn't a bug in qtdemux. Just a bad assumption in the segment-seek
tests.
The assumption is that if I do an accurate segment seek for [start:A, stop:B],
the resulting newsegment would have [start:A, stop:B, position:A]... which is
wrong.
The only thing that can be assumed is:
* newsegment.position WILL be equal to seek.start
* the sum of all the newsegments duration will be equal to ABS(seek.stop -
seek.start). (if there's only one, then ABS(newsegment.stop - newsegment.start)
== ABS(seek.stop - seek.start))
I was adding to that the (not always correct) assumptions that:
* newsegment.start would be equal to seek.start
* newsegment.stop would be equal to seek.stop
The two assumptions are correct for most demuxer/decoders... but with
quicktime's EDL system... it can be wrong.
closing this bug again. Sorry for the noise, better be sure than regret it
later :)
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=544509.
More information about the Gstreamer-bugs
mailing list