When the decoder detects a format change, it overwrites the values stored in sh_audio (this affects the members sample_format, samplerate, channels). In the case when the old audio data still needs to be played/filtered, the audio format as identified by sh_audio and the format used for the decoder buffer can mismatch. In particular, they will mismatch in the very unlikely but possible case the audio chain is reinitialized while old data is draining during a format change. Or in other words, sh_audio might contain the new format, while the audio chain is still configured to use the old format. Currently, the audio code (player/audio.c and init_audio_filters) access sh_audio to get the current format. This is in theory incorrect for the reasons mentioned above. Use the decoder buffer's format instead, which should be correct at any point. |
||
---|---|---|
DOCS | ||
TOOLS | ||
audio | ||
compat | ||
demux | ||
etc | ||
mpvcore | ||
osdep | ||
stream | ||
sub | ||
ta | ||
video | ||
.gitignore | ||
.travis.yml | ||
Copyright | ||
LICENSE | ||
Makefile | ||
README.md | ||
configure | ||
talloc.h | ||
travis-deps | ||
version.sh |
README.md
mpv
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. For
more information see the output of ./configure --help
for a list of options,
or look at the list of enabled and disabled features printed after running
./configure
. If you think you have support for some feature installed
but configure fails to detect it, the file config.log
may contain
information about the reasons for the failure.
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.
configure --enable-*
parameters
The --enable-*
parameters unconditionally force options on, completely
skipping autodetection. This behavior is unlike what you may be used to from
autoconf-based configure scripts that can decide to override you. This greater
level of control comes at a price. You may have to provide the correct compiler
and linker flags yourself.
If you used one of these options and experience a compilation or linking failure, make sure you have passed the necessary compiler/linker flags to configure.
mpv's configure script is greedy and automatically enables features as a result
of autodetection. The cases where you may want to use --enable-*
are very
limited.
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
onirc.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
.