summaryrefslogtreecommitdiffstats
path: root/DOCS
Commit message (Collapse)AuthorAgeFilesLines
* DOCS/man/input.rst: fix incorrect syntaxsavoury12024-03-061-10/+10
| | | | | | Some incorrect syntax is used in DOCS/man/input.rst with https://github.com/mpv-player/mpv/commit/c678033c1d60b48ae02fbbe4815869b9504a17f6 causing failure of PDF manual generation with rst2pdf. There are single rather than double back-ticks for insert-at and insert-at-play so this is fixed and a couple of typos are also corrected with this commit.
* options: add --deinterlace-field-parity option1nsane0002024-03-042-0/+12
| | | | | | | | Previously there was no way to specify the field order of interlaced videos when deinterlacing with inbuilt filters. Lavfi deinterlacers seemed to prefer top field order while inbuilt ones (vdpaupp, vavpp, d3d11vpp) seemed to prefer bottom field order. The default "auto" option should work exactly as before while specifying either "tff" or "bff" should force the specified field order
* DOCS/options: fix Vulkan typopsykose2024-03-021-1/+1
|
* command: add begin-vo-dragging commandnanahi2024-03-012-0/+8
| | | | | | This command initializes a vo dragging request for VOs that implement the new VOCTRL_BEGIN_DRAGGING voctrl. This allows scripts to begin vo dragging for any button press event.
* Revert "player: add ao-volume option, to set the system volume at startup"Dudemanguy2024-03-013-14/+6
| | | | | | | | Ended up being a bad idea. As a property, this inherently has more functionality and the tradeoff of being able to do --ao-volume wasn't worth it. This reverts commit 58ed620c064971535e60778612777750aa5e2f4d.
* DOCS/options: clarify --sub-blur and --osd-blur optionsnanahi2024-02-271-2/+4
| | | | | Clarify that these options only apply to the font borders, not to the texts themselves.
* vo_gpu_next: add --border-background optionDudemanguy2024-02-262-0/+5
| | | | | Allow for setting the border background independently from the background option.
* vo_gpu/vo_gpu_next: rework --alpha into --background optionDudemanguy2024-02-262-22/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | The --alpha option currently covers two related but different concepts: whether or not to ignore the alpha component and possibly blending it with a background. Because of the way the option currently works, it is impossible to have a transparent window (which requires setting --alpha=yes) while blending it with the background at the same time. To solve this, let's rework it so it it superseded by the background option. --background controls what kind of background to set for the image if possible. It can be blended with the set background color, with tiles, or not blended at all (the last one is still broken on X11/mesa except for GLX, *sigh*). In this new paradigm, --alpha=no has no real purpose because you can simply set the background to color and whatever color you want for exactly the same effect. So the option is removed. Instead, the hint set by windowing backends (i.e. setting ra_ctx->opts.want_alpha) can by done with the --background option. As an aside, the colors in vo_gpu are currently bugged due to not pre-multiplying the alpha and it seems no one ever noticed. The next commit fixes that. vo_gpu_next support happens latter since it requires new things from libplacebo. Fixes #9615.
* player: rename --background to --background-colorDudemanguy2024-02-262-1/+2
| | | | | This better represents what it actually does. --background will be used for another, related option in the next commit.
* osd_libass: update the OSD bar's dent and border sizeGuido Cella2024-02-261-1/+1
| | | | | Make the OSD bar markers bigger so we can default to a smaller, better-looking border size, without sacrificing markers' visibility.
* DOCS/options: make --scale documentation more consistentdokur0chan2024-02-261-8/+9
| | | | | | | | | | | | Beef up the barebones description for the Mitchell filter and make it consistent with the other --scale examples. In addition to this, make some wording changes to make the language in the documentation a bit more unified. Before this change it was pretty obvious that multiple authors contributed to this part of the manual (at completely different timeframes), so the language was somewhat disjointed. The Mitchell description was also not very helpful.
* DOCS: move ALSA option documentation to ao.rstnanahi2024-02-262-51/+47
| | | | | | All other ao options are documented there so make ALSA the same. Also remove the (Linux only) wording since some systems (e.g. FreeBSD) provide compatibility layer for it.
* DOCS/options: clarify the impact of --audio-buffernanahi2024-02-261-1/+1
| | | | | | | | While making this larger do make audio filters react slower, it doesn't always make softvol react slower. This is because the softvol reaction speed is related to the ao buffer size which on many systems have an upper limit, typically much lower than 200 ms. In this case the softvol won't react slower. Change the wording to clarify this.
* DOCS/options: remove lavrresample referencenanahi2024-02-261-7/+2
| | | | | lavrresample is removed in c8b8fe9981c654c0539ca77056ed6451a3da7367. The replacement is the internal swresample filter.
* DOCS/options: remove --alsa-devicenanahi2024-02-261-3/+0
| | | | This option was removed in 809d160c1ec1c050d1877e66f93fcffc98fe4e83.
* DOCS/ao: update SDL ao version referencenanahi2024-02-261-2/+2
| | | | This hasn't been true since 1dcf511376545de7624863b76d7f30dc3bb44ac9.
* DOCS: add `insert` commands and args to interface-changesDavid Vaughan2024-02-261-0/+6
|
* input/player: add loadfile/loadlist insert-at commandDavid Vaughan2024-02-261-5/+31
|
* input: add insert-next support for drag-and-dropDavid Vaughan2024-02-261-7/+8
| | | | | | | This commit adds a DND_INSERT_NEXT action option for drag-and-drop, allows for selecting it through the --drag-and-drop=insert-next option, and adds the necessary plumbing to make that happen when something is dragged onto the player.
* player: add loadlist insert-next commandsDavid Vaughan2024-02-261-0/+7
| | | | | | | | Analogous changes to the previous commit ("add loadfile insert-next commands"), but for the `loadlist` command. This allows us to insert a new playlist next in the current playlist, rather than just appending it to the end.
* player: add loadfile insert-next commandsDavid Vaughan2024-02-261-0/+6
| | | | | | | | | | | | | This commit adds two new commands (`insert-next` and `insert-next-play`) which mirror the existing commands, `append` and `append-play` in functionality, with the difference that they insert directly after the current playlist entry, rather than at the end of the playlist. This change gives MPV a piece of functionality already found in (for example) Spotify's media player: "play next". Additionally, using the new `insert-next` command, users can trivially write a script to play a new piece of media immediately without otherwise clearing or altering the remainder of the playlist.
* DOCS/man: remove outdated softvol entryDudemanguy2024-02-251-13/+2
| | | | 69ae23fdd1e39f4e7aa30082e36cc635d954bccf removed this option completely.
* player: add ao-volume option, to set the system volume at startupLeonardo Boss2024-02-253-6/+14
| | | | closes #12353
* player: set hidpi-window-scale to no by defaultDudemanguy2024-02-242-1/+2
| | | | | | | | | | | | | | | | | | This has defaulted to yes for a very long time, but evidentally it annoys a lot of people (including myself). My argument is that this makes no sense. mpv is for videos; not text. A 1920x1080 video should open as 1920x1080 regardless of whatever the DPI settings of the OS is. This can get very silly when you consider watching a 4k video which will get this additional scale factor which is virtually never desirable. Whether or not the OS and/or WM prevents it from getting larger than the screen depends on a lot of things. Previously some windowing backends required that this option be set to yes in order to report a dpi scale value other than 1, but this should be fixed with the previous commits. The only difference is whether or not to scale the window by the additional factor. Fixes #13465.
* DOCS/options: clarify hidpi-window-scaleDudemanguy2024-02-241-4/+3
|
* DOCS: make mentions of macOS consistentder richter2024-02-214-4/+4
| | | | | change all mentions and variations of OSX, OS X, MacOSX, MacOS X, etc consistent. use the official naming macOS.
* DOCS/man: document Ctrl+WHEEL_UP/WHEEL_DOWN keybindsnanahi2024-02-211-2/+4
| | | | Also remove the existing redundant wordings.
* DOCS/mpv: update ancient profiles config examplellyyr2024-02-201-11/+13
| | | | | Hopefully actually useful now. Also updates big-cache to not be smaller than the current default.
* vo: make libmpv last in the auto-probing order for cocoa-cb onlyder richter2024-02-201-1/+5
| | | | | | | | | | | | | | | | | | | | this partially reverts commit 7b5a258. back then the only properly working vo on macOS was cocoa-cb (libmpv). it would always use the deprecated opengl cocoa backend or no vo at all. because of that libmpv was moved to the top of the auto-probing order, so the preferred vo was used on macOS only. we now have a working vulkan gpu/gpu-next backend on macOS which should be the new default vo. though disabling the auto-probing again for libmpv would probably cause the undesired behaviour on macOS that cocoa-cb would never be auto selected again. especially if not build with vulkan support or without vulkan driver on macOS, this would lead to no video output at all. so instead of completely reverting the mentioned commit, we instead move libmpv to the bottom of the auto-probing order but only auto select it when mpv was built with cocoa-cb support. this restores the previous behaviour on all other platforms besides macOS, but also lets us auto select cocoa-cb if supported.
* DOCS/man: add description of display-names property for waylandnanahi2024-02-161-1/+4
| | | | | | On wayland, depending on the wl_output protocol version used, the display-names property can have different values. Mention this in the documentation, like for other platforms.
* DOCS: document --input-preprocess-wheel optionnanahi2024-02-152-0/+15
| | | | | | Document the use cases for enabling or disabling the wheel preprocessing. Also note that this option has no effect on any filtering already done by the OS/driver.
* DOCS/lua: clarify `repeatable` and `complex` for `add_key_binding`gaesa2024-02-151-5/+6
| | | | | | | | | | | | | | | | The current documentation lacks clarity regarding the interaction between the `repeatable` and `complex` options. Through an analysis of the source code (`player/lua/defaults.lua` and `player/js/defaults.js`), it was observed that the `repeatable` option is only meaningful when the `complex` option is not enabled. Additionally, the `complex` option in the existing documentation is confusing, actually `fn` can be called on key repeat when `complex` is `true` and `repeatable` is not `true`. To address these issues, the documentation for the `repeatable` option was updated to specify that it only applies when the `complex` option is not set to `true`. Furthermore, the description of the `complex` and `event` were revised to acknowledge the occurrence of key repeat events.
* DOCS/options: mention that sub-clear-on-seek can now break thingsDudemanguy2024-02-151-1/+3
| | | | | | | | | | | | | | | | | This is technically due to the previous commits that made subtitle rendering more efficient by eliminating redraws, but working around this particular edge case is useless. The sub-clear-on-seek option was originally introduced in d5940fabcd6b477c72430c84e460975060807646 and specifically is a workaround for completely broken mkv files. There is no reason to use it otherwise. Because that option disables all duplicate checking and the previous commits rework subtitle rendering in the still image case to be dependent on keeping track of packets, the end result is that you will get the same line rendered multiple times. However the important case of broken mkv files with duplicate ReadOrder fields still work just fine with --no-video. So instead of bothering trying to make this option "work", just clarify that stuff can break since, again, there's no reason to use it other than as a workaround for broken files.
* DOCS/man: more words about --teletext-pageMohammad AlSaleh2024-02-131-2/+11
| | | | Signed-off-by: Mohammad AlSaleh <CE.Mohammad.AlSaleh@gmail.com>
* sub: allow setting lavc txt_page special values via teletext_pageMohammad AlSaleh2024-02-132-2/+6
| | | | | | | | * Range of accepted values for teletext_page now include 0 and -1. * 0 means "subtitle" and -1 means "*". * Make 0 the default. Signed-off-by: Mohammad AlSaleh <CE.Mohammad.AlSaleh@gmail.com>
* player/command: add deinterlace-active propertyDudemanguy2024-02-071-0/+5
|
* player: add an auto option to deinterlaceDudemanguy2024-02-073-11/+11
| | | | | | | | | | Deinterlacing required that the user set it on/off themselves, but we actually have handy flags for detecting if a frame is interlaced. So it's pretty simple to make an auto option using that. Unfortunately, life is not quite that simple and there are known cases of false positives from the ffmpeg flags so we can't make auto the default value. However, it still may have some utility for some people, and the detection could potentially be improved upon later. Closes #10358.
* player: remove all rpi-specific codeDudemanguy2024-02-053-29/+1
| | | | | | | | | | | | | | | | | | | | | | vo_rpi and its related code has pretty much historically been a disaster in mpv. The build regularly gets broken and since nobody uses it, it takes months for anyone to notice. There was also that time where fullscreen was broken for about a year and a half. Also building in waf was entirely broken for about a couple of years or so due to mysterious reasons no one ever figured out (meson magically fixed it). Anyways, once again the build is broken due to rpi being forgotten about again, but instead of pretending to support this crap. Just drop it all. Nowadays, mmal hwdec is a relic since these devices are better off using the v4l2m2m ffmpeg fork instead which actually uses KMS properly. RPI 1 and 2 probably can't do this and will remain broken but oh well blame Broadcom for being special snowflakes and not using standard APIs (my rockpro worked out of the box; just saying). RPI 2 is nearly 10 years old anyways, so I think you can afford a new SBC by now. If we were nicer, there would be a deprecation period, but this is broken in the last major release anyway so too late. Closes #13402.
* command: add load-input-confGuido Cella2024-02-042-0/+6
| | | | | | | | | | | | | | | | This can be used to auto reload the input configuration file, e.g. in vim: autocmd BufWritePost ~/.config/mpv/input.conf silent !echo load-input-conf %:p | socat - /tmp/mpvsocket Partially fixes #6362. Additionally this can be used as a replacement for deprecated input sections if they are ever actually removed. For example, if you want to define different bindings for images, you can load-input-conf an input.conf for images, and load the original again when switching to a video. Though currently you would have to redefine builtin bindings that were overwritten with image ones in the default input.conf.
* command: add load-config-fileGuido Cella2024-02-042-0/+6
| | | | | | | | Unlike set include mpv.conf, this works after playback has started. It can be used to auto reload the configuration, e.g. in vim: autocmd BufWritePost ~/.config/mpv/mpv.conf silent !echo load-config-file %:p | socat - /tmp/mpvsocket Partially fixes #6362.
* DOCS/mpv: document how mf:// URLs are formedGuido Cella2024-02-021-1/+12
|
* x11_common: support --title-barnanahi2024-02-021-1/+1
| | | | | | | | | Some X11 window managers support controlling the title bar independently from other window decorations with _MOTIF_WM_HINTS. This allows hiding the title bar while keeping other decorations like the resizing borders. Let mpv respect the --title-bar option on X11 so --no-title-bar can hide the title bar only like on win32.
* vo_gpu_next: save cache to separate filesKacper Michajłow2024-01-311-6/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Save the cache to separate files to avoid loading/saving a huge combined libplacebo.cache. This approach allows the saving of only new cache objects and avoids resaving the entire cache, especially even if only a tiny change was made. This commit improves the cold start time of mpv and avoids saving data when it's not necessary. Number of changes were made: - each cached object is saved in its own file - cache files are prefixed with the name of cached object - cache directory is cleaned on each uninit - the least recently used cache files are removed if cumulative cache size is above limit - files used in the recent 24 hours are not removed to allow changes to mpv.conf without worrying about the cache being removed during experimentation - shader cache size limit is set to 128 MiB - icc cache size limit is set to 1.5 GiB - cache objects are loaded/saved as needed This commit eliminates the runtime performance penalty associated with the size cache. While we continue to maintain the cache limit to prevent retaining stale objects, mpv now only loads a small subset of files that are currently required for playback, instead of loading all files.
* osc: add osc-windowcontrols_title optionDudemanguy2024-01-221-0/+7
| | | | | This allows the title shown with the windowcontrols to be controlled separately from the normal osc title. Fixes #13295.
* f_auto_filters: change fallback deinterlace to bwdifDudemanguy2024-01-213-2/+3
| | | | | | | I don't actually deinterlace ever but allegedly this is better than yadif, and there's no real reason to not have this be the fallback deinterlace when we're not using hw frames. Also change various mentions of yadif to bwdif. Ref #12835.
* sub: add `--sub-lavc-o` optionMohammad AlSaleh2024-01-211-0/+7
| | | | | | | We have `--vd-lavc-o` and `--ad-lavc-o`, but no equivalent option for subtitles. Signed-off-by: Mohammad AlSaleh <CE.Mohammad.AlSaleh@gmail.com>
* player: remove --term-remaining-playtime optionDudemanguy2024-01-202-4/+1
| | | | | This wasn't useful and didn't even really do what it said anyway. Closes #12167.
* command: export current-gpu-context propertynanahi2024-01-202-0/+5
| | | | | | | This exports `current-gpu-context` property, which is the string description of the current active GPU context. This allows scripts to uniquely identify the platform and backend used for --vo=gpu and --vo=gpu-next.
* DOCS/*: remove mentions of Libavllyyr2024-01-205-18/+14
|
* scripting: don't observe properties with type nilGuido Cella2024-01-201-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | mp.observe_property('foo', nil, ...) calls the handler at least 2 times on each playlist change even when the property doesn't change. This is dangerous because if you haven't read observe_property's documentation in a long time this is easy to forget, and you can end up using it for handlers that are computationally expensive or that cause unintended side effects. Therefore, this commit discourages its use more explicitly in the documentation, and replaces its usages in scripts. For console.lua, observing focused with type nil leads to calling mp.osd_message('') when changing file while playing in the terminal with the console disabled. I don't notice issues from this, but it's safer to avoid it. For playlist and track-list this doesn't really matter since they trigger multiple changes on each new file anyway, but changing it can avoid encouraging people to imitate the code. One usage of none in stats.lua is kept because according to b9084dfd47 it is a hack to replicate the deprecated tick event.
* DOCS: reorder --volume-max documentation to where --volume isnanahi2024-01-201-4/+4
|
* DOCS: add documentation for --volume-gain optionsnanahi2024-01-202-0/+8
|
* console.lua: style log lines in the terminalGuido Cella2024-01-141-4/+10
| | | | | | | | | | When running the console in the terminal, style log lines with the same escape sequences as msg.c. mp.input can also specify terminal escape sequences, e.g. a script to select a playlist entry can invert the color of the selection. Also add a missing newline to help's error message.
* DOCS/mpv: the playback position is not remembered after poweroffGuido Cella2024-01-131-4/+4
| | | | | | | | | | | This doesn't actually work on either Windows or Linux with --terminal. With --no-terminal or --no-input-terminal the SIGTERM handler is never registered, so it definitely can't work. Just remove the note about signals because it would be complicated to explain that they don't terminate abruptly only with --terminal and only if that signal has a handler, and it wouldn't be of interest to most users.
* player: add forced choice to subs-with-matching-audioDudemanguy2024-01-132-5/+8
| | | | | | | | | | fe875083b3d30b06ef77745f40570e8f63afec2 confused things a bit and made --no-subs-with-matching-audio actually mean what it says: no subtitles if the languages match. However, the option actually meant no non-forced subtitles not no subtitles at all. This isn't really intuitive so instead of changing the behavior back to the old way (we already have a release since then), add a third option "forced" which is equivalent to the old meaning of --no-subs-with-matching audio. Fixes #13151.
* scripting: add mp.inputGuido Cella2024-01-133-6/+100
| | | | This lets scripts get textual input from the user using console.lua.
* vo_gpu_next: respect d3d11 swapchain output format preferencenanahi2024-01-061-0/+5
| | | | | | | | | | Currently, libplacebo always tries to reconfigure the d3d11 swapchain to a 10-bit output format because disable_10bit_sdr isn't set to true, even when an 8-bit format is explicitly requested via --d3d11-output-format. Fix this by passing the requested output format preference to libplacebo. Document that this option may be ignored.
* DOCS/options: note that --geometry doesn't fully work on waylandDudemanguy2024-01-041-0/+5
| | | | | Positioning windows won't work on wayland so note it here to hopefully avoid confusing users.
* DOCS/ao: change wrong note on which driver is preferredGuido Cella2024-01-011-3/+2
| | | | |