GNOME Bugzilla – Bug 683169
mpeg4videoparse doesn't handle VOP_coded=0 properly
Last modified: 2013-02-14 10:12:48 UTC
Created attachment 223156 [details] [review] Patch. Check VOP_coded and set 0 duration when appropriate Some VOPs have VOP_coded set to 0, which means they have no data. Mpeg4Videoparser still gives such VOPs full duration, which results in broken timestamps.
Thanks, pushed: commit d3219a261a5a7b7340b63c80010009a73b032759 Author: Matej Knopp <matej.knopp@gmail.com> Date: Sat Sep 1 21:46:19 2012 +0200 mpeg4videoparse: set 0 duration when vop_coded is 0 https://bugzilla.gnome.org/show_bug.cgi?id=683169 Patch 369/369, eh? :)
Well, it turned out I was testing this on a broken file. vop_coded 0 means that the previous frame should be repeated, so it should have valid duration
Created attachment 235958 [details] [review] Revert the previous patch
Ideally you'd use "git revert" for this patch. Could you attach a new one with that?
commit 829076358eeed3d27b897ba76be1a0acc86b0095 Author: Tim-Philipp Müller <tim.muller@collabora.co.uk> Date: Thu Feb 14 09:40:08 2013 +0000 Revert "mpeg4videoparse: set 0 duration when vop_coded is 0" This reverts commit d3219a261a5a7b7340b63c80010009a73b032759. vop_coded 0 means that the previous frame should be repeated, so it should have valid duration after all. https://bugzilla.gnome.org/show_bug.cgi?id=683169