So do I. There is no VP9 item in DXVA Checker. Please fix it.
Already submitted a bug report.
I am not sure though, if or not I misunderstand VP9 Decode Acceleration technology.
More testing on this issue.First I know for now, AMD only support VP9 on Chrome.
But even so, CPU usage is far lower on MPC-BE than Chrome which supposed to support VP9 Decode Acceleration with 16.12.1.
Chrome on this video:
This is a nVIDIA user's testing(not me), seems works fine with VP9 decoding:
Vonchen, is your browser displaying "vpx hardware enabled" by default, or did you use about://flags to force it? Mine keeps displaying software, both 55 and 57 versions of chrome on windows 7, unless I force it. (still doesn't work, obviously, even tough relive patchnotes say it should)
I am using Chrome 55.0.2883.87 m (64-bit) on Windows 10 64bit. And it seems there are some different from Windows 7's version from your describe.
1.My "chrome://flags" is all default settings, I can not see VP9 option in there to do so call "forct it".
2.My "vpx hardware enabled" is default "Hardware accelerated" in "chrome://gpu"
But anyway it seems not really VP9 enabled, almost about 100% High CPU usage and shutters for 4kfps60 videos.
I do not understand what's different from pure software VP9 decoding from this.
I found another way is to use Microsoft Edge and force VP9 on it, Edge also use high CPU but only about 70% and smooth play on 4kfps60, while AMD say only Chrome can support it for now. But Edge is Windows 10 platform limited.
16.12.2, this issue still exist.
Chrome plays vp9 4kfps60 not smooth/stutter and high cpu usage almost 98%(80%+6%+5%).
I think Crimson Relive has implemented GPU-assisted vp9 decoding indeed, but the current driver version has some bug.
I do some test. After changing the value of
from "0" to "1", DXVA Checker could identify vp9 profile, and MPC-BE could handle gpu-assisted vp9 decoding correctly, cpu usage descended from 20% to 10% (The video's bitrate I tested was low), but other players such as MPC-HC, LAV Filters and MPV could not.
hi,I know this tip.
But sound can not sync with the video, in my case. So I have to give up this tip.
Instead I use Edge for better and smooth vp9 4kfps60 videos.(still high cpu usage)
1 of 1 people found this helpful
I got a solution for Chrome from reddit, someone told me this tip:
By this way, Chrome can handle 4kfps60 vp9 in a low cpu usage and smooth playing.
This flag indeed helps, tough in my case I had to use both yours and
for this to work, so looks more or less like
chrome.exe --ignore-gpu-blacklist --enable-accelerated-vpx-decode=2
The result is smooth playback with reasonable cpu workload(20-30%, at 2,5GHz clock out of 4GHz available in my case), and you can see GPU being busy when decoding:
Yes, you can also check this url : chrome://media-internals/
This will give you chrome real time info of video decoding status.
When the parameter is used, Chrome uses GpuVideoDecoder instead of VpxVideoDecoder.
By the way, If anyone want to try Microsoft Edge to play VP9 h/w , you have to do this first:
1.open Edge and type "about:flags" in url bar.
3.Restart Edge then open the online videos you want.
By this way, Edge use lower CPU usage than Chrome(without the parameter) and smooth play(But generally speaking it still use very high CPU usage).
I set it to always on but 4k 60 fps on youtube still has dropped frames ....a lot....and cannot be watched. Chrome still losing about 300 frames on a 7000 frame clip.
But on 17.1.1 driver update says that only chrome was enabled for 4k 60 fps ....
I tested this on E3-1230v2 CPU so I wonder we still need an I7 or powerful CPU if want to use Edge with VP9.
I noticed some frame drop on Chrome too(with the --enable-accelerated-vpx-decode=2 parameter) but not so much so it is still acceptable for 4k60fps.
Anyway AMD says it only support Chrome for now. But what I really got is I need this parameter while launching Chrome :
Or we just got the same thing as non-VP9 driver before Relive.
For now this VP9 support is still not clear for me(it says support Chrome but I have to modify the way it launch by a special parameter) and do not know why it goes this way.
So I ask question here but as you see this post , no official one really explain this new feature and how it works on Relive.
Just a FYI:
I have a RX460 , now I bought a new RX470 card for it's price and performance to replace my RX460.
On RX470 it still works the way described at this post on 17.2.1.
Just an update.
After Windows 10 Creators Update, the parameter "--enable-accelerated-vpx-decode=2" seems will (sometimes/unknown reason) makes videos reverse(skip/jump backword/flashing) image so the video is not watchable on Chrome and Youtube. At least on my case.
If I not to use the parameter with Chrome I will still have 90%~ CPU usage while playing VP9 4k@60FPS videos and have frame drop so it is not watchable too.
So it seems has no way to use VP9 acceleration on 4k@FPS60 for now with Creators Update driver.
Windows 10 64bit 1703.
RX470 with Relive17.5.2.
So 17.6.2 still has this issue even on RX470. Plus now the parameter "--enable-accelerated-vpx-decode=2" makes video unwatchable(flashing and jumping image).
But if I use Chrome default, it has 90% CPU usage(E3-1230v2 4core 8thread) and the video is unwatchable (many frames dropped).
This issue started from 2016.12 and six month pasted still no any answer.
(on one of driver release notes said fix vp9 issue on Chromium, but for real Chrome using it is not fix. Or Chromium does not mean Chrome?)
Does RX400s or Relive driver really support VP9 acceleration on 4k(3840 x 2160)@FPS60 on Chrome?
If it really has 4k@FPS60 VP9 acceleration support, can anyone answer why CPU usage is so high?(or at least tell me why so many frames dropped if I do not use the parameter "--enable-accelerated-vpx-decode=2" )
The videos are all fine on H.264 with 0 or 1 frames dropped but only has 1080P option.
Chrome 59.0.3071.86 64bit
I finally found this article tell me that the Relive VP9 is more that a software solution with GPU, I do realizes it said that VP9 on Relive is not as power as dedicated hardware decode solution. But with a 90% usage on E3-1230v2 CPU and many frames dropped, does it really make sense?
Even on 4k@FPS24 it has 50% CPU usage, but if has 0 frame dropped:
Another video with high frames dropped on 4k@FPS60:
video with high frames dropped on 4k@FPS60:
1 of 1 people found this helpful
Polaris cards support hybrid acceleration of VP9 (not real hardware acceleration like H.264/H.265 etc), so basically they are using the GPU and the CPU to decode VP9 format and not the fixed-function ASIC.
Also they don't expose the device driver on DXVA Checker and that hybrid VP9 driver can only be used by Chrome ( I don't know about Edge) and not by Media Players like MPC-HC, PotPlayer etc)
Now the main issue is that Creators Update broke something in the pipeline and by forcing Chrome to use hybrid acceleration of VP9 in YouTube, the video is stuttering heavily.
AMD needs to fix the driver for Creators Update and sometime in near future - why not - Chrome needs to enable it by default or offer an easy switch to turn it on/off instead of that line full of switches.
I've just tried 17.7.1 x64 on Windows 10 x64 Creators Update (15063.483) and it still stutters heavily using Chrome x64 v59 and forced VP9 hybrid acceleration of RX 470/8GB Sapphire card.
Is AMD looking at it at all ?
It seems that latest Chrome Canary v62 (x64) works like a charm using VP9 hybrid acceleration of a Polaris card and Creators Update!
You can read the whole details here: