Rendering seems to be too slow on Chromium

[podborski]

One can build Chromium with HEVC support enabled such as here. However on win10 I had some issues with the performance of the renderer.

Repackaging and playback of 4k HEVC works well (tested with the me.html test page and content created with Nokia Creator).

However rendering seems a bit slow. After the MPD is loaded and renderer is initialised, it is hard to navigate through the scene.

[JWSon]

This issue depends on HEVC support of hardware acceleration on chromium of win10.

I tested rendering of webGL using example of three.js to see whether or not it's the only problem of our project.

*Experiment environments

• 4K test files(.mp4): avc and hevc
• os: win10
• browser: chromium ver 74.0.3729.108.
• support codec of gpu
  

*Execution time of teximage2D

• avc
  

• hevc
  

*Support of video decoding on GPU

• avc
  

• hevc
  

*Decoder

• avc
  

• hevc
  

-> GPU supports hevc decoding but Chromium is not available. Referring to this link, MojoVideoDecoder is a hardware decoder and FFmpegVideoDecoder is not clear. when Chromium lowers the hardware support resolution of avc to 1920x1080, the decoder of the 4k avc file changes to FFmpegVideoDecoder and the same problem occurred as hevc.
texImage2d function is delayed because it reads pixels from the CPU when hardware decoding is not possible (reference link).

[podborski]

@JWSon I don't think it is related to video decoding at all, since the rendering is already too laggy when the video is paused and no decoder is involved. Please see the discussion in #8 for more details.

[podborski]

Since the issue seems to be related with Chromium webGL performance (under the hood) I think we can not fix it here.