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 750437 - [RFC]:fix the invalid base time on newsegment after seek with gapless playing
[RFC]:fix the invalid base time on newsegment after seek with gapless playing
Status: RESOLVED DUPLICATE of bug 750013
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
1.4.5
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-06-05 06:20 UTC by matsumura
Modified: 2015-06-08 00:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
the patch to fix the invalid base time (557 bytes, patch)
2015-06-05 06:20 UTC, matsumura
none Details | Review

Description matsumura 2015-06-05 06:20:45 UTC
Created attachment 304630 [details] [review]
the patch to fix the invalid base time

I try to fix the following bug myself.
https://bugzilla.gnome.org/show_bug.cgi?id=750013

When I applied this patch, the playback didn't halt. 

Please refer and comment to this patch and the bug.
Comment 1 Sebastian Dröge (slomo) 2015-06-05 07:46:28 UTC
Can you check with latest GIT master? The code in question changed because of similar sounding bugs, and this is most likely fixed already.

Alternatively, do you have a testcase to reproduce this reliably?
Comment 2 Sebastian Dröge (slomo) 2015-06-05 07:48:22 UTC
And is this exactly about bug #750013, or is this a separate problem?
Comment 3 matsumura 2015-06-05 09:12:36 UTC
Thanks for your reply.

I have tried the latest GIT master of gst-plugins-base.
But the problem reproduced.

The problem is same as bug #750013.
Comment 4 Tim-Philipp Müller 2015-06-05 09:19:02 UTC
Let's keep the discussion in the existing bug then please. Could you attach your patch there instead? Thanks!

*** This bug has been marked as a duplicate of bug 750013 ***
Comment 5 matsumura 2015-06-08 00:35:26 UTC
Certainly.
I also attached this patch to bug 750013.

Continuously, I'll discuss by 750013.