GNOME Bugzilla – Bug 619064
h264parse: broken timestamps after seeking
Last modified: 2010-06-29 12:13:10 UTC
Created attachment 161414 [details] [review] fix In some cases h264parse produces wrong timestamps after seeks. It's due to this check in gsth264parse.c, around line 1182: if (h264parse->last_outbuf_dts != GST_CLOCK_TIME_NONE && outbuf_dts != GST_CLOCK_TIME_NONE && outbuf_dts <= h264parse->last_outbuf_dts) outbuf_dts = GST_CLOCK_TIME_NONE; h264parse->last_outbuf_dts is set to GST_CLOCK_TIME_NONE in _init and it's not being reset during a flush.
Comment on attachment 161414 [details] [review] fix (PS: I think the description and summary line in the commit message should be swapped)
commit 2441c79afa426848f2896434249dd38646cceff7 Author: Alessandro Decina <alessandro.d@gmail.com> Date: Tue May 18 21:32:22 2010 +0200 h264parse: fix wrong timestamps in some cases after seeking. Reset ->last_outbuf_dts on flush-stop. Fixes #619064.
can you tell me which release will include thus fix? thanks in advance.
The next release, obviously, which is 0.10.19.
just because according to http://gstreamer.freedesktop.org/wiki/ReleasePlanning2010 bad is frozen since may 7. or is it outdated? i'd like to be see this fix in 10.19:-)
*** Bug 619294 has been marked as a duplicate of this bug. ***
*** Bug 621973 has been marked as a duplicate of this bug. ***