[Bug 762509] vaapidecoder: h264: decoder stores too many pictures in the DPB before output

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=762509

--- Comment #24 from Matt Staples <staples255 at gmail.com> ---
The decode order in attachment 349511 starts with POC values -72, -71, -76,
-75, -78, -77, -74, -73,...

With the original vaapi code, the first few frames (or rather field pairs) are
held by the DPB and then sent out in proper numerical order starting with field
pair (-77,-78).

My change causes the first complete field pair (-71,-72) to go out as soon as
it's fully decoded, so when it subsequently completes decoding field pair (-76,
-75), it's too late to send that out in order.

The libav decoder appears to handle that problem by simply dropping any frames
that can't be sent out in order.  I'd like to amend my patch to do the same
thing, however, I'm not sure that's a spec-compliant implementation.  Does the
libav decoder pass compliance tests?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.