<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - VCE dual instance encoding inconsistent since st/va: enable dual instances encode by sync surface" href="https://bugs.freedesktop.org/show_bug.cgi?id=98005#c32">Comment # 32</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - VCE dual instance encoding inconsistent since st/va: enable dual instances encode by sync surface" href="https://bugs.freedesktop.org/show_bug.cgi?id=98005">bug 98005</a> from <a class="email" href="mailto:boyuan.zhang@amd.com" title="Boyuan Zhang <boyuan.zhang@amd.com>"> Boyuan Zhang</a> <pre>Hi Andy, To summarise your test results, basically you saw the following 3 issues with CQP, is it correct? - Issue #1. For large clip, sometime you can "invalid GstVaapiCodedBuffer size (0 bytes)" error. - Issue #2. Random corruption observed when using CQP. Corruption issue is gone after disable the statement "if (context->desc.h264enc.rate_ctrl.rate_ctrl_method !=PIPE_H264_ENC_RATE_CONTROL_METHOD_DISABLE" - Issue #3. Encoding speed is twice faster when setting QP<=28 So far I'm lucky enough that my test haven't trigger any of the issue yet. I will spend more time to try from my side. Again, if you could share the commands you were using to trigger the above 3 issue, that would be very appreciated. In the meantime, I would like to push the 2 patches to upstream first. Because this two patches don't change the behaviour of CQP, but only fixing VBR/CBR. Therefore, I believe CQP fix should be apart from these 2 patches. Regards, Boyuan</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>