Skip to content

White lines during playback #16259

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
6 tasks done
karjonas opened this issue Apr 17, 2025 · 7 comments
Open
6 tasks done

White lines during playback #16259

karjonas opened this issue Apr 17, 2025 · 7 comments
Labels
down-upstream features and bugs that need to be implemented and fixed upstream os:linux

Comments

@karjonas
Copy link

karjonas commented Apr 17, 2025

mpv Information

mpv v0.40.0-dirty Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
 built on Apr  4 2025 07:28:54
libplacebo version: v7.349.0
FFmpeg version: n7.1
FFmpeg library versions:
   libavcodec      61.19.100
   libavdevice     61.3.100
   libavfilter     10.4.100
   libavformat     61.7.100
   libavutil       59.39.100
   libswresample   5.3.100
   libswscale      8.3.100

Other Information

- Linux version: Arch Linux
- Kernel Version: Linux station 6.14.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 10 Apr 2025 18:43:59 +0000 x86_64 GNU/Linux
- GPU Model: VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 32 [Radeon RX 7700 XT / 7800 XT] [1002:747e] (rev c8)
- Mesa/GPU Driver Version: Mesa 25.0.3-arch1.1
- Window Manager and Version: sway version 1.10.1
- Source of mpv: Official Arch Linux package
- Latest known working version: 0.39.0
- Issue started after the following happened: Upgrading to 0.40.0

Reproduction Steps

When playing any video (I've only tried h264 and 265 formats) white horizontal lines appears from time to time.

Expected Behavior

No white horizontal lines.

Actual Behavior

output.mp4

White horizontal lines. When using a screen-recorder on the machine the issue didn't happen so I had to record using a phone.

Log File

output.txt

Sample Files

No response

I carefully read all instruction and confirm that I did the following:

  • I tested with the latest mpv version to validate that the issue is not already fixed.
  • I provided all required information including system and mpv version.
  • I produced the log file with the exact same set of files, parameters, and conditions used in "Reproduction Steps", with the addition of --log-file=output.txt.
  • I produced the log file while the behaviors described in "Actual Behavior" were actively observed.
  • I attached the full, untruncated log file.
  • I attached the backtrace in the case of a crash.
@llyyr
Copy link
Contributor

llyyr commented Apr 17, 2025

Does it happen when the mpv window isn't fullscreen? Can you start sway with export WLR_SCENE_DISABLE_DIRECT_SCANOUT=1 in your env and see if it happens still?

@karjonas
Copy link
Author

Does it happen when the mpv window isn't fullscreen?

No.

Can you start sway with export WLR_SCENE_DISABLE_DIRECT_SCANOUT=1 in your env and see if it happens still?

It happens still.

@llyyr
Copy link
Contributor

llyyr commented Apr 17, 2025

It happens still.

Are you absolutely certain? If the issue doesn't happen if you're screen recording or the window isn't fullscreen, then it points to an issue with direct scanout. But if it still happens with no direct scanout, then it's hard to say what the cause could be.

Can you provide WAYLAND_DEBUG=1 mpv [file] output when sway is launched with that env variable?

Also try --gpu-api=opengl

@kasper93
Copy link
Member

kasper93 commented Apr 17, 2025

Does it happen with --vo=gpu-next also try mpv-git, there was small change in libplacebo, but I doubt it is affecting you.

@karjonas
Copy link
Author

It happens still.

Are you absolutely certain? If the issue doesn't happen if you're screen recording or the window isn't fullscreen, then it points to an issue with direct scanout. But if it still happens with no direct scanout, then it's hard to say what the cause could be.

Can you provide WAYLAND_DEBUG=1 mpv [file] output when sway is launched with that env variable?

Also try --gpu-api=opengl

You're right, I confused sway with mpv and used the env variable on mpv but it does indeed work when I set it when launching sway.

Do I need to these the other options or is this enough to pin it down?

@llyyr
Copy link
Contributor

llyyr commented Apr 17, 2025

Do I need to these the other options or is this enough to pin it down?

You can --gpu-api=opengl, if it happens with that too then you report to https://gitlab.freedesktop.org/drm/amd/-/issues/ and if it happens with only the default --gpu-api=vulkan, then you report to mesa.

@karjonas
Copy link
Author

karjonas commented May 1, 2025

@sfan5 sfan5 added the down-upstream features and bugs that need to be implemented and fixed upstream label May 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
down-upstream features and bugs that need to be implemented and fixed upstream os:linux
Projects
None yet
Development

No branches or pull requests

4 participants