GPU accelaration with Carrizo only working with MS Edge

[-sandro-]

Hello,
I own a laptop with a a10-8700p CPU, however when I try to play 4K videos on youtube html5 player GPU playback it only works on Edge (and IE) on Windows 10.
When I try to play videos on FF and Chrome at 1080p the CPU stays at about 60-70% while 4K ones are unplayable.

HW acceleration seems active on Chrome at least.

 

[monstercameron]

Hello,
I own a laptop with a a10-8700p CPU, however when I try to play 4K videos on youtube html5 player GPU playback it only works on Edge (and IE) on Windows 10.
When I try to play videos on FF and Chrome at 1080p the CPU stays at about 60-70% while 4K ones are unplayable.

HW acceleration seems active on Chrome at least.

maybe chrome and ff are using vp8 codec?

 

[ViRGE]

maybe chrome and ff are using vp8 codec?

That would be my guess as well. Google will send you VP9-encoded material if they can, damn the processing requirements.

 

[monstercameron]

That would be my guess as well. Google will send you VP9-encoded material if they can, damn the processing requirements.

just did a quick check and I can confirm that chrome uses vp9 and ie uses mp4. It is unfortunate that amd decided against a vp9 hardware decoder.

 

[TheRyuu]

maybe chrome and ff are using vp8 codec?

vp8 might actually have hardware decoding support but they don't really use vp8 anymore (because it's shit). They'll serve it for compatibility but the DASH stuff only uses vp9 and h264 for video.

just did a quick check and I can confirm that chrome uses vp9 and ie uses mp4. It is unfortunate that amd decided against a vp9 hardware decoder.

vp9 is too new to have dedicated hardware decoding support in widespread adoption (also Google is really the only one using it on YouTube). It's newer than the h264 standard and can wind up looking better at the same or less bitrate than h264 so YouTube uses it because it looks just as good (or better) and uses less bandwidth.

There may be Chrome extensions which can force a certain kind of video codec IIRC or you can just keep using IE/Edge for that sort of thing. I know you can disable vp9 in Firefox in about:config but I don't know if Firefox supports hardware decoding of h264.

 

[-sandro-]

You were right, on IE I see AVC1 while on Chrome VP8. Any way to force avc1?

UPDATE: I tried to use this ext https://chrome.google.com/webstore/detail/h264ify/aleakchihdccplidncghkekgioiakgal but even thought it uses avc now it still uses software decoding for some reason. The same goes for Firefox forcing AVC.... so why would HW decoding work only MS products?

 

[monstercameron]

It was the same way with bobcat and other apus. I'm guessing a missing identifier string is not enabled.

 

[-sandro-]

It was the same way with bobcat and other apus. I'm guessing a missing identifier string is not enabled.

Shouldn't be just the same for every browser since it's just HTML5 playback?

 

[monstercameron]

I believe ie and ff use system codecs while chrome uses their own. I've sent emails describing this to amd. The decoder works its just not being sent any work.

 

[TheRyuu]

I believe ie and ff use system codecs while chrome uses their own. I've sent emails describing this to amd. The decoder works its just not being sent any work.

I don't think the hardware decoder supports vp9. It may support vp8 but nobody uses vp8 anymore.

 

[monstercameron]

I don't think the hardware decoder supports vp9. It may support vp8 but nobody uses vp8 anymore.

I know that the latest uvd doesn't support vp9. Iirc amd themselves said they want to be behind h.265.

 

[-sandro-]

I don't think the hardware decoder supports vp9. It may support vp8 but nobody uses vp8 anymore.

It doesn't decode avc either on non MS browsers.

 

[-sandro-]

I believe ie and ff use system codecs while chrome uses their own. I've sent emails describing this to amd. The decoder works its just not being sent any work.

So it should work on FF however it behaves like Chrome.

 

[monstercameron]

Try messing with some variables in the about:config or similar.

 

[ViRGE]

Try messing with some variables in the about:config or similar.

Setting media.webm.enabled to false is how you disable VP9 on Firefox. If you do that and you're still not getting hardware decoding of H.264 then I don't know what's going on. FF has full support for hardware decoding on AMD/NV/Intel at this point in time.

 

[-sandro-]

I still haven't found a solution for this for non-MS browsers. Maybe it's time ro actually ditch AMD for good.

 

[Bouowmx]

chrome://gpu
chrome://flags/#ignore-gpu-blacklist

I got most of chrome://gpu features enabled on Intel HD Graphics P3000 by enabling chrome://flags/#ignore-gpu-blacklist

 

[-sandro-]

No change

EDIT: it actually works if you use h264fy to make it use AVC1 files. Thanks!!!