Command line video player
Go to file
wm4 a0e89daf49 gl_lcms: actually acquire mutex
Prevents race conditions (which can happen only in theory anyway).
2013-12-22 12:25:51 +01:00
DOCS af_export: require filename argument 2013-12-21 21:43:17 +01:00
TOOLS
audio msg: rename mp_msg_log -> mp_msg 2013-12-21 22:13:04 +01:00
bstr
common msg: remove global state 2013-12-21 23:11:12 +01:00
compat
demux demux: don't prefix tag output with demuxer name 2013-12-21 22:13:05 +01:00
etc
input msg: rename mp_msg_log -> mp_msg 2013-12-21 22:13:04 +01:00
misc charset_conv: mp_msg conversions 2013-12-21 21:43:16 +01:00
options options: make --msglevel extend previous settings 2013-12-22 12:18:01 +01:00
osdep path-macosx: attempt to fix build 2013-12-22 01:36:45 +01:00
player msg: remove global state 2013-12-21 23:11:12 +01:00
stream msg: rename mp_msg_log -> mp_msg 2013-12-21 22:13:04 +01:00
sub msg: rename mp_msg_log -> mp_msg 2013-12-21 22:13:04 +01:00
ta ta: fix compilation with NDEBUG 2013-12-19 21:27:02 +01:00
video gl_lcms: actually acquire mutex 2013-12-22 12:25:51 +01:00
waftools
.gitignore
.travis.yml
Copyright
LICENSE
README.md
bootstrap.py
old-configure Rename getch2....c/h to terminal....c/h 2013-12-19 21:31:27 +01:00
old-makefile
talloc.h
travis-deps
version.sh
wscript
wscript_build.py Rename getch2....c/h to terminal....c/h 2013-12-19 21:31:27 +01:00

README.md

mpv

Build Status

Overview

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

If you are wondering what's different from mplayer2 and MPlayer you can read more about the changes.

Compilation

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 './bootstrap.py' 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.

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.

NOTE: Using the old build system (with ./old-configure) should still work, but will be removed in a future version of mpv.

Essential dependencies (incomplete list):

  • gcc or clang
  • X development headers (xlib, X extensions, libvdpau, libGL, libXv, ...)
  • Audio output development headers (libasound, pulseaudio)
  • fribidi, freetype, fontconfig development headers (for libass)
  • libass
  • FFmpeg libraries (libavutil libavcodec libavformat libswscale libpostproc)
  • libjpeg
  • libquvi if you want to play Youtube videos directly
  • libx264/libmp3lame/libfdk-aac if you want to use encoding (has to be explicitly enabled when compiling ffmpeg)

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.

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. See the wiki article about the issue.

Bug reports

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

Contributing

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.

Contacts

These forms of contact are meant to ask questions about mpv usage, give feedback on mpv and discuss it's development.

If possible, please avoid posting bugs here and use the issue tracker instead.

  • Users IRC Channel: #mpv-player on irc.freenode.net
  • Users Mailing List: mpv-users@googlegroups.com (Archive / Subscribe).
  • Devel Mailing List: mpv-devel@googlegroups.com (Archive / Subscribe)

To contact the mpv team in private write to mpv-team@googlegroups.com.