<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Broken VP9 video playback colors on AMD Ryzen 5 (PRO) Mobile 2500U in Chromium"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109080#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Broken VP9 video playback colors on AMD Ryzen 5 (PRO) Mobile 2500U in Chromium"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109080">bug 109080</a>
from <span class="vcard"><a class="email" href="mailto:zajec5@gmail.com" title="Rafał Miłecki <zajec5@gmail.com>"> <span class="fn">Rafał Miłecki</span></a>
</span></b>
<pre>Hey Boyuan,
thanks for looking at this issue! I agree it's quite confusing, but I finally
found out what's going on.
*****
Let me provide a new summary of Mesa releases & this problem:
1) Accelerated VP9 decoding in Chromium is broken with 18.1 & 18.2.
2) Video Acceleration DOESN'T WORK in Chromium with 18.3.0 - 18.3.3
3) Accelerated VP9 decoding in Chromium is broken with 18.3.4 & 19.0.
By "broken" I mean corrupted colors.
*****
Earlier confusion was due to the commit 55e7de7b1935 ("radeonsi: enable vcn
jpeg decode for raven") EXPOSING a <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - gallium/st/va: change va max_profiles when using Radeon VCN Hardware"
href="show_bug.cgi?id=109107">bug 109107</a> which was related to reporting
profiles. That commit STOPPED Chromium from using Video Acceleration and made
it report following errors:
[21202:21202:0317/122002.223002:ERROR:vaapi_wrapper.cc(587)] :
vaQueryConfigProfiles returned: 14
[21202:21202:0317/122002.223045:ERROR:vaapi_wrapper.cc(587)] :
vaQueryConfigProfiles returned: 14
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - gallium/st/va: change va max_profiles when using Radeon VCN Hardware"
href="show_bug.cgi?id=109107">Bug 109107</a> got fixed with the commit 21cdb828a3f4 ("st/va: fix the incorrect
max profiles report") and since then:
1) Chromium uses Video Acceleration again
2) I see corrupted VP9 YouTube colors again
So the commit 55e7de7b1935 ("radeonsi: enable vcn jpeg decode for raven")
DIDN'T FIX anything but has only hidden the original problem. It stopped
Chromium from using Video Acceleration including VP9 hardware decoding.
*****
The problem is still there (in the 18.3.4, 19.0 and master) and needs to be
fixed :(</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>