summaryrefslogtreecommitdiffstats
path: root/DOCS
Commit message (Collapse)AuthorAgeFilesLines
* DOCS/options: clarify `no-config` is a command line flagllyyr2023-10-271-0/+1
| | | | This option does nothing when put inside config files.
* javascript: use --js-memory-report option instead of MPV_LEAK_REPORTDudemanguy2023-10-263-2/+10
| | | | | | | | The MPV_LEAK_REPORT environment variable was previously read in order to determine whether or not to enable memory reporting for javascript scripts. This is kind of weird and deviates from the norm of exposing an option to the user. So let's just add --js-memory-report and disable it by default instead.
* options: rename --play-dir to --play-directionDudemanguy2023-10-252-2/+3
| | | | | | --play-dir sounds like it has something to do with directories so change it. The play_dir variable is used a bunch everywhere internally so whatever just leave it alone instead of renaming that.
* options: rename --watch-later-directory to --watch-later-dirDudemanguy2023-10-252-1/+2
| | | | Same logic as the previous commit.
* options: rename --screenshot-directory to --screenshot-dirDudemanguy2023-10-252-1/+2
| | | | | Less characters is better? Other options use -dir for directory so consistency I guess.
* options: rename --sub-ass-force-style to --sub-ass-style-overridesDudemanguy2023-10-252-3/+4
| | | | | | | This option has exactly the same semantics are other mpv options that override a particular thing with something from the user. So instead of the "force-style" name, use "-overrides" which is more consistent. The plural form is used since it's a list option.
* options: rename --override-display-fps to --display-fps-overrideDudemanguy2023-10-252-2/+3
| | | | | | Other similar options are in the form of --foo-override not --override-foo. The display-fps one was backwards so flip it around the other way for consistency reasons.
* options: rename --fps to --container-fps-overrideDudemanguy2023-10-254-8/+10
| | | | | | This better reflects what it actually does. As a bonus, script writers won't be misled into thinking that fps displays the actual video or display fps.
* options: disable --allow-delayed-peak-detect by defaultKacper Michajłow2023-10-252-1/+2
| | | | | | Peak detection greatly increases HDR experience. Performance hit of non-delayed detection is not that significant and is in line with current default settings.
* DOCS/contribute: increase hard column limit to 100Dudemanguy2023-10-221-2/+2
| | | | | | | I'm guilty of violating this, but surely I can't be the only one. 85 is pretty small and there's plenty of lines in the codebase that go well over that. Surely nobody programs on tiny screens anymore and the kernel raised the limit to 100 a few years ago so let's just copy that.
* stats.lua: disable tonemapping plot by defaultDudemanguy2023-10-221-1/+1
| | | | | | Nobody except a chosen few (I'm not one of them) even knows what it means. Multiple people thought it was actually some kind of rendering bug. Just disable it by default. Closes #12671.
* DOCS/contribute: stop pretending that C11 isn't allowedDudemanguy2023-10-211-6/+7
| | | | | Doesn't really make much of a different in practice aside from us dropping ancient legacy fallbacks but still.
* osdep: drop atomic fallbackNRK2023-10-201-2/+1
| | | | | even msvc (which mpv apparently doesn't support) supports C11 atomics now. no need to carry around fallback with subtle semantic differences.
* stream_cdda: deprecate --cdda-toc-bias and always check for offsetsDudemanguy2023-10-192-5/+1
| | | | | | | | | | | | | | | | I started going through the blame but once I got to mplayer commits from 20 years ago, I stopped bothering. This obscure option has always been disabled by default, but there's zero reason, as far as I know, to not just enable it today. Some CDs (particularly very old ones) have the first sector shifted a bit and not starting exactly at 0. This makes the logic that tries to get all the chapters completely fail and thus you can't skip through tracks. However if you just enable this obscure option, it just works. For anything that starts exactly at 0, the calculated offset is just 0 anyway so it's a no-op and works exactly the same. So basically, there's literally no reason to not just always try to correct for the offset of the first sector by default. Fixes #8777.
* DOCS/options: remove obsolete noticeGuido Cella2023-10-171-4/+0
| | | | | This may have been true 10 years ago but now reset-on-next-file can definitely reset options that weren't explicitly set.
* DOCS/mpv: fix typos in List OptionsGuido Cella2023-10-171-5/+3
|
* DOCS/interface-changes: remove redundant changeGuido Cella2023-10-171-1/+0
| | | | directory-mode's default was changed again to auto afterwards.
* af_scaletempo2: better defaultsChristoph Heinrich2023-10-151-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Why a bigger search-interval is required: scaletempo2 doesn't do a good job when the signal contains frequencies less then 1/search_interval. With a search interval of 30ms that means anything below 33.333Hz sounds bad. Depending on the genre it's very for music to contain frequencies down to 30Hz, and sometimes even a little bit below that. Therefore a higher default value is needed to handle such cases. Based on that an argument can be made for a value of 50, as that should work down to 20Hz, or something even higher because movies sometimes have some infrasonic content. However the downside of big search intervals is increased CPU usage and intelligibility at higher speeds, as it effectively leads to parts of the audio being skipped. A value of 40 can handle frequencies down to 25Hz, enough for all music except very rare edge cases, while still providing decent intelligibility. Why a smaller window-size is required: Large values reduce intelligibility at high speeds and therefore small values are preferred. However when values get too small it starts to sound weird (similar to librubberband). In my testing a value of 10 already works well, but adding a small safety margin seems like a good idea, especially since it made no noticeable difference to intelligibility, which is why 12 was chosen.
* vo_gpu/vo_gpu_next: add vulkan support for macOSder richter2023-10-141-0/+14
| | | | | | | | add support for vulkan through metal and a translation layer like MoltenVK. also add the possibility to use different render timing modes for testing. i still consider this experimental atm.
* f_decoder_wrapper: change video-codec to show description or nameKacper Michajłow2023-10-141-0/+1
| | | | | | | | Not both of them. Formating it as `<name> (<desc>)` produced arguably silly string like `hevc (HEVC (High Efficiency Video Coding))`. Unpack this to show only description if available or name otherwise. Produces way nicer results in stats.lua and similar places where this name is printed.
* defaults.lua: add a disabled parameter to timer constructorsMike Will2023-10-111-2/+6
| | | | | | | | Added to the functions `mp.add_timeout` and `mp.add_periodic_timer`. If the `disabled` argument is set to `true` or a truthy value, the timer will wait to be manually started with a call to its `resume()` method.
* DOCS/options: vdpau requires GLXGuido Cella2023-10-111-1/+2
| | | | | | | Only vpdau-copy works with EGL. 2d1d815cc7 already added this to manpage, and 1c8d2246bf removed it again, but that seems to be a mistake because I can only get vdpau to work with GLX, and another user also reported that only vdpau-copy was working for him with the default EGL.
* libmpv: add mpv_time_ns()Dudemanguy2023-10-101-0/+2
| | | | | | 9606c3fca9d568dc43711017dcb35a408c0d2883 added mp_time_ns(). Since we apparently expose the mp_time_us() to clients already, there's no reason to not also expose the new nanosecond one.
* DOCS/lua: update read_options exampleGuido Cella2023-10-101-2/+2
| | | | | This still shows the old way of calling read_options even though it was deprecated 8 years in ago 327b091909e.
* console.lua: exit with with Ctrl+[Guido Cella2023-10-101-1/+1
| | | | | This binding commonly closes similar input buffers like vim's Command-line mode and dmenu.
* command: add playlist-next-playlist and playlist-prev-playlistGuido Cella2023-10-092-0/+8
| | | | | | | | | | | | playlist-prev-playlist goes to the beginning of the previous playlist because this seems more useful and symmetrical to playlist-next-playlist. It does not go to the beginning when the current playlist-path starts with the previous playlist-path, e.g. with mpv --loop-playlist foo/, which expands to foo/{1..9}.zip, the current playlist path foo/1.zip beings with the playlist-path foo/ of {2..9}.zip and thus playlist-prev-playlist goes to 9.zip rather than to 2.zip. Closes #12495.
* DOCS/input: document the full sub-propertyGuido Cella2023-10-071-0/+30
|
* console: show completion suggestions as tableChristoph Heinrich2023-10-071-2/+10
| | | | | | | | | | | | Completion suggestions are now nicely formatted into a table. Maximum width of the table is estimated based on OSD size and font size. This requires a new scaling factor option `font_hw_ratio`. A factor of 2.15 works great for me, but the default is 2.0 to avoid problems with other fonts. The space between columns is automatically adjusted to be between 2 and 8 spaces. It tries to use as few rows as possible.
* demux: change the default of metadata-codepage to autoDudemanguy2023-10-072-4/+4
| | | | | | | There's really no reason not to do this especially since sub-codepage already defaults to auto. Also change logging in charset_conv since telling us that the data is UTF-8 if the passed codepage value is "auto" or "utf-8" is really not useful information (that's the expectation).
* demux_cue: deprecate --demuxer-cue-codepage for --metadata-codepageDudemanguy2023-10-072-3/+1
| | | | | | | | | What are cue sheets not metadata or something? No reason this needs to be a separate option so just deprecate it. This does mean that the default value changes from "auto" to "utf-8" for this obscure fringe case. I really hope people don't use non-UTF-8 cuesheets, but the next commit will change the default of --metadata-codepage to "auto" so there's no actual change in behavior to users.
* charset_conv: remove ancient warning about deprecated syntaxDudemanguy2023-10-071-3/+0
| | | | | wm4 removed this in 4adfde5dd1e67775228a345cea00ea03ba6bc68f and left a warning. Nobody needs to know that enca:pl used to work.
* af_scaletempo: overlap is a factor not a percentageChristoph Heinrich2023-10-071-2/+2
|
* DOCS/mpv: update mpv.conf's documentationGuido Cella2023-10-061-17/+21
|
* af/vf-command: add ability to target a specific lavfi filterAshyni2023-10-051-8/+13
| | | | fixes: #11180
* external_files: remove duplicate from cover art whitelistGuido Cella2023-10-041-2/+2
| | | | | I made a mistake in 0070a5820e here because there were 2 separate groups of "front" filenames.
* path: don't override "cache" and "state" paths with configdirsfan52023-10-022-0/+4
| | | | | | | | | | This reverts commit 576e86bfa18a0a79e591988ad93ed009edc40849 (functionally). Right now, the --config-dir option silently causes all watch_later and cache files to be written in the --config-dir as well. This is pretty uninitutive and also not desirable in most cases so get rid of this. libmpv users will have to set the corresponding options or env vars if they want to keep the old behaviour.
* external_files: base cover-art-whitelist on cover-art-auto-extsGuido Cella2023-10-011-3/+4
| | | | | | | | | | Combine the cover art whitelist with the extensions in --cover-art-auto-exts instead of hardcoding them. This is shorter, checks for more extensions, saves us from updating the whitelist everytime we add a new image extension, and since the whitelist had gotten so big and the priority is calculated as MP_ARRAY_SIZE(cover_files) - n, files like cover.jpg were taking priority over cover art loaded by --cover-art-auto=exact.
* DOCS/interface-changes: also mention --window-affinityDudemanguy2023-10-011-0/+1
| | | | | Added in 2c738ca54b16cdd1982473672bd39068fcf8d948. I guess we seem to always mention any added option these days so might as well.
* DOCS/interface-changes: mention --backdrop-typeKacper Michajłow2023-10-011-0/+1
| | | | Added in f19ada7b583e9bf78de38d228a956c365b5c417b
* DOCS/lua: remove superfluous parameterChristoph Heinrich2023-09-301-1/+1
| | | | This seems to have been a leftover from copying the entry below it.
* command: deprecate shared-script-propertiesDudemanguy2023-09-271-0/+1
| | | | user-data is simply better.
* DOCS/options: update lavfi-complex examplesGuido Cella2023-09-271-2/+2
| | | | | Show how to stack 3 or more videos, and remove the life filter example because it should be used with av://lavfi:life.
* af_scaletempo2: raise max playback rate to 8.0llyyr2023-09-271-1/+1
| | | | | | 4.0 was too low and copied from Chromium defaults when the filter was initially written, there's no good reason for it to be so low, so double it.
* DOCS/options: add example for custom pitch correction filterllyyr2023-09-271-2/+16
|
* DOCS/mpv: update the wheel bindingsGuido Cella2023-09-271-2/+2
| | | | Update the docs to the new bindings set by 981a9372ff.
* win32: add option to change backdrop styleDeadSix2023-09-271-0/+10
|
* DOCS/options: update libplacebo-opts documentation URLNiklas Haas2023-09-261-1/+1
|
* input.conf: make `u` toggle between force and yesllyyr2023-09-251-3/+3
| | | | | | | | There was a discrepancy in what the keybind was advertised to do in the manual, and what the comment in input.conf described it to be doing. It makes very little sense to add a keybind that changes the default and doesn't allow you to get back to the default. This keybind is much more useful if it toggles between yes/force instead of no/force.
* DOCS/input: update aegisub URLGuido Cella2023-09-251-1/+1
|
* vo_gpu: remove --scaler-lut-sizeNiklas Haas2023-09-252-8/+1
| | | | | | | Pointless bloat option, hard-coded as 256 now in libplacebo and no reason not to also hard-code in mpv. See-Also: haasn/libplacebo@64d7c5aab06766a9492d3cfffd35333792052cd9
* vo_gpu: remove --scale-cutoff etcNiklas Haas2023-09-252-8/+1
| | | | | | | Pointless bloat option, hard-coded as 1e-3 now in libplacebo and no reason not to also hard-code in mpv. See-Also: haasn/libplacebo@64d7c5aab06766a9492d3cfffd35333792052cd9
* DOCS/af: update audio filters sectionllyyr2023-09-241-6/+22
|
* DOCS/man: remove outdated note about gnome and idle-inhibitDudemanguy2023-09-241-3/+0
| | | | They support it now.
* stream_cdda: move cdrom-device to cdda_paramsDudemanguy2023-09-222-2/+3
| | | | | | There is zero reason for this to be an MPOpt. Because of how the OPT_SUBSTRACT works, the option gets renamed to cdda-device instead, but probably not a big deal since the old alias is still in place.
* DOCS/options: remove some stray tabsDudemanguy2023-09-211-2/+2
| | | | | Accidentally added in 2c738ca54b16cdd1982473672bd39068fcf8d948 on a couple of lines. This is what I get for only looking at git webui diff.
* win32: add --window-cornersKacper Michajłow2023-09-212-0/+10
| | | | Allows to set preference for window corners rounding for DWM.
* win32: add an option to control window title bar stateKacper Michajłow2023-09-212-0/+7
| | | | Fixes: #11432
* win32: add an option to change window affinityDeadSix2023-09-211-4/+11
|
* vo_gpu: allow deband-iterations to be 0llyyr2023-09-211-1/+1
| | | | | THis allows adding grain without debanding. libplacebo already supported this, so no changes are required there.
* drm: remove selecting the card number with --drm-connectorDudemanguy2023-09-212-6/+5
| | | | | | f56043759494dd584c8d82e7890f92fada18e34b deprecated this since the --drm-device path option was added as a replacement. Drop the card number selection logic.
* options: remove --vf-defaults and --af-defaultsDudemanguy2023-09-213-10/+3
| | | | | | | These were deprecated a long time ago and apparently didn't even work with lavfi filters. Go ahead and remove them and additionally clean up some code related to them. m_config_from_obj_desc_and_args becomes much simpler now and a couple of arguments can be completely removed.
* options: remove deprecated --record-file optionDudemanguy2023-09-212-10/+1
| | | | | | No wonder wm4 wanted to get rid of this. This option requires touching a bunch of crap in the core player code. --stream-record works perfectly fine and is a lot nicer so there's no need for this to exist anymore.
* options: remove a few options marked with .deprecation_messageDudemanguy2023-09-213-26/+2
| | | | | | | | | | | A bit different from the OPT_REPLACED/OPT_REMOVED ones in that the options still possibly do something but they have a deprecation message. Most of these are old and have no real usage. The only potentially controversial ones are the removal of --oaffset and --ovoffset which were deprecated years ago and seemingly have no real replacement. There's a cryptic message about --audio-delay but who knows. The less encoding mode code we have, the better so just chuck it.
* command: stop restarting playback when writing to playlist-posDudemanguy2023-09-212-4/+5
| | | | | | | | | e9e93b4dbe748cd341a6fbea355e6ba013ada81b added a warning about writing the same value to the playlist-pos property that in the future it would stop restarting playback. Instead, you should use the playlist-play-index command for that. Well go ahead and drop the old deprecated behavior now and do what wm4 wanted this to do: just ignore if the same value is written again.
* command: remove some old deprecated properitiesDudemanguy2023-09-212-9/+3
| | | | | | | | drop-frame-count and vo-drop-frame-count are ancient and have no reason to exist anymore. The other change is that support for writing to display-fps has been removed, and the property is strictly read-only now. 3a2dc8b22e9f947c9cd3a91445b0731b8df1d798 is what deprecated it with a warning to users, so we can remove it without much trouble.
* options: remove ancient option fallbacks/deprecationDudemanguy2023-09-212-37/+5
| | | | | | | | | | | | | We've got an ungodly amount of OPT_REPLACED and OPT_REMOVED sitting around in the code. This is harmless, but the vast majority of these are ancient. 26f4f18c0629998a9b91e94722d166866d8b80a3 is the last commit that touched the majority of these and of course that only changed how options were declared so all of this stuff was deprecated even before that. No use in keeping these, so just delete them all. As an aside, there was actually a cocoa_opts but it had only a single option which was replaced by something else and empty otherwise. So that entire thing was just simply removed. OPT_REPLACED/OPT_REMOVED declarations that were added in 0.35 or later were kept as is.
* builtin.conf: remove deprecated opengl-hq profileDudemanguy2023-09-211-0/+1
| | | | | Deprecated in 65979986a923a8f08019b257c3fe72cd5e8ecf68. 6 years is more than enough time.
* demux_playlist: add --directory-mode=autoGuido Cella2023-09-212-2/+4
| | | | This is a more useful default with --shuffle.
* options: make video-crop validation more strictKacper Michajłow2023-09-201-1/+1
|
* vo_gpu: match libplacebo debanding defaultsNiklas Haas2023-09-202-2/+3
| | | | | | |