From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99029] VCE VAAPI segfault using ffmpeg
Date: Tue, 09 May 2017 14:15:22 +0000 [thread overview]
Message-ID: <bug-99029-502-bGbMtP2yn3@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99029-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 854 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99029
Martin Bednar <martin@serafean.cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|13.0 |17.1
--- Comment #2 from Martin Bednar <martin@serafean.cz> ---
After fixing https://bugs.freedesktop.org/show_bug.cgi?id=100972 ,
ffmpeg -hwaccel vaapi -hwaccel_output_format vaapi -i Elephants_Dream_HD.avi
-vf format=yuv420p,hwupload -threads 2 -acodec copy -vaapi_device
/dev/dri/renderD128 -bf 0 -c:v h264_vaapi -c:v h264_vaapi -profile:v 77
~/test.mkv
seems to work (ffmpeg from git master).
Performance is atrocious though : I get about an encoding rate of about 2 FPS.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2241 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-05-09 14:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 14:37 [Bug 99029] VCE VAAPI segfault using ffmpeg bugzilla-daemon
2016-12-08 14:41 ` bugzilla-daemon
2016-12-08 14:54 ` bugzilla-daemon
2017-05-09 14:15 ` bugzilla-daemon [this message]
2017-05-09 15:40 ` bugzilla-daemon
2017-05-11 13:40 ` bugzilla-daemon
2017-05-11 14:03 ` bugzilla-daemon
2017-05-11 16:32 ` bugzilla-daemon
2019-09-18 19:22 ` 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-99029-502-bGbMtP2yn3@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