Downloads of v 2018.07.22:


Last Update:

24 Jul 2018

Package Maintainer(s):

Software Author(s):

  • mpv team


mpv video media player multimedia

mpv (Portable)

This is not the latest version of mpv (Portable) available.

  • 1
  • 2
  • 3

2018.07.22 | Updated: 24 Jul 2018



Downloads of v 2018.07.22:



Software Author(s):

  • mpv team

  • 1
  • 2
  • 3
mpv (Portable) 2018.07.22

This is not the latest version of mpv (Portable) available.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


To install mpv (Portable), run the following command from the command line or from PowerShell:


To upgrade mpv (Portable), run the following command from the command line or from PowerShell:


To uninstall mpv (Portable), run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade mpv.portable -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade mpv.portable -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure mpv.portable installed
    name: mpv.portable
    state: present
    version: 2018.07.22
    source: STEP 3 URL

See docs at

chocolatey_package 'mpv.portable' do
  action    :install
  version  '2018.07.22'
  source   'STEP 3 URL'

See docs at

    Name: mpv.portable,
    Version: 2018.07.22,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller mpv.portable
   Name     = 'mpv.portable'
   Ensure   = 'Present'
   Version  = '2018.07.22'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'mpv.portable':
  provider => 'chocolatey',
  ensure   => '2018.07.22',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install mpv.portable version="2018.07.22" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved as a trusted package on 24 Jul 2018.


mpv is a fork of mplayer2 and MPlayer. It shares some features with the former projects while introducing many more.

Streamlined CLI options##

MPlayer's options parser was improved to behave more like other CLI programs, and many option names and semantics were reworked to make them more intuitive and memorable.

On Screen Controller##

While mpv has no official GUI, it has a small controller that is triggered by mouse movement.

High quality video output##

mpv has a OpenGL based video output that is capable of many features loved by videophiles, such as video scaling with popular high quality algorithms, color management, frame timing, interpolation, and more.

GPU video decoding##

mpv leverages the FFmpeg hwaccel APIs to support VDPAU, VAAPI, DXVA2, VDA and VideoToolbox video decode acceleration.


A straightforward C API was designed from the ground up to make mpv usable as a library and facilitate easy integration into other applications.

Active development##

mpv is under active development, focusing on code refactoring and cleanups as well as adding features. Want a feature? Post a patch or request it!

mpv is a fork of mplayer2, which is a fork of MPlayer.

mpv as a whole is licensed under the GNU General Public License GPL version 2
or later (called GPLv2+ in this document, see LICENSE.GPL for full license
text) by default, or the GNU Lesser General Public License LGPL version 2 or
later (LGPLv2.1+ in this document, see LICENSE.LGPL for full license text) if
built with the --enable-lgpl configure switch.

Most source files are LGPLv2.1+ or GPLv2+, but some files are available under
more liberal licenses, such as BSD, MIT, ISC, and possibly others. Look at the
copyright header of each source file, and grep the sources for "Copyright" if
you need to know details. C source files without Copyright notice are usually
licensed as LGPLv2.1+. Also see the list of files with specific licenses below
(not all files can have a standard license header).

All new contributions must be LGPLv2.1+ licensed. Using a more liberal license
compatible to LGPLv2.1+ is also ok.

Changes done to GPL code must come with the implicit/explicit agreement that the
project can relicense the changes to LGPLv2.1+ at a later point without asking
the contributor. This is a safeguard for making potential relicensing of
remaining GPL code to LGPLv2.1+ easier.

For information about authors and contributors, consult the git log, which
contains the complete SVN and CVS history as well.

"v2.1+" in this context means "version 2.1 or later".

Some libraries are GPLv2+ or GPLv3+ only. Building mpv with Samba support makes
it GPLv3+.

mpv can be built as LGPLv2.1+ with the --enable-lgpl configure option. To add
a LGPL mode to mpv, MPlayer code had to be relicensed from GPLv2+ to LGPLv2.1+
by asking the MPlayer authors for permission. Since permission could not be
obtained from everyone, LGPL mode disables the following features, some of
them quite central:
- Linux X11 video output
- BSD audio output via OSS
- NVIDIA/Linux hardware decoding (vdpau, although nvdec usually works)
- Linux TV input
- minor features: jack, DVD, CDDA, SMB, CACA, legacy direct3d VO
Some of these will be fixed in the future. The intended use for LGPL mode is
with libmpv, and currently it's not recommended to build mpv CLI in LGPL mode
at all.

