vo_gpu: d3d11: fix storage lifetime of compound literals
Somehow I got the idea that compound literals had function-scoped lifetime. Instead, like all other objects with automatic storage duration, compound literals are block-scoped, so they become invalid after exiting the block they were declared in. It seems like a recent change to GCC actually reuses the memory that the compound literals used to occupy, which was causing a few bugs. The pattern of conditionally assigning a pointer to a compound literal was used in a few places in ra_d3d11 where the Direct3D API expects either a pointer to an initialised struct or NULL. Change these to ensure the lifetime of the struct includes the API call. Should fix #6775.
|3 days ago|
|.github||1 year ago|
|DOCS||3 weeks ago|
|TOOLS||3 weeks ago|
|audio||4 months ago|
|ci||11 months ago|
|common||1 week ago|
|demux||1 month ago|
|etc||8 months ago|
|filters||5 months ago|
|input||8 months ago|
|libmpv||8 months ago|
|misc||11 months ago|
|options||4 months ago|
|osdep||1 month ago|
|player||1 month ago|
|stream||3 months ago|
|sub||5 months ago|
|ta||1 year ago|
|test||1 year ago|
|video||2 days ago|
|waftools||1 month ago|
|.gitignore||2 years ago|
|.travis.yml||2 months ago|
|Copyright||1 year ago|
|LICENSE.GPL||1 year ago|
|LICENSE.LGPL||1 year ago|
|README.md||10 months ago|
|RELEASE_NOTES||4 months ago|
|VERSION||1 year ago|
|appveyor.yml||1 month ago|
|bootstrap.py||1 year ago|
|mpv_talloc.h||3 years ago|
|version.sh||4 months ago|
|wscript||1 month ago|
|wscript_build.py||1 month ago|
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.
--vo=xvon Linux), but this use is not recommended or supported.
For semi-official builds and third-party packages please see mpv.io/installation.
There is no complete changelog; however, changes to the player core interface are listed in the interface changelog.
Changes to the C API are documented in the client API changelog.
The release list has a summary of most of the important changes on every release.
Changes to the default key bindings are indicated in restore-old-bindings.conf.
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 the
./bootstrap.py 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
--disable-*** switch is printed; if the option is disabled by
--enable-*** switch is printed. Either way, you can use
--disable-** regardless of what is printed by
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.
./bootstrap.py ./waf configure ./waf ./waf install
Essential dependencies (incomplete list):
Most of the above libraries are available in suitable versions on normal Linux distributions. For ease of compiling the latest git master of everything, you may wish to use the separately available build wrapper (mpv-build) which first compiles FFmpeg libraries and libass, and then compiles the player statically linked against those.
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.
Generally, mpv should work with the latest release as well as the git version of FFmpeg. Libav support is currently broken, because they did not add certain FFmpeg API changes which mpv relies on.
mpv does not support linking against FFmpeg versions it was not built with, even if the linked version is supposedly ABI-compatible with the version it was compiled against. Expect malfunctions, crashes, and security issues if you do it anyway.
The reason for not supporting this is because it creates far too much complexity with little to no benefit, coupled with absurd and unusable FFmpeg API artifacts.
Newer mpv versions will refuse to start if runtime and compile time FFmpeg library versions mismatch.
Every other month, an arbitrary git snapshot is made, and is assigned a 0.X.0 version number. No further maintenance is done.
The goal of releases is to make Linux distributions happy. Linux distributions are also expected to apply their own patches in case of bugs and security issues.
Releases other than the latest release are unsupported and unmaintained.
See the release policy document for more information.
Please use the issue tracker provided by GitHub to send us bug reports or feature requests. Follow the template’s instructions or the issue will likely be ignored or closed as invalid.
Using the bug tracker as place for simple questions is fine but IRC is recommended (see Contact below).
Please read contribute.md.
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.
mpv is a fork of MPlayer. Much has changed, and in general, mpv should be considered a completely new program, rather than a MPlayer drop-in replacement.
For details see FAQ entry.
If you are wondering what’s different from mplayer2 and MPlayer, an incomplete and largely unmaintained list of changes is located here.
GPLv2 “or later” by default, LGPLv2.1 “or later” with
Most activity happens on the IRC channel and the github issue tracker.
To contact the
mpv team in private write to
only if discretion is required.