Opera 81.0.4196.0 developer update

[andrew84]

andrew84 @Guest last edited by andrew84

@johnd78 I can add a remark here. When I say 'no issues' on Chrome/Edge or on laptop I mean that there's no such heavy CPU overload (task manager shows 100% all the time -straight line on top) and continuous video freezes.
Maybe, technically the issue is also on Chrome/Edge or on laptop (wrong decoder is in use or similar problem) but just the overload is not so heavy. I'm not very familiar with all this video decoding stuff.

[A Former User]

A Former User @andrew84 last edited by

@andrew84 Looked at Chrome Canary logs, it uses FFmpegVideoDecoder for D3D11 instead of VDAVideoDecoder. No idea why or how.

[l33t4opera]

l33t4opera @Guest last edited by l33t4opera

Hi @johnd78, the "FFmpegVideoDecoder" means there's no HW acceleration for video decoding.
Did you check what it says about it under "opera:gpu"?
When a video is replayed, what codec it uses (you can check it on YT under "Stats for nerds").

[A Former User]

A Former User @l33t4opera last edited by

@l33t4opera This is a very special issue that @andrew84 had.

[andrew84]

andrew84 @l33t4opera last edited by This post is deleted!

[andrew84]

andrew84 @Guest last edited by andrew84

@johnd78 So the correct decoder is VDAVideoDecoder for the h.264?
If I'm getting it right from the log, in O82 (in my case) is used WMFVideoDecoder which is also incorrect?

[andrew84]

andrew84 @l33t4opera last edited by andrew84

@l33t4opera you can check the logs and screenshot.
https://forums.opera.com/post/264733

https://forums.opera.com/post/264590

[A Former User]

A Former User @andrew84 last edited by

@andrew84 For H.264 hardware decoding, "VDAVideoDecoder" is used. "FFmpegVideoDecoder" for Chrome or "WMFVideoDecoder" for Opera means no hardware acceleration for video decoding.

[A Former User]

A Former User @andrew84 last edited by

@andrew84
So in Chrome you also have problems with hardware H.264 decoding on the desktop, the load on the CPU in Chrome in your screenshot is too high. Try to use the switch --disable-features=D3D11VideoDecoder in Chrome, it is possible that the CPU load will be reduced to the Edge level. The case with Edge is special, there are significant differences in the browser code from chromium.

Bottom line: code changes on Chromium 93 broke the hardware H.264 decoding on some Intel integrated graphics cards, this is still not fixed in Chromium 97.
As a workaround, you can use the --disable-features=D3D11VideoDecoder switch.

[andrew84]

andrew84 @Guest last edited by andrew84

@johnd78 said in Opera 81.0.4196.0 developer update:

code changes on Chromium 93 broke the hardware H.264 decoding on some Intel integrated graphics cards, this is still not fixed in Chromium 97.

Thanks for the info.
The bug is reported and confirmed from their (Chromium) side?

[A Former User]

A Former User @andrew84 last edited by

@andrew84 said in Opera 81.0.4196.0 developer update:

The bug is reported and confirmed from their (Chromium) side?

I don't know for sure.