From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110850] Vlc fails to decode video using vaapi
Date: Tue, 03 Sep 2019 13:25:30 +0000 [thread overview]
Message-ID: <bug-110850-502-B5PExnRsAF@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110850-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1152 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110850
--- Comment #1 from C. Leu <kle@bluewin.ch> ---
(In reply to Akarshan Biswas from comment #0)
I can confirm a similar issue. In my case, the problem occurs on older Radeon
hardware (HD 3650) which uses the r600 driver. The result is the same, no
hardware acceleration is possible through the integrated unified video decoder
(UVD). CPU has around 100% load.
It seems that the VA-API is broken, at least for certain systems.
Mesa version: 19.0.8
OS: Kubuntu 18.04.3 LTS with kernel 5.0.0-27
Kaffeine: 2.0.18
Error message:
libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
libva info: Found init function __vaDriverInit_1_1
libva info: va_openDriver() returns 0
[00007fabb0002bd0] glconv_vaapi_x11 gl error: vaDeriveImage: invalid
VAImageFormat
[00007fabbc1cbe10] main video output error: video output creation failed
[00007fabe8031800] main decoder error: failed to create video output
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1940 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-09-03 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 7:05 [Bug 110850] Vlc fails to decode video using vaapi bugzilla-daemon
2019-09-03 13:25 ` bugzilla-daemon [this message]
2019-09-25 18:50 ` 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-110850-502-B5PExnRsAF@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;
as well as URLs for NNTP newsgroup(s).