mpv-player / mpv-player/mpv

video artifacts when using scale-antiring

Open
#14,745 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

os:win
Dominant language
C
Stars
37k
Forks
3.5k
Avg merge
1d 10h
Merged PRs (30d)
22

Description

mpv Information
mpv v0.38.0-715-ge3a9ce22 Copyright © 2000-2024 mpv/MPlayer/mplayer2 projects
 built on Aug 22 2024 00:14:46
libplacebo version: v7.349.0 (v7.349.0-5-g82bf46a-dirty)
FFmpeg version: N-116755-g9d15fe77e
FFmpeg library versions:
   libavcodec      61.11.100
   libavdevice     61.2.100
   libavfilter     10.2.102
   libavformat     61.5.101
   libavutil       59.34.100
   libswresample   5.2.100
   libswscale      8.2.100
Other Information
- Windows version: 22H2 19045.2913
- GPU model, driver and version: Intel(R) HD Graphics 5500

	Stuurprogrammaversie:	20.19.15.5171
	Datum stuurprogramma:	4/11/2020
	DirectX-versie:	12 (FL 11.1)
	Fysieke locatie:	PCI-bus 0, apparaat 2, functie 0

	Gebruik	0%
	Toegewezen GPU-geheugen	
	Gedeeld GPU-geheugen	0,1/2,0 GB
	GPU-geheugen	0,1/2,0 GB
- Source of mpv: shinchiro
- Introduced in version: idk, always been there
Reproduction Steps

idk what the source of the problem is, but i use this config file, and when commenting
scale-antiring = 0.4
the problem goes away, but when using mpv --no-config --scale-antiring=0.4 the problem is also resolved, so i don't really know what the source of the problem is.

Expected Behavior

correct video playback

Actual Behavior

Schermopname (2)

Log File

output.txt

Sample Files

i can't
this is the file i'm having issues with (torrent)
the same problem with this video

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the linked configuration with the minimal mpv --no-config --scale-antiring=0.4 invocation, then inspect output.txt while reproducing the artifacts on the reported Windows and Intel HD Graphics 5500 setup. Done means the source of the rendering difference is identified and playback no longer shows the reported artifacts under the relevant configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
computer-graphics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.