diff options
| author | wm4 <wm4@nowhere> | 2019-10-31 16:45:28 +0100 |
|---|---|---|
| committer | wm4 <wm4@nowhere> | 2019-10-31 16:51:12 +0100 |
| commit | a7230dfed0bf563fd9f4673c3020d1cf8461febf (patch) | |
| tree | d34d333e6f627842aa55e4737a441710d700820d /DOCS/man/vo.rst | |
| parent | 2c43d2b75a88b8e0e8f0a715f993ffc1c8977d13 (diff) | |
| download | mpv-a7230dfed0bf563fd9f4673c3020d1cf8461febf.tar.bz2 mpv-a7230dfed0bf563fd9f4673c3020d1cf8461febf.tar.xz | |
sws_utils, zimg: destroy vo_x11 and vo_drm performance
Raise swscale and zimg default parameters. This restores screenshot
quality settings (maybe) unset in the commit before. Also expose some
more libswscale and zimg options.
Since these options are also used for VOs like x11 and drm, this will
make x11/drm/etc. much slower. For compensation, provide a profile that
sets the old option values: sw-fast. I'm also enabling zimg here, just
as an experiment.
The core problem is that we have a single set of command line options
which control the settings used for most swscale/zimg uses. This was
done in the previous commit. It cannot differentiate between the VOs,
which need to be realtime and may accept/require lower quality options,
and things like screenshots or vo_image, which can be slower, but should
not sacrifice quality by default.
Should this have two sets of options or something similar to do the
right thing depending on the code which calls libswscale? Maybe. Or
should I just ignore the problem, make it someone else's problem (users
who want to use software conversion VOs), provide a sub-optimal
solution, and call it a day? Definitely, sounds good, pushing to master,
goodbye.
Diffstat (limited to 'DOCS/man/vo.rst')
| -rw-r--r-- | DOCS/man/vo.rst | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/DOCS/man/vo.rst b/DOCS/man/vo.rst index ea2d3ee645..50db983f06 100644 --- a/DOCS/man/vo.rst +++ b/DOCS/man/vo.rst @@ -71,6 +71,9 @@ Available video output drivers are: Shared memory video output driver without hardware acceleration that works whenever X11 is present. + Since mpv 0.30.0, you may need to use ``--profile=sw-fast`` to get decent + performance. + .. note:: This is a fallback only, and should not be normally used. ``vdpau`` (X11 only) @@ -383,6 +386,9 @@ Available video output drivers are: Depends on support of true color by modern terminals to display the images at full color range. On Windows it requires an ansi terminal such as mintty. + Since mpv 0.30.0, you may need to use ``--profile=sw-fast`` to get decent + performance. + ``--vo-tct-algo=<algo>`` Select how to write the pixels to the terminal. @@ -482,6 +488,9 @@ Available video output drivers are: environment (e.g. no X). Does not support hardware acceleration (if you need this, check the ``drm`` backend for ``gpu`` VO). + Since mpv 0.30.0, you may need to use ``--profile=sw-fast`` to get decent + performance. + The following global options are supported by this video output: ``--drm-connector=[<gpu_number>.]<name>`` @@ -583,4 +592,7 @@ Available video output drivers are: Shared memory video output driver without hardware acceleration that works whenever Wayland is present. + Since mpv 0.30.0, you may need to use ``--profile=sw-fast`` to get decent + performance. + .. note:: This is a fallback only, and should not be normally used. |