The following files are still GPL only (--enable-lgpl disables them):

    audio/out/ao_jack.c             will stay GPL
    audio/out/ao_oss.c              will stay GPL
    demux/demux_tv.c                will stay GPL
    stream/ai_*                     will stay GPL (TV code)
    stream/audio_in.*               will stay GPL (TV code)
    stream/dvb*                     must stay GPL
    stream/frequencies.*            must stay GPL
    stream/stream_cdda.c            unknown
    stream/stream_dvb.*             must stay GPL
    stream/stream_dvd.c             unknown
    stream/stream_dvd_common.*      unknown
    stream/stream_dvdnav.c          unknown
    stream/stream_smb.c             will stay GPLv3
    stream/stream_tv.c              will stay GPL
    stream/tv*                      will stay GPL
    video/out/vo_caca.c             unknown
    video/out/vo_direct3d.c         unknown
    video/out/vo_vaapi.c            probably impossible (some company's code)
    video/out/vo_vdpau.c            probably impossible (nVidia's code)
    video/out/vo_x11.c              probably impossible
    video/out/vo_xv.c               probably impossible
    video/out/x11_common.*          probably impossible
    video/vdpau.c                   hard (GPL-only parts must be ifdefed)
    video/vdpau.h                   unknown
    video/vdpau_mixer.*             actual code must be rewritten
    DOCS/man/                       GPLv2+                    unknown license, probably GPLv2+ or LGPLv2+
    etc/mplayer-input.conf          unknown license, probably GPLv2+
    mpv.desktop                     unknown license, probably GPLv2+
    etc/restore-old-bindings.conf   unknown license, probably GPLv2+

The following files contain some optional GPL code (--enable-lgpl disables it):

    options/parse_commandline.c     dvd:// expansion

None of the exceptions listed above affect the final binary if it's built as
LGPL. Linked libraries still can affect the final license (for example if
FFmpeg was built as GPL).
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
The embedded software have been downloaded from the listed download
location on <>
and can be verified by doing the following:

1. Go to


	to download the installer.

2. Get the checksum using one of the following methods:
  - Using powershell function 'Get-FileHash'
  - Use chocolatey utility 'checksum.exe'

3. The checksums should match the following:

  checksumType: SHA256
  checksum32: AD1D504098F51AD6190E9BED5F5BAAD55C409A587DB7D0EB764D40C08D1885CF
  checksum64: 9A65CE6D0F267E2F8B1B4ED7FE115B9A06AE622DC6AEF42D8668DEA094855618

The file 'LICENSE.txt' has been obtained from <>
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$packageArgs = @{
    packageName = 'mpv.install'
    file        = gi $toolsDir\*_x32.7z
    file64      = gi $toolsDir\*_x64.7z
    destination = "$toolsDir"

Get-ChocolateyUnzip @packageArgs

# mpv can't be shimmed, the shim doesn't work with
# as of 2016.01.18, there is a dll dependency, so mpv can't be hardlinked to chocolatey\bin
# adding to PATH until chocolatey implements a /usr/lib equivalent
$pathType = 'User'
If ( Test-ProcessAdminRights ) { $pathType = 'Machine' }
Install-ChocolateyPath $toolsDir $pathType
$packageName = 'mpv.portable'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

# Remove from Machine PATH
$machinePath = Get-EnvironmentVariable -Name PATH -Scope Machine
if ( $machinePath.Contains($toolsDir) ) {
	$cleanMachinePath = $([Environment]::GetEnvironmentVariable("PATH",[EnvironmentVariableTarget]::Machine)).Replace("$toolsDir;",'')
	[Environment]::SetEnvironmentVariable("PATH", "$cleanMachinePath", [EnvironmentVariableTarget]::Machine)
# Remove from User PATH
$userPath = Get-EnvironmentVariable -Name 'PATH' -Scope User
if ( $userPath.Contains($toolsDir) ) {
	$cleanUserPath = $([Environment]::GetEnvironmentVariable("PATH", [EnvironmentVariableTarget]::User)).Replace("$toolsDir;",'')
	 [Environment]::SetEnvironmentVariable("PATH", "$cleanUserPath", [EnvironmentVariableTarget]::User)
md5: 4DFB09BD058887547F8C61B0A867F5B5 | sha1: 40EB1C974F10B2DD9F725B3B3D9B0C77311ECD02 | sha256: AD1D504098F51AD6190E9BED5F5BAAD55C409A587DB7D0EB764D40C08D1885CF | sha512: 97425EE14F93805B9F111F0A1EED111D94AFDBC1DB737CC2E271557FCBA21CB0E6238CEF4F9DA1847FFB95014305D12B526AE75A998BF446AE5CABE700193041
md5: 26609A7016BA31E862122E1BDA9D8650 | sha1: A348A92E63D6D307C4F5AA966CD75C216D186891 | sha256: 9A65CE6D0F267E2F8B1B4ED7FE115B9A06AE622DC6AEF42D8668DEA094855618 | sha512: 3ECB71E03A6AF507666864985851F19DBD7A631C17EEED10EF290DA884958FF7D0CB2E003036279ED2F3D96357F4F43A19E5B291A7735FF0640AE0D0DC57DC8E

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
mpv (Portable) 2020.1.27 1254 Tuesday, March 17, 2020 Approved
mpv (Portable) 2019.12.29 444 Thursday, January 23, 2020 Approved
mpv (Portable) 2019.11.02 714 Monday, November 11, 2019 Approved
mpv (Portable) 2018.10.02 604 Wednesday, October 3, 2018 Approved
mpv (Portable) 2018.07.31 335 Wednesday, August 1, 2018 Approved
mpv (Portable) 2018.07.22 250 Tuesday, July 24, 2018 Approved
mpv (Portable) 2017.12.25 625 Saturday, December 30, 2017 Approved
mpv (Portable) 2017.09.13 783 Wednesday, September 13, 2017 Approved
mpv (Portable) 2017.07.18 691 Thursday, July 20, 2017 Approved

This package has no dependencies.

Discussion for the mpv (Portable) Package

Ground Rules:

  • This discussion is only about mpv (Portable) and the mpv (Portable) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or mpv (Portable), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus