The issue tracker is located on GitHub. Report bugs and feature requests there. You can also ask on the IRC channel.
Please provide enough information so that the bug can be reproduced without much trouble. Also include any details that could help us hunt down the bug. Use your common sense for this: if it looks a platform specific bug, include you OS version; if it's a video display problem, include video card model and video driver type and version; etc.
This guide goes on with recurring scenarios and which information might be needed to properly isolate the bug.
Paste the content of the
config.logfile that waf creates in the
Paste the compilation error result from
./waf buildif you went past the configure step.
Mind the config
Make sure it's actually a bug. A lot of times users forget they added something in their config file and think mpv is misbehaving. Always try to use the
--no-configCLI option before reporting.
--no-configremoves the buggy behavior, the bug is triggered by a particular set of options. Work your way through your config file and add the options manually one-by-one together with
--no-configuntil you find the smallest set of options that triggers the bug. Include the
./mpv [options] filecommand in your bug report.
Bugs related to specific files and formats:
If the bug is related to a particular format or container, make sure that it works with
avplaycompiled against the same FFmpeg or Libav version you compiled mpv against.
Include a sample that triggers the bug. If the file is too large, you can try cutting a sample to avoid uploading the entire file. Test whether the small file still works and still triggers the problem.
Cutting the sample can sometimes cause the file not to work anymore (usually the case for mp4), or the bug not to be triggered (e.g. when the bug is related to seeking).
To cut a sample you can use the
ddUNIX command, like follows:
dd if=sample-file of=small-sample-file bs=1024 count=10000
The above command will copy the first
block size (bs) x countbytes of the input file (
if) to the output file (
Unfortunately the mpv project doesn't have a private FTP to host files since it would cost money, so you will have to host the file on a server of yours. Using a hosting service is also ok but make sure it doesn't need people to queue in order to download stuff (Dropbox and datafilehost.com are recommended).
If the bug can be triggered with ffmpeg/ffplay/avconv/avplay, you can upload the sample to the ffmpeg samples FTP. See http://ffmpeg.org/bugreports.html.
Crashes / Segmentation faults
Include the stacktrace. On UNIX systems you can get the stacktrace with the following steps:
- Start mpv within gdb:
- Run it with:
run --no-config [options] file
- Perform any operation that triggers the crash
thread apply all backtraceand include its result in your report.
On OS X if you are running the application bundle
mpv.appthe system will automatically generate a backtrace among other user useful information as part of the "Crash Report". You can just paste that in that case.
- Start mpv within gdb:
Regressions / functionality that once worked:
Please provide a git commit from the past (or a mpv version in case of stable releases) where you recall the functionality used to work correctly.
BONUS: If you want to be extra nice you can perform a binary search with
git bisectto find the exact commit that broke this functionality.