wm4 e901bb7c99 audio: respect --end/--length with spdif passthrough
In theory, we can't really do this, because we don't know when a spdif
frame ends. Spdif transports compressed audio through audio setups that
were originally designed for PCM only (which includes the audio filter
chain, the AO API, most audio output APIs, etc.), and to reach this
goal, spdif pretends to be PCM. Compressed data frames are padded with
zeros, until a certain data rate is reached, which corresponds to a
pseudo-PCM format with 2 bytes per sample and 2 channels at 48000 Hz.
Of course an actual spdif frame is significantly larger than a frame
of the PCM format it pretends to be, so cutting audio data on frame
boundaries (as according to the pseudo-PCM format) merely yields an
incomplete and broken frame, not audio that plays for the desired
duration.

However, sending an incomplete frame might still be much better than the
current behavior, which simply ignores --end/--length (but still lets
the video end at the exact end time).

Should this result in trouble with real spdif receivers, this commit
probably has to be reverted.
2013-11-23 21:42:31 +01:00
2013-11-23 21:40:33 +01:00
2013-04-26 20:45:39 +02:00
2013-11-22 13:00:26 +01:00
2013-11-21 21:22:36 +01:00
2013-11-20 18:13:05 +01:00
2013-11-21 21:22:36 +01:00
2013-11-21 21:22:36 +01:00
2013-11-21 21:22:36 +01:00
2013-11-21 21:22:36 +01:00
2013-11-21 21:22:36 +01:00
2013-10-13 01:36:09 +02:00

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.

To contact the mpv team in private write to [email protected].

S
Description
No description provided
Readme
212 MiB
0 Stars 1 Watchers 0 Forks
Languages
C 86.5%
Lua 5.8%
Swift 2.3%
C++ 1.5%
Meson 1.1%
Other 2.8%