<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - [gst-vaapi] H264 video playback regression between 5fe72d9 and 0.5.5" href="https://bugs.freedesktop.org/show_bug.cgi?id=67190#c17">Comment # 17</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - [gst-vaapi] H264 video playback regression between 5fe72d9 and 0.5.5" href="https://bugs.freedesktop.org/show_bug.cgi?id=67190">bug 67190</a> from <a class="email" href="mailto:gb.devel@gmail.com" title="Gwenole Beauchesne <gb.devel@gmail.com>"> Gwenole Beauchesne</a> <pre>Hi, I pushed something to the git master branch. It works, though I am not fully satisfied yet. Rationale: - If VPP is not supported, or not available (libva >= 1.2.0, libva-intel-driver >= 1.2.0), then we fallback to displaying the raw surface. This will be wrong in most cases where video cropping or deinterlacing was needed. At least, we now display something and no longer exit. - If VPP is supported, then an intermediate surface is used to receive the outcome of video processing. Currently, the target surface format is arbitrarily set to YUV 4:2:0 (most probably NV12, under the hoods). A future optimization is to use another format that would be more suitable to the compositor, e.g. packed YUV 4:2:2 (YUY2). Though, we need to determine a proper threshold/balance between extra memory bandwidth (YUV 4:2:2 requires more bytes), or extra GPU/EU processing power (shaders are used for YUV 4:2:0, but direct sampling from YUV 4:2:2 is possible on most hardware).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>