<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Corrupted videos VA-API HW encoding radeonsi" href="https://bugs.freedesktop.org/show_bug.cgi?id=98278#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Corrupted videos VA-API HW encoding radeonsi" href="https://bugs.freedesktop.org/show_bug.cgi?id=98278">bug 98278</a> from <a class="email" href="mailto:adf.lists@gmail.com" title="Andy Furniss <adf.lists@gmail.com>"> Andy Furniss</a> <pre>(In reply to Andy Furniss from <a href="show_bug.cgi?id=98278#c13">comment #13</a>) > While OMX may appear to work with cbr IME it doesn't work properly = you > don't end up getting the rate you asked for other than by luck. While testing with just one sample is probably not the best thing - I just revisited this and it does seem to work as long as bitrate isn't too high max 85M. Though I have vague memories of thinking it was OK before and then it went inconsistent. It could be because OMX does less/different setup of the h/w compared to vaapi WRT rate control/hrd stuff (I have see this by adding printfs) and when testing vaapi and omx some stated get carried over between the two.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>