mpv-player / mpv-player/mpv

buffer upon cycling video tracks instead of desyncing

Open
#10,657 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Important Information

Provide following Information:

  • mpv-x86_64-20220918
  • Windows 10 Home 21H2 19044.2006

I have many files with multiple video tracks. Whenever I use the cycle video track key, the track changes and starts playing, then freezes a bit, after which it goes fast forward until it catches up to the audio (all of this happening in a the span of a second I'd say). mpv might be doing some loading / buffering stuff when I change the video track and this behavior is understandable and normal but is there no way to make it start displaying after it is done with it's internal stuff thus avoiding the visual freeze and the catching up resulting, I think, in a more polished experience?

Reproduction steps

Have file with multiple video tracks.
Use "_" key to change video track.

Expected behavior

Play the new video track without the initial freeze and the fast forward.

Actual behavior

New video track starts playing, then freezes a bit, after which it goes fast forward until it catches up to the audio (all of this happening in a the span of a second or so)

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

Reproduce the issue with a file containing multiple video tracks on mpv-x86_64-20220918 and Windows 10, using the underscore key to cycle tracks. Trace the video-track switching and playback timing behavior; done means the new track changes without the initial freeze or fast-forward catch-up.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.