mpv-player / mpv-player/mpv

can't switch edition when using the `--reset-on-next-file=all` option

Open
#16,802 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.40.0-324-g764da9919 Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
 built on Sep 16 2025 01:08:51
libplacebo version: v7.354.0 (v7.351.0-67-g515da95-dirty)
FFmpeg version: N-121087-g162e5a112
FFmpeg library versions:
   libavcodec      62.15.100
   libavdevice     62.2.100
   libavfilter     11.9.100
   libavformat     62.5.100
   libavutil       60.13.100
   libswresample   6.2.100
   libswscale      9.3.100
Other Information
- Windows version: Windows 10 22H2
- GPU model, driver and version:
- Source of mpv: https://github.com/zhongfly/mpv-winbuild
- Latest known working version:
- Issue started after the following happened:
Reproduction Steps
  • prepare an MKV file containing multiple editions
  • mpv test.mkv --no-config --reset-on-next-file=all --log-file=log.txt or
    mpv test.mkv --no-config --reset-on-next-file=edition --log-file=log.txt
  • run set edition 1 in console
Expected Behavior

the 2nd edition starts playing

Actual Behavior

the 1st edition restarts playing

Log File

log.txt

Sample Files

N/A

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 reproducing the issue with an MKV containing multiple editions and each listed --reset-on-next-file value, then trace the handling of the reset option and the set edition console command. The fix is complete when edition 1 switches to edition 2 instead of restarting edition 1 in both cases.

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.