manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
VIDEO OUTPUT DRIVERS
|
|
|
|
====================
|
|
|
|
|
|
|
|
Video output drivers are interfaces to different video output facilities. The
|
|
|
|
syntax is:
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``--vo=<driver1[:suboption1[=value]:...],driver2,...[,]>``
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
Specify a priority list of video output drivers to be used.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
If the list has a trailing ',', mpv will fall back on drivers not contained
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
in the list. Suboptions are optional and can mostly be omitted.
|
|
|
|
|
2013-11-30 23:12:10 +00:00
|
|
|
You can also set defaults for each driver. The defaults are applied before the
|
|
|
|
normal driver parameters.
|
|
|
|
|
|
|
|
``--vo-defaults=<driver1[:parameter1:parameter2:...],driver2,...>``
|
|
|
|
Set defaults for each driver.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
.. note::
|
|
|
|
|
|
|
|
See ``--vo=help`` for a list of compiled-in video output drivers.
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
|
2014-04-19 13:29:05 +00:00
|
|
|
The recommended output drivers are ``--vo=vdpau`` and ``--vo=opengl-hq``.
|
|
|
|
All other drivers are just for compatibility or special purposes.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
.. admonition:: Example
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
|
2012-09-23 14:10:00 +00:00
|
|
|
``--vo=opengl,xv,``
|
2013-07-08 16:02:14 +00:00
|
|
|
Try the ``opengl`` driver, then the ``xv`` driver, then others.
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
|
|
|
|
Available video output drivers are:
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``xv`` (X11 only)
|
2013-09-10 13:09:24 +00:00
|
|
|
Uses the XVideo extension to enable hardware-accelerated display. This is
|
2013-07-08 16:02:14 +00:00
|
|
|
the most compatible VO on X, but may be low-quality, and has issues with
|
2012-08-07 21:53:14 +00:00
|
|
|
OSD and subtitle display.
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
|
2014-04-19 13:29:05 +00:00
|
|
|
.. note:: This driver is for compatibility with old systems.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``adaptor=<number>``
|
2014-09-01 02:25:57 +00:00
|
|
|
Select a specific XVideo adapter (check xvinfo results).
|
2013-07-08 16:02:14 +00:00
|
|
|
``port=<number>``
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
Select a specific XVideo port.
|
2013-07-08 16:02:14 +00:00
|
|
|
``ck=<cur|use|set>``
|
2014-09-01 02:25:57 +00:00
|
|
|
Select the source from which the color key is taken (default: cur).
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
|
|
|
|
cur
|
2014-09-01 02:25:57 +00:00
|
|
|
The default takes the color key currently set in Xv.
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
use
|
2014-09-01 02:25:57 +00:00
|
|
|
Use but do not set the color key from mpv (use the ``--colorkey``
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
option to change it).
|
|
|
|
set
|
2014-09-01 02:25:57 +00:00
|
|
|
Same as use but also sets the supplied color key.
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``ck-method=<man|bg|auto>``
|
2014-09-01 02:25:57 +00:00
|
|
|
Sets the color key drawing method (default: man).
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
|
|
|
|
man
|
2014-09-01 02:25:57 +00:00
|
|
|
Draw the color key manually (reduces flicker in some cases).
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
bg
|
2014-09-01 02:25:57 +00:00
|
|
|
Set the color key as window background.
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
auto
|
2014-09-01 02:25:57 +00:00
|
|
|
Let Xv draw the color key.
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
|
2013-07-21 23:03:22 +00:00
|
|
|
``colorkey=<number>``
|
2014-09-01 02:25:57 +00:00
|
|
|
Changes the color key to an RGB value of your choice. ``0x000000`` is
|
2013-07-21 23:03:22 +00:00
|
|
|
black and ``0xffffff`` is white.
|
|
|
|
|
|
|
|
``no-colorkey``
|
2014-09-01 02:25:57 +00:00
|
|
|
Disables color-keying.
|
2013-07-21 23:03:22 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``x11`` (X11 only)
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
Shared memory video output driver without hardware acceleration that works
|
|
|
|
whenever X11 is present.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
.. note:: This is a fallback only, and should not be normally used.
|
2012-10-23 23:06:00 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``vdpau`` (X11 only)
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
Uses the VDPAU interface to display and optionally also decode video.
|
2013-01-30 23:39:45 +00:00
|
|
|
Hardware decoding is used with ``--hwdec=vdpau``.
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
|
2014-05-02 14:57:39 +00:00
|
|
|
.. note::
|
|
|
|
|
|
|
|
Earlier versions of mpv (and MPlayer, mplayer2) provided sub-options
|
2014-09-01 02:25:57 +00:00
|
|
|
to tune vdpau post-processing, like ``deint``, ``sharpen``, ``denoise``,
|
2014-05-02 14:57:39 +00:00
|
|
|
``chroma-deint``, ``pullup``, ``hqscaling``. These sub-options are
|
|
|
|
deprecated, and you should use the ``vdpaupp`` video filter instead.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``sharpen=<-1-1>``
|
2014-05-02 14:57:39 +00:00
|
|
|
(Deprecated. See note about ``vdpaupp``.)
|
|
|
|
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
For positive values, apply a sharpening algorithm to the video, for
|
|
|
|
negative values a blurring algorithm (default: 0).
|
2013-07-08 16:02:14 +00:00
|
|
|
``denoise=<0-1>``
|
2014-05-02 14:57:39 +00:00
|
|
|
(Deprecated. See note about ``vdpaupp``.)
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
Apply a noise reduction algorithm to the video (default: 0; no noise
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
reduction).
|
2013-07-08 16:02:14 +00:00
|
|
|
``deint=<-4-4>``
|
2014-05-02 14:57:39 +00:00
|
|
|
(Deprecated. See note about ``vdpaupp``.)
|
|
|
|
|
2014-05-02 15:08:19 +00:00
|
|
|
Select deinterlacing mode (default: 0). In older versions (as well as
|
|
|
|
MPlayer/mplayer2) you could use this option to enable deinterlacing.
|
|
|
|
This doesn't work anymore, and deinterlacing is enabled with either
|
|
|
|
the ``D`` key (by default mapped to the command ``cycle deinterlace``),
|
|
|
|
or the ``--deinterlace`` option. Also, to select the default deint mode,
|
|
|
|
you should use something like ``--vf-defaults=vdpaupp:deint-mode=temporal``
|
|
|
|
instead of this sub-option.
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
|
|
|
|
0
|
2014-05-02 15:08:19 +00:00
|
|
|
Pick the ``vdpaupp`` video filter default, which corresponds to 3.
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
1
|
2013-07-08 16:02:14 +00:00
|
|
|
Show only first field.
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
2
|
2013-07-08 16:02:14 +00:00
|
|
|
Bob deinterlacing.
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
3
|
2013-07-08 16:02:14 +00:00
|
|
|
Motion-adaptive temporal deinterlacing. May lead to A/V desync
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
with slow video hardware and/or high resolution.
|
|
|
|
4
|
2013-07-08 16:02:14 +00:00
|
|
|
Motion-adaptive temporal deinterlacing with edge-guided spatial
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
interpolation. Needs fast video hardware.
|
2013-07-08 16:02:14 +00:00
|
|
|
``chroma-deint``
|
2014-05-02 14:57:39 +00:00
|
|
|
(Deprecated. See note about ``vdpaupp``.)
|
|
|
|
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
Makes temporal deinterlacers operate both on luma and chroma (default).
|
|
|
|
Use no-chroma-deint to solely use luma and speed up advanced
|
|
|
|
deinterlacing. Useful with slow video memory.
|
2013-07-08 16:02:14 +00:00
|
|
|
``pullup``
|
2014-05-02 14:57:39 +00:00
|
|
|
(Deprecated. See note about ``vdpaupp``.)
|
|
|
|
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
Try to apply inverse telecine, needs motion adaptive temporal
|
|
|
|
deinterlacing.
|
2013-07-08 16:02:14 +00:00
|
|
|
``hqscaling=<0-9>``
|
2014-05-02 14:57:39 +00:00
|
|
|
(Deprecated. See note about ``vdpaupp``.)
|
|
|
|
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
0
|
|
|
|
Use default VDPAU scaling (default).
|
|
|
|
1-9
|
|
|
|
Apply high quality VDPAU scaling (needs capable hardware).
|
2013-07-08 16:02:14 +00:00
|
|
|
``fps=<number>``
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
Override autodetected display refresh rate value (the value is needed
|
|
|
|
for framedrop to allow video playback rates higher than display
|
|
|
|
refresh rate, and for vsync-aware frame timing adjustments). Default 0
|
|
|
|
means use autodetected value. A positive value is interpreted as a
|
|
|
|
refresh rate in Hz and overrides the autodetected value. A negative
|
|
|
|
value disables all timing adjustment and framedrop logic.
|
2013-07-08 16:02:14 +00:00
|
|
|
``composite-detect``
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
NVIDIA's current VDPAU implementation behaves somewhat differently
|
|
|
|
under a compositing window manager and does not give accurate frame
|
|
|
|
timing information. With this option enabled, the player tries to
|
|
|
|
detect whether a compositing window manager is active. If one is
|
|
|
|
detected, the player disables timing adjustments as if the user had
|
2013-07-08 16:02:14 +00:00
|
|
|
specified ``fps=-1`` (as they would be based on incorrect input). This
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
means timing is somewhat less accurate than without compositing, but
|
2013-07-08 16:02:14 +00:00
|
|
|
with the composited mode behavior of the NVIDIA driver, there is no
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
hard playback speed limit even without the disabled logic. Enabled by
|
2013-07-08 16:02:14 +00:00
|
|
|
default, use ``no-composite-detect`` to disable.
|
|
|
|
``queuetime_windowed=<number>`` and ``queuetime_fs=<number>``
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
Use VDPAU's presentation queue functionality to queue future video
|
|
|
|
frame changes at most this many milliseconds in advance (default: 50).
|
|
|
|
See below for additional information.
|
2013-07-08 16:02:14 +00:00
|
|
|
``output_surfaces=<2-15>``
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
Allocate this many output surfaces to display video frames (default:
|
|
|
|
3). See below for additional information.
|
2013-08-17 17:57:18 +00:00
|
|
|
``colorkey=<#RRGGBB|#AARRGGBB>``
|
|
|
|
Set the VDPAU presentation queue background color, which in practice
|
|
|
|
is the colorkey used if VDPAU operates in overlay mode (default:
|
vo_vdpau: use color close to black as default colorkey (instead of green)
The VDPAU default colorkey, although it seems to be driver specific, is
usually green. This is a pretty annoying color, and you usually see it
briefly (as flashes) if the VDPAU window resizes.
Change it to some shade of black. The new default color is close to what
MPlayer picks as colorkey (and apparently it worked well for them):
VdpColor vdp_bg = {0.01, 0.02, 0.03, 0};
Since our OPT_COLOR can set 8 bit colors only, we use '#020507' instead,
which should be the same assuming 8 bit colors.
Obviously, you can't use black, because black is a way too common color,
and would make it too easy to observe the colorkey effect when e.g.
moving a terminal with black background over the video window.
2013-08-17 18:05:28 +00:00
|
|
|
``#020507``, some shade of black). If the alpha component of this value
|
|
|
|
is 0, the default VDPAU colorkey will be used instead (which is usually
|
|
|
|
green).
|
2013-08-18 03:12:21 +00:00
|
|
|
``force-yuv``
|
|
|
|
Never accept RGBA input. This means mpv will insert a filter to convert
|
|
|
|
to a YUV format before the VO. Sometimes useful to force availability
|
|
|
|
of certain YUV-only features, like video equalizer or deinterlacing.
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
|
2014-09-01 02:25:57 +00:00
|
|
|
Using the VDPAU frame queuing functionality controlled by the queuetime
|
2013-07-08 16:02:14 +00:00
|
|
|
options makes mpv's frame flip timing less sensitive to system CPU load and
|
|
|
|
allows mpv to start decoding the next frame(s) slightly earlier, which can
|
|
|
|
reduce jitter caused by individual slow-to-decode frames. However, the
|
|
|
|
NVIDIA graphics drivers can make other window behavior such as window moves
|
|
|
|
choppy if VDPAU is using the blit queue (mainly happens if you have the
|
|
|
|
composite extension enabled) and this feature is active. If this happens on
|
|
|
|
your system and it bothers you then you can set the queuetime value to 0 to
|
|
|
|
disable this feature. The settings to use in windowed and fullscreen mode
|
|
|
|
are separate because there should be no reason to disable this for
|
|
|
|
fullscreen mode (as the driver issue should not affect the video itself).
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
|
|
|
|
You can queue more frames ahead by increasing the queuetime values and the
|
2013-07-08 16:02:14 +00:00
|
|
|
``output_surfaces`` count (to ensure enough surfaces to buffer video for a
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
certain time ahead you need at least as many surfaces as the video has
|
|
|
|
frames during that time, plus two). This could help make video smoother in
|
|
|
|
some cases. The main downsides are increased video RAM requirements for
|
|
|
|
the surfaces and laggier display response to user commands (display
|
|
|
|
changes only become visible some time after they're queued). The graphics
|
|
|
|
driver implementation may also have limits on the length of maximum
|
|
|
|
queuing time or number of queued surfaces that work well or at all.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``direct3d_shaders`` (Windows only)
|
2012-08-07 21:53:14 +00:00
|
|
|
Video output driver that uses the Direct3D interface.
|
|
|
|
|
2014-04-19 13:29:05 +00:00
|
|
|
.. note:: This driver is for compatibility with systems that don't provide
|
|
|
|
proper OpenGL drivers.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``prefer-stretchrect``
|
|
|
|
Use ``IDirect3DDevice9::StretchRect`` over other methods if possible.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``disable-stretchrect``
|
|
|
|
Never render the video using ``IDirect3DDevice9::StretchRect``.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``disable-textures``
|
|
|
|
Never render the video using D3D texture rendering. Rendering with
|
|
|
|
textures + shader will still be allowed. Add ``disable-shaders`` to
|
|
|
|
completely disable video rendering with textures.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``disable-shaders``
|
2012-08-07 21:53:14 +00:00
|
|
|
Never use shaders when rendering video.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``only-8bit``
|
2012-08-07 21:53:14 +00:00
|
|
|
Never render YUV video with more than 8 bits per component.
|
2013-07-08 16:02:14 +00:00
|
|
|
Using this flag will force software conversion to 8-bit.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``disable-texture-align``
|
2012-08-07 21:53:14 +00:00
|
|
|
Normally texture sizes are always aligned to 16. With this option
|
|
|
|
enabled, the video texture will always have exactly the same size as
|
|
|
|
the video itself.
|
|
|
|
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
Debug options. These might be incorrect, might be removed in the future,
|
|
|
|
might crash, might cause slow downs, etc. Contact the developers if you
|
|
|
|
actually need any of these for performance or proper operation.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``force-power-of-2``
|
2012-08-07 21:53:14 +00:00
|
|
|
Always force textures to power of 2, even if the device reports
|
|
|
|
non-power-of-2 texture sizes as supported.
|
|
|
|
|
2014-11-18 15:30:24 +00:00
|
|
|
``texture-memory=<mode>``
|
2012-08-07 21:53:14 +00:00
|
|
|
Only affects operation with shaders/texturing enabled, and (E)OSD.
|
2014-11-18 15:30:24 +00:00
|
|
|
Possible values:
|
|
|
|
|
|
|
|
``default`` (default)
|
|
|
|
Use ``D3DPOOL_DEFAULT``, with a ``D3DPOOL_SYSTEMMEM`` texture for
|
|
|
|
locking. If the driver supports ``D3DDEVCAPS_TEXTURESYSTEMMEMORY``,
|
|
|
|
``D3DPOOL_SYSTEMMEM`` is used directly.
|
|
|
|
|
|
|
|
``default-pool``
|
|
|
|
Use ``D3DPOOL_DEFAULT``. (Like ``default``, but never use a
|
|
|
|
shadow-texture.)
|
|
|
|
|
|
|
|
``default-pool-shadow``
|
|
|
|
Use ``D3DPOOL_DEFAULT``, with a ``D3DPOOL_SYSTEMMEM`` texture for
|
|
|
|
locking. (Like ``default``, but always force the shadow-texture.)
|
|
|
|
|
|
|
|
``managed``
|
|
|
|
Use ``D3DPOOL_MANAGED``.
|
|
|
|
|
|
|
|
``scratch``
|
|
|
|
Use ``D3DPOOL_SCRATCH``, with a ``D3DPOOL_SYSTEMMEM`` texture for
|
|
|
|
locking.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``swap-discard``
|
|
|
|
Use ``D3DSWAPEFFECT_DISCARD``, which might be faster.
|
|
|
|
Might be slower too, as it must(?) clear every frame.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``exact-backbuffer``
|
2012-08-07 21:53:14 +00:00
|
|
|
Always resize the backbuffer to window size.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``direct3d`` (Windows only)
|
2012-08-07 21:53:14 +00:00
|
|
|
Same as ``direct3d_shaders``, but with the options ``disable-textures``
|
|
|
|
and ``disable-shaders`` forced.
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
|
2014-04-19 13:29:05 +00:00
|
|
|
.. note:: This driver is for compatibility with old systems.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``opengl``
|
2012-09-29 16:36:05 +00:00
|
|
|
OpenGL video output driver. It supports extended scaling methods, dithering
|
|
|
|
and color management.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2012-10-23 23:06:00 +00:00
|
|
|
By default, it tries to use fast and fail-safe settings. Use the alias
|
2012-11-15 13:25:20 +00:00
|
|
|
``opengl-hq`` to use this driver with defaults set to high quality
|
2012-10-23 23:06:00 +00:00
|
|
|
rendering.
|
2012-09-23 14:10:00 +00:00
|
|
|
|
2015-01-20 20:15:04 +00:00
|
|
|
Requires at least OpenGL 2.1.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2012-10-14 21:58:49 +00:00
|
|
|
Some features are available with OpenGL 3 capable graphics drivers only
|
|
|
|
(or if the necessary extensions are available).
|
2012-10-02 23:54:13 +00:00
|
|
|
|
2015-01-23 16:09:25 +00:00
|
|
|
OpenGL ES 2.0 and 3.0 are supported as well.
|
|
|
|
|
2013-11-03 23:00:18 +00:00
|
|
|
Hardware decoding over OpenGL-interop is supported to some degree. Note
|
|
|
|
that in this mode, some corner case might not be gracefully handled, and
|
2014-09-01 02:25:57 +00:00
|
|
|
color space conversion and chroma upsampling is generally in the hand of
|
2013-11-03 23:00:18 +00:00
|
|
|
the hardware decoder APIs.
|
|
|
|
|
2015-01-20 20:46:19 +00:00
|
|
|
``scale=<filter>``
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``bilinear``
|
2015-01-21 22:08:41 +00:00
|
|
|
Bilinear hardware texture filtering (fastest, very low quality).
|
|
|
|
This is the default for compatibility reasons.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2014-04-17 19:53:42 +00:00
|
|
|
``spline36``
|
2015-01-21 21:22:42 +00:00
|
|
|
Mid quality and speed. This is the default when using ``opengl-hq``.
|
2014-04-17 19:53:42 +00:00
|
|
|
|
2015-01-21 22:08:41 +00:00
|
|
|
``lanczos``
|
|
|
|
Lanczos scaling. Provides mid quality and speed. Generally worse
|
|
|
|
than ``spline36``, but it results in a slightly sharper image
|
|
|
|
which is good for some content types. The number of taps can be
|
2015-01-20 20:46:19 +00:00
|
|
|
controlled with ``scale-radius``, but is best left unchanged.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2015-01-23 16:09:25 +00:00
|
|
|
This filter corresponds to the old ``lanczos3`` alias if the default
|
|
|
|
radius is used, while ``lanczos2`` corresponds to a radius of 2.
|
2015-01-22 19:06:27 +00:00
|
|
|
|
vo_opengl: separate kernel and window
This makes the core much more elegant, reusable, reconfigurable and also
allows us to more easily add aliases for specific configurations.
Furthermore, this lets us apply a generic blur factor / window function
to arbitrary filters, so we can finally "mix and match" in order to
fine-tune windowing functions.
A few notes are in order:
1. The current system for configuring scalers is ugly and rapidly
getting unwieldy. I modified the man page to make it a bit more
bearable, but long-term we have to do something about it; especially
since..
2. There's currently no way to affect the blur factor or parameters of
the window functions themselves. For example, I can't actually
fine-tune the kaiser window's param1, since there's simply no way to
do so in the current API - even though filter_kernels.c supports it
just fine!
3. This removes some lesser used filters (especially those which are
purely window functions to begin with). If anybody asks, you can get
eg. the old behavior of scale=hanning by using
scale=box:scale-window=hanning:scale-radius=1 (and yes, the result is
just as terrible as that sounds - which is why nobody should have
been using them in the first place).
4. This changes the semantics of the "triangle" scaler slightly - it now
has an arbitrary radius. This can possibly produce weird results for
people who were previously using scale-down=triangle, especially if
in combination with scale-radius (for the usual upscaling). The
correct fix for this is to use scale-down=bilinear_slow instead,
which is an alias for triangle at radius 1.
In regards to the last point, in future I want to make it so that
filters have a filter-specific "preferred radius" (for the ones that
are arbitrarily tunable), once the configuration system for filters has
been redesigned (in particular in a way that will let us separate scale
and scale-down cleanly). That way, "triangle" can simply have the
preferred radius of 1 by default, while still being tunable. (Rather
than the default radius being hard-coded to 3 always)
2015-03-25 03:40:28 +00:00
|
|
|
(This filter is an alias for ``sinc``-windowed ``sinc``)
|
|
|
|
|
2015-01-21 22:08:41 +00:00
|
|
|
``ewa_lanczos``
|
|
|
|
Elliptic weighted average Lanczos scaling. Also known as Jinc.
|
2015-02-23 23:52:17 +00:00
|
|
|
Relatively slow, but very good quality. The radius can be
|
|
|
|
controlled with ``scale-radius``. Increasing the radius makes the
|
2015-01-20 20:46:19 +00:00
|
|
|
filter sharper but adds more ringing.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
vo_opengl: separate kernel and window
This makes the core much more elegant, reusable, reconfigurable and also
allows us to more easily add aliases for specific configurations.
Furthermore, this lets us apply a generic blur factor / window function
to arbitrary filters, so we can finally "mix and match" in order to
fine-tune windowing functions.
A few notes are in order:
1. The current system for configuring scalers is ugly and rapidly
getting unwieldy. I modified the man page to make it a bit more
bearable, but long-term we have to do something about it; especially
since..
2. There's currently no way to affect the blur factor or parameters of
the window functions themselves. For example, I can't actually
fine-tune the kaiser window's param1, since there's simply no way to
do so in the current API - even though filter_kernels.c supports it
just fine!
3. This removes some lesser used filters (especially those which are
purely window functions to begin with). If anybody asks, you can get
eg. the old behavior of scale=hanning by using
scale=box:scale-window=hanning:scale-radius=1 (and yes, the result is
just as terrible as that sounds - which is why nobody should have
been using them in the first place).
4. This changes the semantics of the "triangle" scaler slightly - it now
has an arbitrary radius. This can possibly produce weird results for
people who were previously using scale-down=triangle, especially if
in combination with scale-radius (for the usual upscaling). The
correct fix for this is to use scale-down=bilinear_slow instead,
which is an alias for triangle at radius 1.
In regards to the last point, in future I want to make it so that
filters have a filter-specific "preferred radius" (for the ones that
are arbitrarily tunable), once the configuration system for filters has
been redesigned (in particular in a way that will let us separate scale
and scale-down cleanly). That way, "triangle" can simply have the
preferred radius of 1 by default, while still being tunable. (Rather
than the default radius being hard-coded to 3 always)
2015-03-25 03:40:28 +00:00
|
|
|
(This filter is an alias for ``jinc``-windowed ``jinc``)
|
|
|
|
|
2015-02-23 23:52:17 +00:00
|
|
|
``ewa_lanczossharp``
|
|
|
|
A slightly sharpened version of ewa_lanczos, preconfigured to use
|
|
|
|
an ideal radius and parameter. If your hardware can run it, this is
|
|
|
|
probably what you should use by default.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``mitchell``
|
2015-02-23 17:55:31 +00:00
|
|
|
Mitchell-Netravali. The ``B`` and ``C`` parameters can be set with
|
|
|
|
``scale-param1`` and ``scale-param2``. This filter is very good at
|
vo_opengl: refactor scaler configuration
This merges all of the scaler-related options into a single
configuration struct, and also cleans up the way they're passed through
the code. (For example, the scaler index is no longer threaded through
pass_sample, just the scaler configuration itself, and there's no longer
duplication of the params etc.)
In addition, this commit makes scale-down more principled, and turns it
into a scaler in its own right - so there's no longer an ugly separation
between scale and scale-down in the code.
Finally, the radius stuff has been made more proper - filters always
have a radius now (there's no more radius -1), and get a new .resizable
attribute instead for when it's tunable.
User-visible changes:
1. scale-down has been renamed dscale and now has its own set of config
options (dscale-param1, dscale-radius) etc., instead of reusing
scale-param1 (which was arguably a bug).
2. The default radius is no longer fixed at 3, but instead uses that
filter's preferred radius by default. (Scalers with a default radius
other than 3 include sinc, gaussian, box and triangle)
3. scale-radius etc. now goes down to 0.5, rather than 1.0. 0.5 is the
smallest radius that theoretically makes sense, and indeed it's used
by at least one filter (nearest).
Apart from that, it should just be internal changes only.
Note that this sets up for the refactor discussed in #1720, which would
be to merge scaler and window configurations (include parameters etc.)
into a single, simplified string. In the code, this would now basically
just mean getting rid of all the OPT_FLOATRANGE etc. lines related to
scalers and replacing them by a single function that parses a string and
updates the struct scaler_config as appropriate.
2015-03-26 00:55:32 +00:00
|
|
|
downscaling (see ``dscale``).
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2015-03-15 06:11:51 +00:00
|
|
|
``oversample``
|
|
|
|
A version of nearest neighbour that (naively) oversamples pixels,
|
|
|
|
so that pixels overlapping edges get linearly interpolated instead
|
|
|
|
of rounded. This essentially removes the small imperfections and
|
|
|
|
judder artifacts caused by nearest-neighbour interpolation, in
|
|
|
|
exchange for adding some blur. This filter is good at temporal
|
|
|
|
interpolation, and also known as "smoothmotion" (see ``tscale``).
|
|
|
|
|
2015-01-21 21:22:42 +00:00
|
|
|
There are some more filters, but most are not as useful. For a complete
|
|
|
|
list, pass ``help`` as value, e.g.::
|
2013-09-08 10:02:30 +00:00
|
|
|
|
2015-01-20 20:46:19 +00:00
|
|
|
mpv --vo=opengl:scale=help
|
2013-07-22 00:14:15 +00:00
|
|
|
|
2015-02-23 17:55:31 +00:00
|
|
|
``scale-param1=<value>``, ``scale-param2=<value>``
|
|
|
|
Set filter parameters. Ignored if the filter is not tunable.
|
|
|
|
Currently, this affects the following filter parameters:
|
2012-08-07 21:53:14 +00:00
|
|
|
|
vo_opengl: separate kernel and window
This makes the core much more elegant, reusable, reconfigurable and also
allows us to more easily add aliases for specific configurations.
Furthermore, this lets us apply a generic blur factor / window function
to arbitrary filters, so we can finally "mix and match" in order to
fine-tune windowing functions.
A few notes are in order:
1. The current system for configuring scalers is ugly and rapidly
getting unwieldy. I modified the man page to make it a bit more
bearable, but long-term we have to do something about it; especially
since..
2. There's currently no way to affect the blur factor or parameters of
the window functions themselves. For example, I can't actually
fine-tune the kaiser window's param1, since there's simply no way to
do so in the current API - even though filter_kernels.c supports it
just fine!
3. This removes some lesser used filters (especially those which are
purely window functions to begin with). If anybody asks, you can get
eg. the old behavior of scale=hanning by using
scale=box:scale-window=hanning:scale-radius=1 (and yes, the result is
just as terrible as that sounds - which is why nobody should have
been using them in the first place).
4. This changes the semantics of the "triangle" scaler slightly - it now
has an arbitrary radius. This can possibly produce weird results for
people who were previously using scale-down=triangle, especially if
in combination with scale-radius (for the usual upscaling). The
correct fix for this is to use scale-down=bilinear_slow instead,
which is an alias for triangle at radius 1.
In regards to the last point, in future I want to make it so that
filters have a filter-specific "preferred radius" (for the ones that
are arbitrarily tunable), once the configuration system for filters has
been redesigned (in particular in a way that will let us separate scale
and scale-down cleanly). That way, "triangle" can simply have the
preferred radius of 1 by default, while still being tunable. (Rather
than the default radius being hard-coded to 3 always)
2015-03-25 03:40:28 +00:00
|
|
|
bcspline
|
|
|
|
Spline parameters (``B`` and ``C``). Defaults to 0.5 for both.
|
2015-02-23 17:55:31 +00:00
|
|
|
|
vo_opengl: separate kernel and window
This makes the core much more elegant, reusable, reconfigurable and also
allows us to more easily add aliases for specific configurations.
Furthermore, this lets us apply a generic blur factor / window function
to arbitrary filters, so we can finally "mix and match" in order to
fine-tune windowing functions.
A few notes are in order:
1. The current system for configuring scalers is ugly and rapidly
getting unwieldy. I modified the man page to make it a bit more
bearable, but long-term we have to do something about it; especially
since..
2. There's currently no way to affect the blur factor or parameters of
the window functions themselves. For example, I can't actually
fine-tune the kaiser window's param1, since there's simply no way to
do so in the current API - even though filter_kernels.c supports it
just fine!
3. This removes some lesser used filters (especially those which are
purely window functions to begin with). If anybody asks, you can get
eg. the old behavior of scale=hanning by using
scale=box:scale-window=hanning:scale-radius=1 (and yes, the result is
just as terrible as that sounds - which is why nobody should have
been using them in the first place).
4. This changes the semantics of the "triangle" scaler slightly - it now
has an arbitrary radius. This can possibly produce weird results for
people who were previously using scale-down=triangle, especially if
in combination with scale-radius (for the usual upscaling). The
correct fix for this is to use scale-down=bilinear_slow instead,
which is an alias for triangle at radius 1.
In regards to the last point, in future I want to make it so that
filters have a filter-specific "preferred radius" (for the ones that
are arbitrarily tunable), once the configuration system for filters has
been redesigned (in particular in a way that will let us separate scale
and scale-down cleanly). That way, "triangle" can simply have the
preferred radius of 1 by default, while still being tunable. (Rather
than the default radius being hard-coded to 3 always)
2015-03-25 03:40:28 +00:00
|
|
|
gaussian
|
2015-02-23 17:55:31 +00:00
|
|
|
Scale parameter (``t``). Increasing this makes the result blurrier.
|
|
|
|
Defaults to 1.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
vo_opengl: separate kernel and window
This makes the core much more elegant, reusable, reconfigurable and also
allows us to more easily add aliases for specific configurations.
Furthermore, this lets us apply a generic blur factor / window function
to arbitrary filters, so we can finally "mix and match" in order to
fine-tune windowing functions.
A few notes are in order:
1. The current system for configuring scalers is ugly and rapidly
getting unwieldy. I modified the man page to make it a bit more
bearable, but long-term we have to do something about it; especially
since..
2. There's currently no way to affect the blur factor or parameters of
the window functions themselves. For example, I can't actually
fine-tune the kaiser window's param1, since there's simply no way to
do so in the current API - even though filter_kernels.c supports it
just fine!
3. This removes some lesser used filters (especially those which are
purely window functions to begin with). If anybody asks, you can get
eg. the old behavior of scale=hanning by using
scale=box:scale-window=hanning:scale-radius=1 (and yes, the result is
just as terrible as that sounds - which is why nobody should have
been using them in the first place).
4. This changes the semantics of the "triangle" scaler slightly - it now
has an arbitrary radius. This can possibly produce weird results for
people who were previously using scale-down=triangle, especially if
in combination with scale-radius (for the usual upscaling). The
correct fix for this is to use scale-down=bilinear_slow instead,
which is an alias for triangle at radius 1.
In regards to the last point, in future I want to make it so that
filters have a filter-specific "preferred radius" (for the ones that
are arbitrarily tunable), once the configuration system for filters has
been redesigned (in particular in a way that will let us separate scale
and scale-down cleanly). That way, "triangle" can simply have the
preferred radius of 1 by default, while still being tunable. (Rather
than the default radius being hard-coded to 3 always)
2015-03-25 03:40:28 +00:00
|
|
|
sharpen3, sharpen5
|
vo_opengl: refactor shader generation (part 2)
This adds stuff related to gamma, linear light, sigmoid, BT.2020-CL,
etc, as well as color management. Also adds a new gamma function (gamma22).
This adds new parameters to configure the CMS settings, in particular
letting us target simple colorspaces without requiring usage of a 3DLUT.
This adds smoothmotion. Mostly working, but it's still sensitive to
timing issues. It's based on an actual queue now, but the queue size
is kept small to avoid larger amounts of latency.
Also makes “upscale before blending” the default strategy.
This is justified because the "render after blending" thing doesn't seme
to work consistently any way (introduces stutter due to the way vsync
timing works, or something), so this behavior is a bit closer to master
and makes pausing/unpausing less weird/jumpy.
This adds the remaining scalers, including bicubic_fast, sharpen3,
sharpen5, polar filters and antiringing. Apparently, sharpen3/5 also
consult scale-param1, which was undocumented in master.
This also implements cropping and chroma transformation, plus
rotation/flipping. These are inherently part of the same logic, although
it's a bit rough around the edges in some case, mainly due to the fallback
code paths (for bilinear scaling without indirection).
2015-03-12 21:18:16 +00:00
|
|
|
Sharpening strength. Increasing this makes the image sharper but
|
|
|
|
adds more ringing and aliasing. Defaults to 0.5.
|
|
|
|
|
vo_opengl: separate kernel and window
This makes the core much more elegant, reusable, reconfigurable and also
allows us to more easily add aliases for specific configurations.
Furthermore, this lets us apply a generic blur factor / window function
to arbitrary filters, so we can finally "mix and match" in order to
fine-tune windowing functions.
A few notes are in order:
1. The current system for configuring scalers is ugly and rapidly
getting unwieldy. I modified the man page to make it a bit more
bearable, but long-term we have to do something about it; especially
since..
2. There's currently no way to affect the blur factor or parameters of
the window functions themselves. For example, I can't actually
fine-tune the kaiser window's param1, since there's simply no way to
do so in the current API - even though filter_kernels.c supports it
just fine!
3. This removes some lesser used filters (especially those which are
purely window functions to begin with). If anybody asks, you can get
eg. the old behavior of scale=hanning by using
scale=box:scale-window=hanning:scale-radius=1 (and yes, the result is
just as terrible as that sounds - which is why nobody should have
been using them in the first place).
4. This changes the semantics of the "triangle" scaler slightly - it now
has an arbitrary radius. This can possibly produce weird results for
people who were previously using scale-down=triangle, especially if
in combination with scale-radius (for the usual upscaling). The
correct fix for this is to use scale-down=bilinear_slow instead,
which is an alias for triangle at radius 1.
In regards to the last point, in future I want to make it so that
filters have a filter-specific "preferred radius" (for the ones that
are arbitrarily tunable), once the configuration system for filters has
been redesigned (in particular in a way that will let us separate scale
and scale-down cleanly). That way, "triangle" can simply have the
preferred radius of 1 by default, while still being tunable. (Rather
than the default radius being hard-coded to 3 always)
2015-03-25 03:40:28 +00:00
|
|
|
oversample
|
2015-03-15 05:27:11 +00:00
|
|
|
Minimum distance to an edge before interpolation is used. Setting
|
|
|
|
this to 0 will always interpolate edges, whereas setting it to 0.5
|
|
|
|
will never interpolate, thus behaving as if the regular nearest
|
|
|
|
neighbour algorithm was used. Defaults to 0.0.
|
|
|
|
|
vo_opengl: separate kernel and window
This makes the core much more elegant, reusable, reconfigurable and also
allows us to more easily add aliases for specific configurations.
Furthermore, this lets us apply a generic blur factor / window function
to arbitrary filters, so we can finally "mix and match" in order to
fine-tune windowing functions.
A few notes are in order:
1. The current system for configuring scalers is ugly and rapidly
getting unwieldy. I modified the man page to make it a bit more
bearable, but long-term we have to do something about it; especially
since..
2. There's currently no way to affect the blur factor or parameters of
the window functions themselves. For example, I can't actually
fine-tune the kaiser window's param1, since there's simply no way to
do so in the current API - even though filter_kernels.c supports it
just fine!
3. This removes some lesser used filters (especially those which are
purely window functions to begin with). If anybody asks, you can get
eg. the old behavior of scale=hanning by using
scale=box:scale-window=hanning:scale-radius=1 (and yes, the result is
just as terrible as that sounds - which is why nobody should have
been using them in the first place).
4. This changes the semantics of the "triangle" scaler slightly - it now
has an arbitrary radius. This can possibly produce weird results for
people who were previously using scale-down=triangle, especially if
in combination with scale-radius (for the usual upscaling). The
correct fix for this is to use scale-down=bilinear_slow instead,
which is an alias for triangle at radius 1.
In regards to the last point, in future I want to make it so that
filters have a filter-specific "preferred radius" (for the ones that
are arbitrarily tunable), once the configuration system for filters has
been redesigned (in particular in a way that will let us separate scale
and scale-down cleanly). That way, "triangle" can simply have the
preferred radius of 1 by default, while still being tunable. (Rather
than the default radius being hard-coded to 3 always)
2015-03-25 03:40:28 +00:00
|
|
|
``scale-blur=<value>``
|
|
|
|
Kernel scaling factor (also known as a blur factor). Decreasing this
|
|
|
|
makes the result sharper, increasing it makes it blurrier (default 0).
|
|
|
|
If set to 0, the kernel's preferred blur factor is used. Note that
|
|
|
|
setting this too low (eg. 0.5) leads to bad results. It's generally
|
|
|
|
recommended to stick to values between 0.8 and 1.2.
|
|
|
|
|
|
|
|
``scale-radius=<value>``
|
vo_opengl: refactor scaler configuration
This merges all of the scaler-related options into a single
configuration struct, and also cleans up the way they're passed through
the code. (For example, the scaler index is no longer threaded through
pass_sample, just the scaler configuration itself, and there's no longer
duplication of the params etc.)
In addition, this commit makes scale-down more principled, and turns it
into a scaler in its own right - so there's no longer an ugly separation
between scale and scale-down in the code.
Finally, the radius stuff has been made more proper - filters always
have a radius now (there's no more radius -1), and get a new .resizable
attribute instead for when it's tunable.
User-visible changes:
1. scale-down has been renamed dscale and now has its own set of config
options (dscale-param1, dscale-radius) etc., instead of reusing
scale-param1 (which was arguably a bug).
2. The default radius is no longer fixed at 3, but instead uses that
filter's preferred radius by default. (Scalers with a default radius
other than 3 include sinc, gaussian, box and triangle)
3. scale-radius etc. now goes down to 0.5, rather than 1.0. 0.5 is the
smallest radius that theoretically makes sense, and indeed it's used
by at least one filter (nearest).
Apart from that, it should just be internal changes only.
Note that this sets up for the refactor discussed in #1720, which would
be to merge scaler and window configurations (include parameters etc.)
into a single, simplified string. In the code, this would now basically
just mean getting rid of all the OPT_FLOATRANGE etc. lines related to
scalers and replacing them by a single function that parses a string and
updates the struct scaler_config as appropriate.
2015-03-26 00:55:32 +00:00
|
|
|
Set radius for filters listed below, must be a float number between 0.5
|
|
|
|
and 16.0. Defaults to the filter's preferred radius if not specified.
|
2014-08-25 22:41:30 +00:00
|
|
|
|
vo_opengl: separate kernel and window
This makes the core much more elegant, reusable, reconfigurable and also
allows us to more easily add aliases for specific configurations.
Furthermore, this lets us apply a generic blur factor / window function
to arbitrary filters, so we can finally "mix and match" in order to
fine-tune windowing functions.
A few notes are in order:
1. The current system for configuring scalers is ugly and rapidly
getting unwieldy. I modified the man page to make it a bit more
bearable, but long-term we have to do something about it; especially
since..
2. There's currently no way to affect the blur factor or parameters of
the window functions themselves. For example, I can't actually
fine-tune the kaiser window's param1, since there's simply no way to
do so in the current API - even though filter_kernels.c supports it
just fine!
3. This removes some lesser used filters (especially those which are
purely window functions to begin with). If anybody asks, you can get
eg. the old behavior of scale=hanning by using
scale=box:scale-window=hanning:scale-radius=1 (and yes, the result is
just as terrible as that sounds - which is why nobody should have
been using them in the first place).
4. This changes the semantics of the "triangle" scaler slightly - it now
has an arbitrary radius. This can possibly produce weird results for
people who were previously using scale-down=triangle, especially if
in combination with scale-radius (for the usual upscaling). The
correct fix for this is to use scale-down=bilinear_slow instead,
which is an alias for triangle at radius 1.
In regards to the last point, in future I want to make it so that
filters have a filter-specific "preferred radius" (for the ones that
are arbitrarily tunable), once the configuration system for filters has
been redesigned (in particular in a way that will let us separate scale
and scale-down cleanly). That way, "triangle" can simply have the
preferred radius of 1 by default, while still being tunable. (Rather
than the default radius being hard-coded to 3 always)
2015-03-25 03:40:28 +00:00
|
|
|
``sinc`` and derivatives, ``jinc`` and derivatives, ``gaussian``, ``box`` and ``triangle``
|
2014-08-25 22:41:30 +00:00
|
|
|
|
|
|
|
Note that depending on filter implementation details and video scaling
|
|
|
|
ratio, the radius that actually being used might be different
|
|
|
|
(most likely being increased a bit).
|
|
|
|
|
2015-01-20 20:46:19 +00:00
|
|
|
``scale-antiring=<value>``
|
2015-01-18 17:57:12 +00:00
|
|
|
Set the antiringing strength. This tries to eliminate ringing, but can
|
|
|
|
introduce other artifacts in the process. Must be a float number
|
|
|
|
between 0.0 and 1.0. The default value of 0.0 disables antiringing
|
|
|
|
entirely.
|
|
|
|
|
2015-02-27 03:32:22 +00:00
|
|
|
Note that this doesn't affect the special filters ``bilinear``,
|
|
|
|
``bicubic_fast`` or ``sharpen``.
|
2015-01-18 17:57:12 +00:00
|
|
|
|
vo_opengl: separate kernel and window
This makes the core much more elegant, reusable, reconfigurable and also
allows us to more easily add aliases for specific configurations.
Furthermore, this lets us apply a generic blur factor / window function
to arbitrary filters, so we can finally "mix and match" in order to
fine-tune windowing functions.
A few notes are in order:
1. The current system for configuring scalers is ugly and rapidly
getting unwieldy. I modified the man page to make it a bit more
bearable, but long-term we have to do something about it; especially
since..
2. There's currently no way to affect the blur factor or parameters of
the window functions themselves. For example, I can't actually
fine-tune the kaiser window's param1, since there's simply no way to
do so in the current API - even though filter_kernels.c supports it
just fine!
3. This removes some lesser used filters (especially those which are
purely window functions to begin with). If anybody asks, you can get
eg. the old behavior of scale=hanning by using
scale=box:scale-window=hanning:scale-radius=1 (and yes, the result is
just as terrible as that sounds - which is why nobody should have
been using them in the first place).
4. This changes the semantics of the "triangle" scaler slightly - it now
has an arbitrary radius. This can possibly produce weird results for
people who were previously using scale-down=triangle, especially if
in combination with scale-radius (for the usual upscaling). The
correct fix for this is to use scale-down=bilinear_slow instead,
which is an alias for triangle at radius 1.
In regards to the last point, in future I want to make it so that
filters have a filter-specific "preferred radius" (for the ones that
are arbitrarily tunable), once the configuration system for filters has
been redesigned (in particular in a way that will let us separate scale
and scale-down cleanly). That way, "triangle" can simply have the
preferred radius of 1 by default, while still being tunable. (Rather
than the default radius being hard-coded to 3 always)
2015-03-25 03:40:28 +00:00
|
|
|
``scale-window=<window>``
|
|
|
|
(Advanced users only) Choose a custom windowing function for the kernel.
|
|
|
|
Defaults to the filter's preferred window if unset. Use
|
|
|
|
``scale-window=help`` to get a list of supported windowing functions.
|
|
|
|
|
2015-03-27 05:18:32 +00:00
|
|
|
``scale-wparam=<window>``
|
|
|
|
(Advanced users only) Configure the parameter for the window function
|
|
|
|
given by ``scale-window``. Ignored if the window is not tunable.
|
|
|
|
Currently, this affects the following window parameters:
|
|
|
|
|
|
|
|
kaiser
|
|
|
|
Window parameter (alpha). Defaults to 6.33.
|
|
|
|
blackman
|
|
|
|
Window parameter (alpha). Defaults to 0.16.
|
|
|
|
gaussian
|
|
|
|
Scale parameter (t). Increasing this makes the window wider.
|
|
|
|
Defaults to 1.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``scaler-resizes-only``
|
2013-05-25 21:47:55 +00:00
|
|
|
Disable the scaler if the video image is not resized. In that case,
|
2015-01-20 20:46:19 +00:00
|
|
|
``bilinear`` is used instead whatever is set with ``scale``. Bilinear
|
2013-05-25 21:47:55 +00:00
|
|
|
will reproduce the source image perfectly if no scaling is performed.
|
2015-01-20 20:46:19 +00:00
|
|
|
Note that this option never affects ``cscale``.
|
2013-05-25 21:47:55 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``pbo``
|
2013-10-23 15:50:49 +00:00
|
|
|
Enable use of PBOs. This is slightly faster, but can sometimes lead to
|
|
|
|
sporadic and temporary image corruption (in theory, because reupload
|
|
|
|
is not retried when it fails), and perhaps actually triggers slower
|
|
|
|
paths with drivers that don't support PBOs properly.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``dither-depth=<N|no|auto>``
|
2013-04-18 21:41:32 +00:00
|
|
|
Set dither target depth to N. Default: no.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2013-03-28 20:39:17 +00:00
|
|
|
no
|
2012-10-11 00:04:08 +00:00
|
|
|
Disable any dithering done by mpv.
|
2013-03-28 20:39:17 +00:00
|
|
|
auto
|
2013-07-08 16:02:14 +00:00
|
|
|
Automatic selection. If output bit depth cannot be detected,
|
2012-08-07 21:53:14 +00:00
|
|
|
8 bits per component are assumed.
|
|
|
|
8
|
|
|
|
Dither to 8 bit output.
|
|
|
|
|
|
|
|
Note that the depth of the connected video display device can not be
|
|
|
|
detected. Often, LCD panels will do dithering on their own, which
|
2013-07-08 16:02:14 +00:00
|
|
|
conflicts with ``opengl``'s dithering and leads to ugly output.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``dither-size-fruit=<2-8>``
|
2013-05-25 23:48:39 +00:00
|
|
|
Set the size of the dither matrix (default: 6). The actual size of
|
2013-05-27 21:41:37 +00:00
|
|
|
the matrix is ``(2^N) x (2^N)`` for an option value of ``N``, so a
|
2013-05-25 23:48:39 +00:00
|
|
|
value of 6 gives a size of 64x64. The matrix is generated at startup
|
|
|
|
time, and a large matrix can take rather long to compute (seconds).
|
|
|
|
|
2013-05-26 17:37:59 +00:00
|
|
|
Used in ``dither=fruit`` mode only.
|
2013-05-25 23:48:39 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``dither=<fruit|ordered|no>``
|
2015-01-23 16:09:25 +00:00
|
|
|
Select dithering algorithm (default: fruit). (Normally, the
|
|
|
|
``dither-depth`` option controls whether dithering is enabled.)
|
2013-05-25 23:48:39 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``temporal-dither``
|
2013-05-25 23:48:39 +00:00
|
|
|
Enable temporal dithering. (Only active if dithering is enabled in
|
|
|
|
general.) This changes between 8 different dithering pattern on each
|
|
|
|
frame by changing the orientation of the tiled dithering matrix.
|
|
|
|
Unfortunately, this can lead to flicker on LCD displays, since these
|
|
|
|
have a high reaction time.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``debug``
|
|
|
|
Check for OpenGL errors, i.e. call ``glGetError()``. Also request a
|
2012-08-07 21:53:14 +00:00
|
|
|
debug OpenGL context (which does nothing with current graphics drivers
|
|
|
|
as of this writing).
|
|
|
|
|
2015-03-13 18:30:31 +00:00
|
|
|
``interpolation``
|
|
|
|
Reduce stuttering caused by mismatches in the video fps and display
|
|
|
|
refresh rate (also known as judder).
|
|
|
|
|
|
|
|
This essentially attempts to interpolate the missing frames by
|
|
|
|
convoluting the video along the temporal axis. The filter used can be
|
|
|
|
controlled using the ``tscale`` setting.
|
|
|
|
|
|
|
|
Note that this relies on vsync to work, see ``swapinterval`` for more
|
|
|
|
information.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``swapinterval=<n>``
|
2012-08-22 13:45:34 +00:00
|
|
|
Interval in displayed frames between two buffer swaps.
|
2015-03-08 23:19:50 +00:00
|
|
|
1 is equivalent to enable VSYNC, 0 to disable VSYNC. Defaults to 1 if
|
|
|
|
not specified.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2015-03-13 18:30:31 +00:00
|
|
|
Note that this depends on proper OpenGL vsync support. On some platforms
|
|
|
|
and drivers, this only works reliably when in fullscreen mode. It may
|
|
|
|
also require driver-specific hacks if using multiple monitors, to
|
|
|
|
ensure mpv syncs to the right one. Compositing window managers can
|
|
|
|
also lead to bad results, as can missing or incorrect display FPS
|
|
|
|
information (see ``--display-fps``).
|
|
|
|
|
vo_opengl: refactor scaler configuration
This merges all of the scaler-related options into a single
configuration struct, and also cleans up the way they're passed through
the code. (For example, the scaler index is no longer threaded through
pass_sample, just the scaler configuration itself, and there's no longer
duplication of the params etc.)
In addition, this commit makes scale-down more principled, and turns it
into a scaler in its own right - so there's no longer an ugly separation
between scale and scale-down in the code.
Finally, the radius stuff has been made more proper - filters always
have a radius now (there's no more radius -1), and get a new .resizable
attribute instead for when it's tunable.
User-visible changes:
1. scale-down has been renamed dscale and now has its own set of config
options (dscale-param1, dscale-radius) etc., instead of reusing
scale-param1 (which was arguably a bug).
2. The default radius is no longer fixed at 3, but instead uses that
filter's preferred radius by default. (Scalers with a default radius
other than 3 include sinc, gaussian, box and triangle)
3. scale-radius etc. now goes down to 0.5, rather than 1.0. 0.5 is the
smallest radius that theoretically makes sense, and indeed it's used
by at least one filter (nearest).
Apart from that, it should just be internal changes only.
Note that this sets up for the refactor discussed in #1720, which would
be to merge scaler and window configurations (include parameters etc.)
into a single, simplified string. In the code, this would now basically
just mean getting rid of all the OPT_FLOATRANGE etc. lines related to
scalers and replacing them by a single function that parses a string and
updates the struct scaler_config as appropriate.
2015-03-26 00:55:32 +00:00
|
|
|
``dscale=<filter>``
|
|
|
|
Like ``scale``, but apply these filters on downscaling instead. If this
|
|
|
|
option is unset, the filter implied by ``scale`` will be applied.
|
|
|
|
|
2014-11-14 14:22:37 +00:00
|
|
|
``cscale=<filter>``
|
2015-01-20 20:46:19 +00:00
|
|
|
As ``scale``, but for interpolating chroma information. If the image
|
2015-03-13 00:59:10 +00:00
|
|
|
is not subsampled, this option is ignored entirely.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
vo_opengl: separate kernel and window
This makes the core much more elegant, reusable, reconfigurable and also
allows us to more easily add aliases for specific configurations.
Furthermore, this lets us apply a generic blur factor / window function
to arbitrary filters, so we can finally "mix and match" in order to
fine-tune windowing functions.
A few notes are in order:
1. The current system for configuring scalers is ugly and rapidly
getting unwieldy. I modified the man page to make it a bit more
bearable, but long-term we have to do something about it; especially
since..
2. There's currently no way to affect the blur factor or parameters of
the window functions themselves. For example, I can't actually
fine-tune the kaiser window's param1, since there's simply no way to
do so in the current API - even though filter_kernels.c supports it
just fine!
3. This removes some lesser used filters (especially those which are
purely window functions to begin with). If anybody asks, you can get
eg. the old behavior of scale=hanning by using
scale=box:scale-window=hanning:scale-radius=1 (and yes, the result is
just as terrible as that sounds - which is why nobody should have
been using them in the first place).
4. This changes the semantics of the "triangle" scaler slightly - it now
has an arbitrary radius. This can possibly produce weird results for
people who were previously using scale-down=triangle, especially if
in combination with scale-radius (for the usual upscaling). The
correct fix for this is to use scale-down=bilinear_slow instead,
which is an alias for triangle at radius 1.
In regards to the last point, in future I want to make it so that
filters have a filter-specific "preferred radius" (for the ones that
are arbitrarily tunable), once the configuration system for filters has
been redesigned (in particular in a way that will let us separate scale
and scale-down cleanly). That way, "triangle" can simply have the
preferred radius of 1 by default, while still being tunable. (Rather
than the default radius being hard-coded to 3 always)
2015-03-25 03:40:28 +00:00
|
|
|
``tscale=<filter>``
|
2015-03-13 18:30:31 +00:00
|
|
|
The filter used for interpolating the temporal axis (frames). This is
|
|
|
|
only used if ``interpolation`` is enabled. The only valid choices
|
|
|
|
for ``tscale`` are separable convolution filters (use ``tscale=help``
|
vo_opengl: separate kernel and window
This makes the core much more elegant, reusable, reconfigurable and also
allows us to more easily add aliases for specific configurations.
Furthermore, this lets us apply a generic blur factor / window function
to arbitrary filters, so we can finally "mix and match" in order to
fine-tune windowing functions.
A few notes are in order:
1. The current system for configuring scalers is ugly and rapidly
getting unwieldy. I modified the man page to make it a bit more
bearable, but long-term we have to do something about it; especially
since..
2. There's currently no way to affect the blur factor or parameters of
the window functions themselves. For example, I can't actually
fine-tune the kaiser window's param1, since there's simply no way to
do so in the current API - even though filter_kernels.c supports it
just fine!
3. This removes some lesser used filters (especially those which are
purely window functions to begin with). If anybody asks, you can get
eg. the old behavior of scale=hanning by using
scale=box:scale-window=hanning:scale-radius=1 (and yes, the result is
just as terrible as that sounds - which is why nobody should have
been using them in the first place).
4. This changes the semantics of the "triangle" scaler slightly - it now
has an arbitrary radius. This can possibly produce weird results for
people who were previously using scale-down=triangle, especially if
in combination with scale-radius (for the usual upscaling). The
correct fix for this is to use scale-down=bilinear_slow instead,
which is an alias for triangle at radius 1.
In regards to the last point, in future I want to make it so that
filters have a filter-specific "preferred radius" (for the ones that
are arbitrarily tunable), once the configuration system for filters has
been redesigned (in particular in a way that will let us separate scale
and scale-down cleanly). That way, "triangle" can simply have the
preferred radius of 1 by default, while still being tunable. (Rather
than the default radius being hard-coded to 3 always)
2015-03-25 03:40:28 +00:00
|
|
|
to get a list). The default is ``oversample``.
|
2015-03-13 18:30:31 +00:00
|
|
|
|
|
|
|
Note that the maximum supported filter radius is currently 3, and that
|
2015-03-15 20:18:16 +00:00
|
|
|
using filters with larger radius may introduce issues when pausing or
|
2015-03-13 18:30:31 +00:00
|
|
|
framestepping, proportional to the radius used. It is recommended to
|
|
|
|
stick to a radius of 1 or 2.
|
|
|
|
|
vo_opengl: refactor scaler configuration
This merges all of the scaler-related options into a single
configuration struct, and also cleans up the way they're passed through
the code. (For example, the scaler index is no longer threaded through
pass_sample, just the scaler configuration itself, and there's no longer
duplication of the params etc.)
In addition, this commit makes scale-down more principled, and turns it
into a scaler in its own right - so there's no longer an ugly separation
between scale and scale-down in the code.
Finally, the radius stuff has been made more proper - filters always
have a radius now (there's no more radius -1), and get a new .resizable
attribute instead for when it's tunable.
User-visible changes:
1. scale-down has been renamed dscale and now has its own set of config
options (dscale-param1, dscale-radius) etc., instead of reusing
scale-param1 (which was arguably a bug).
2. The default radius is no longer fixed at 3, but instead uses that
filter's preferred radius by default. (Scalers with a default radius
other than 3 include sinc, gaussian, box and triangle)
3. scale-radius etc. now goes down to 0.5, rather than 1.0. 0.5 is the
smallest radius that theoretically makes sense, and indeed it's used
by at least one filter (nearest).
Apart from that, it should just be internal changes only.
Note that this sets up for the refactor discussed in #1720, which would
be to merge scaler and window configurations (include parameters etc.)
into a single, simplified string. In the code, this would now basically
just mean getting rid of all the OPT_FLOATRANGE etc. lines related to
scalers and replacing them by a single function that parses a string and
updates the struct scaler_config as appropriate.
2015-03-26 00:55:32 +00:00
|
|
|
``dscale-radius``, ``cscale-radius``, ``tscale-radius``, etc.
|
|
|
|
Set filter parameters for ``dscale``, ``cscale`` and ``tscale``,
|
|
|
|
respectively.
|
vo_opengl: separate kernel and window
This makes the core much more elegant, reusable, reconfigurable and also
allows us to more easily add aliases for specific configurations.
Furthermore, this lets us apply a generic blur factor / window function
to arbitrary filters, so we can finally "mix and match" in order to
fine-tune windowing functions.
A few notes are in order:
1. The current system for configuring scalers is ugly and rapidly
getting unwieldy. I modified the man page to make it a bit more
bearable, but long-term we have to do something about it; especially
since..
2. There's currently no way to affect the blur factor or parameters of
the window functions themselves. For example, I can't actually
fine-tune the kaiser window's param1, since there's simply no way to
do so in the current API - even though filter_kernels.c supports it
just fine!
3. This removes some lesser used filters (especially those which are
purely window functions to begin with). If anybody asks, you can get
eg. the old behavior of scale=hanning by using
scale=box:scale-window=hanning:scale-radius=1 (and yes, the result is
just as terrible as that sounds - which is why nobody should have
been using them in the first place).
4. This changes the semantics of the "triangle" scaler slightly - it now
has an arbitrary radius. This can possibly produce weird results for
people who were previously using scale-down=triangle, especially if
in combination with scale-radius (for the usual upscaling). The
correct fix for this is to use scale-down=bilinear_slow instead,
which is an alias for triangle at radius 1.
In regards to the last point, in future I want to make it so that
filters have a filter-specific "preferred radius" (for the ones that
are arbitrarily tunable), once the configuration system for filters has
been redesigned (in particular in a way that will let us separate scale
and scale-down cleanly). That way, "triangle" can simply have the
preferred radius of 1 by default, while still being tunable. (Rather
than the default radius being hard-coded to 3 always)
2015-03-25 03:40:28 +00:00
|
|
|
|
|
|
|
See the corresponding options for ``scale``.
|
|
|
|
|
2015-02-06 02:37:21 +00:00
|
|
|
``linear-scaling``
|
vo_opengl: refactor shader generation (part 2)
This adds stuff related to gamma, linear light, sigmoid, BT.2020-CL,
etc, as well as color management. Also adds a new gamma function (gamma22).
This adds new parameters to configure the CMS settings, in particular
letting us target simple colorspaces without requiring usage of a 3DLUT.
This adds smoothmotion. Mostly working, but it's still sensitive to
timing issues. It's based on an actual queue now, but the queue size
is kept small to avoid larger amounts of latency.
Also makes “upscale before blending” the default strategy.
This is justified because the "render after blending" thing doesn't seme
to work consistently any way (introduces stutter due to the way vsync
timing works, or something), so this behavior is a bit closer to master
and makes pausing/unpausing less weird/jumpy.
This adds the remaining scalers, including bicubic_fast, sharpen3,
sharpen5, polar filters and antiringing. Apparently, sharpen3/5 also
consult scale-param1, which was undocumented in master.
This also implements cropping and chroma transformation, plus
rotation/flipping. These are inherently part of the same logic, although
it's a bit rough around the edges in some case, mainly due to the fallback
code paths (for bilinear scaling without indirection).
2015-03-12 21:18:16 +00:00
|
|
|
Scale in linear light. This is automatically enabled if
|
|
|
|
``target-prim``, ``target-trc``, ``icc-profile`` or
|
|
|
|
``sigmoid-upscaling`` is set. It should only be used with a
|
|
|
|
``fbo-format`` that has at least 16 bit precision.
|
2015-02-06 02:37:21 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``fancy-downscaling``
|
2012-09-29 16:36:05 +00:00
|
|
|
When using convolution based filters, extend the filter size
|
|
|
|
when downscaling. Trades quality for reduced downscaling performance.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2014-11-28 22:57:06 +00:00
|
|
|
This is automatically disabled for anamorphic video, because this
|
2015-01-23 16:09:25 +00:00
|
|
|
feature doesn't work correctly with different scale factors in
|
|
|
|
different directions.
|
2014-11-28 22:57:06 +00:00
|
|
|
|
2015-01-06 09:47:26 +00:00
|
|
|
``sigmoid-upscaling``
|
2015-02-06 02:37:21 +00:00
|
|
|
When upscaling, use a sigmoidal color transform to avoid emphasizing
|
|
|
|
ringing artifacts. This also enables ``linear-scaling``.
|
2015-01-06 09:47:26 +00:00
|
|
|
|
|
|
|
``sigmoid-center``
|
|
|
|
The center of the sigmoid curve used for ``sigmoid-upscaling``, must
|
|
|
|
be a float between 0.0 and 1.0. Defaults to 0.75 if not specified.
|
|
|
|
|
|
|
|
``sigmoid-slope``
|
|
|
|
The slope of the sigmoid curve used for ``sigmoid-upscaling``, must
|
|
|
|
be a float between 1.0 and 20.0. Defaults to 6.5 if not specified.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``no-npot``
|
2012-08-07 21:53:14 +00:00
|
|
|
Force use of power-of-2 texture sizes. For debugging only.
|
|
|
|
Borders will be distorted due to filtering.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``glfinish``
|
2014-08-15 21:36:02 +00:00
|
|
|
Call ``glFinish()`` before and after swapping buffers (default: disabled).
|
|
|
|
Slower, but might help getting better results when doing framedropping.
|
2015-01-23 16:09:25 +00:00
|
|
|
Can completely ruin performance. The details depend entirely on the
|
|
|
|
OpenGL driver.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2014-08-15 21:36:13 +00:00
|
|
|
``waitvsync``
|
|
|
|
Call ``glXWaitVideoSyncSGI`` after each buffer swap (default: disabled).
|
|
|
|
This may or may not help with video timing accuracy and frame drop. It's
|
|
|
|
possible that this makes video output slower, or has no effect at all.
|
|
|
|
|
2015-01-23 16:09:25 +00:00
|
|
|
X11/GLX only.
|
2014-08-15 21:36:13 +00:00
|
|
|
|
2015-04-14 12:29:05 +00:00
|
|
|
``dwmflush=<no|windowed|yes>``
|
|
|
|
Calls ``DwmFlush`` after swapping buffers on Windows (default: no).
|
2015-03-16 23:15:28 +00:00
|
|
|
It also sets ``SwapInterval(0)`` to ignore the OpenGL timing. Values
|
2015-04-14 12:29:05 +00:00
|
|
|
are: no (disabled), windowed (only in windowed mode), yes (also in
|
|
|
|
full screen).
|
2015-03-16 23:15:28 +00:00
|
|
|
This may help getting more consistent frame intervals, especially with
|
|
|
|
high-fps clips - which might also reduce dropped frames. Typically a
|
|
|
|
value of 1 should be enough since full screen may bypass the DWM.
|
|
|
|
|
|
|
|
Windows only.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``sw``
|
2012-10-02 23:54:13 +00:00
|
|
|
Continue even if a software renderer is detected.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``backend=<sys>``
|
2013-07-22 00:14:15 +00:00
|
|
|
The value ``auto`` (the default) selects the windowing backend. You
|
|
|
|
can also pass ``help`` to get a complete list of compiled in backends
|
|
|
|
(sorted by autoprobe order).
|
|
|
|
|
2012-08-07 21:53:14 +00:00
|
|
|
auto
|
|
|
|
auto-select (default)
|
|
|
|
cocoa
|
2014-09-01 02:25:57 +00:00
|
|
|
Cocoa/OS X
|
2012-08-07 21:53:14 +00:00
|
|
|
win
|
|
|
|
Win32/WGL
|
2015-01-23 16:09:25 +00:00
|
|
|
x11, x11es
|
|
|
|
X11/GLX (the ``es`` variant forces GLES)
|
2013-02-28 18:55:02 +00:00
|
|
|
wayland
|
|
|
|
Wayland/EGL
|
2015-01-23 16:09:25 +00:00
|
|
|
x11egl, x11egles
|
|
|
|
X11/EGL (the ``es`` variant forces GLES)
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``fbo-format=<fmt>``
|
2012-10-14 21:58:49 +00:00
|
|
|
Selects the internal format of textures used for FBOs. The format can
|
|
|
|
influence performance and quality of the video output. (FBOs are not
|
|
|
|
always used, and typically only when using extended scalers.)
|
2013-10-23 15:46:57 +00:00
|
|
|
``fmt`` can be one of: rgb, rgba, rgb8, rgb10, rgb10_a2, rgb16, rgb16f,
|
|
|
|
rgb32f, rgba12, rgba16, rgba16f, rgba32f.
|
2014-12-17 20:35:05 +00:00
|
|
|
Default: rgba.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2015-02-03 16:12:04 +00:00
|
|
|
``gamma=<0.1..2.0>``
|
|
|
|
Set a gamma value (default: 1.0). If gamma is adjusted in other ways
|
|
|
|
(like with the ``--gamma`` option or key bindings and the ``gamma``
|
|
|
|
property), the value is multiplied with the other gamma value.
|
2015-02-03 07:34:52 +00:00
|
|
|
|
|
|
|
Recommended values based on the environmental brightness:
|
|
|
|
|
|
|
|
1.0
|
2015-02-03 16:12:04 +00:00
|
|
|
Brightly illuminated (default)
|
2015-02-03 07:34:52 +00:00
|
|
|
0.9
|
|
|
|
Slightly dim
|
|
|
|
0.8
|
|
|
|
Pitch black room
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2015-02-07 12:54:18 +00:00
|
|
|
``gamma-auto``
|
|
|
|
Automatically corrects the gamma value depending on ambient lighting
|
|
|
|
conditions (adding a gamma boost for dark rooms).
|
|
|
|
|
|
|
|
With ambient illuminance of 64lux, mpv will pick the 1.0 gamma value
|
|
|
|
(no boost), and slightly increase the boost up until 0.8 for 16lux.
|
|
|
|
|
|
|
|
NOTE: Only implemented on OS X.
|
|
|
|
|
vo_opengl: refactor shader generation (part 2)
This adds stuff related to gamma, linear light, sigmoid, BT.2020-CL,
etc, as well as color management. Also adds a new gamma function (gamma22).
This adds new parameters to configure the CMS settings, in particular
letting us target simple colorspaces without requiring usage of a 3DLUT.
This adds smoothmotion. Mostly working, but it's still sensitive to
timing issues. It's based on an actual queue now, but the queue size
is kept small to avoid larger amounts of latency.
Also makes “upscale before blending” the default strategy.
This is justified because the "render after blending" thing doesn't seme
to work consistently any way (introduces stutter due to the way vsync
timing works, or something), so this behavior is a bit closer to master
and makes pausing/unpausing less weird/jumpy.
This adds the remaining scalers, including bicubic_fast, sharpen3,
sharpen5, polar filters and antiringing. Apparently, sharpen3/5 also
consult scale-param1, which was undocumented in master.
This also implements cropping and chroma transformation, plus
rotation/flipping. These are inherently part of the same logic, although
it's a bit rough around the edges in some case, mainly due to the fallback
code paths (for bilinear scaling without indirection).
2015-03-12 21:18:16 +00:00
|
|
|
``target-prim=<value>``
|
|
|
|
Specifies the primaries of the display. Video colors will be adapted
|
|
|
|
to this colorspace if necessary. Valid values are:
|
|
|
|
|
|
|
|
auto
|
|
|
|
Disable any adaptation (default)
|
2015-03-31 05:31:35 +00:00
|
|
|
bt.470m
|
vo_opengl: refactor shader generation (part 2)
This adds stuff related to gamma, linear light, sigmoid, BT.2020-CL,
etc, as well as color management. Also adds a new gamma function (gamma22).
This adds new parameters to configure the CMS settings, in particular
letting us target simple colorspaces without requiring usage of a 3DLUT.
This adds smoothmotion. Mostly working, but it's still sensitive to
timing issues. It's based on an actual queue now, but the queue size
is kept small to avoid larger amounts of latency.
Also makes “upscale before blending” the default strategy.
This is justified because the "render after blending" thing doesn't seme
to work consistently any way (introduces stutter due to the way vsync
timing works, or something), so this behavior is a bit closer to master
and makes pausing/unpausing less weird/jumpy.
This adds the remaining scalers, including bicubic_fast, sharpen3,
sharpen5, polar filters and antiringing. Apparently, sharpen3/5 also
consult scale-param1, which was undocumented in master.
This also implements cropping and chroma transformation, plus
rotation/flipping. These are inherently part of the same logic, although
it's a bit rough around the edges in some case, mainly due to the fallback
code paths (for bilinear scaling without indirection).
2015-03-12 21:18:16 +00:00
|
|
|
ITU-R BT.470 M
|
2015-03-31 05:31:35 +00:00
|
|
|
bt.601-525
|
vo_opengl: refactor shader generation (part 2)
This adds stuff related to gamma, linear light, sigmoid, BT.2020-CL,
etc, as well as color management. Also adds a new gamma function (gamma22).
This adds new parameters to configure the CMS settings, in particular
letting us target simple colorspaces without requiring usage of a 3DLUT.
This adds smoothmotion. Mostly working, but it's still sensitive to
timing issues. It's based on an actual queue now, but the queue size
is kept small to avoid larger amounts of latency.
Also makes “upscale before blending” the default strategy.
This is justified because the "render after blending" thing doesn't seme
to work consistently any way (introduces stutter due to the way vsync
timing works, or something), so this behavior is a bit closer to master
and makes pausing/unpausing less weird/jumpy.
This adds the remaining scalers, including bicubic_fast, sharpen3,
sharpen5, polar filters and antiringing. Apparently, sharpen3/5 also
consult scale-param1, which was undocumented in master.
This also implements cropping and chroma transformation, plus
rotation/flipping. These are inherently part of the same logic, although
it's a bit rough around the edges in some case, mainly due to the fallback
code paths (for bilinear scaling without indirection).
2015-03-12 21:18:16 +00:00
|
|
|
ITU-R BT.601 (525-line SD systems, eg. NTSC), SMPTE 170M/240M
|
2015-03-31 05:31:35 +00:00
|
|
|
bt.601-625
|
vo_opengl: refactor shader generation (part 2)
This adds stuff related to gamma, linear light, sigmoid, BT.2020-CL,
etc, as well as color management. Also adds a new gamma function (gamma22).
This adds new parameters to configure the CMS settings, in particular
letting us target simple colorspaces without requiring usage of a 3DLUT.
This adds smoothmotion. Mostly working, but it's still sensitive to
timing issues. It's based on an actual queue now, but the queue size
is kept small to avoid larger amounts of latency.
Also makes “upscale before blending” the default strategy.
This is justified because the "render after blending" thing doesn't seme
to work consistently any way (introduces stutter due to the way vsync
timing works, or something), so this behavior is a bit closer to master
and makes pausing/unpausing less weird/jumpy.
This adds the remaining scalers, including bicubic_fast, sharpen3,
sharpen5, polar filters and antiringing. Apparently, sharpen3/5 also
consult scale-param1, which was undocumented in master.
This also implements cropping and chroma transformation, plus
rotation/flipping. These are inherently part of the same logic, although
it's a bit rough around the edges in some case, mainly due to the fallback
code paths (for bilinear scaling without indirection).
2015-03-12 21:18:16 +00:00
|
|
|
ITU-R BT.601 (625-line SD systems, eg. PAL/SECAM), ITU-R BT.470 B/G
|
2015-03-31 05:31:35 +00:00
|
|
|
bt.709
|
vo_opengl: refactor shader generation (part 2)
This adds stuff related to gamma, linear light, sigmoid, BT.2020-CL,
etc, as well as color management. Also adds a new gamma function (gamma22).
This adds new parameters to configure the CMS settings, in particular
letting us target simple colorspaces without requiring usage of a 3DLUT.
This adds smoothmotion. Mostly working, but it's still sensitive to
timing issues. It's based on an actual queue now, but the queue size
is kept small to avoid larger amounts of latency.
Also makes “upscale before blending” the default strategy.
This is justified because the "render after blending" thing doesn't seme
to work consistently any way (introduces stutter due to the way vsync
timing works, or something), so this behavior is a bit closer to master
and makes pausing/unpausing less weird/jumpy.
This adds the remaining scalers, including bicubic_fast, sharpen3,
sharpen5, polar filters and antiringing. Apparently, sharpen3/5 also
consult scale-param1, which was undocumented in master.
This also implements cropping and chroma transformation, plus
rotation/flipping. These are inherently part of the same logic, although
it's a bit rough around the edges in some case, mainly due to the fallback
code paths (for bilinear scaling without indirection).
2015-03-12 21:18:16 +00:00
|
|
|
ITU-R BT.709 (HD), IEC 61966-2-4 (sRGB), SMPTE RP177 Annex B
|
2015-03-31 05:31:35 +00:00
|
|
|
bt.2020
|
vo_opengl: refactor shader generation (part 2)
This adds stuff related to gamma, linear light, sigmoid, BT.2020-CL,
etc, as well as color management. Also adds a new gamma function (gamma22).
This adds new parameters to configure the CMS settings, in particular
letting us target simple colorspaces without requiring usage of a 3DLUT.
This adds smoothmotion. Mostly working, but it's still sensitive to
timing issues. It's based on an actual queue now, but the queue size
is kept small to avoid larger amounts of latency.
Also makes “upscale before blending” the default strategy.
This is justified because the "render after blending" thing doesn't seme
to work consistently any way (introduces stutter due to the way vsync
timing works, or something), so this behavior is a bit closer to master
and makes pausing/unpausing less weird/jumpy.
This adds the remaining scalers, including bicubic_fast, sharpen3,
sharpen5, polar filters and antiringing. Apparently, sharpen3/5 also
consult scale-param1, which was undocumented in master.
This also implements cropping and chroma transformation, plus
rotation/flipping. These are inherently part of the same logic, although
it's a bit rough around the edges in some case, mainly due to the fallback
code paths (for bilinear scaling without indirection).
2015-03-12 21:18:16 +00:00
|
|
|
ITU-R BT.2020 (UHD)
|
2015-03-30 12:54:52 +00:00
|
|
|
apple
|
|
|
|
Apple RGB
|
|
|
|
adobe
|
|
|
|
Adobe RGB (1998)
|
|
|
|
prophoto
|
|
|
|
ProPhoto RGB (ROMM)
|
|
|
|
cie1931
|
|
|
|
CIE 1931 RGB (not to be confused with CIE XYZ)
|
vo_opengl: refactor shader generation (part 2)
This adds stuff related to gamma, linear light, sigmoid, BT.2020-CL,
etc, as well as color management. Also adds a new gamma function (gamma22).
This adds new parameters to configure the CMS settings, in particular
letting us target simple colorspaces without requiring usage of a 3DLUT.
This adds smoothmotion. Mostly working, but it's still sensitive to
timing issues. It's based on an actual queue now, but the queue size
is kept small to avoid larger amounts of latency.
Also makes “upscale before blending” the default strategy.
This is justified because the "render after blending" thing doesn't seme
to work consistently any way (introduces stutter due to the way vsync
timing works, or something), so this behavior is a bit closer to master
and makes pausing/unpausing less weird/jumpy.
This adds the remaining scalers, including bicubic_fast, sharpen3,
sharpen5, polar filters and antiringing. Apparently, sharpen3/5 also
consult scale-param1, which was undocumented in master.
This also implements cropping and chroma transformation, plus
rotation/flipping. These are inherently part of the same logic, although
it's a bit rough around the edges in some case, mainly due to the fallback
code paths (for bilinear scaling without indirection).
2015-03-12 21:18:16 +00:00
|
|
|
|
|
|
|
``target-trc=<value>``
|
|
|
|
Specifies the transfer characteristics (gamma) of the display. Video
|
|
|
|
colors will be adjusted to this curve. Valid values are:
|
|
|
|
|
|
|
|
auto
|
|
|
|
Disable any adaptation (default)
|
2015-03-31 05:31:35 +00:00
|
|
|
bt.1886
|
vo_opengl: refactor shader generation (part 2)
This adds stuff related to gamma, linear light, sigmoid, BT.2020-CL,
etc, as well as color management. Also adds a new gamma function (gamma22).
This adds new parameters to configure the CMS settings, in particular
letting us target simple colorspaces without requiring usage of a 3DLUT.
This adds smoothmotion. Mostly working, but it's still sensitive to
timing issues. It's based on an actual queue now, but the queue size
is kept small to avoid larger amounts of latency.
Also makes “upscale before blending” the default strategy.
This is justified because the "render after blending" thing doesn't seme
to work consistently any way (introduces stutter due to the way vsync
timing works, or something), so this behavior is a bit closer to master
and makes pausing/unpausing less weird/jumpy.
This adds the remaining scalers, including bicubic_fast, sharpen3,
sharpen5, polar filters and antiringing. Apparently, sharpen3/5 also
consult scale-param1, which was undocumented in master.
This also implements cropping and chroma transformation, plus
rotation/flipping. These are inherently part of the same logic, although
it's a bit rough around the edges in some case, mainly due to the fallback
code paths (for bilinear scaling without indirection).
2015-03-12 21:18:16 +00:00
|
|
|
ITU-R BT.1886 curve, without the brightness drop (approx. 1.961)
|
|
|
|
srgb
|
|
|
|
IEC 61966-2-4 (sRGB)
|
|
|
|
linear
|
|
|
|
Linear light output
|
2015-03-31 05:31:35 +00:00
|
|
|
gamma1.8
|
2015-03-30 12:54:52 +00:00
|
|
|
Pure power curve (gamma 1.8), also used for Apple RGB
|
2015-03-31 05:31:35 +00:00
|
|
|
gamma2.2
|
vo_opengl: refactor shader generation (part 2)
This adds stuff related to gamma, linear light, sigmoid, BT.2020-CL,
etc, as well as color management. Also adds a new gamma function (gamma22).
This adds new parameters to configure the CMS settings, in particular
letting us target simple colorspaces without requiring usage of a 3DLUT.
This adds smoothmotion. Mostly working, but it's still sensitive to
timing issues. It's based on an actual queue now, but the queue size
is kept small to avoid larger amounts of latency.
Also makes “upscale before blending” the default strategy.
This is justified because the "render after blending" thing doesn't seme
to work consistently any way (introduces stutter due to the way vsync
timing works, or something), so this behavior is a bit closer to master
and makes pausing/unpausing less weird/jumpy.
This adds the remaining scalers, including bicubic_fast, sharpen3,
sharpen5, polar filters and antiringing. Apparently, sharpen3/5 also
consult scale-param1, which was undocumented in master.
This also implements cropping and chroma transformation, plus
rotation/flipping. These are inherently part of the same logic, although
it's a bit rough around the edges in some case, mainly due to the fallback
code paths (for bilinear scaling without indirection).
2015-03-12 21:18:16 +00:00
|
|
|
Pure power curve (gamma 2.2)
|
2015-03-31 05:31:35 +00:00
|
|
|
gamma2.8
|
2015-03-30 12:54:52 +00:00
|
|
|
Pure power curve (gamma 2.8), also used for BT.470-BG
|
|
|
|
prophoto
|
|
|
|
ProPhoto RGB (ROMM)
|
vo_opengl: refactor shader generation (part 2)
This adds stuff related to gamma, linear light, sigmoid, BT.2020-CL,
etc, as well as color management. Also adds a new gamma function (gamma22).
This adds new parameters to configure the CMS settings, in particular
letting us target simple colorspaces without requiring usage of a 3DLUT.
This adds smoothmotion. Mostly working, but it's still sensitive to
timing issues. It's based on an actual queue now, but the queue size
is kept small to avoid larger amounts of latency.
Also makes “upscale before blending” the default strategy.
This is justified because the "render after blending" thing doesn't seme
to work consistently any way (introduces stutter due to the way vsync
timing works, or something), so this behavior is a bit closer to master
and makes pausing/unpausing less weird/jumpy.
This adds the remaining scalers, including bicubic_fast, sharpen3,
sharpen5, polar filters and antiringing. Apparently, sharpen3/5 also
consult scale-param1, which was undocumented in master.
This also implements cropping and chroma transformation, plus
rotation/flipping. These are inherently part of the same logic, although
it's a bit rough around the edges in some case, mainly due to the fallback
code paths (for bilinear scaling without indirection).
2015-03-12 21:18:16 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``icc-profile=<file>``
|
|
|
|
Load an ICC profile and use it to transform linear RGB to screen output.
|
vo_opengl: refactor shader generation (part 2)
This adds stuff related to gamma, linear light, sigmoid, BT.2020-CL,
etc, as well as color management. Also adds a new gamma function (gamma22).
This adds new parameters to configure the CMS settings, in particular
letting us target simple colorspaces without requiring usage of a 3DLUT.
This adds smoothmotion. Mostly working, but it's still sensitive to
timing issues. It's based on an actual queue now, but the queue size
is kept small to avoid larger amounts of latency.
Also makes “upscale before blending” the default strategy.
This is justified because the "render after blending" thing doesn't seme
to work consistently any way (introduces stutter due to the way vsync
timing works, or something), so this behavior is a bit closer to master
and makes pausing/unpausing less weird/jumpy.
This adds the remaining scalers, including bicubic_fast, sharpen3,
sharpen5, polar filters and antiringing. Apparently, sharpen3/5 also
consult scale-param1, which was undocumented in master.
This also implements cropping and chroma transformation, plus
rotation/flipping. These are inherently part of the same logic, although
it's a bit rough around the edges in some case, mainly due to the fallback
code paths (for bilinear scaling without indirection).
2015-03-12 21:18:16 +00:00
|
|
|
Needs LittleCMS 2 support compiled in. This option overrides the
|
|
|
|
``target-prim`` and ``target-trc`` options. It also enables
|
2015-02-06 02:37:21 +00:00
|
|
|
``linear-scaling``.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2014-02-24 23:04:30 +00:00
|
|
|
``icc-profile-auto``
|
|
|
|
Automatically select the ICC display profile currently specified by
|
|
|
|
the display settings of the operating system.
|
|
|
|
|
2015-01-26 01:18:47 +00:00
|
|
|
NOTE: Only implemented on OS X and X11
|
2014-02-24 23:04:30 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``icc-cache=<file>``
|
|
|
|
Store and load the 3D LUT created from the ICC profile in this file.
|
2014-09-01 02:25:57 +00:00
|
|
|
This can be used to speed up loading, since LittleCMS 2 can take a while
|
2013-07-08 16:02:14 +00:00
|
|
|
to create the 3D LUT. Note that this file contains an uncompressed LUT.
|
|
|
|
Its size depends on the ``3dlut-size``, and can be very big.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``icc-intent=<value>``
|
vo_opengl: refactor shader generation (part 2)
This adds stuff related to gamma, linear light, sigmoid, BT.2020-CL,
etc, as well as color management. Also adds a new gamma function (gamma22).
This adds new parameters to configure the CMS settings, in particular
letting us target simple colorspaces without requiring usage of a 3DLUT.
This adds smoothmotion. Mostly working, but it's still sensitive to
timing issues. It's based on an actual queue now, but the queue size
is kept small to avoid larger amounts of latency.
Also makes “upscale before blending” the default strategy.
This is justified because the "render after blending" thing doesn't seme
to work consistently any way (introduces stutter due to the way vsync
timing works, or something), so this behavior is a bit closer to master
and makes pausing/unpausing less weird/jumpy.
This adds the remaining scalers, including bicubic_fast, sharpen3,
sharpen5, polar filters and antiringing. Apparently, sharpen3/5 also
consult scale-param1, which was undocumented in master.
This also implements cropping and chroma transformation, plus
rotation/flipping. These are inherently part of the same logic, although
it's a bit rough around the edges in some case, mainly due to the fallback
code paths (for bilinear scaling without indirection).
2015-03-12 21:18:16 +00:00
|
|
|
Specifies the ICC intent used for the color transformation (when using
|
|
|
|
``icc-profile``).
|
2014-03-31 22:17:07 +00:00
|
|
|
|
2012-08-07 21:53:14 +00:00
|
|
|
0
|
|
|
|
perceptual
|
|
|
|
1
|
2014-02-26 21:58:48 +00:00
|
|
|
relative colorimetric (default)
|
2012-08-07 21:53:14 +00:00
|
|
|
2
|
|
|
|
saturation
|
|
|
|
3
|
2014-02-26 21:58:48 +00:00
|
|
|
absolute colorimetric
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``3dlut-size=<r>x<g>x<b>``
|
|
|
|
Size of the 3D LUT generated from the ICC profile in each dimension.
|
|
|
|
Default is 128x256x64.
|
2014-03-26 00:46:38 +00:00
|
|
|
Sizes must be a power of two, and 512 at most.
|
2012-08-07 21:53:14 +00:00
|
|
|
|
2015-04-11 17:16:34 +00:00
|
|
|
``blend-subtitles=<yes|video|no>``
|
2015-03-23 01:42:19 +00:00
|
|
|
Blend subtitles directly onto upscaled video frames, before
|
|
|
|
interpolation and/or color management (default: no). Enabling this
|
|
|
|
causes subtitles to be affected by ``icc-profile``, ``target-prim``,
|
|
|
|
``target-trc``, ``interpolation``, ``gamma`` and ``linear-scaling``.
|
|
|
|
It also increases subtitle performance when using ``interpolation``.
|
|
|
|
|
|
|
|
The downside of enabling this is that it restricts subtitles to the
|
|
|
|
visible portion of the video, so you can't have subtitles exist in the
|
|
|
|
black margins below a video (for example).
|
|
|
|
|
2015-04-11 17:16:34 +00:00
|
|
|
If ``video`` is selected, the behavior is similar to ``yes``, but subs
|
|
|
|
are drawn at the video's native resolution, and scaled along with the
|
|
|
|
video.
|
|
|
|
|
2015-03-27 10:44:25 +00:00
|
|
|
.. warning:: This changes the way subtitle colors are handled. Normally,
|
|
|
|
subtitle colors are assumed to be in sRGB and color managed
|
|
|
|
as such. Enabling this makes them treated as being in the
|
|
|
|
video's color space instead. This is good if you want
|
|
|
|
things like softsubbed ASS signs to match the video colors,
|
|
|
|
but may cause SRT subtitles or similar to look slightly off.
|
2015-03-27 09:25:28 +00:00
|
|
|
|
2013-09-19 14:55:56 +00:00
|
|
|
``alpha=<blend|yes|no>``
|
2015-02-06 22:23:27 +00:00
|
|
|
Decides what to do if the input has an alpha component (default: blend).
|
2013-09-19 14:55:56 +00:00
|
|
|
|
|
|
|
blend
|
|
|
|
Blend the frame against a black background.
|
|
|
|
yes
|
|
|
|
Try to create a framebuffer with alpha component. This only makes sense
|
|
|
|
if the video contains alpha information (which is extremely rare). May
|
|
|
|
not be supported on all platforms. If alpha framebuffers are
|
|
|
|
unavailable, it silently falls back on a normal framebuffer. Note
|
2015-01-23 16:09:25 +00:00
|
|
|
that if you set the ``fbo-format`` option to a non-default value,
|
|
|
|
a format with alpha must be specified, or this won't work.
|
2013-09-19 14:55:56 +00:00
|
|
|
no
|
|
|
|
Ignore alpha component.
|
2013-03-28 20:44:27 +00:00
|
|
|
|
2013-12-01 22:39:13 +00:00
|
|
|
``rectangle-textures``
|
|
|
|
Force use of rectangle textures (default: no). Normally this shouldn't
|
|
|
|
have any advantages over normal textures. Note that hardware decoding
|
|
|
|
overrides this flag.
|
|
|
|
|
2014-12-09 20:34:01 +00:00
|
|
|
``background=<color>``
|
|
|
|
Color used to draw parts of the mpv window not covered by video.
|
|
|
|
See ``--osd-color`` option how colors are defined.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``opengl-hq``
|
2012-09-29 16:36:05 +00:00
|
|
|
Same as ``opengl``, but with default settings for high quality rendering.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
This is equivalent to::
|
2012-09-29 16:36:05 +00:00
|
|
|
|
vo_opengl: refactor scaler configuration
This merges all of the scaler-related options into a single
configuration struct, and also cleans up the way they're passed through
the code. (For example, the scaler index is no longer threaded through
pass_sample, just the scaler configuration itself, and there's no longer
duplication of the params etc.)
In addition, this commit makes scale-down more principled, and turns it
into a scaler in its own right - so there's no longer an ugly separation
between scale and scale-down in the code.
Finally, the radius stuff has been made more proper - filters always
have a radius now (there's no more radius -1), and get a new .resizable
attribute instead for when it's tunable.
User-visible changes:
1. scale-down has been renamed dscale and now has its own set of config
options (dscale-param1, dscale-radius) etc., instead of reusing
scale-param1 (which was arguably a bug).
2. The default radius is no longer fixed at 3, but instead uses that
filter's preferred radius by default. (Scalers with a default radius
other than 3 include sinc, gaussian, box and triangle)
3. scale-radius etc. now goes down to 0.5, rather than 1.0. 0.5 is the
smallest radius that theoretically makes sense, and indeed it's used
by at least one filter (nearest).
Apart from that, it should just be internal changes only.
Note that this sets up for the refactor discussed in #1720, which would
be to merge scaler and window configurations (include parameters etc.)
into a single, simplified string. In the code, this would now basically
just mean getting rid of all the OPT_FLOATRANGE etc. lines related to
scalers and replacing them by a single function that parses a string and
updates the struct scaler_config as appropriate.
2015-03-26 00:55:32 +00:00
|
|
|
--vo=opengl:scale=spline36:cscale=spline36:dscale=mitchell:dither-depth=auto:fbo-format=rgba16:fancy-downscaling:sigmoid-upscaling
|
2012-09-29 16:36:05 +00:00
|
|
|
|
|
|
|
Note that some cheaper LCDs do dithering that gravely interferes with
|
2013-07-08 16:02:14 +00:00
|
|
|
``opengl``'s dithering. Disabling dithering with ``dither-depth=no`` helps.
|
2012-09-29 16:36:05 +00:00
|
|
|
|
2012-10-14 21:58:49 +00:00
|
|
|
Unlike ``opengl``, ``opengl-hq`` makes use of FBOs by default. Sometimes you
|
2013-07-08 16:02:14 +00:00
|
|
|
can achieve better quality or performance by changing the ``fbo-format``
|
|
|
|
suboption to ``rgb16f``, ``rgb32f`` or ``rgb``. Known problems include
|
2012-10-14 21:58:49 +00:00
|
|
|
Mesa/Intel not accepting ``rgb16``, Mesa sometimes not being compiled with
|
2014-09-01 02:25:57 +00:00
|
|
|
float texture support, and some OS X setups being very slow with ``rgb16``
|
2013-07-08 16:02:14 +00:00
|
|
|
but fast with ``rgb32f``.
|
2012-09-29 16:36:05 +00:00
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``sdl``
|
2012-12-28 07:07:14 +00:00
|
|
|
SDL 2.0+ Render video output driver, depending on system with or without
|
2013-07-08 16:02:14 +00:00
|
|
|
hardware acceleration. Should work on all platforms supported by SDL 2.0.
|
|
|
|
For tuning, refer to your copy of the file ``SDL_hints.h``.
|
2012-12-28 07:07:14 +00:00
|
|
|
|
2014-04-19 13:29:05 +00:00
|
|
|
.. note:: This driver is for compatibility with systems that don't provide
|
|
|
|
proper graphics drivers, or which support GLES only.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``sw``
|
2013-01-04 16:43:37 +00:00
|
|
|
Continue even if a software renderer is detected.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``switch-mode``
|
2013-02-24 22:36:40 +00:00
|
|
|
Instruct SDL to switch the monitor video mode when going fullscreen.
|
|
|
|
|
video: add vaapi decode and output support
This is based on the MPlayer VA API patches. To be exact it's based on
a very stripped down version of commit f1ad459a263f8537f6c from
git://gitorious.org/vaapi/mplayer.git.
This doesn't contain useless things like benchmarking hacks and the
demo code for GLX interop. Also, unlike in the original patch, decoding
and video output are split into separate source files (the separation
between decoding and display also makes pixel format hacks unnecessary).
On the other hand, some features not present in the original patch were
added, like screenshot support.
VA API is rather bad for actual video output. Dealing with older libva
versions or the completely broken vdpau backend doesn't help. OSD is
low quality and should be rather slow. In some cases, only either OSD
or subtitles can be shown at the same time (because OSD is drawn first,
OSD is prefered).
Also, libva can't decide whether it accepts straight or premultiplied
alpha for OSD sub-pictures: the vdpau backend seems to assume
premultiplied, while a native vaapi driver uses straight. So I picked
straight alpha. It doesn't matter much, because the blending code for
straight alpha I added to img_convert.c is probably buggy, and ASS
subtitles might be blended incorrectly.
Really good video output with VA API would probably use OpenGL and the
GL interop features, but at this point you might just use vo_opengl.
(Patches for making HW decoding with vo_opengl have a chance of being
accepted.)
Despite these issues, decoding seems to work ok. I still got tearing
on the Intel system I tested (Intel(R) Core(TM) i3-2350M). It was also
tested with the vdpau vaapi wrapper on a nvidia system; however this
was rather broken. (Fortunately, there is no reason to use mpv's VAAPI
support over native VDPAU.)
2013-08-09 12:01:30 +00:00
|
|
|
``vaapi``
|
|
|
|
Intel VA API video output driver with support for hardware decoding. Note
|
|
|
|
that there is absolutely no reason to use this, other than wanting to use
|
|
|
|
hardware decoding to save power on laptops, or possibly preventing video
|
|
|
|
tearing with some setups.
|
|
|
|
|
2014-04-19 13:29:05 +00:00
|
|
|
.. note:: This driver is for compatibility with crappy systems. You can
|
|
|
|
use vaapi hardware decoding with ``--vo=opengl`` too.
|
|
|
|
|
video: add vaapi decode and output support
This is based on the MPlayer VA API patches. To be exact it's based on
a very stripped down version of commit f1ad459a263f8537f6c from
git://gitorious.org/vaapi/mplayer.git.
This doesn't contain useless things like benchmarking hacks and the
demo code for GLX interop. Also, unlike in the original patch, decoding
and video output are split into separate source files (the separation
between decoding and display also makes pixel format hacks unnecessary).
On the other hand, some features not present in the original patch were
added, like screenshot support.
VA API is rather bad for actual video output. Dealing with older libva
versions or the completely broken vdpau backend doesn't help. OSD is
low quality and should be rather slow. In some cases, only either OSD
or subtitles can be shown at the same time (because OSD is drawn first,
OSD is prefered).
Also, libva can't decide whether it accepts straight or premultiplied
alpha for OSD sub-pictures: the vdpau backend seems to assume
premultiplied, while a native vaapi driver uses straight. So I picked
straight alpha. It doesn't matter much, because the blending code for
straight alpha I added to img_convert.c is probably buggy, and ASS
subtitles might be blended incorrectly.
Really good video output with VA API would probably use OpenGL and the
GL interop features, but at this point you might just use vo_opengl.
(Patches for making HW decoding with vo_opengl have a chance of being
accepted.)
Despite these issues, decoding seems to work ok. I still got tearing
on the Intel system I tested (Intel(R) Core(TM) i3-2350M). It was also
tested with the vdpau vaapi wrapper on a nvidia system; however this
was rather broken. (Fortunately, there is no reason to use mpv's VAAPI
support over native VDPAU.)
2013-08-09 12:01:30 +00:00
|
|
|
``scaling=<algorithm>``
|
|
|
|
default
|
|
|
|
Driver default (mpv default as well).
|
|
|
|
fast
|
|
|
|
Fast, but low quality.
|
|
|
|
hq
|
|
|
|
Unspecified driver dependent high-quality scaling, slow.
|
|
|
|
nla
|
|
|
|
``non-linear anamorphic scaling``
|
|
|
|
|
|
|
|
``deint-mode=<mode>``
|
|
|
|
Select deinterlacing algorithm. Note that by default deinterlacing is
|
|
|
|
initially always off, and needs to be enabled with the ``D`` key
|
|
|
|
(default key binding for ``cycle deinterlace``).
|
|
|
|
|
2013-09-20 13:55:13 +00:00
|
|
|
This option doesn't apply if libva supports video post processing (vpp).
|
|
|
|
In this case, the default for ``deint-mode`` is ``no``, and enabling
|
|
|
|
deinterlacing via user interaction using the methods mentioned above
|
|
|
|
actually inserts the ``vavpp`` video filter. If vpp is not actually
|
|
|
|
supported with the libva backend in use, you can use this option to
|
|
|
|
forcibly enable VO based deinterlacing.
|
|
|
|
|
video: add vaapi decode and output support
This is based on the MPlayer VA API patches. To be exact it's based on
a very stripped down version of commit f1ad459a263f8537f6c from
git://gitorious.org/vaapi/mplayer.git.
This doesn't contain useless things like benchmarking hacks and the
demo code for GLX interop. Also, unlike in the original patch, decoding
and video output are split into separate source files (the separation
between decoding and display also makes pixel format hacks unnecessary).
On the other hand, some features not present in the original patch were
added, like screenshot support.
VA API is rather bad for actual video output. Dealing with older libva
versions or the completely broken vdpau backend doesn't help. OSD is
low quality and should be rather slow. In some cases, only either OSD
or subtitles can be shown at the same time (because OSD is drawn first,
OSD is prefered).
Also, libva can't decide whether it accepts straight or premultiplied
alpha for OSD sub-pictures: the vdpau backend seems to assume
premultiplied, while a native vaapi driver uses straight. So I picked
straight alpha. It doesn't matter much, because the blending code for
straight alpha I added to img_convert.c is probably buggy, and ASS
subtitles might be blended incorrectly.
Really good video output with VA API would probably use OpenGL and the
GL interop features, but at this point you might just use vo_opengl.
(Patches for making HW decoding with vo_opengl have a chance of being
accepted.)
Despite these issues, decoding seems to work ok. I still got tearing
on the Intel system I tested (Intel(R) Core(TM) i3-2350M). It was also
tested with the vdpau vaapi wrapper on a nvidia system; however this
was rather broken. (Fortunately, there is no reason to use mpv's VAAPI
support over native VDPAU.)
2013-08-09 12:01:30 +00:00
|
|
|
no
|
2013-09-20 13:55:13 +00:00
|
|
|
Don't allow deinterlacing (default for newer libva).
|
video: add vaapi decode and output support
This is based on the MPlayer VA API patches. To be exact it's based on
a very stripped down version of commit f1ad459a263f8537f6c from
git://gitorious.org/vaapi/mplayer.git.
This doesn't contain useless things like benchmarking hacks and the
demo code for GLX interop. Also, unlike in the original patch, decoding
and video output are split into separate source files (the separation
between decoding and display also makes pixel format hacks unnecessary).
On the other hand, some features not present in the original patch were
added, like screenshot support.
VA API is rather bad for actual video output. Dealing with older libva
versions or the completely broken vdpau backend doesn't help. OSD is
low quality and should be rather slow. In some cases, only either OSD
or subtitles can be shown at the same time (because OSD is drawn first,
OSD is prefered).
Also, libva can't decide whether it accepts straight or premultiplied
alpha for OSD sub-pictures: the vdpau backend seems to assume
premultiplied, while a native vaapi driver uses straight. So I picked
straight alpha. It doesn't matter much, because the blending code for
straight alpha I added to img_convert.c is probably buggy, and ASS
subtitles might be blended incorrectly.
Really good video output with VA API would probably use OpenGL and the
GL interop features, but at this point you might just use vo_opengl.
(Patches for making HW decoding with vo_opengl have a chance of being
accepted.)
Despite these issues, decoding seems to work ok. I still got tearing
on the Intel system I tested (Intel(R) Core(TM) i3-2350M). It was also
tested with the vdpau vaapi wrapper on a nvidia system; however this
was rather broken. (Fortunately, there is no reason to use mpv's VAAPI
support over native VDPAU.)
2013-08-09 12:01:30 +00:00
|
|
|
first-field
|
|
|
|
Show only first field (going by ``--field-dominance``).
|
|
|
|
bob
|
2013-09-20 13:55:13 +00:00
|
|
|
bob deinterlacing (default for older libva).
|
video: add vaapi decode and output support
This is based on the MPlayer VA API patches. To be exact it's based on
a very stripped down version of commit f1ad459a263f8537f6c from
git://gitorious.org/vaapi/mplayer.git.
This doesn't contain useless things like benchmarking hacks and the
demo code for GLX interop. Also, unlike in the original patch, decoding
and video output are split into separate source files (the separation
between decoding and display also makes pixel format hacks unnecessary).
On the other hand, some features not present in the original patch were
added, like screenshot support.
VA API is rather bad for actual video output. Dealing with older libva
versions or the completely broken vdpau backend doesn't help. OSD is
low quality and should be rather slow. In some cases, only either OSD
or subtitles can be shown at the same time (because OSD is drawn first,
OSD is prefered).
Also, libva can't decide whether it accepts straight or premultiplied
alpha for OSD sub-pictures: the vdpau backend seems to assume
premultiplied, while a native vaapi driver uses straight. So I picked
straight alpha. It doesn't matter much, because the blending code for
straight alpha I added to img_convert.c is probably buggy, and ASS
subtitles might be blended incorrectly.
Really good video output with VA API would probably use OpenGL and the
GL interop features, but at this point you might just use vo_opengl.
(Patches for making HW decoding with vo_opengl have a chance of being
accepted.)
Despite these issues, decoding seems to work ok. I still got tearing
on the Intel system I tested (Intel(R) Core(TM) i3-2350M). It was also
tested with the vdpau vaapi wrapper on a nvidia system; however this
was rather broken. (Fortunately, there is no reason to use mpv's VAAPI
support over native VDPAU.)
2013-08-09 12:01:30 +00:00
|
|
|
|
|
|
|
``scaled-osd=<yes|no>``
|
|
|
|
If enabled, then the OSD is rendered at video resolution and scaled to
|
|
|
|
display resolution. By default, this is disabled, and the OSD is
|
|
|
|
rendered at display resolution if the driver supports it.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``null``
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
Produces no video output. Useful for benchmarking.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``caca``
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
Color ASCII art video output driver that works on a text console.
|
|
|
|
|
2014-04-19 13:29:05 +00:00
|
|
|
.. note:: This driver is a joke.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``image``
|
2012-08-06 17:15:04 +00:00
|
|
|
Output each frame into an image file in the current directory. Each file
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
takes the frame number padded with leading zeros as name.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``format=<format>``
|
2012-08-06 17:15:04 +00:00
|
|
|
Select the image file format.
|
|
|
|
|
|
|
|
jpg
|
2012-11-15 13:25:20 +00:00
|
|
|
JPEG files, extension .jpg. (Default.)
|
2012-08-06 17:15:04 +00:00
|
|
|
jpeg
|
|
|
|
JPEG files, extension .jpeg.
|
|
|
|
png
|
|
|
|
PNG files.
|
|
|
|
ppm
|
|
|
|
Portable bitmap format.
|
|
|
|
pgm
|
|
|
|
Portable graymap format.
|
|
|
|
pgmyuv
|
|
|
|
Portable graymap format, using the YV12 pixel format.
|
|
|
|
tga
|
|
|
|
Truevision TGA.
|
|
|
|
|
2013-07-08 16:02:14 +00:00
|
|
|
``png-compression=<0-9>``
|
2012-08-06 17:15:04 +00:00
|
|
|
PNG compression factor (speed vs. file size tradeoff) (default: 7)
|
2013-07-08 16:02:14 +00:00
|
|
|
``png-filter=<0-5>``
|
2013-06-15 13:14:06 +00:00
|
|
|
Filter applied prior to PNG compression (0 = none; 1 = sub; 2 = up;
|
|
|
|
3 = average; 4 = Paeth; 5 = mixed) (default: 5)
|
2013-07-08 16:02:14 +00:00
|
|
|
``jpeg-quality=<0-100>``
|
2012-08-23 12:12:30 +00:00
|
|
|
JPEG quality factor (default: 90)
|
2013-07-08 16:02:14 +00:00
|
|
|
``(no-)jpeg-progressive``
|
2012-11-15 13:25:20 +00:00
|
|
|
Specify standard or progressive JPEG (default: no).
|
2013-07-08 16:02:14 +00:00
|
|
|
``(no-)jpeg-baseline``
|
2012-11-15 13:25:20 +00:00
|
|
|
Specify use of JPEG baseline or not (default: yes).
|
2013-07-08 16:02:14 +00:00
|
|
|
``jpeg-optimize=<0-100>``
|
2012-08-22 13:45:34 +00:00
|
|
|
JPEG optimization factor (default: 100)
|
2013-07-08 16:02:14 +00:00
|
|
|
``jpeg-smooth=<0-100>``
|
manpage: merge new manpage
About a year ago, ubitux converted most of the old manpage from the
hard to maintain nroff format to reStructuredText. This was not merged
back into the master repository immediately. The argument was that the
new manpage still required work to be done. However, progress was very
slow. Even worse: the old manpage wasn't updated, because it was
scheduled for deletion, and updating it would have meant useless work.
Now the situation is that the new manpage still isn't finished, and the
old manpage is grossly out of sync with the player. This is not helpful
for users. Additionally, keeping the new manpage in a separate branch,
while the normal development repository for code had the old manpage,
was very inconvenient, because you couldn't just update the
documentation in the same commit as the code.
Even though the new manpage isn't finished yet, merging it now seems to
be the best course of action. Squash-merge the manpage development
branch [1], revision e89f5dd3f2, which branches from the mplayer2
master branch after revision 159102e0cb.
Committers:
* Clément Bœsch <ubitux@gmail.com> (Initial conversion to RST.)
* Uoti Urpala <uau@mplayer2.org> (Many updates.)
* Myself (Minor edits.)
Most text of the manpage has been directly taken from the old manpage,
because this is a conversion, not a complete rewrite.
[1] http://git.mplayer2.org/uau/mplayer2.git/log/?h=man
2012-08-02 19:37:33 +00:00
|
|
|
smooth factor (default: 0)
|
2013-07-08 16:02:14 +00:00
|
|
|
``jpeg-dpi=<1->``
|
2012-08-06 17:15:04 +00:00
|
|
|
JPEG DPI (default: 72)
|
2013-07-08 16:02:14 +00:00
|
|
|
``outdir=<dirname>``
|
2012-08-06 17:15:04 +00:00
|
|
|
Specify the directory to save the image files to (default: ``./``).
|
2013-04-15 20:37:02 +00:00
|
|
|
|
|
|
|
``wayland`` (Wayland only)
|
|
|
|
Wayland shared memory video output as fallback for ``opengl``.
|
|
|
|
|
2014-04-19 13:29:05 +00:00
|
|
|
.. note:: This driver is for compatibility with systems that don't provide
|
|
|
|
working OpenGL drivers.
|
|
|
|
|
2013-04-15 20:37:02 +00:00
|
|
|
``alpha``
|
|
|
|
Use a buffer format that supports videos and images with alpha
|
2013-10-16 10:36:34 +00:00
|
|
|
information
|
2014-02-11 17:55:25 +00:00
|
|
|
``rgb565``
|
|
|
|
Use RGB565 as buffer format. This format is implemented on most
|
|
|
|
platforms, especially on embedded where it is far more efficient then
|
|
|
|
RGB8888.
|
|
|
|
``triple-buffering``
|
|
|
|
Use 3 buffers instead of 2. This can lead to more fluid playback, but
|
|
|
|
uses more memory.
|
|
|
|
|
2014-12-09 20:36:45 +00:00
|
|
|
``opengl-cb``
|
|
|
|
For use with libmpv direct OpenGL embedding; useless in any other contexts.
|
|
|
|
(See ``<mpv/opengl_cb.h>``.)
|
2015-01-08 16:06:17 +00:00
|
|
|
Usually, ``opengl-cb`` renders frames asynchronously by client and this
|
|
|
|
can cause some frame drops. In order to provide a way to handle this
|
|
|
|
situation, ``opengl-cb`` has its own frame queue and calls update callback
|
|
|
|
more frequently if the queue is not empty regardless of existence of new frame.
|
|
|
|
Once the queue is filled, ``opengl-cb`` drops frames automatically.
|
2015-01-05 14:25:58 +00:00
|
|
|
|
2015-01-08 16:06:17 +00:00
|
|
|
With default options, ``opengl-cb`` renders only the latest frame and drops
|
|
|
|
all frames handed over while waiting render function after update callback.
|
|
|
|
|
|
|
|
``frame-queue-size=<1..100>``
|
|
|
|
The maximum count of frames which the frame queue can hold (default: 1)
|
|
|
|
|
|
|
|
``frame-drop-mode=<pop|clear>``
|
|
|
|
Select the behavior when the frame queue is full.
|
|
|
|
|
|
|
|
pop
|
|
|
|
Drop the oldest frame in the frame queue. (default)
|
|
|
|
clear
|
|
|
|
Drop all frames in the frame queue.
|
|
|
|
|
2015-03-19 22:48:32 +00:00
|
|
|
This also supports many of the suboptions the ``opengl`` VO has. Run
|
2015-01-05 14:25:58 +00:00
|
|
|
``mpv --vo=opengl-cb:help`` for a list.
|
|
|
|
|
|
|
|
This also supports the ``vo_cmdline`` command.
|
2015-03-29 13:12:11 +00:00
|
|
|
|
|
|
|
``rpi`` (Raspberry Pi)
|
|
|
|
Native video output on the Raspberry Pi using the MMAL API.
|
|
|
|
|
|
|
|
``display=<number>``
|
|
|
|
Select the display number on which the video overlay should be shown
|
|
|
|
(default: 0).
|
|
|
|
|
|
|
|
``layer=<number>``
|
|
|
|
Select the dispmanx layer on which the video overlay should be shown
|
|
|
|
(default: -10). Note that mpv will also use the 2 layers above the
|
|
|
|
selected layer, to handle the window background and OSD. Actual video
|
|
|
|
rendering will happen on the layer above the selected layer.
|
2015-04-16 19:43:01 +00:00
|
|
|
|
|
|
|
``drm`` (Direct Rendering Manager)
|
|
|
|
Video output driver using Kernel Mode Setting / Direct Rendering Manager.
|
|
|
|
Does not support hardware acceleration. Should be used when one doesn't
|
|
|
|
want to install full-blown graphical environment (e.g. no X).
|
|
|
|
|
|
|
|
``connector=<number>``
|
|
|
|
Select the connector to use (usually this is a monitor.) If set to -1,
|
|
|
|
mpv renders the output on the first available connector. (default: -1)
|
|
|
|
|
|
|
|
``devpath=<filename>``
|
|
|
|
Path to graphic card device.
|
|
|
|
(default: /dev/dri/card0)
|