<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Using hardware video encoding with amdgpu/vaapi crashes system immediately" href="https://bugs.freedesktop.org/show_bug.cgi?id=102203#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Using hardware video encoding with amdgpu/vaapi crashes system immediately" href="https://bugs.freedesktop.org/show_bug.cgi?id=102203">bug 102203</a> from <a class="email" href="mailto:adf.lists@gmail.com" title="Andy Furniss <adf.lists@gmail.com>"> Andy Furniss</a> <pre>VCE does seen to have suffered some regressions recently - I stopped testing it in March due to one in mesa that broke my normal testing. It's possible that gstreamer regressed and the mesa commit just exposed its deficiencies. Whatever the reason there are more issues now and I don't know what caused them or when they started due to ignoring VCE for so long. ffmpeg was OK last time I tried - but it clearly isn't for you. On the 4K speed - even when everything was working perfectly ffmpeg always was half the speed of gstreamer for me. I could in a very artificial test get 4K60p encode with gstreamer (pre-prepared raw nv12 video in ram). Getting that speed in other circumstances gets tricky as CPU bottlenecks get involved for things like making the nv12 from other formats to feed the encoder.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>