This release should work with FFmpeg 2.0 and Libav 9.8. It probably also works with FFmpeg 1.2, 1.1 and (if libavresample is enabled) FFmpeg 1.0. git version of FFmpeg and Libav work too, however it could be that later git versions of them introduce breaking API changes. libass 0.10.2 or later is recommended.

Brief list of major changes since 0.1.x:

• New icon.
• Add an On Screen Controller (OSC). This is a minimal GUI for use with the mouse. You should never see it if you use the keyboard only. It can be disabled entirely with echo osc=no >> ~/.mpv/config.
• Subtitles: make automatic charset detection the default.
• More intuitive chapter seeking behavior (in some cases, seeking to the previous chapter went to the start of the previous chapter, instead of the end of it).
• Add a command that allows seeking to next/previous subtitle (sub_seek).
• OSX: native VDA support (2-2.5x reduction in CPU usage over the previous VDA decoder).
• OSX: Cocoa fixes and improvements.
• Linux: support for VA-API hardware decoding and display.
• Wayland: fixes and improvements.
• OpenBSD: Add sndio audio output.
• Preliminary Lua scripting support. It's not done yet, it's not documented, and it sucks. It is needed for the OSC though.
• Switch to GPL version 2 or later for mpv as a whole (see Copyright file for details).
• Many more bug fixes and features. The full list of changes can be viewed with git log v0.1.0..v0.2.0.

Support for the 0.1.x releases is discontinued. Further 0.2.x releases will be bug fixes only.

Edit:

For some reason, this is disjoint from the release/0.1 branch. There is another 0.1.6 "release" at commit 7973487. Not sure how that happened.

Some minor bug fixes, but most of all fix the version display. It was showing UNKNOWN as version, now it should correctly display "0.1.1".

This release should work with FFmpeg 2.0 and Libav 9.8. It probably also works with FFmpeg 1.2, 1.1 and (if libavresample is enabled) FFmpeg 1.0. git version of FFmpeg and Libav work too, however it could be that later git versions of them introduce breaking API changes.

There is nothing special about this release. We just thought it was about time to start making releases, and git master seems to be relatively stable currently.

If there are bugs to fix, a branch named "release_0.1" will be created. The branch will contain fixes cherry-picked from master. Fixed versions will be released as v0.1.1, v0.1.2, etc.

Once v0.2.0 is released, support for v0.1.x will be dropped. Major releases will probably be made every 2 months.

Once the milestone 1 is completed, v1 will be released. This might happen before v0.2 is actually released.