From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102203] Using hardware video encoding with amdgpu/vaapi crashes system immediately
Date: Thu, 17 Aug 2017 20:23:32 +0000 [thread overview]
Message-ID: <bug-102203-502-F80NQIoW4e@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102203-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2058 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102203
dwagner <jb5sgc1n.nya@20mm.eu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from dwagner <jb5sgc1n.nya@20mm.eu> ---
(In reply to Andy Furniss from comment #3)
> Does it help if you set the env
>
> VAAPI_DISABLE_INTERLACE=1
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".
> and modify the -vf to look like
>
> -vf 'scale=1920:1072,format=nv12|vaapi,hwupload'
Works for me as well as my original command line.
> 1072 is a strange height to use though it doesn't hurt my setup.
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.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3830 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-08-17 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-13 22:04 [Bug 102203] Using hardware video encoding with amdgpu/vaapi crashes system immediately bugzilla-daemon
2017-08-14 7:01 ` bugzilla-daemon
2017-08-14 15:38 ` bugzilla-daemon
2017-08-15 22:54 ` bugzilla-daemon
2017-08-17 20:23 ` bugzilla-daemon [this message]
2017-08-17 21:59 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-102203-502-F80NQIoW4e@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox