Video player based on MPlayer/mplayer2
Clone or download
Pull request Compare This branch is 18 commits ahead, 4423 commits behind mpv-player:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

mpv VGA vector graphics fork

This fork of mpv contains additional video filters (-vf canny, -vf vector) to produce vector graphics on the standard PC VGA port. X and Y deflection is output on the red and green color channel. A digital beam enable signal is provided on the blue color channel output.

Additional depenencies over regular mpv

Usage examples

Output vector graphics on the VGA port configured to 2048x200 left of the primary monitor:

mpv --fs --geometry=<WIDTH-PRIMARY-MONITOR>:0 --loop --vf scale=576:512,lavfi=[edgedetect=high=0.04:low=0.03],vector:width=2048:height=200 <VIDEO>

If you don't have the edgedetect filter you can use the canny filter instead:

mpv --fs --geometry=<WIDTH-PRIMARY-MONITOR>:0 --loop --vf scale=576:512,canny:t1=128:t2=130,vector:width=2048:height=200 <VIDEO>

The optimal values for t1 (or low) and t2 (or high) can depend on source video. Just try a few.

Original mpv README



mpv is a media player based on MPlayer and mplayer2. It supports a wide variety of video file formats, audio and video codecs, and subtitle types.

Releases can be found on the release list.


For semi-official builds and third-party packages please see


Compiling with full features requires development files for several external libraries. Below is a list of some important requirements.

The mpv build system uses waf but we don't store it in your source tree. The script './' will download the latest version of waf that was tested with the build system.

For a list of the available build options use ./waf configure --help. If you think you have support for some feature installed but configure fails to detect it, the file build/config.log may contain information about the reasons for the failure.

NOTE: To avoid cluttering the output with unreadable spam, --help only shows one of the two switches for each option. If the option is autodetected by default, the --disable-*** switch is printed; if the option is disabled by default, the --enable-*** switch is printed. Either way, you can use --enable-*** or --disable-** regardless of what is printed by --help.

To build the software you can use ./waf build: the result of the compilation will be located in build/mpv. You can use ./waf install to install mpv to the prefix after it is compiled.

Essential dependencies (incomplete list):

  • gcc or clang
  • X development headers (xlib, X extensions, libvdpau, libGL, libXv, ...)
  • Audio output development headers (libasound/ALSA, pulseaudio)
  • FFmpeg libraries (libavutil libavcodec libavformat libswscale libavfilter and either libswresample or libavresample) At least FFmpeg 2.4.0 or Libav 11 is required.
  • zlib
  • iconv (normally provided by the system libc)
  • libass (OSD, OSC, text subtitles)
  • Lua (optional, required for the OSC pseudo-GUI and youtube-dl integration)
  • libjpeg (optional, used for screenshots only)
  • Enca (optional, for subtitle charset detection)
  • vdpau and vaapi libraries for hardware decoding on Linux (optional)

Libass dependencies:

  • gcc or clang, yasm on x86 and x86_64
  • fribidi, freetype, fontconfig development headers (for libass)
  • harfbuzz (optional, required for correct rendering of combining characters, particularly for correct rendering of non-English text on OSX, and Arabic/Indic scripts on any platform)

FFmpeg dependencies:

  • gcc or clang, yasm on x86 and x86_64
  • OpenSSL (has to be explicitly enabled when compiling ffmpeg)
  • libx264/libmp3lame/libfdk-aac if you want to use encoding (has to be explicitly enabled when compiling ffmpeg)
  • Libav also works, but some features will not work. (See section below.)

Most of the above libraries are available in suitable versions on normal Linux distributions. However FFmpeg is an exception (distro versions may be too old to work at all or work well). For that reason you may want to use the separately available build wrapper (mpv-build) that first compiles FFmpeg libraries and libass, and then compiles the player statically linked against those.

If you are running Mac OSX and using homebrew we provide homebrew-mpv, an up to date formula that compiles mpv with sensible dependencies and defaults for OSX.

If you want to build a Windows binary, you either have to use MSYS2 and MinGW, or cross-compile from Linux with MinGW. See Windows compilation.

FFmpeg vs. Libav

Generally, mpv should work with the latest release as well as the git version of both FFmpeg and Libav. But FFmpeg is preferred, and some mpv features work with FFmpeg only (subtitle formats in particular).

Release cycle

Every few months, a new release is cut off of the master branch and is assigned a 0.X.0 version number.

As part of the maintenance process, minor releases are made, which are assigned 0.X.Y version numbers. Minor releases contain bug fixes only. They never merge the master branch, and no features are added to it. Only the latest release is maintained.

The goal of releases is to provide stability and an unchanged base for the sake of Linux distributions. If you want the newest features, just use the master branch, which is stable most of the time, except sometimes, when it's not.

Releases other than the latest release are unsupported and unmaintained.

See the release policy document for more information.

Bug reports

Please use the issue tracker provided by GitHub to send us bug reports or feature requests.


For small changes you can just send us pull requests through GitHub. For bigger changes come and talk to us on IRC before you start working on them. It will make code review easier for both parties later on.

Relation to MPlayer and mplayer2

mpv is based on mplayer2, which in turn is based on the original MPlayer (also called mplayer, mplayer-svn, mplayer1). Many changes have been made, a large part of which is incompatible or completely changes how the player behaves. Although there are still many similarities to its ancestors, mpv should generally be treated as a completely different program.

mpv was forked because we wanted to modernize MPlayer. This includes removing cruft (including features which stopped making sense 10 years ago), and of course adding modern features. Such huge and intrusive changes made it infeasible to work directly with MPlayer, which is mostly focused on preservation, so a fork had to be made. (Actually, mpv is based on mplayer2, which already started this process of removing cruft.)

In general, mpv should be considered a completely new program, rather than a MPlayer drop-in replacement.

If you are wondering what's different from mplayer2 and MPlayer, an incomplete list of changes is located here.


Most activity happens on the IRC channel and the github issue tracker. The mailing lists are mostly unused.

  • GitHub issue tracker: issue tracker (report bugs here)
  • User IRC Channel: #mpv on
  • Developer IRC Channel: #mpv-devel on

To contact the mpv team in private write to Use only if discretion is required.


Mostly GPLv2 or later. See details.