mpv-player / mpv-player/mpv

Unable to clear --start option with commands

Open
#18,275 1 comment 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.41.0-744-g304426c39 Copyright © 2000-2026 mpv/MPlayer/mplayer2 projects
 built on Jun 10 2026 00:25:12
libplacebo version: v7.365.0 (v7.360.0-80-gd4624cb-dirty)
FFmpeg version: N-124930-g2576e0943
FFmpeg library versions:
   libavcodec      62.36.101
   libavdevice     62.4.100
   libavfilter     11.17.100
   libavformat     62.19.101
   libavutil       60.33.100
   libswresample   6.4.100
   libswscale      9.8.100
Other Information
- Windows version: Microsoft Windows [Version 10.0.19041.6456]
- Source of mpv: https://github.com/shinchiro/mpv-winbuild-cmake/releases
Reproduction Steps

Load MPV with a file-specific option for --start:

mpv --{ start=5 video.mp4 --}

Run the commands in MPV console:

set file-local-options/start none
set start none
playlist-play-index current

It will reload the video, but it will be at the start position of 5, instead of having no start position and playing back at 0.

However, if you use the global option --start=5:

mpv --start=5 video.mp4

Then you are able to clear the option, reload the file and have it play the file from the beginning:

set start none
playlist-play-index current

This also gets a little more messy if you try to clear these options from a script. If you set the global --start option in MPV (mpv --start=5 video.mp4) and then in invoke mp.set_property('start', 'none') in a JS script, it does not seem to clear the value, because then running mp.command('playlist-play-index current') will still set the starting position of the video to 5 seconds.

Expected Behavior

Setting properties start and file-local-options/start to none (clearing them) should allow you to reload the playlist without any start position via playlist-play-index current.

Actual Behavior

After setting properties start and file-local-options/start to none and then reloading with playlist-play-index current, the starting playback position still uses the previous start value before it was cleared.

Log File

output.txt

Sample Files

No response

I carefully read all instruction and confirm that I did the following:
  • I tested and confirmed that the issue exists with the latest release version or newer.
  • 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 console commands involving start, file-local-options/start, and playlist-play-index current, then compare the global option path with the file-local option path. Check the handling behind the set command and the JavaScript mp.set_property API; done means clearing both properties causes a reload to begin at position 0.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.