dasharo-issues icon indicating copy to clipboard operation
dasharo-issues copied to clipboard

Artifacts in video playback in some players using HW acceleration

Open mkopec opened this issue 1 year ago • 6 comments

Component

Dasharo firmware

Device

NovaCustom V54 14th Gen, NovaCustom V56 14th Gen

Dasharo version

v0.9.0-rc9

Dasharo Tools Suite version

No response

Test case ID

No response

Brief summary

Playback of some media with hardware-accelerated (va-api) decode results in artifacts

How reproducible

100% in freetube

How to reproduce

  • Boot Ubuntu 24.04
  • Install FreeTube from Ubuntu App Store
  • Start video playback

Also reported to appear in virt-manager

Expected behavior

  • Video is played normally

Actual behavior

  • Artifacts appear

Screenshots

image

Additional context

Reported by per-astra-ad-deum on Matrix

Not sure if it's firmware-related yet

Solutions you've tried

No response

mkopec avatar Jul 11 '24 08:07 mkopec

Looks like the exact same issue as https://issues.chromium.org/issues/40281838 . Most likely nothing we can do from firmware.

The issue appears in Chromium and derivatives when VA-API hw accelerated decode is enabled, independent of used video codec (AV1, VP9, VP8, HEVC, AVC)

mkopec avatar Jul 11 '24 13:07 mkopec

This issue could have been resolved at least partially, e.g. FreeTube is now working as expected. Turned out the issue was Wayland-related; forcing Wayland-mode on Chromium and FreeTube solved the issue in these programs.

The issue persists on some other apps though, like in Virt-Manager.

PerAstraAdDeum avatar Aug 19 '24 13:08 PerAstraAdDeum

These artifacts do appear on v0.9.1-rc3 and v0.9.1-rc4 on FreeTube app. YouTube on Firefox and Chromium plays without issues.

philipanda avatar Aug 30 '24 07:08 philipanda

What distro are you using? Chances are hardware acceleration isn't enabled on Chromium. Firefox never had an issue with this, so it's working as expected. To enable hardware acceleration on Chromium, edit the file ~/.config/chromium-flags.conf by adding --enable-features=VaapiVideoDecodeLinuxGL you can check if hardware video acceleration is enabled by running intel_gpu_top (part of intel-gpu-tools)

On FreeTube app, see if starting the app with these arguments fixes the issue with the artifacts: --enable-features=WaylandWindowDecorations --ozone-platform-hint=auto --enable-features=VaapiVideoDecodeLinuxGL --gpu-context=wayland. Again, you can check if hardware video acceleration is working by running intel_gpu_top.

PerAstraAdDeum avatar Aug 30 '24 09:08 PerAstraAdDeum

Forgot to add but I am using a V560TNE with an NVIDIA dGPU. The OS is Ubuntu 24.04. Interestingly after using the arguments you gave only once video on FreeTube AND Chromium looks fine every time no matter if I give them again or not and this even persists after reboots and snap reinstalls.

Chromium is using the iGPU from what I can tell though. intel_gpu_top does show that Video and VideoEnhance engines are busy when playing a video on freetube or in Chromium.

philipanda avatar Sep 02 '24 06:09 philipanda

Thank you for your contribution! It is possible that changing ~/.config/chromium-flags.conf counts for all Electron-based apps, maybe that is why the changes persists?

Also, what kernel do you use? AFAIK, Ubuntu 24.04 uses the older 6.8 LTS-Kernel?

And if you want to troubleshoot further, try installing virt-manager (check This page for a how-to for Ubuntu) and see if 3D acceleration works for you please.

PerAstraAdDeum avatar Sep 03 '24 11:09 PerAstraAdDeum

I'm no longer convinced this has something to do with Dasharo firmware. I've reported the issue on various sites and it seems like this problem is present on other platforms as well. Check this link for example: Heavy graphic glitches when using Virtio with 3D acceleration

PerAstraAdDeum avatar Feb 24 '25 10:02 PerAstraAdDeum

I've noticed that this issue here is listed among the "Known issues" on the Dasharo newsletter for the release of version 1.0.0. for V54 MTL.

As I've said in my previous post, this is most likely not a firmware issue. Check the link I've provided, there are numerous reports from other notebook vendors and models - namely LG Gram and Lenovo ThinkPad - and the most likely culprit is a bug in Mesa.

I suggest closing this issue.

PerAstraAdDeum avatar Sep 19 '25 15:09 PerAstraAdDeum