dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109538] VAAPI HEVC encoding is unstable and produces garbled output
Date: Sun, 03 Feb 2019 12:57:55 +0000	[thread overview]
Message-ID: <bug-109538-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1615 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=109538

            Bug ID: 109538
           Summary: VAAPI HEVC encoding is unstable and produces garbled
                    output
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: tempel.julian@gmail.com

Do

ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128
-hwaccel_output_format vaapi -i 1080p_h.264_60fps.mp4 -c:v hevc_vaapi -qp 22
-tier high -c:a copy output.mp4

Several times and browse the web with Firefox while doing so. Sooner or later
(rather sooner) the encoding will either hang or the driver crashes completely
and I need to perform a hard reset.
The encoding settings don't seem to matter as long -c:v hevc_vaapi is used.
-c:v h264_vaapi seems to be totally stable.

The encoding result of -c:v hevc_vaapi also shows a garbled line at the bottom
of the video, while -c:v h264_vaapi looks fine.

This is with a RX 580
mesa-git 19.1.0_devel.107212.ab940b0d972
linux 4.20.6 & drm-next-5.1-wip f9028b9278422fdf186f1b88662e28ed24e13df8
libva 2.4
ffmpeg-git b429c86d84cfc964c84bc68ec56799802de2b25a

There seems to be a difference between linux 4.20.6 & drm-next-5.1-wip though.
I couldn't make the stable kernel crash entirely, instead just the encoding
process started to hang.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2909 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

             reply	other threads:[~2019-02-03 12:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-03 12:57 bugzilla-daemon [this message]
2019-07-10 12:54 ` [Bug 109538] VAAPI HEVC encoding is unstable and produces garbled output bugzilla-daemon
2019-08-02 20:10 ` bugzilla-daemon
2019-11-19  9:12 ` 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-109538-502@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