summaryrefslogtreecommitdiffstats
path: root/DOCS/interface-changes.rst
Commit message (Collapse)AuthorAgeFilesLines
* Release 0.38.0v0.38.0release/0.38sfan58 days1-0/+8
|
* DOCS: document the new way to handle interface changesDudemanguy2024-03-201-3/+6
| | | | | | | Manually editing interface-changes.rst is a giant maintenance pain that causes merge conflicts all the time. Stop doing that nonsense and instead have changes be written to files in DOCS/interface-changes. Also remove that one sentence in changes.rst because it's just not true.
* builtin.conf: remove debanding from the high-quality profileKacper Michajłow2024-03-191-0/+1
| | | | | | | | | | | | | | | Debanding is an inherently destructive process. It is not needed for most high-quality sources and only produces an adverse smoothing effect when applied to fine-detailed content, removing detail. It should only be applied when necessary, either manually with the `b` keybind or with an automatic profile. Additionally, it is quite computationally heavy with no real benefit for high-quality content. By default, and especially in the high-quality profile, mpv should preserve source detail and quality as much as possible. Additional processing should be opt-in.
* options: remove --focus-on-open and add --focus-onder richter2024-03-101-0/+1
| | | | | | | | | replaces the old focus-on-open option with a more generic focus-on options that can be extended. adjust the only platform that uses that option. Fixes #8337
* vf_format: add hdr10plus sub-parameter to format video filterKacper Michajłow2024-03-091-0/+1
|
* vo: add video-target-params propertyKacper Michajłow2024-03-071-0/+1
|
* options: add --deinterlace-field-parity option1nsane0002024-03-041-0/+1
| | | | | | | | 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
* command: add begin-vo-dragging commandnanahi2024-03-011-0/+1
| | | | | | 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-011-2/+0
| | | | | | | | 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.
* vo_gpu_next: add --border-background optionDudemanguy2024-02-261-0/+1
| | | | | Allow for setting the border background independently from the background option.
* vo_gpu/vo_gpu_next: rework --alpha into --background optionDudemanguy2024-02-261-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | 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-261-0/+1
| | | | | This better represents what it actually does. --background will be used for another, related option in the next commit.
* DOCS: add `insert` commands and args to interface-changesDavid Vaughan2024-02-261-0/+6
|
* player: add ao-volume option, to set the system volume at startupLeonardo Boss2024-02-251-0/+2
| | | | closes #12353
* player: set hidpi-window-scale to no by defaultDudemanguy2024-02-241-0/+1
| | | | | | | | | | | | | | | | | | 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: make mentions of macOS consistentder richter2024-02-211-1/+1
| | | | | change all mentions and variations of OSX, OS X, MacOSX, MacOS X, etc consistent. use the official naming macOS.
* DOCS: document --input-preprocess-wheel optionnanahi2024-02-151-0/+1
| | | | | | 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.
* sub: allow setting lavc txt_page special values via teletext_pageMohammad AlSaleh2024-02-131-0/+1
| | | | | | | | * 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: add an auto option to deinterlaceDudemanguy2024-02-071-0/+1
| | | | | | | | | | 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-051-0/+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-041-0/+1
| | | | | | | | | | | | | | | | 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-041-0/+1
| | | | | | | | 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.
* f_auto_filters: change fallback deinterlace to bwdifDudemanguy2024-01-211-0/+1
| | | | | | | 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.
* player: remove --term-remaining-playtime optionDudemanguy2024-01-201-0/+1
| | | | | This wasn't useful and didn't even really do what it said anyway. Closes #12167.
* command: export current-gpu-context propertynanahi2024-01-201-0/+1
| | | | | | | 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: add documentation for --volume-gain optionsnanahi2024-01-201-0/+1
|
* player: add forced choice to subs-with-matching-audioDudemanguy2024-01-131-0/+1
| | | | | | | | | | 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-131-0/+1
| | | | This lets scripts get textual input from the user using console.lua.
* DOCS/interface-changes: add --secondary-sub-ass-overrideJohhanSam2023-12-241-0/+1
| | | | Option added in b563b2ae
* filter_sdh: add --sub-filter-sdh-enclosures optionDudemanguy2023-12-081-0/+1
| | | | | | | | | | | This filter is a bit complicated, but one of the essential parts of it is removing text enclosed by particular set of characters (e.g. text inbetween []). This was previously hardcoded to only take into account parenthesis and brackets, but people may want to filter more things so make this customizable. The option only takes "left hand characters" so the right pair is mapped internally if applicable. If not, then we just use the same character. Fixes #8268 since the unicode character in question can just be passed to this option.
* DOCS/interface-changes: document renaming of MP_KEY_BACKnanahi2023-12-061-0/+1
| | | | The navigation key is renamed to avoid conflict with MP_KEY_FORWARD.
* image_writer: default to lossless AVIF screenshotsKacper Michajłow2023-12-041-0/+1
| | | | | Also change the example to crf=23. crf=32 is pretty bad quality, don't give users bad usage ideas.
* image_writer: use common format selection for AVIF screenshotsKacper Michajłow2023-12-041-0/+1
| | | | --screenshot-avif-pixfmt no longer defaults to yuv420p.
* options: add --osd-bar-border-sizeGuido Cella2023-11-271-0/+1
| | | | | Closes #1484. The default size is smaller than the previous --osd-border-size default value of 3 with the default --osd-bar-h.
* options: add secondary-sub-delayRipose2023-11-261-0/+2
| | | | | | | | | | | | | Add --secondary-sub-delay option and decouple --sub-delay from secondary subtitles. This produces desirable behavior in most cases as secondary and primary subtitles tracks tend to be timed independently of one another. This feature is implemented by turning the sub_delay field in mp_subtitle_opts into an array of 2 floats. From here the track index is either passed around or derived when sub_delay is needed. There are some cases in dec_sub.c where it is possible for dec_sub.order (equivalent to track index) to be -1. In these cases, sub_delay is inferred as 0.
* player: remove shared-script-properties propertyDudemanguy2023-11-221-0/+2
| | | | | | | | | | | | This property was never encouraged. The manual even stated that "You should avoid using it, unless you absolutely have to." Since we now have user-data which is superior in every single way and replaces this, delete this property. The manual also has threatened people for years with the line "It's a makeshift solution which could go away any time (for example, when a better solution becomes available)." We were nice and deprecated it in 1d00aee8e191c9689a20e67e3d6dfd2af6ad2588 for a while to give script authors some time to update. Let's remove it for good now.
* Release 0.37.0v0.37.0release/0.37sfan52023-11-211-4/+2
|
* options: add more properties to default watch-later-optionsKacper Michajłow2023-11-121-0/+1
| | | | | | | | | | | | | | | | | | | Adds: --secondary-sub-visibility --video-aspect-method --video-unscaled --video-pan-x --video-pan-y --video-rotate --video-crop --video-zoom --video-scale-x --video-scale-y --video-align-x --video-align-y Those properties are related to playback state and are likely expected to be restored when resuming playback.
* options: remove not relevant props from default watch-later-optionsKacper Michajłow2023-11-121-0/+2
| | | | | | | | | | | | Removes: --border --fullscreen --ontop --osd-level --pause Those options are not really content related. I don't see much gain to save them per each watch later entry.
* cocoa: remove OpenGL cocoa backendder richter2023-11-101-0/+1
| | | | | | the OpenGL cocoa backend was deprecated in 0.29, it has lot of bugs, is completely unmaintained and can't properly playback anything anymore on the newest macOS. it is time to remove it.
* mac: change display name retrieval to localizedName NSScreen propertyder richter2023-11-101-0/+2
| | | | | | | | | | | | | | | the old displayName property via the IODisplay API is not working anymore on ARM based macs and was broken in at least one other case. instead we use the new localizedName property introduced in 10.15 of the NSScreen. we don't need any backwards compatibility since 10.15 is the oldest version we support now. configs and scripts that use the options and properties fs-screen-name, screen-name or display-names need to be adjusted since the names could differ from the previous implementation via the IODisplay API. Fixes #9697
* vo_gpu_next: add --target-gamut optionNiklas Haas2023-11-081-0/+1
| | | | Fixes: https://github.com/mpv-player/mpv/issues/12777
* player/command: remove hdr-metadata propertyKacper Michajłow2023-11-051-0/+1
| | | | | It is now included in video-out-params and was never released in stable version, so we can safely remove it.
* csputils: add pl_hdr_metadata to mp_colorspace and deprecate sig_peakKacper Michajłow2023-11-051-0/+1
| | | | | Note this commit does not change all uses of sig-peak, this is for future refactoring.
* demux: make hysteresis-secs respect cache-secsNRK2023-10-301-0/+2
| | | | | | | | | | | | currently hysteresis-secs only works when the demuxer-max-bytes fills up. but it's possible for the cache-secs/demuxer-readahead-secs to be reached first. in those cases, hysteresis-secs doesn't work and keeps buffering non-stop. but the goal of this option was to save power by avoiding non-stop buffering so go ahead and make it respect cache-secs as well. additionally remove some redundant repetition from the docs.
* m_option: drop support for -del for list optionsDudemanguy2023-10-301-0/+1
| | | | | | 5f74ed58286a1339412554932f31844ec1b64280 deprecated this many years ago. The utility is questionable at best given that -remove exists and is more natural to use. Free up some code and drop it.
* options: make --screenshot-directory/--watch-later-directory aliasesDudemanguy2023-10-301-2/+2
| | | | By popular demand I guess.
* javascript: use --js-memory-report option instead of MPV_LEAK_REPORTDudemanguy2023-10-261-0/+2
| | | | | | | | 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-251-0/+1
| | | | | | --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-251-0/+1
| | | | Same logic as the previous commit.
* options: rename --screenshot-directory to --screenshot-dirDudemanguy2023-10-251-0/+1
| | | | | 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-251-0/+1
| | | | | | | 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-251-0/+1
| | | | | | 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-251-0/+1
| | | | | | 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-251-0/+1
| | | | | | Peak detection greatly increases HDR experience. Performance hit of non-delayed detection is not that significant and is in line with current default settings.
* stream_cdda: deprecate --cdda-toc-bias and always check for offsetsDudemanguy2023-10-191-0/+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/interface-changes: remove redundant changeGuido Cella2023-10-171-1/+0
| | | | directory-mode's default was changed again to auto afterwards.
* 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.
* command: add playlist-next-playlist and playlist-prev-playlistGuido Cella2023-10-091-0/+1
| | | | | | | | | | | | 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.
* demux: change the default of metadata-codepage to autoDudemanguy2023-10-071-0/