mpv-player / mpv-player/mpv

A "Seek failed" error occurs when playing a link with a username and password.

Open
#13,965 3 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

Important Information

Provide following Information:

  • mpv version
    mpv v0.38.0-62-ge7b0d6b3 Copyright © 2000-2024 mpv/MPlayer/mplayer2 projects
  • Windows Version
    Windows 11 23H2 OS build:22631.3447
  • Source of the mpv binary
    https://github.com/shinchiro/mpv-winbuild-cmake
  • If known which version of mpv introduced the problem
  • GPU model, driver and version
    GPU model: NVIDIA GeForce RTX 3070 Driver version: 552.22
  • Possible screenshot or video of visual glitches
    Record video
Reproduction steps

Try to reproduce your issue with --no-config first. If it isn't reproducible
with --no-config try to first find out which option or script causes your issue.

If the issue is performance-related, try to reproduce it with --no-config
--profile=fast, which is designed to work on lower-end mobile devices.
Additionally, enable hardware decoding with --hwdec=yes or the Ctrl+h shortcut.

Describe the reproduction steps as precise as possible. It's very likely that
the bug you experience wasn't reproduced by the developer because the workflow
differs from your own.
.\mpv.com --no-config "http://fgqt:cqtwcjaq@dav.mypikpak.com/1/2.mkv"

Expected behavior

mpv should be able to play links with username and password normally

Actual behavior

Links with user names and passwords sometimes cannot be played, and links that can be played appear to be seek failed. But the link can be played without user password.

Log file

Make a log file made with -v -v or --log-file=output.txt, attach it to
the issue, and replace this text with a link to it.
output.txt
Without the log file, this issue will be closed for ignoring the issue template.

In the case of a crash, please provide a backtrace.

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 command from the issue with --no-config, comparing the authenticated URL with the same link without credentials. Inspect output.txt and the reported seek failure; done means authenticated links play and seek normally without the error.

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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.