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 534258 - basesink not accumulated time in some cases.
basesink not accumulated time in some cases.
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal normal
: 0.10.20
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-21 21:12 UTC by Sjoerd Simons
Modified: 2008-05-22 08:36 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
When nothing else is available use the last buffers start_time as the segment stop time (771 bytes, patch)
2008-05-21 21:13 UTC, Sjoerd Simons
committed Details | Review

Description Sjoerd Simons 2008-05-21 21:12:20 UTC
When a basesink is playing a stream that doesn't have a segment end and the buffers contain no duration then the segments last_stop doesn't get update. Causing no time to be accumulated when a new segment comes in. 

I've got a pipeline that's concatinating several mkv's and sending them out over rtp. When one isn't completely finished (for whatever reason). This go horribly wrong as all buffers after the broken mkv will be too late.
Comment 1 Sjoerd Simons 2008-05-21 21:13:51 UTC
Created attachment 111301 [details] [review]
When nothing else is available use the last buffers start_time as the segment stop time
Comment 2 Sebastian Dröge (slomo) 2008-05-22 08:36:05 UTC
2008-05-22  Sebastian Dröge  <slomo@circular-chaos.org>

        Patch by: Sjoerd Simons <sjoerd at luon dot net>

        * libs/gst/base/gstbasesink.c: (gst_base_sink_get_sync_times):
        If nothing else can be used, use the last buffer's start time as
        the segment's last stop. Fixes bug #534258.