mpv-player / mpv-player/mpv

scripts loading twice when mpv folder in appdata

Open
#14,438 7 comments 1 reaction 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-556-g95ac3222 Copyright © 2000-2024 mpv/MPlayer/mplayer2 projects
 built on Jun 25 2024 04:06:53
libplacebo version: v7.349.0 (v7.349.0-rc1-3-g1fd3c7b-dirty)
FFmpeg version: N-116015-g23531c977
FFmpeg library versions:
   libavcodec      61.8.100
   libavdevice     61.2.100
   libavfilter     10.2.102
   libavformat     61.4.100
   libavutil       59.26.100
   libswresample   5.2.100
   libswscale      8.2.100
Other Information
Reproduction Steps

download mpv
extract to %appdata%
rename folder to mpv
create scripts folder
create a new file inside scripts folder (use anything other than .lua)
open mpv

Expected Behavior

scripts load once

Actual Behavior

scripts are loaded twice

[   0.017][e][cplayer] Can't load unknown script: C:/Users/Test/AppData/Roaming/mpv/scripts/only1script.txt
[   0.017][e][cplayer] Can't load unknown script: C:\Users\Test\AppData\Roaming/mpv/scripts/only1script.txt
Log File

dups.log

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.

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 with the reported Windows reproduction steps and inspect dups.log, focusing on how the scripts directory under %appdata% is discovered. Done means the same non-Lua file produces only one load attempt and one corresponding error path when mpv starts.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.