<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:jb5sgc1n.nya@20mm.eu" title="dwagner <jb5sgc1n.nya@20mm.eu>"> <span class="fn">dwagner</span></a>
</span> changed
<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>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>FIXED
</td>
</tr></table>
<p>
<div>
<b><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#c4">Comment # 4</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 <span class="vcard"><a class="email" href="mailto:jb5sgc1n.nya@20mm.eu" title="dwagner <jb5sgc1n.nya@20mm.eu>"> <span class="fn">dwagner</span></a>
</span></b>
<pre>(In reply to Andy Furniss from <a href="show_bug.cgi?id=102203#c3">comment #3</a>)
<span class="quote">> Does it help if you set the env
>
> VAAPI_DISABLE_INTERLACE=1</span >
Yes! I wonder how "interlace" is still a thing so many years after CRTs became
obsolete, and no interlaced videos were ever involved in my attempts, but
whatever this variable does, it changed the hardware encoding experience for me
from "crashes all the time" to "does not crash and even produces a proper video
in about 50% of invocations".
Weirdly, about half of the times I start the very same ffmpeg command line for
the very same input file, the output video shows mixed up positions of frames,
as in "not frames 1-2-3-4-5-6 but e.g. 1-4-2-3-5-6 shown in sequence".
<span class="quote">> and modify the -vf to look like
>
> -vf 'scale=1920:1072,format=nv12|vaapi,hwupload'</span >
Works for me as well as my original command line.
<span class="quote">> 1072 is a strange height to use though it doesn't hurt my setup.</span >
At one point in time, I got error messages from ffmpeg that the encoder was
incompatible with sizes that are not even multiples of 16 - that's why I
introduced this scaling just for testing. But this scaling is not relevant
anymore, works the same now with or without it.
I think we can close this bug report: While the
distorted-frame-sequence-half-the-times symptom is unpleasant, it's quite
different from "crashing all the time".
And now that I experienced that h.264 hardware encoding on an RX 460 (in 4k)
does not even reach realtime speed, it seems to me that I should probably stick
to "x264 -preset ultrafast" for live streaming anyway.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>