CHROMIUM: s5p-mfc: Only set timestamp/timecode for new frames.
Timestamp i of a previously decoded buffer was overwritten for some
H.264 streams with timestamp i+1 of the next buffer. This happened when
encountering frame_type S5P_FIMV_DECODE_FRAME_SKIPPED, indicating no
new frame.
In most cases this wrong indexing might not have been noticed except
for a one frame delay in frame presentation. For H.264 streams though
that require reordering of frames for presentation, it caused a slightly
erratic presentation time lookup and consequently dropped frames in the
Pepper Flash plugin.
BUG=chromium:278621
TEST=Ran on Daisy with drmtest2, NBC and CNN Flash videos.
Signed-off-by: Ilja H. Friedel <ihf@google.com>
Change-Id: I921f164df04525e1c5669f2a2227fb047c69b172
Reviewed-on: https://chromium-review.googlesource.com/169898
Reviewed-by: John Sheu <sheu@chromium.org>
Reviewed-by: Ilja Friedel <ihf@chromium.org>
Commit-Queue: Ilja Friedel <ihf@chromium.org>
Tested-by: Ilja Friedel <ihf@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/170096
1 file changed
