Problems with WebM files

[A Former User]

A Former User last edited by

Hi

I have noticed Opera is having a few problems with WebM videos. The problems are:

1. On the WebM videos it should be possible to seek a specific time, but it is not working. It works with Firefox and Edge, but Chrome is with the same problem.
2. Even if my graphics chip (Intel HD Graphics 520) has VP8 and VP9 decoding capabilities, Opera doesn't use them. Edge and Chrome use the video capabilities, while Firefox has the same problem. The browsers that use it use 2% of the graphics chip processing while between 1% and 2% of video decoding capabilities, while the ones that don't use 17% of the graphics chip processing time.
3. The quality of the sound of WebM files that are played in Opera is degraded. I have noticed this on Chrome too.

The problem 1 is happening both with Windows 10 and Xubuntu 17.10, while the problem 2 I noticed only on Windows 10 (should test Xubuntu later), and the problem 3 happened only on Xubuntu 17.10.

On Windows 10, the Opera version is 50.0.2762.45, on Xubuntu 17.10 is 50.0.2762.58.

[burnout426]

burnout426 Volunteer last edited by

What does opera://gpu and chrome://gpu say about vpx decoding for you? Is vpx acceleration disabled?

[A Former User]

A Former User last edited by A Former User

Yes, on opera://gpu, on the part where it says Problems Detected, there is:

VPx decoding is too slow on Intel Broadwell, Skylake, and CherryView: 616318 Applied Workarounds: disable_accelerated_vpx_decode

Unfortunately I can't read the bug description as it asks for an account. But if Chrome has it working, wasn't that solved?

Is there some answer regarding the other two problems (particularly the first)?

Thank you.

Edit: Chrome has the same disable_accelerated_vpx_decode workaround, so why there is a so big difference in graphics processing usage between Chrome and Opera?

[burnout426]

burnout426 Volunteer @Guest last edited by

@furret29 said in Problems with WebM files:

But if Chrome has it working, wasn't that solved?

Not sure.

@furret29 said in Problems with WebM files:

On the WebM videos it should be possible to seek a specific time, but it is not working.

I tested with http://video.webmfiles.org/big-buck-bunny_trailer.webm and seeking is working there no problem for me.

[burnout426]

burnout426 Volunteer @Guest last edited by

@furret29 said in Problems with WebM files:

The quality of the sound of WebM files that are played in Opera is degraded. I have noticed this on Chrome too.

Do you have an example webm file?

[burnout426]

burnout426 Volunteer @Guest last edited by

@furret29 said in Problems with WebM files:

Edit: Chrome has the same disable_accelerated_vpx_decode workaround

Yeah, it's listed here.

, so why there is a so big difference in graphics processing usage between Chrome and Opera?

Not sure. Maybe someone else will know.

[A Former User]

A Former User last edited by

I have found why it was not possible to seek the WebM videos. Chrome and Opera expect the server to answer the requests with Accept-Ranges: bytes, the server was configured wrongly.

Is there a way to test Opera with the vpx decoding enabled, to see if it is really slow?

[burnout426]

burnout426 Volunteer @Guest last edited by

@furret29 said in Problems with WebM files:

I have found why it was not possible to seek the WebM videos.

Okay.

@furret29 said in Problems with WebM files:

Is there a way to test Opera with the vpx decoding enabled, to see if it is really slow?

I tried looking for a way earlier, but couldn't find one. Will ask around and look at chrome source and bugs etc. to see if there's a way.

[burnout426]

burnout426 Volunteer last edited by burnout426

What version of Windows 10 do you have?

VPX decoding isn't support before the Anniversary update. But, it might only work right with the Creators update and or the Fall Creators update.

Also, try opera://flags#ignore-gpu-blacklist to see if that will override the blocking.

As for Linux, VPX decoding isn't supported in Chromium. But, there's a pathc here that people are working on.

[A Former User]

A Former User last edited by

My Windows 10 version is 1709 (Fall Creators Update), so it should have the capability.

Unfortunately the flags had no effect and still couldn't use the hardware capabilities. What I noticed is that when the video is in full screen, the GPU Processing usage is significantly reduced and the Video Processing increases to numbers close to Google Chrome.

What I can be sure is that hardware decoding capabilities exist and work on both Windows 10 and Xubuntu 17.10, they only aren't being used.

Regarding audio difference on Xubuntu, the best word I could find to define the sound is "muffled". I have noticed this difference on every file with audio encoded using opus. To encode I use, for example:

ffmpeg -i INPUT -acodec libopus -application audio -b:a 320k -vbr on -f ogg -flags +global_header OUTPUT

This is very noticeable with high frequency sound, some instruments become completely inaudible. Maybe a voice optimization which degrades sound fidelity?