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 21:59:06 +0000 [thread overview]
Message-ID: <bug-102203-502-GV9I04bqSI@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102203-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1010 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102203
--- Comment #5 from Andy Furniss <adf.lists@gmail.com> ---
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.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1895 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
prev parent reply other threads:[~2017-08-17 21:59 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
2017-08-17 21:59 ` bugzilla-daemon [this message]
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-GV9I04bqSI@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