mpv-player / mpv-player/mpv

how to use my own custom ffmpeg build binaries with mpv player, using windows os

Open
#15,360 4 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

No response

Other Information
Just would like to know how to use my own custom ffmpeg build binaries with mpv player, using windows os.

Is there something in the config file to set or can I replace ffmpeg binaries in a folder?

I'm using portable mpv player and I didn't find any ffmpeg binaries anywhere.

Thanks in advance.
Reproduction Steps

none

Expected Behavior

none

Actual Behavior

none

Log File

none

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

The issue names portable mpv on Windows and custom FFmpeg binaries but no files, tests, or entry points. Start by checking the portable package contents and the project's Windows/build documentation. Done means documenting whether custom FFmpeg binaries are supported and, if so, where they must be configured or placed.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.