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 610296 - [qtdemux] Confusion with gst/qt segments
[qtdemux] Confusion with gst/qt segments
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
git master
Other All
: Normal normal
: 0.10.19
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-02-17 19:18 UTC by Thiago Sousa Santos
Modified: 2010-02-18 11:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
qtdemux: Use the correct duration when comparing segments (1.10 KB, patch)
2010-02-17 19:28 UTC, Thiago Sousa Santos
accepted-commit_now Details | Review
qtdemux: Use the correct duration when comparing segments (1.27 KB, patch)
2010-02-17 21:38 UTC, Thiago Sousa Santos
none Details | Review
qtdemux: Use the correct duration when comparing segments (1.28 KB, patch)
2010-02-18 10:55 UTC, Thiago Sousa Santos
committed Details | Review

Description Thiago Sousa Santos 2010-02-17 19:18:06 UTC
Due to qtdemux having to handle gst and edts segments, a mistake was introduced in 8ca984d5

The problem is that (on segment activation) the edts entry duration is used instead of the total gst segment duration.

Patches follow.
Comment 1 Thiago Sousa Santos 2010-02-17 19:28:53 UTC
Created attachment 154067 [details] [review]
qtdemux: Use the correct duration when comparing segments

Do not confuse QtDemuxSegments with GstSegments when
comparing the total file duration with the segment duration

Fixes #610296
Comment 2 Mark Nauwelaerts 2010-02-17 20:09:26 UTC
Should the debug (warning) message not be adjusted as well ?

I am not sure whether comparing a QtDemuxSegment.time to a GstSegment.stop works ok, since they are on a different timeline (global time versus media/track time).  IIRC, I originally intended to compare the total file duration (in a GstSegment.duration) to a QtDemuxSegment.time (which are both in the same global timeline).
Comment 3 Thiago Sousa Santos 2010-02-17 21:38:22 UTC
Created attachment 154083 [details] [review]
qtdemux: Use the correct duration when comparing segments

Updated patch with Mark's comments
Comment 4 Mark Nauwelaerts 2010-02-18 10:08:43 UTC
What is the reason for qtdemux->segment.stop != -1 in there
(or perhaps still a leftover from a previous version,
might have to be qtdemux->segment.duration) ?
Comment 5 Thiago Sousa Santos 2010-02-18 10:55:15 UTC
Created attachment 154120 [details] [review]
qtdemux: Use the correct duration when comparing segments

Yes, that was a left over, this version has it fixed.
Comment 6 Mark Nauwelaerts 2010-02-18 11:08:28 UTC
OK [FWIW] :)
Comment 7 Thiago Sousa Santos 2010-02-18 11:12:26 UTC
Module: gst-plugins-good
Branch: master
Commit: f1c61e1d84ee83336bfb59aa9ec8a49afbd92539
URL:    http://cgit.freedesktop.org/gstreamer/gst-plugins-good/commit/?id=f1c61e1d84ee83336bfb59aa9ec8a49afbd92539

Author: Thiago Santos <thiago.sousa.santos@collabora.co.uk>
Date:   Wed Feb 17 16:27:33 2010 -0300

qtdemux: Use the correct duration when comparing segments

Do not confuse QtDemuxSegments with GstSegments when
comparing the total file duration with the segment duration

Fixes #610296