Opera 81.0.4196.0 developer update
-
burnout426 Volunteer last edited by
@andrew84 For the Opera that shows x86, I'd double-check in the task manager to make sure it's not a 32-bit Opera process. Besides that, not sure.
-
andrew84 last edited by
@burnout426 Sorry, my bad.
Opera developer process was 32b bit for some reason on laptop. I didn't notice. But it was installed in Program files (not in Program files x86) and I always use autoupdate. -
A Former User last edited by
@andrew84 Everything is clear in the logs.
Judging by the desktop logs, O82 uses WMFVideoDecoder instead of VDAVideoDecoder for D3D11 due to the "Failed to initialize D3D11VideoDecoder" error. In this case, there is no hardware acceleration for the video.
With--disable-features = D3D11VideoDecodereverything is fine, VDAVideoDecoder is applied.
The laptop successfully uses VDAVideoDecoder with D3D11VideoDecoder.
In the Chromium bugtracker, I saw a mention of a similar problem. It looks like some chromium code changes may cause falling back from HW encoder to SW openh264 encoder for Intel graphics. But this is a side effect of solving another bug.
I did not see this problem directly in the chromium bugtracker. -
andrew84 last edited by andrew84
@johnd78 it's safe to use this switch --disable-features = D3D11VideoDecoder as a temporary solution or there are some limitations in this case? Or it's the same as without the h264ify extension?
-
A Former User last edited by
@andrew84 It is absolutely safe to use the
--disable-features = D3D11VideoDecoderswitch. Regardless of the h264ify extension. -
-
A Former User last edited by
@andrew84 It is still not clear why you have no problems in Chrome and Edge. The bug tracker mentioned that the latest codecs are added to the Chrome builds.
-
burnout426 Volunteer last edited by
@andrew84, dev would like you do produce a media-internals log in Chrome Canary (with h264ify and the same video). Thanks.
-
burnout426 Volunteer last edited by
@andrew84 Please uninstall it, delete the install folder, install the 64-bit version, and test again (if you haven't already) to see if there's any difference.
-
A Former User last edited by
@andrew84 Found a recent thread on the ixbt forum (Russian). Very similar to your problem with hardware H.264 decoding, I think related directly.
-
andrew84 last edited by
@burnout426 Yes, I already did it and the result is the same (plays fine/acceptable on laptop)
-
andrew84 last edited by
@burnout426 Yes
chrome://gpu https://textuploader.com/t5ar3
chrome://media-internals https://textuploader.com/t5ar8
-
andrew84 last edited by andrew84
@johnd78 Yes, very similar.
The only difference is that it works fine on laptop here in both Chrome(I checked in Beta) and in Opera.
*on Desktop I have the issue in Vivaldi and in Opera. -
A Former User last edited by
@andrew84 In your case, the difference is in the video card. For desktop g3450 - Intel HD Graphics. For laptop i3 3110m - Intel HD Graphics 4000.
-
andrew84 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 last edited by
@andrew84 Looked at Chrome Canary logs, it uses FFmpegVideoDecoder for D3D11 instead of VDAVideoDecoder. No idea why or how.
-
l33t4opera last edited by l33t4operaHi @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"). -
-
-
andrew84 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?
