RepoMirrors/mpv
1
0
Fork 0
mirror of https://github.com/mpv-player/mpv synced 2024-12-26 17:12:36 +00:00
Code Issues Releases Wiki Activity
5009e13431
mpv/DOCS/interface-changes.rst

1033 lines
60 KiB
ReStructuredText
Raw Normal View History

DOCS: add a changelog for option/command/property changes All these make up both user interface and API. It's a good idea to actually keep track of changes to it.
2015-05-22 17:00:13 +00:00
Introduction
============
DOCS/interface-changes: fix typo
2016-01-23 10:41:28 +00:00
mpv provides access to its internals via the following means:
DOCS: add a changelog for option/command/property changes All these make up both user interface and API. It's a good idea to actually keep track of changes to it.
2015-05-22 17:00:13 +00:00
- options
- commands
- properties
- events
DOCS/compatibility.rst: add this file Another thing nobody will read. I'm attempting to document the rules by which incompatible changes can be made. These rules have always been present in this project, but I don't think they were written down. Or maybe they were, but I forgot where. I think due to the time of the day it became increasingly incoherent (not necessarily near the end of the text). Hopefully no logical or freudian lapses in there.
2019-10-05 00:11:55 +00:00
- hooks
The sum of these mechanisms is sometimes called command interface.
DOCS: add a changelog for option/command/property changes All these make up both user interface and API. It's a good idea to actually keep track of changes to it.
2015-05-22 17:00:13 +00:00
All of these are important for interfacing both with end users and API users
(which include Lua scripts, libmpv, and the JSON IPC). As such, they constitute
a large part of the user interface and APIs.
DOCS/compatibility.rst: add this file Another thing nobody will read. I'm attempting to document the rules by which incompatible changes can be made. These rules have always been present in this project, but I don't think they were written down. Or maybe they were, but I forgot where. I think due to the time of the day it became increasingly incoherent (not necessarily near the end of the text). Hopefully no logical or freudian lapses in there.
2019-10-05 00:11:55 +00:00
Also see compatibility.rst.
DOCS: document the new way to handle interface changes 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.
2024-02-28 16:24:09 +00:00
This document lists changes to them. New options/commands/etc. are not always
listed.
**Never** write to this file directly except when making releases. New changes
are added in the interface-changes directory instead. See contribute.md for more
details.
DOCS: add a changelog for option/command/property changes All these make up both user interface and API. It's a good idea to actually keep track of changes to it.
2015-05-22 17:00:13 +00:00
Interface changes
=================
::
player: remove shared-script-properties property 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.
2023-09-21 16:35:14 +00:00
--- mpv 0.38.0 ---
Release 0.38.0
2024-04-17 19:18:44 +00:00
- add `term-size` property
- add the `escape-ass` command
- add `>` for fixed precision floating-point property expansion
- add `--input-comands` option
- change `--pulse-latency-hacks` default to `yes`
- add `context-menu` command
- add `menu-data` property
- add `--vo-tct-buffering` option
command: add begin-vo-dragging command 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.
2024-02-26 23:19:16 +00:00
- add `begin-vo-dragging` command
options: add --deinterlace-field-parity option 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
2024-03-05 01:20:01 +00:00
- add `--deinterlace-field-parity` option
DOCS: add documentation for --volume-gain options
2023-12-17 20:16:58 +00:00
- add `--volume-gain`, `--volume-gain-min`, and `--volume-gain-max` options
command: export current-gpu-context property 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.
2023-12-21 04:05:31 +00:00
- add `current-gpu-context` property
DOCS/interface-changes: add --secondary-sub-ass-override Option added in b563b2ae
2023-12-21 22:28:42 +00:00
- add `--secondary-sub-ass-override` option
DOCS: document --input-preprocess-wheel option 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.
2024-02-12 08:45:20 +00:00
- add `--input-preprocess-wheel` option
player: remove shared-script-properties property 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.
2023-09-21 16:35:14 +00:00
- remove shared-script-properties (user-data is a replacement)
options: add secondary-sub-delay 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.
2023-11-23 03:13:57 +00:00
- add `--secondary-sub-delay`, decouple secondary subtitles from
`--sub-delay`
options: add --osd-bar-border-size Closes #1484. The default size is smaller than the previous --osd-border-size default value of 3 with the default --osd-bar-h.
2023-11-24 14:28:02 +00:00
- add the `--osd-bar-border-size` option
image_writer: use common format selection for AVIF screenshots --screenshot-avif-pixfmt no longer defaults to yuv420p.
2023-12-03 17:25:09 +00:00
- `--screenshot-avif-pixfmt` no longer defaults to yuv420p
image_writer: default to lossless AVIF screenshots Also change the example to crf=23. crf=32 is pretty bad quality, don't give users bad usage ideas.
2023-12-03 17:51:36 +00:00
- `--screenshot-avif-opts` defaults to lossless screenshot
DOCS/interface-changes: document renaming of MP_KEY_BACK The navigation key is renamed to avoid conflict with MP_KEY_FORWARD.
2023-12-05 04:55:21 +00:00
- rename key `MP_KEY_BACK` to `MP_KEY_GO_BACK`
filter_sdh: add --sub-filter-sdh-enclosures option 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.
2023-11-05 18:51:43 +00:00
- add `--sub-filter-sdh-enclosures` option
scripting: add mp.input This lets scripts get textual input from the user using console.lua.
2024-01-02 17:58:32 +00:00
- added the `mp.input` scripting API to query the user for textual input
player: add forced choice to subs-with-matching-audio 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.
2023-12-28 16:16:42 +00:00
- add `forced` choice to `subs-with-matching-audio`
player: remove --term-remaining-playtime option This wasn't useful and didn't even really do what it said anyway. Closes #12167.
2024-01-20 22:17:08 +00:00
- remove `--term-remaining-playtime` option
f_auto_filters: change fallback deinterlace to bwdif 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.
2024-01-21 02:45:00 +00:00
- change fallback deinterlace to bwdif
command: add load-config-file 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.
2024-01-10 23:43:12 +00:00
- add the command `load-config-file`
command: add load-input-conf 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.
2024-01-14 20:36:32 +00:00
- add the command `load-input-conf`
player: remove all rpi-specific code 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.
2024-02-03 20:27:46 +00:00
- remove `--vo=rpi`, `--gpu-context=rpi`, and `--hwdec=mmal`
player: add an auto option to deinterlace 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.
2024-01-22 02:37:47 +00:00
- add `auto` choice to `--deinterlace`
sub: allow setting lavc txt_page special values via teletext_page * 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>
2024-01-14 18:20:08 +00:00
- change `--teletext-page` default from 100 to 0 ("subtitle" in lavc)
player: set hidpi-window-scale to no by default 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.
2024-02-13 23:35:23 +00:00
- change `--hidpi-window-scale` default to `no`
DOCS: add `insert` commands and args to interface-changes
2024-02-25 03:43:59 +00:00
- add `insert-next`, `insert-next-play`, `insert-at`, and `insert-at-play`
actions to `loadfile` and `loadlist` commands
- add `index` argument to `loadfile` and `loadlist` commands
- move the `options` argument of the `loadfile` command from the third
parameter to the fourth (after `index`)
- add `--drag-and-drop=insert-next` option
player: rename --background to --background-color This better represents what it actually does. --background will be used for another, related option in the next commit.
2024-02-21 15:48:51 +00:00
- rename `--background` to `--background-color`
vo_gpu/vo_gpu_next: rework --alpha into --background option 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.
2024-02-16 16:40:52 +00:00
- remove `--alpha` and reintroduce `--background` option for better control
over blending alpha components into specific background types
vo_gpu_next: add --border-background option Allow for setting the border background independently from the background option.
2024-02-21 16:38:52 +00:00
- add `--border-background` option
vo: add video-target-params property
2023-08-31 14:59:14 +00:00
- add `video-target-params` property
vf_format: add hdr10plus sub-parameter to format video filter
2024-02-10 23:50:02 +00:00
- add `hdr10plus` sub-parameter to `format` video filter
options: remove --focus-on-open and add --focus-on 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
2024-03-10 12:44:40 +00:00
- remove `--focus-on-open` and add replacement `--focus-on`
builtin.conf: remove debanding from the high-quality profile 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.
2023-12-27 15:39:29 +00:00
- remove debanding from the high-quality profile
path-win: move state directory to %LOCALAPPDATA% %LOCALAPPDATA% is where the local application state belongs.
2023-07-26 19:25:52 +00:00
--- mpv 0.37.0 ---
- `--save-position-on-quit` and its associated commands now store state files
in %LOCALAPPDATA% instead of %APPDATA% directory by default on Windows.
options: restore old default sub selection behavior 1669c4698d237eb885aa3f9c5b81983de6009418 notably flipped the default of --subs-with-matching-audio from yes to no as part of a series of changes that gave more control over sub selection behavior. While the increased amount of options is definitely nice, changing the default to no results in very unintuitive behavior. For example, setting alang=en and slang=en in your config will not show any subtitles since the audio stream is English as well so --subs-with-matching-audio being no causes the subs to not be be selected. This is very weird for users who reasonably expect slang being set to actually result in showing subs and this is what mpv did for the past decade. The other case is when a subtitle does not have a language tag but is flagged as default. Because --subs-fallback (a new option), defaults to no, these subtitles also will not be loaded. This is also strange for users since mpv previously loaded these and they would need to change the value of this option. It's also inconsistent because audio tracks that are tagged as default are also loaded by default. The new behavior seems to have mostly just confused users, and it also regresses their configs for unclear reasons. Let's just set the options to be back in line with the old behavior with is what most users expect. --subs-with-matching-audio goes back to being yes and the new option --subs-fallback should be default. Fixes #11854.
2023-07-24 17:16:12 +00:00
- change `--subs-with-matching-audio` default from `no` to `yes`
- change `--subs-fallback` default from `no` to `default`
vo_gpu_next: add --hdr-peak-percentile
2023-08-04 14:18:16 +00:00
- add the `--hdr-peak-percentile` option
builtin.conf: add --hdr-peak-percentile=99.995 to gpu-hq This is higher quality but comes with a slight performance hit, especially for weaker iGPUs, so I don't want to enable it out of the box even when --hdr-compute-peak=auto.
2023-08-04 14:24:57 +00:00
- include `--hdr-peak-percentile` in the `gpu-hq` profile
ao_audiotrack: enable pcm-float by default Since recent commits this should work 100% as well as s16.
2023-08-06 16:47:12 +00:00
- change `--audiotrack-pcm-float` default from `no` to `yes`
player/command: add video-params/aspect-name With pretty printed aspect ratio and related format.
2023-08-11 15:14:27 +00:00
- add video-params/aspect-name
player: make sub-pos a float value mpv makes this option an integer, but the underlying ass API actually accepts doubles. From some testing, there is no meaningful precision difference between float or double (it seems to go in roughly 0.05 steps), so just make it a float. sd_lavc also can handle non-integer values here. Closes #11583.
2023-08-10 20:51:44 +00:00
- change type of `--sub-pos` to float
player: add --term-remaining-playtime option The OSC reports the speed-adjusted remaining time, but the terminal does not. This is a weird mismatch and the OSC's default behavior makes sense, so let's just do some division and add an option to disable it. Also named "remaining-playtime" after the OSC option. Fixes #10445.
2023-08-10 23:53:45 +00:00
- The remaining time printed in the terminal is now adjusted for speed by default.
You can disable this with `--no-term-remaining-playtime`.
player: add playlist-path properties A bit of a long standing pain with scripting is that when opening a file that gets interpreted as a playlist (like an m3u), the original path of the file gets thrown away later. Workarounds basically consist of getting the filename before mpv expands the path, but that's not really reliable. Instead of throwing it away, save the original playlist path by copying to the playlist entries when applicable (demuxer playlist and the playlist option). Then expose these as properties: playlist-path for the currently playing entry and playlist/N/playlist-path for each specific entry. Closes #8508, #7605.
2023-08-11 04:27:28 +00:00
- add `playlist-path` and `playlist/N/playlist-path` properties
x11: add --x11-wid-title option This deliberately wasn't being done when mpv was embedded (fbccddb48b4c71c18300b092ef7a3860be2a659a). There are some applications that would benefit from mpv setting a title since they don't do so themselves (such as tabbed), but at the same time some others would probably rather not have this behavior (like smplayer). Add an option that allows an embedded mpv to set the title if the user wishes. Fixes #11528.
2023-08-10 02:11:53 +00:00
- add `--x11-wid-title` option
vo_gpu_next: add --libplacebo-opts To help test not-yet-exposed options, and for debugging purposes.
2023-08-18 15:25:52 +00:00
- add `--libplacebo-opts` option
player: make all autoload extensions configurable --audio-file-auto, --cover-art-auto, and --sub-auto all work by using an internally hardcoded list that determine what file extensions get recognized. This is fine and people periodically update it, but we can actually expose this as a stringlist option instead. This way users can add or remove any file extension for any type. For the most part, this is pretty pretty easy and involves making sub_exts, etc. the defaults for the new options (--audio-file-auto-exts, --cover-art-auto-exts, and --sub-auto-exts). There's actually one slight complication however. The input code uses mp_might_be_subtitle_file which guesses if the file drag and dropped file is a subtitle. The input ctx has no access to mpctx so we have to be clever here. For this, the trick is to recognize that we can leverage the m_option_change_callback. We add a new flag, UPDATE_SUB_EXTS, which fires when the player starts up. Then in the callback, we can set the value of sub_exts in external_files to opts->sub_auto_exts. Whenever the option updates, the callback is fired again and sub_exts updates. That way mp_might_be_subtitle_file can just operate off of this global variable instead of trying to mess with the core mpv state directly. Fixes #12000.
2023-08-10 22:36:22 +00:00
- add `--audio-file-exts`, `--cover-art-auto-exts`, and `--sub-auto-exts`
player: remove special auto option from alang/slang/vlang This proved to be too problematic. Depending on the value of --subs-with-matching-audio, you could either end up with cases where --slang wasn't respected and users didn't get subtitles or alternatively cases where subtitles were given and the user didn't ask for them. Fundamentally, the OS language functionality doesn't really map well to slang (and for alang/vlang it makes zero sense; not that anyone actually used it). Instead of trying to shove it in an option where it doesn't belong, we should split this off into something else. So for now, just remove the special handling of "auto" and flip slang back to NULL.
2023-08-07 02:39:17 +00:00
- change `slang` default back to NULL
- remove special handling of the `auto` value from `--alang/slang/vlang` options
player: add --subs-match-os-language option This is the replacement for the previous auto option for slang. It behaves similar however it never overrides slang if that is set and will instead try to pick the subtitle that matches the user's language if appropriately flagged by the file.
2023-08-07 04:49:37 +00:00
- add `--subs-match-os-language` as a replacement for `--slang=auto`
player: add always to --subs-fallback-forced In general, forced tracks should only be shown if they match the language of the audio. However some people do want them no matter what, so add an always option to this so such tracks are always selected.
2023-08-26 04:38:57 +00:00
- add `always` option to `--subs-fallback-forced`
player: remove auto choice from sub-forced-only First of all, this never worked. Or if it ever did, it was in some select few scenarios. c9474dc9ed6172a5f17f66f4b7d367da6b077909 is what originally added support for the auto choice. However, that commit worked by propagating a value to a fake option used internally. This shouldn't have ever worked because the underlying m_config_cache was never updated so the value shouldn't have been preserved when accessed in sd_lavc. And indeed with some testing, the value there is always 0 unsurprisingly. This was later rewritten in ba7cc071068f4f57ae354e77f64552712fda6855 along with a lot of other sub changes, but with that, it was still mostly broken. The reason is because one of the key parts of having to hit this logic (prefer_forced) required `--no-subs-with-matching-audio` to be set. If the audio language matches the subtitle language (the requirement also excludes forced subs), the option makes no subtitle selection in the first place so pick->forced_only_def is not set to true and nothing even happens. Another way around this would be to attempt to change your OS language (like with the LANG environment variable) so that the subtitle track gets selected but then audio_matches mistakenly becomes false because it compares the OS language to the audio language which then make preferred_forced 0, so nothing happens. I don't think there's a scenario where pick->forced_only_def is actually set to true (thus meaning `auto` is useless), but maybe someone could contrive something very strange. Regardless, it's definitely not something even remotely common. fbe8f9919428a7ed24a61899bfd85bbb7680e389 changed track selection again but didn't consider this particular case. The net result is that DVD/PGS subs become equivalent to --sub-forced-only being yes, so this a change in behavior and probably not a good one. Note that I wasn't able to actually observe any difference in a PGS sample. It still displayed subtitles fine but that sample probably didn't have the right flags to hit the sub-forced-only logic. Anyways, the auto feature is extremely questionable at best and in my view, not actually worth it. It is meant to be used with `--no-subs-with-matching-audio` to display forced pictures in subtitle tracks that are not marked as forced, but that contradicts that particular option's purpose and description in the manual (secretly selecting a track under certain conditions even though it says not to). Instead of trying to shove all this logic into select_default_track which is already insanely complicated as it is, recognize that this is a trivial lua script. If you absolutely want to turn --sub-forced-only on under these certain conditions (DVD/PGS subtitles, matching audio and subtitle languages, etc.), just look at the current-tracks property and do your thing. The very, very niche behavior that this option tried to accomplish basically never worked, no user even knows what this option does, and well it's just not worth supporting in core mpv code. Drop all this code for sanity's sake and change --sub-forced-only back to a bool.
2023-08-28 22:24:24 +00:00
- remove `auto` choice from `--sub-forced-only`
- remove `auto-forced-only` property
player: rename --sub-forced-only to --sub-forced-events-only The old name is pretty bad and users mistakenly think it has something to do with selecting forced subtitles (that would be --subs-fallback-forced). Instead of giving it such a generic name, make it clearer that this has to do specifically with forced sub events which is only relevant for a small minority of subtitles.
2023-08-29 01:15:49 +00:00
- rename `--sub-forced-only` to `--sub-forced-events-only`
command: remove sub-forced-only-cur property Since we no longer have the auto choice, this is always exactly equal to the value of the option (sub-forced-events-only). Remove the property and alias it.
2023-08-29 01:45:38 +00:00
- remove `sub-forced-only-cur` property (`--sub-forced-events-only` is a replacement)
player/command: remove video-aspect property 4 years is enough of deprecation period.
2023-08-25 13:22:15 +00:00
- remove deprecated `video-aspect` property
vo: add --video-crop Just cropping by VO that works with hwdec. Fixes: #12222
2023-08-25 17:21:21 +00:00
- add `--video-crop`
player/command: add video-params/crop-[w,h,x,y]
2023-08-25 17:29:33 +00:00
- add `video-params/crop-[w,h,x,y]`
vo_gpu: remove --tone-mapping-mode `--vo=gpu-next` no longer uses this option, being replaced entirely by a luminance-based approach internally. And even for `--vo=gpu`, the values other than 'hybrid' are universally inferior in quality. In the interest of gradually reducing the amount of option bloat here, remove this mostly-pointless option.
2023-07-18 13:35:13 +00:00
- remove `--tone-mapping-mode`
player: redo --subs-fallback-forced In the never ending quest of trying to satisfy every possible user request for subtitle autoselection, I ended up redoing how --subs-fallback-forced works. The old behavior had it as strictly a fallback-type option when there were no lang matches, but now we can make it an active part of compare_track and it works along with slang to select the desired track. Since it's a three state option, the no option still works to avoid selecting any forced subtitle tracks. The meaning of always slightly changes to mean "only select forced subtitle tracks" and yes remains essentially the same (no special priority given besides the audio matching subtitle language case).
2023-09-02 02:54:41 +00:00
- change `--subs-fallback-forced` so that it works alongside `--slang`
vo_gpu: vo_gpu_next: support --icc-3dlut-size=auto And make it the default. In libplacebo, this uses internal heuristics to pick a good size based on the actual ICC characteristics. This is significantly less wasteful than always generating a 64x64x64 3DLUT (the old status quo). In vo_gpu, for simplicity, just default to 65x65x65. Note that this provides slightly better accuracy than the old default of 64x64x64 for technical reasons, and matches what libplacebo defaults to for typical display profiles.
2023-09-14 18:31:57 +00:00
- add `--icc-3dlut-size=auto` and make it the default
filter_kernels: add ewa_lanczos4sharpest Mainly for vo_gpu_next.
2023-09-15 10:27:48 +00:00
- add `--scale=ewa_lanczos4sharpest`
vo_gpu: remove --scale-wblur etc No need for this since it's entirely redundant with just changing the filter radius directly. In fact, that's the whole *point* of the filter radius - it does not modify the filter, it modifies the scaling of the window. Of course, this does not work for non-resizable kernels. But, really, who cares?
2023-09-16 11:41:18 +00:00
- remove `--scale-wblur`, `--cscale-wblur`, `--dscale-wblur`, `--tscale-wblur`
filter_kernels: remove bcspline filter After fixing the B and C params for bcspline, it ended up being the same thing as bicubic. There's no reason to have two names for the same filter, so remove bcspline and keep bicubic to match libplacebo.
2023-09-17 00:00:16 +00:00
- remove `bcspline` filter (`bicubic` is now the same as `bcspline`)
demux: prepend some cache options with demuxer --cache-dir is an awful name that leads to confusion (see #12418). Change the name to --demuxer-cache-dir and --demuxer-cache-unlink-files instead.
2023-09-18 16:43:25 +00:00
- rename `--cache-dir` and `--cache-unlink-files` to `--demuxer-cache-dir` and
`--demuxer-cache-unlink-files`
vo: enable correct-downscaling, linear-downscaling, sigmoid-upscaling
2023-09-16 19:42:03 +00:00
- enable `--correct-downscaling`, `--linear-downscaling`, `--sigmoid-upscaling`
vo: make cscale follow scale by default
2023-09-16 23:47:43 +00:00
- `--cscale` defaults to `--scale` if not defined
vo: change tscale to oversample by default Keep it sharp, let users opt-in more blurry result.
2023-09-17 16:51:58 +00:00
- change `--tscale` default to `oversample`
builtin.conf: modernize internal profiles The goal is to provide simple to understand quality/performance level profiles for the users. Instead of default and gpu-hq profile. There main profiles were added: - fast: can run on any hardware - default: balanced profile between quality and performance - high-quality: out of the box high quality experience. Intended mostly for dGPU. Summary of three profiles, including default one: [fast] scale=bilinear cscale=bilinear (implicit) dscale=bilinear dither=no correct-downscaling=no linear-downscaling=no sigmoid-upscaling=no hdr-compute-peak=no [default] (implicit mpv defaults) scale=lanczos cscale=lanczos dscale=mitchell dither-depth=auto correct-downscaling=yes linear-downscaling=yes sigmoid-upscaling=yes hdr-compute-peak=yes [high-quality] (inherits default options) scale=ewa_lanczossharp cscale=ewa_lanczossharp (implicit) hdr-peak-percentile=99.995 hdr-contrast-recovery=0.30 allow-delayed-peak-detect=no deband=yes scaler-lut-size=8
2023-09-12 21:25:20 +00:00
- change `--dither-depth` to `auto`
- deprecate `--profile=gpu-hq`, add `--profile=<fast|high-quality>`
vo_gpu: default to dscale=hermite This new filter is slightly sharper, and significantly faster, than mitchell. It also tends to preserve detail better. All in all, there is no reason not to use it by default, especially from a performance PoV. (In vo_gpu_next, hermite is implemented efficiently using hardware accelerated bilinear interpolation) See-Also: https://code.videolan.org/videolan/libplacebo/-/commit/75b3947b2c07803456483ec6976c037bad91b5dd
2023-09-20 00:09:05 +00:00
- change `--dscale` default to `hermite`
vo_gpu: match libplacebo peak detection defaults This probably makes `vo_gpu` tone mapping worse, or something, but who cares. The status quo for a while now has been to use `vo_gpu_next` if you care about HDR rendering at all. See-Also: haasn/libplacebo@ec60dd156b82753a2e2d8a399899244605f4d1bf See-Also: haasn/libplacebo@0903cbd05d7fc0391cbd99954924a39b855c8a1b
2023-09-20 16:27:23 +00:00
- update defaults to `--hdr-peak-decay-rate=20`, `--hdr-scene-threshold-low=1.0`,
`--hdr-scene-threshold-high=3.0`
vo_gpu: match libplacebo debanding defaults The defaults were awful and horribly regressed many files while also not fixing banding on files that actually needed it, sometimes even *increasing* banding due to the low threshold. Fixes: 12ffce0f224056f91a20c9f0b197f4973931efbe See-Also: haasn/libplacebo@e1e43376d16d5112ee1254534664b0b85110139b
2023-09-20 16:30:23 +00:00
- update defaults to `--deband-threshold=48`, `--deband-grain=32`
demux_playlist: add --directory-mode=auto This is a more useful default with --shuffle.
2023-09-19 19:16:23 +00:00
- add `--directory-mode=auto` and make it the default
builtin.conf: remove deprecated opengl-hq profile Deprecated in 65979986a923a8f08019b257c3fe72cd5e8ecf68. 6 years is more than enough time.
2023-09-20 00:14:02 +00:00
- remove deprecated `--profile=opengl-hq`
options: remove ancient option fallbacks/deprecation 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.
2023-09-20 00:56:00 +00:00
- remove several legacy fallbacks for old deprecated options (now they will just
error out like normal)
command: remove some old deprecated properities 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.
2023-09-20 01:10:10 +00:00
- remove deprecated `drop-frame-count` and `vo-drop-frame-count` property aliases
- remove the ability to write to the `display-fps` property (use `override-display-fps`
instead)
command: stop restarting playback when writing to playlist-pos 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.
2023-09-20 01:54:40 +00:00
- writing the current value to playlist-pos will no longer restart playback (use
`playlist-play-index` instead)
options: remove a few options marked with .deprecation_message 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.
2023-09-20 04:37:51 +00:00
- remove deprecated `--oaoffset`, `--oafirst`, `--ovoffset`, `--ovfirst`,
`--demuxer-force-retry-on-eof`, `--fit-border` options
options: remove deprecated --record-file option 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.
2023-09-20 03:56:17 +00:00
- remove deprecated `--record-file` option
options: remove --vf-defaults and --af-defaults 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.
2023-09-20 04:51:51 +00:00
- remove deprecated `--vf-defaults` and `--af-defaults` options
drm: remove selecting the card number with --drm-connector f56043759494dd584c8d82e7890f92fada18e34b deprecated this since the --drm-device path option was added as a replacement. Drop the card number selection logic.
2023-09-20 05:26:25 +00:00
- `--drm-connector` no longer allows selecting the card number (use `--drm-device`
instead)
win32: add an option to control window title bar state Fixes: #11432
2023-03-19 05:38:32 +00:00
- add `--title-bar` option
win32: add --window-corners Allows to set preference for window corners rounding for DWM.
2023-08-21 22:12:33 +00:00
- add `--window-corners` option
stream_cdda: move cdrom-device to cdda_params 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.
2023-09-19 21:14:24 +00:00
- rename `--cdrom-device` to `--cdda-device`
vo_gpu: remove --scale-cutoff etc 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
2023-09-20 16:12:15 +00:00
- remove `--scale-cutoff`, `--cscale-cutoff`, `--dscale-cutoff`, `--tscale-cutoff`
vo_gpu: remove --scaler-lut-size 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
2023-09-20 16:18:59 +00:00
- remove `--scaler-lut-size`
command: deprecate shared-script-properties user-data is simply better.
2023-09-26 21:41:41 +00:00
- deprecate shared-script-properties (user-data is a replacement)
DOCS/interface-changes: mention --backdrop-type Added in f19ada7b583e9bf78de38d228a956c365b5c417b
2023-10-01 16:23:54 +00:00
- add `--backdrop-type` option
DOCS/interface-changes: also mention --window-affinity Added in 2c738ca54b16cdd1982473672bd39068fcf8d948. I guess we seem to always mention any added option these days so might as well.
2023-10-01 17:47:55 +00:00
- add `--window-affinity` option
path: don't override "cache" and "state" paths with configdir 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.
2023-10-02 11:14:52 +00:00
- `--config-dir` no longer forces cache and state files to also reside in there
demux_cue: deprecate --demuxer-cue-codepage for --metadata-codepage 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.
2023-10-01 17:31:06 +00:00
- deprecate `--demuxer-cue-codepage` in favor of `--metadata-codepage`
demux: change the default of metadata-codepage to auto 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).
2023-10-01 18:21:56 +00:00
- change the default of `metadata-codepage` to `auto`
command: add playlist-next-playlist and playlist-prev-playlist 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.
2023-10-07 14:53:52 +00:00
- add `playlist-next-playlist` and `playlist-prev-playlist` commands
f_decoder_wrapper: change video-codec to show description or name 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.
2023-09-01 01:15:10 +00:00
- change `video-codec` to show description or name, not both
stream_cdda: deprecate --cdda-toc-bias and always check for offsets 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.
2023-10-18 19:19:17 +00:00
- deprecate `--cdda-toc-bias` option, offsets are always checked now
options: disable --allow-delayed-peak-detect by default Peak detection greatly increases HDR experience. Performance hit of non-delayed detection is not that significant and is in line with current default settings.
2023-10-06 21:54:37 +00:00
- disable `--allow-delayed-peak-detect` by default
options: rename --fps to --container-fps-override 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.
2023-10-15 14:36:56 +00:00
- rename `--fps` to `--container-fps-override`
options: rename --override-display-fps to --display-fps-override 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.
2023-10-15 15:18:49 +00:00
- rename `--override-display-fps` to `--display-fps-override`
options: rename --sub-ass-force-style to --sub-ass-style-overrides 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.
2023-10-15 15:28:40 +00:00
- rename `--sub-ass-force-style` to `--sub-ass-style-overrides`
options: make --screenshot-directory/--watch-later-directory aliases By popular demand I guess.
2023-10-29 20:47:06 +00:00
- alias `--screenshot-directory` to `--screenshot-dir`
- alias `--watch-later-directory` to `--watch-later-dir`
options: rename --play-dir to --play-direction --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.
2023-10-15 16:04:05 +00:00
- rename `--play-dir` to `--play-direction`
javascript: use --js-memory-report option instead of MPV_LEAK_REPORT 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.
2023-10-25 23:17:25 +00:00
- `--js-memory-report` is now used for enabling memory reporting for javascript
scripts
m_option: drop support for -del for list options 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.
2023-10-25 19:10:37 +00:00
- drop support for `-del` syntax for list options
demux: make hysteresis-secs respect cache-secs 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.
2023-10-21 11:26:46 +00:00
- `--demuxer-hysteresis-secs` now respects `--cache-secs` and/or
`--demuxer-readahead-secs` as well
csputils: add pl_hdr_metadata to mp_colorspace and deprecate sig_peak Note this commit does not change all uses of sig-peak, this is for future refactoring.
2023-08-31 14:28:04 +00:00
- add hdr metadata to `video-params` property
vo_gpu_next: add --target-gamut option Fixes: https://github.com/mpv-player/mpv/issues/12777
2023-10-31 19:41:19 +00:00
- add `--target-gamut`
mac: change display name retrieval to localizedName NSScreen property 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
2023-11-08 00:26:29 +00:00
- change the way display names are retrieved on macOS, usage of options and properties
`--fs-screen-name`, `--screen-name` and `display-names` needs to be adjusted
cocoa: remove OpenGL cocoa backend 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.
2023-11-10 13:34:29 +00:00
- remove OpenGL cocoa backend that was deprecated in 0.29
Release 0.37.0
2023-11-21 18:47:46 +00:00
- remove `border`, `fullscreen`, `ontop`, `osd-level` and `pause`
options: remove not relevant props from default watch-later-options 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.
2023-10-01 16:15:21 +00:00
from default `--watch-later-options`
Release 0.37.0
2023-11-21 18:47:46 +00:00
- add `video-*` and `secondary-sub-visibility` to default `--watch-later-options`
player: add --force-render option mpv has an internal optimization on a couple of platforms where it will not render any frames if the window is minimized or hidden. There's at least once possible use case for wanting to force a render anyway (screensharing with pipeware) so let's just add a simple switch for this that always forces mpv to render. Closes #10846.
2022-11-11 19:57:53 +00:00
--- mpv 0.36.0 ---
vo_gpu_next: add --target-contrast option For better control over target display levels.
2023-06-30 03:46:51 +00:00
- add `--target-contrast`
vo_gpu_next: allow to use ICC profile luminance value Also while at it respect target-peak option when ICC profile is used. Fixes #11449
2023-04-23 20:49:33 +00:00
- Target luminance value is now also applied when ICC profile is used.
`--icc-use-luma` has been added to use ICC profile luminance value.
If target luminance and ICC luminance is not used, old behavior apply,
defaulting to 203 nits. (Only applies for `--vo=gpu-next`)
player: set playlist title to media title if not set already The playlist title only got set when it was specified in the playlist file. If there is a title after opening a file, that should also be reflected in the playlist.
2023-03-06 19:22:03 +00:00
- `playlist/N/title` gets set upon opening the file if it wasn't already set
and a title is available.
vo_kitty: Introduce modern sixel alternative See https://sw.kovidgoyal.net/kitty/graphics-protocol/ This makes no attempt at querying terminal features or handling terminal errors, as it would require mpv to pass the response codes from the terminal to the vo instead of interpreting them as keystrokes made by the user and acting very unpredictably. Tested with kitty and konsole. Fixes #9605
2022-12-13 14:58:13 +00:00
- add the `--vo=kitty` video output driver, as well as the options
`--vo-kitty-cols`, `--vo-kitty-rows`, `--vo-kitty-width`,
`--vo-kitty-height`, `--vo-kitty-left`, `--vo-kitty-top`,
`--vo-kitty-config-clear`, `--vo-kitty-alt-screen` and
`--vo-kitty-use-shm`
player: add --force-render option mpv has an internal optimization on a couple of platforms where it will not render any frames if the window is minimized or hidden. There's at least once possible use case for wanting to force a render anyway (screensharing with pipeware) so let's just add a simple switch for this that always forces mpv to render. Closes #10846.
2022-11-11 19:57:53 +00:00
- add `--force-render`
vo_sixel: Rename draw-clear -> config-clear
2022-12-20 09:29:49 +00:00
- add `--vo-sixel-config-clear`, `--vo-sixel-alt-screen` and
vo_sixel: Alias/deprecate exit-clear -> alt-screen Also update documentation to reflect actual behavior.
2022-12-20 09:22:51 +00:00
`--vo-sixel-buffered`
wayland: add support for content-type protocol The content-type protocol allows mpv to send compositor a hint about the type of content being displayed on its surface so it could potentially make some sort of optimization. Fundamentally, this is pretty simple but since this requires a very new wayland-protocols version (1.27), we have to mess with the build to add a new define and add a bunch of if's in here. The protocol itself exposes 4 different types of content: none, photo, video, and game. To do that, let's add a new option (wayland-content-type) that lets users control what hint to send to the compossitor. Since the previous commit adds a VOCTRL that notifies us about the content being displayed, we can also add an auto value to this option. As you'd expect, the compositor hint would be set to photo if mpv's core detects an image, video for other things, and it is set to none for the special case of forcing a window when there is not a video track. For completion's sake, game is also allowed as a value for this option, but in practice there shouldn't be a reason to use that.
2022-11-15 21:51:45 +00:00
- add `--wayland-content-type`
vo_sixel: Alias/deprecate exit-clear -> alt-screen Also update documentation to reflect actual behavior.
2022-12-20 09:22:51 +00:00
- deprecate `--vo-sixel-exit-clear` and alias it to
`--vo-sixel-alt-screen`
drm: remove legacy API The legacy DRM API adds some complexity to the DRM code. There are only 4 drivers that do not support the DRM Atomic API: 1. radeon (early GCN amd cards) 2. gma500 (ancient intel GPUs) 3. ast (ASPEED SoCs) 4. nouveau Going forward, new DRM drivers will be guaranteed to support the atomic API so this is a safe removal.
2022-11-12 15:40:20 +00:00
- deprecate `--drm-atomic`
demux: add --demuxer-hysteresis-secs option to save power with caching Buffering ahead nonstop into the cache results in nonstop disk or network activity to read stream data from wherever it may originate. Currently, there's no way to configure the demuxer to back off once it's buffered ahead enough data, since the cache limit will be perpetually not-reached as a stream continues to play, until the entire stream is eventually buffered. On a laptop with an i9-12900H with decoding performed by the iGPU, watching a locally-saved 1080p video which hasn't been buffered into the page cache consumes approximately 15 W even with caching enabled. When configuring a hysteresis to make the demuxer back off, power consumption drops to 9 W when watching the same video, resulting in a whopping 6 W of power savings. To make it possible to attain significant power savings via caching, add a --demuxer-hysteresis-secs option to configure a hysteresis to make the demuxer back off until there's only the configured number of seconds remaining in the cache from the current playback position. This feature is disabled by default.
2022-12-29 06:01:07 +00:00
- add `--demuxer-hysteresis-secs`
player: add video-sync=display-tempo So far there was no way to sync video to display and have audio sync to video without changes in pitch. With this option the audio does not get resampled (pitch change) and instead the corrected audio speed is applied to audio filters.
2022-08-03 21:47:07 +00:00
- add `--video-sync=display-tempo`
player: don't force saving start in watch-later-options The watch-later mechanism has always unconditionally wrote start to files to save the playback position. When this was later expanded to watch-later-options, this logic was kept in place. But we don't actually have to unconditionally write this and can allow users to remove the option from the list if they want to. The start value still requires some special handling; it should always be written if possible regardless of the value changing. However, we can just place it within the default set of options for watch-later-options so it can be removed like any other.
2023-01-08 06:16:15 +00:00
- the `start` option is no longer unconditionally written by
watch-later. It is still written by default but you may
various: fix typos Found by codespell
2023-03-27 20:42:17 +00:00
need to explicitly add `start` depending on how you have
player: don't force saving start in watch-later-options The watch-later mechanism has always unconditionally wrote start to files to save the playback position. When this was later expanded to watch-later-options, this logic was kept in place. But we don't actually have to unconditionally write this and can allow users to remove the option from the list if they want to. The start value still requires some special handling; it should always be written if possible regardless of the value changing. However, we can just place it within the default set of options for watch-later-options so it can be removed like any other.
2023-01-08 06:16:15 +00:00
`--watch-later-options` configured.
vd_lavc: add "auto" choice for vd-lavc-dr --vd-lavc-dr defaulted to "yes", which caused issues on certain hardware. Instead of disabling it, add a new "auto" value and make it the default. The "auto" choice will enable DR only when we can request host-cached buffers (as signalled by the new VO_DR_FLAG_HOST_CACHED). Co-authored-by: Nicolas F. <ovdev@fratti.ch> Co-authored-by: Niklas Haas <git@haasn.dev>
2023-01-21 14:45:11 +00:00
- add `--vd-lavc-dr=auto` and make it the default
wayland: add wp-fractional-scale-v1 support This protocol is pretty important since it finally lets us solve the longstanding issue of fractional scaling in wayland (no more mpv doing rendering over the target resolution and then being scaled down). This protocol also can completely replace the buffer_scale usage that we are currently using for integer scaling so hopefully this can be removed sometime in the future. Note that vo_dmabuf_wayland is omitted from the fractional scale handling because we want the compositor to handle all the scaling for that VO. Fixes #9443.
2023-01-23 20:16:43 +00:00
- add support for the fractional scale protocol in wayland
- in wayland, hidpi window scaling now scales the window by the compositor's
dpi scale factor by default (can be disabled with --no-hidpi-window-scale
if fractional scaling support exists).
video/image_writer: change screenshot-tag-colorspace default to yes With significant improvements to the color tagging support in various screenshot formats, e.g. cICP in FFmpeg, and JPEG XL's generally robust color support, it's safe to default this to yes.
2023-02-08 14:13:00 +00:00
- change --screenshot-tag-colorspace default value from `no` to `yes`
vf_sub: undeprecate 3a9e661e929c34d25810fa903abbd9961f73ecef officially made this video filter deprecated roughly 6 years ago. Every other video filter in that commit has actually been removed since then except for vf_sub. ffmpeg does have its own subtitles filter, but it doesn't have the same control over scale like vf_sub does. That's probably why wm4 never actually removed it. Let's stop scaring users with a warning since this filter probably won't ever get removed. Closes #9254.
2023-02-05 16:27:10 +00:00
- undeprecate vf_sub
vo_gpu_next: expose --tone-mapping=st2094-40 and st2094-10
2023-02-11 17:20:14 +00:00
- add `--tone-mapping=st2094-40` and `--tone-mapping=st2094-10`
DOCS: document JPEG XL default effort change Document the change in 7607432127d5aa4e2a6e8cc05ea112c19aa9ff7f.
2023-02-18 11:16:21 +00:00
- change `--screenshot-jxl-effort` default from `3` to `4`.
vo_gpu_next: add --tone-mapping-visualize
2023-02-19 20:01:40 +00:00
- add `--tone-mapping-visualize`
video: make csp equalizer params float This allows more precise adjustments. Fixes #11316
2023-02-15 21:01:50 +00:00
- change type of `--brightness`, `--saturation`, `--contrast`, `--hue` and
`--gamma` to float.
command: add platform property This returns the value of the target OS that mpv was built on as reported by the build system. It is quite conceivable that script writers and API users would need to make OS-dependent choices in some cases. Such people end up writing boilerplate/hacks to guess what OS they are on. Assuming you trust the build system (if you don't, we're in really deep trouble), then mpv actually knows exactly what OS it was built on. Simply take this information at configuration time, make it a define, and let mp_property_platform return the value. Note that mpv has two build systems (waf and meson), so the names of the detected OSes may not be exactly the same. Since meson is the newer build system, the value of this property follows meson's naming conventions*. In the waf build, there is a small function to map known naming deviations to match meson (i.e. changing "win32" to "windows"). waf's documentation is a nightmare to follow, but it seems to simply take the output of sys.platform in python and strip away any trailing numbers if they exist (exception being win32 and os2)*. *: https://mesonbuild.com/Reference-tables.html#operating-system-names *: https://waf.io/apidocs/Utils.html#waflib.Utils.unversioned_sys_platform
2022-01-23 05:06:26 +00:00
- add `platform` property
player: add --auto-window-resize option mpv's window resizing logic always automatically resized the window whenever the video resolution changed (i.e. advancing forward in a playlist). This simply introduces the option to make this behavior configurable. Every windowing backend would need to implement this behavior in their code since a reconfigure event must always be a resize. The params of the frame changed so you either have to resize the window to the new size of the params or make the params the same size as the window. This commit implements it for wayland, win32, and x11.
2021-10-20 02:47:23 +00:00
- add `--auto-window-resize`
player: use XDG_STATE_HOME for watch_later A pain point for some users is the fact that watch_later is stored in the ~/.config directory when it's really not configuration data. Roughly 2 years ago, XDG_STATE_DIR was added to the XDG Base Directory Specification[0] and its description, user-specific state data, actually perfectly matches what watch_later data is for. Let's go ahead and use this directory as the default for watch_later. This change only affects non-darwin unix-like systems (i.e. Linux, BSDs, etc.). The directory doesn't move for anyone else. Internally, quite a few things change with regards to the path selection. If the platform in question does not have a statedir concept, then the path selection will simply return "home" instead (old behavior). Fixes #9147. [0]: https://gitlab.freedesktop.org/xdg/xdg-specs/-/commit/4f2884e16db35f2962d9b64312917c81be5cb54b
2023-05-03 00:29:27 +00:00
- `--save-position-on-quit` and its associated commands now store state files in
the XDG_STATE_HOME directory by default. This only has an effect on linux/bsd
systems.
player: use XDG_CACHE_HOME by default This adds cache as a possible path for mpv to internally pick (~/.cache/mpv for non-darwin unix-like systems, the usual config directory for everyone else). For gpu shader cache and icc cache, controlling whether or not to write such files is done with the new --gpu-shader-cache and --icc-cache options respectively. Additionally, --cache-on-disk no longer requires explicitly setting the --cache-dir option. The old options, --cache-dir, --gpu-shader-cache-dir, and --icc-cache-dir simply set an override for the directory to save cache files. If unset, then the cache is saved in XDG_CACHE_HOME.
2023-05-03 00:42:23 +00:00
- mpv now implictly saves cache files in XDG_CACHE_HOME by default. This only has
an effect if the user enables options that would lead to cache being stored and
only makes a difference on linux/bsd systems.
- `--cache-on-disk` no longer requires explictly setting the `--cache-dir` option
- add `--icc-cache` and `--gpu-shader-cache` options to control whether or not to
save cache files for these features; explictly setting `--icc-cache-dir` and
`--gpu-shader-cache` is no longer required
vo_gpu_next: remove --tone-mapping-crosstalk Removed upstream, to be replaced by constant 0.04.
2023-05-24 19:32:00 +00:00
- remove the `--tone-mapping-crosstalk` option
vo_gpu_next: add missing --gamut-mapping-mode options Adds the missing upstream values that were exposed by the new gamut mapping API.
2023-06-19 10:59:51 +00:00
- add `--gamut-mapping-mode=perceptual|relative|saturation|absolute|linear`
vo_gpu_next: add --corner-rounding option For better or worse.
2023-06-19 11:06:01 +00:00
- add `--corner-rounding` option
options: set subs-with-matching-audio to off by default This means that subtitles won't be displayed unless the user asks for them
2021-05-26 18:57:35 +00:00
- change `--subs-with-matching-audio` default from `yes` to `no`
options: default slang to auto
2021-05-26 23:08:22 +00:00
- change `--slang` default from blank to `auto`
player: add --input-cursor-passthrough option Add an option for allowing pointer events to pass through the mpv window. This could be useful in cases where a user wants to display transparent images/video with mpv and interact with applications beneath the window. This commit implements this functionality for x11 and wayland. Note that whether or not this actually works likely depends on your window manager and/or compositor. E.g. sway ignores pointer events but the entire window becomes draggable when you float it (nothing under the mpv window receives events). Weston behaves as expected however so that is a compositor bug. Excuse the couple of completely unrelated style fixes (both were originally done by me).
2022-05-12 21:26:49 +00:00
- add `--input-cursor-passthrough` option to allow pointer events to completely
passthrough the mpv window
vo_gpu/vo_gpu_next: enable gpu shader and icc cache by default 4502522a7aee093c923e79a65e4684ea2634af30 changed the way mpv handled and saved cached files. In particular, it made a separate boolean option for actually enabling cache and left the *-dir options as purely just a path (i.e. having a dir set didn't mean you save cache). This technically regressed people's configs, so let's just turn the cache on by default. Linux users already expect random stuff in ~/.cache and well everyone else can just live with some files possibly appearing in their config directory.
2023-07-04 19:48:03 +00:00
- icc and gpu-shader cache are now saved by default (use --no-icc-shader-cache and
--no-gpu-shader-cache to disable)
demux_playlist: add option to control recursive directory loading Directories were always loaded recursively, which can be slow (e.g. one of the subdirectories is a mounting point to a slow device) and can unexpectedly expand into a massive playlist. Due to the problems described in 503dada42f1ea1007768da0dc6a41b67cdf89400, this defaults to recursive loading. ref. https://github.com/mpv-player/mpv/issues/9652
2023-02-11 20:08:38 +00:00
- add `--directory-mode=recursive|lazy|ignore`
Release 0.36.0
2023-07-23 17:10:36 +00:00
- `--hwdec=yes` is now mapped to `auto-safe` rather than `auto` (also used
by ctrl+h keybind)
vo_gpu_next: add --hdr-contrast-recovery/smoothness New upstream feature. Disabled by default.
2023-07-17 14:37:36 +00:00
- add `--hdr-contrast-recovery` and `--hdr-contrast-smoothness`
builtin.conf: add --hdr-contrast-recovery to gpu-hq The first change to the gpu-hq profile in aeons.
2023-07-17 14:48:06 +00:00
- include `--hdr-contrast-recovery` in the `gpu-hq` profile
vo_gpu_next: add new libplacebo-based renderer As discussed in #8799, this will eventually replace vo_gpu. However, it is not yet complete. Currently missing: - OpenGL contexts - hardware decoding - blend-subtitles=video - VOCTRL_SCREENSHOT However, it's usable enough to cover most use cases, and as such is enough to start getting in some crucial testing.
2021-04-09 07:14:54 +00:00
--- mpv 0.35.0 ---
- add the `--vo=gpu-next` video output driver, as well as the options
`--allow-delayed-peak-detect`, `--builtin-scalers`,
`--interpolation-preserve` `--lut`, `--lut-type`, `--image-lut`,
`--image-lut-type` and `--target-lut` along with it.
vo_gpu_next: implement HDR passthrough Completely untested, since Linux still can't into HDR in 2021. Somebody please make sure it works. Technically covers #8219, since gpu-context=drm can be combined with vo=gpu-next.
2021-11-07 22:47:55 +00:00
- add `--target-colorspace-hint`
vo_gpu_next: update for new tone mapping options This was significantly refactored upstream. Switch to new APIs and add new tone mapping curves and options. cf. https://code.videolan.org/videolan/libplacebo/-/merge_requests/212
2022-01-03 02:56:36 +00:00
- add `--tone-mapping-crosstalk`
- add `--tone-mapping` options `auto`, `spline` and `bt.2446a`
- add `--inverse-tone-mapping`
vo_gpu: add --gamut-mapping-mode Merge --gamut-clipping and --gamut-warning into a single option, --gamut-mapping-mode, better corresponding to the new vo_gpu_next APIs and allowing us to easily extend this option as new modes are added in the future.
2022-01-03 03:31:50 +00:00
- add `--gamut-mapping-mode`, replacing `--gamut-clipping` and `--gamut-warning`
vo_gpu: add --tone-mapping-mode This merges the old desaturation control options into a single enumeration, with the goal of both simplifying how these options work and also making this list more extensible (including, notably, new options only supported by vo_gpu_next). For the hybrid option, I decided to port the (slightly tweaked) values from libplacebo's pre-refactor defaults, rather than the old values we had in mpv, to more visually match the look of the vo_gpu_next hybrid.
2022-01-04 00:50:00 +00:00
- add `--tone-mapping-mode`, replacing `--tone-mapping-desaturate` and
`--tone-mapping-desaturate-exponent`.
vf_format: add dolbyvision sub-option Useful to strip dolbyvision from the output, in cases where the user does not want it applied. Doing this as a video filter gives users the abiilty to easily toggle this stripping at runtime in a way that properly propagates to any (potentially stateful) VO. It also thematically fits the rest of the options in vf_format, which are similarly concerned with modifying the video image parameters.
2022-01-07 05:41:55 +00:00
- add `dolbyvision` sub-parameter to `format` video filter
options: only apply sub-visibility to primary subs Previously, the sub-visibility option changed the visibility of all subtitles including secondary ones. This meant that it was not possible to only display secondary subtitles while hiding the primary ones. This modifies the sub-visibility option so that it only affects primary subtitles which allows only secondary subtitles to be displayed.
2022-01-19 17:23:52 +00:00
- `--sub-visibility` no longer has any effect on secondary subtitles
vf_format: support forwarding/stripping film grain metadata
2022-04-01 20:26:23 +00:00
- add `film-grain` sub-parameter to `format` video filter
vo_vaapi_wayland: remove, as it is superceded by vo_dmabuf_wayland
2022-09-29 13:50:51 +00:00
- add experimental `--vo=dmabuf-wayland` video output driver
x11: add --x11-present option With the recent addition of the libxpresent, it should improve frame timings for most users. However, there were known cases of bad behavior (Nvidia) which lead to a construction of a whitelist instead of just enabling this all the time. Since there's no way to predict whatever combination of hardware/drivers/etc. may work correctly, just give users an option to switch the usage of xorg's presentation statistics on/off. The default value, auto, works like before (basically, Mesa drivers and no Nvidia are allowed), but now one can force it on/off if needed.
2022-06-20 00:40:20 +00:00
- add `--x11-present` for controlling whether to use xorg's present extension
af_rubberband: add new engine option in rubberband 3.0.0
2022-07-16 01:17:41 +00:00
- add `engine` option to the `rubberband` audio filter to support the new
engine introduced in rubberband 3.0.0. Defaults to `finer` (new engine).
wayland: add support for configure bounds In wayland-protocols 1.25, xdg-shell got a version bump which added the configure_bounds event. The compositor can send this to clients to indicate that they should not resize past a certain size. For mpv, we'll choose to only listen to this on reconfig events (i.e. when the window first appears and if the video resolution changes later in the playlist). However, this behavior is still exposed as a user option (default on) because it will neccesarily conflict with a user setting a specific geometry size and/or window scale. Presumably, if someone is setting a really large size that goes beyond the bounds of their monitor, they actually want it like that. The wayland-protocols version is newer-ish, but we can get around having to poke the build system by just using a define that exists in the generated xdg-shell header.
2022-05-31 13:36:15 +00:00
- add `--wayland-configure-bounds` option
DOCS: deprecate --gamma-factor and --gamma-auto Removed the outdated information about environmental brightness with respect to --gamma-factor, and mention that the option is deprecated and subject to future removal. Also deprecated the --gamma-auto option as it relies on the same outdated way of doing things.
2022-09-30 21:14:58 +00:00
- deprecate `--gamma-factor`
- deprecate `--gamma-auto`
vulkan: remove --vulkan-disable-events This has had no effect since libplacebo v4.192.0, and was deprecated upstream a year ago. No deprecation period in mpv is justified by this being a debug / work-around option.
2022-10-05 14:35:14 +00:00
- remove `--vulkan-disable-events`
vo_gpu_next: add tunable shader parameters This is a very simple but easy way of doing it. Ideally, it would be nice if we could also add some sort of introspection about shader parameters at runtime, ideally exposing the entire list of parameters as a custom property dict. But that is a lot of effort for dubious gain. It's worth noting that, as currently implemented, re-setting `glsl-shader-opts` to a new value doesn't reset back previously mutated values to their defaults.
2022-11-03 15:16:59 +00:00
- add `--glsl-shader-opts`
player: add --screen-name and --fs-screen-name Simple groundwork for adding a couple of user options that allow selecting the screen with a string name. The next two commits implements these options for xorg and wayland.
2020-11-23 19:26:57 +00:00
--- mpv 0.34.0 ---
drm_common: enable specific device selection by means of path
2021-01-22 21:07:38 +00:00
- deprecate selecting by card number with `--drm-connector`, add
`--drm-device` which can be used instead
mac: use visible frame rectangle for window geometry calculation currently we use the whole screen rectangle to calculate the window geometry. this doesn't take the menu bar or the Dock into account. by default use the visible screen rectangle instead. this is also a change in behaviour, since the window can't be placed outside of this rectangle anymore. also add an option to change to the old behaviour, because it can still be useful in certain cases, like placing the window directly underneath the menu bar when used a desktop background. Fixes #8272
2020-12-13 16:13:18 +00:00
- add `--screen-name` and `--fs-screen-name` flags to allow selecting the
player: add --screen-name and --fs-screen-name Simple groundwork for adding a couple of user options that allow selecting the screen with a string name. The next two commits implements these options for xorg and wayland.
2020-11-23 19:26:57 +00:00
screen by its name instead of the index
mac: use visible frame rectangle for window geometry calculation currently we use the whole screen rectangle to calculate the window geometry. this doesn't take the menu bar or the Dock into account. by default use the visible screen rectangle instead. this is also a change in behaviour, since the window can't be placed outside of this rectangle anymore. also add an option to change to the old behaviour, because it can still be useful in certain cases, like placing the window directly underneath the menu bar when used a desktop background. Fixes #8272
2020-12-13 16:13:18 +00:00
- add `--macos-geometry-calculation` to change the rectangle used for screen
position and size calculation. the old behavior used the whole screen,
which didn't take the menu bar and Dock into account. The new default
behaviour includes both. To revert to the old behavior set this to
`whole`.
player/command: add albumart argument to video-add Enables marking of specific video sources as album art. Co-authored-by: Jan Ekström <jeebjp@gmail.com>
2021-02-26 11:05:24 +00:00
- add an additional optional `albumart` argument to the `video-add` command,
which tells mpv to load the given video as album art.
demux: undeprecate --cache-secs It serves a purpose and a rework of the cache won't be coming anytime soon. This partially reverts commit 8427292eb7c4074e1205c3d73c53c9e82569325f.
2021-04-06 14:04:46 +00:00
- undeprecate `--cache-secs` option
vo_gpu: replace --icc-contrast by --icc-force-contrast Not only does this have semantics that make far more sense, it also has a default that makes far more sense. (Equivalent to the old `icc-contrast=inf`) This removes the weird 1000:1 contrast default assumption which especially broke perceptual profiles and also screws things up for OLED/CRT/etc. Should probably close some issues but I honestly can't be bothered to figure out which of the thousands colorimetry-related issues are affected.
2021-04-26 16:31:16 +00:00
- remove `--icc-contrast` and introduce `--icc-force-contrast`. The latter
defaults to the equivalent of the old `--icc-contrast=inf`, and can
instead be used to specifically set the contrast to any value.
options: add watch-later-options This allows configuring which options are saved by quit-watch-later. Fixes #4126, #4641 and #5567. Toggling a video or audio filter twice would treat the option as changed because the backup value is NULL, and the current value of vf/af is a list with one empty item, so obj_settings_list_equal had to be changed.
2021-07-21 09:06:41 +00:00
- add a `--watch-later-options` option to allow configuring which
options quit-watch-later saves
command: make current-window-scale writeable, 2nd attempt The window-scale property mirrors the respective option (not the effective scale derived from the current window size), and as such setting its value to the same value it had before has no effect. Specifically - the window will not resize. This is consistent as far as property-option bridge behavior goes, but we do end up with an issue that we can't set an arbitrary scale and expect the window to always resize accordingly. We do also have a current-window-scale property which does reflect the actual window size, however, it's been read-only till now. This commit makes current-window-scale RW so that it's now always possible to set an arbitrary scale and expect the window to resize accordingly (without affecting window-scale - like manual resize). Also, mention window-scale no-effect-if-not-changed at the docs. Based on code by @Dudemanguy from commit 873ae0d, with same effect.
2020-11-08 00:36:26 +00:00
- make `current-window-scale` writeable and use it in the default input.conf
input: new option: --no-input-builtin-bindings This is similar to [no-]input-default-bindings, but affects only builtin bindings (while input-default-bindings affects anything which config files can override, like scripting mp.add_key_binding). Arguably, this is what input-default-binding should have always done, however, it does not. The reason we add a new option rather than repurpose/modify the existing option is that it behaves differently enough to raise concerns that it will break some use cases for existing users: - The new option is only applied once on startup, while input-default-bindings can be modified effectively at runtime. - They affects different sets of bindings, and it's possible that the set of input-default-bindings is useful enough to keep. Implementation-wise, both options are trivial, so keeping one or the other or both doesn't affect code complexity. It could be argued that it would be useful to make the new option also effective for runtime changes, however, this opens a can of worms of how the bindings are stored beyond the initial setup. TL;DR: it's impossible to differentiate correctly at runtime between builtin bindings, and those added with mp.add_key_bindings. The gist is that technically mpv needs/uses two binding "classes": - weak/builtin bindings - lower priority than config files. - "user" bindings - config files and "forced" runtime bindings. input-default-bindings affects the first class trivially, but input-builtin-bindings would not be able split this class further at runtime without meaningful changes to a lot of delicate code. So a new option it is. It should be useful to some libmpv clients (players) which want to disable mpv's builtin bindings without breaking mp.add_key_bindings for scripts. Fixes #8809 (again. the previous fix 8edfe70b only improved the docs, while now we're actually making the requested behavior possible)
2021-10-06 23:18:19 +00:00
- add `--input-builtin-bindings` flag to control loading of built-in key
bindings during start-up (default: yes).
player: add track-list/N/image sub-property This exposes whether a video track is detected as an image, which is useful for profile conditions, property expansion and lavfi-complex. The lavf demuxer sets image to true when the existing check detects an image. When the lavf demuxer fails, the mf one guesses if the file is an image by its extension, so sh->image is set to true when the mf demuxer succeds and there's only one file. The mkv demuxer just sets image to true for any attached picture. The timeline demuxer just copies the value of image from source to destination. This sets image to true for attached pictures, standalone images and images added with !new_stream in EDL playlists, but it is imperfect since you could concatenate multiple images in an EDL playlist (which should be done with the mf demuxer anyway). This is good enough anyway since the comment of the modified function already says it is "Imperfect and arbitrary".
2021-10-14 14:36:57 +00:00
- add ``track-list/N/image`` sub-property
vo_gpu: opengl: remove --opengl-restrict As the documentation of the toggle says - the implementation can (and will actually if they follow the GLX/EGL spec) return context version greater than the one requested. This happens with all Mesa drivers that I've tested as well as the Nvidia binary drivers. This toggle seems like a workaround for buggy drivers, yet it's lacking context about the vendor and version. Remove it for now - I'll be happy to reinstate it (partially or in full) as we get concrete details. This allows us to simplify ra_gl_ctx_test_version() making the whole context creation business easier to follow by mere mortals. Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
2021-10-03 12:14:13 +00:00
- remove `--opengl-restrict` option
js: custom-init: use ~~/init.js instead of ~~/.init.js (dot) mpv doesn't have other dot files in its config dir, and it also shouldn't be "invisible". The new name ~~/init.js now replaces ~~/.init.js While mpv usually deprecates things before outright removing them, in this case the old (dot) name is replaced without deprecation: - It's a bad idea to execute hidden scripts, even if at a config dir, and we don't want to do that for the next release cycle too. - We warn if the old (dot) name exists and the new name doesn't, which should be reasonably visible for affected users. - It's likely niche enough to not cause too much pain. If for some reason both names are needed, e.g. when using also an old mpv versions, then the old name could be symlinked to the new one, or simply have one line: `require("~~/init")` to load the new name, while a new mpv version will load (only) the new name without warning.
2021-10-12 13:35:18 +00:00
- js custom-init: use filename ~~/init.js instead of ~~/.init.js (dot)
scripting: load scripts from directories The intention is to provide a slightly nicer way to distribute scripts. For example, you could put multiple source files into the directory, and then import them from the actual script file (this is still unimplemented). At first I wanted to require a config file (because you need to know at least which scripting backend it should use). This wouldn't have been too hard (could have reused/abused the mpv config file parsing mechanism, and I already had working code that was just 2 function calls). But probably better to do this without new config files, because it might become a pain in the distant future. So this just probes for "main.lua", "main.js", etc., until an existing file is found. Another important change is that this skips all directory entries whose name starts with ".". This automatically excludes the "." and ".." special directories, and is probably useful to exclude random crap that might be lying around in the directory (such as editor temporary files, or OSX, in its usual hrmful, annoying, and idiotic modus operandi, sharting all over any directories opened by "Finder"). Although the changelog mentions the docs, they're added only in a later commit.
2020-02-01 17:09:40 +00:00
--- mpv 0.33.0 ---
DOCS/interface-changes: add d3d11-exclusive-fs to list of changes Was forgotten in finishing up the pull request.
2020-04-12 18:38:01 +00:00
- add `--d3d11-exclusive-fs` flag to enable D3D11 exclusive fullscreen mode
when the player enters fullscreen.
scripting: load scripts from directories The intention is to provide a slightly nicer way to distribute scripts. For example, you could put multiple source files into the directory, and then import them from the actual script file (this is still unimplemented). At first I wanted to require a config file (because you need to know at least which scripting backend it should use). This wouldn't have been too hard (could have reused/abused the mpv config file parsing mechanism, and I already had working code that was just 2 function calls). But probably better to do this without new config files, because it might become a pain in the distant future. So this just probes for "main.lua", "main.js", etc., until an existing file is found. Another important change is that this skips all directory entries whose name starts with ".". This automatically excludes the "." and ".." special directories, and is probably useful to exclude random crap that might be lying around in the directory (such as editor temporary files, or OSX, in its usual hrmful, annoying, and idiotic modus operandi, sharting all over any directories opened by "Finder"). Although the changelog mentions the docs, they're added only in a later commit.
2020-02-01 17:09:40 +00:00
- directories in ~/.mpv/scripts/ (or equivalent) now have special semantics
(see mpv Lua scripting docs)
- names starting with "." in ~/.mpv/scripts/ (or equivalent) are now ignored
js: require: directory-scripts: first look at <dir>/modules/ Also, add the function mp.get_script_directory() to let scripts know if they're loaded as a directory and where.
2020-02-07 15:35:48 +00:00
- js modules: ~~/scripts/modules.js/ is no longer used, global paths can be
set with custom init (see docs), dir-scripts first look at <dir>/modules/
DOCS: make mentions of macOS consistent change all mentions and variations of OSX, OS X, MacOSX, MacOS X, etc consistent. use the official naming macOS.
2024-02-20 20:19:40 +00:00
- the macOS bundle now logs to "~/Library/Logs/mpv.log" by default
demux: deprecate --cache-secs Because it's confusing and useless. If nobody complains, we'll have one weird cache configuration option less.
2020-03-05 20:53:51 +00:00
- deprecate the --cache-secs option (once removed, the cache cannot be
limited by time anymore)
command: remove legacy hook API Hopefully nothing uses this. (I know one exception, but, well, what can I do.)
2020-03-06 18:23:14 +00:00
- remove deprecated legacy hook API ("hook-add", "hook-ack"). Use either the
libmpv API (mpv_hook_add(), mpv_hook_continue()), or the Lua scripting
wrappers (mp.add_hook()).
DOCS/interface-changes.rst: add note about property notification changes Commits ba70b150fbe8 and 8a4f812b76be should have mentioned this. These things should be quite useful for client API users, and thus should be mentioned in a prominent place. Although I'm not sure if anyone will understand from this gibberish what this really means.
2020-03-14 00:40:54 +00:00
- improve how property change notifications are delivered on events and on
hooks. In particular, a hook event is only returned to a client after all
changes initiated before the hook point were delivered to the same client.
In addition, it should no longer happen that events and property change
notifications were interleaved in bad ways (it could happen that a
property notification delivered after an event contained a value that was
valid only before the event happened).
player: playlist-pos now use -1 for "no entry selected" It's odd that this state is observable, but is made implicit by making the property unavailable. It's also odd that an API user cannot directly put the player into such a state. Just allow reading/writing -1 (or in fact, any out of bounds index) for this case. I'm also refraining from using OPT_CHOICE for the "no selection" case, because although that would be cleaner in theory, it would cause only problems to API users due to the more complex property type (worse is better). One reason for not restricting the integer range on the input property anymore is that if there are no playlist elements, the range would contain only 1 integer, which cannot be represented anymore since the recent m_option change. This was actually broken with 1 element playlists before (and still is, with the constricted type for OSD and the add/cycle commands). Doesn't matter too much.
2020-03-21 13:44:09 +00:00
- the playlist-pos and playlist-pos-1 properties now can return and accept
-1, and are never unavailable. Out of range indexes are now accepted, but
behave like writing -1.
player: add a number of new playlist contol commands/properties Should give a good deal more explicit control and insight over the player state. Some feel a bit pointless, and/or expose internal weirdness. However, it's not like the existing weirdness didn't exist before, or can be made go away. (In part, the weirdness is because certain in-between states are visible. Hiding them would make things simpler, but less flexible.) Maybe this actually gives users a better idea how the API _should_ look like, too. On a side note, this tries to really guarantee that mpctx->playing is set between playback start/end. For that, the loadfile.c changes assume that mpctx->playing is set (guaranteed by code above the change), and that playing->filename is set (probably could never be false; was broken before and actually would have crashed if that could ever happen; in any case, also add an assert to playlist.c for this). playlist_entry_to_index() now tolerates playlist_entrys that are not part of the playlist. This is also needed for mpctx->playing.
2020-03-21 16:08:43 +00:00
- the playlist-pos and playlist-pos-1 properties deprecate the current
behavior when writing back the current value to the property: currently,
this restarts playback, but in the future, it will do nothing.
Using the "playlist-play-index" command is recommended instead.
- add "playlist-play-index" command
- add playlist-current-pos, playlist-playing-pos properties
lua: restore recent end-file event, and deprecate it Lua changed behavior for this specific event. I considered the change minor enough that it would not need to go through deprecation, but someone hit it immediately and ask on the -dev channel. It's probably better to restore the behavior. But mark it as deprecated, since it's problematic (mismatch with the C API). Unfortunately, no automatic warning is possible. (Or maybe it is, by playing sophisticated Lua tricks such as setting a metatable and overriding indexing, but let's not.)
2020-03-22 18:42:59 +00:00
- Lua end-file events set the "error" field; this is deprecated; use the
"file_error" instead for this specific event. Scripts relying on the
"error" field for end-file will silently break at some point in the
future.
ipc: add --input-ipc-client option While --input-file was removed for justified reasons, wanting to pass down socket FDs this way is legitimate, useful, and easy to implement. One odd thing is that Fixes: #7592
2020-04-08 23:05:51 +00:00
- remove deprecated --input-file option, add --input-ipc-client, which is
vaguely a replacement of the removed option, but not the same
player: mess with track selection details again Some time ago, properties and options were mostly unified. However, the track selection properties/options semantics are incompatible to this change. I'm still trying to handle the fallout. There are two things that are in the way: 1. Track properties somehow return the runtime selection, not the option value (all while properties are supposed to be aliases to options with the same name). 2. The user's track options are not supposed to be changed without interaction. If a track is auto-selected, the property should return its ID, but the option value should remain at "auto". Only if the user actually writes to the property the option should change. E.g. playing e.g. an audio-only file and then a normal video file not play the video file with --vid=no just because the audio file had no video track. In addition to each of them being in conflict with the property/option unification, attempt to fix one of them breaks the other one. Today, we're trying to fix parts of this and avoiding an unfortunate case where you can get a conflicting option/property value, and where trying to select a track does nothing if the track to select has the same ID as the option value. This breaks 2. from above in certain situations. See manpage additions. See: #7608
2020-04-13 13:42:52 +00:00
- change another detail for track selection options (see --aid manpage
entry)
options: don't trigger bool "compact" path for --loop-file In theory an incompatible change, but I think it's for the better. Impact should be relatively low. I hope. Fixes: #7676
2020-05-06 13:27:00 +00:00
- reading loop-file property as native property or mpv_node will now return
"inf" instead of boolean true (also affects loop option)
vo_direct3d: rip out texture video rendering path This isn't useful anymore. We have a much better d3d11 renderer in vo_gpu. D3D11 is available in all supported Windows versions. The StretchRect path might still be useful for someone (???), and leaving it at least evades conflict about users who want to keep using this VO for inexplicable reasons. (Low power usage might be a justified reason, but still, no.) Also fuck the win32 platform, it's a heap of stinky shit. Microsoft is some sort of psycho clown software company. Granted, maybe still better than much of the rest of Silly Con Valley.
2020-05-13 19:35:32 +00:00
- remove some --vo-direct3d-... options (it got dumbed down; use --vo=gpu)
video: clean up some imgfmt related stuff Remove the vaguely defined plane_bits and component_bits fields from struct mp_imgfmt_desc. Add weird replacements for existing uses. Remove the bytes[] field, replace uses with bpp[]. Fix some potential alignment issues in existing code. As a compromise, split mp_image_pixel_ptr() into 2 functions, because I think it's a bad idea to implicitly round, but for some callers being slightly less strict is convenient. This shouldn't really change anything. In fact, it's a 100% useless change. I'm just cleaning up what I started almost 8 years ago (see commit 00653a3eb052). With this I've decided to keep mp_imgfmt_desc, just removing the weird parts, and keeping the saner parts.
2020-05-17 12:57:13 +00:00
- remove video-params/plane-depth property (was too vaguely defined)
player: remove some display-adrop leftovers Forgotten in one of the previous commits. Also undeprecates display-adrop since it's out of sight now.
2020-05-23 02:24:04 +00:00
- remove --video-sync-adrop-size option (implementation was changed, no
replacement for what this option did)
- undeprecate --video-sync=display-adrop
auto_profiles: add this script This is taken from a somewhat older proof-of-concept script. The basic idea, and most of the implementation, is still the same. The way the profiles are actually defined changed. I still feel bad about this being a Lua script, and running user expressions as Lua code in a vaguely defined environment, but I guess as far as balance of effort/maintenance/results goes, this is fine. It's a bit bloated (the Lua scripting state is at least 150KB or so in total), so in order to enable this by default, I decided it should unload itself by default if no auto-profiles are used. (And currently, it does not actually rescan the profile list if a new config file is loaded some time later, so the script would do nothing anyway if no auto profiles were defined.) This still requires defining inverse profiles for "unapplying" a profile. Also this is still somewhat racy. Both will probably be alleviated to some degree in the future.
2020-08-05 20:37:47 +00:00
- deprecate legacy auto profiles (profiles starting with "extension." and
"protocol."). Use conditional auto profiles instead.
command: extend subprocess command stdin, change behavior Make it possible to feed a string to stdin of a subprocess. Out of laziness, it can't be an arbitrary byte string. (Would require adding an option type that takes in a Lua byte string.) Do not set stdin of a subprocess to fd 0 (i.e. mpv's stdin) anymore, because it makes things more consistent. Enabling stdin didn't make too much sense in the first place, so this behavior change seems justifiable. win32 support missing. Fixes: #8003
2020-08-16 00:54:44 +00:00
- the "subprocess" command does not connect spawned processes' stdin to
mpv's stdin anymore. Instead, stdin is connected to /dev/null by default.
To get the old behavior, set the "passthrough_stdin" argument to true.
options: do not accept ":" as separator anymore in key/value lists Accepting ":" in addition to "," seems confusing and dumb. It only causing problems when you want to pass a value that contains ":". Remove support for ":", it is now treated like any other normal character. This affects all options that are listed as "Key/value list" in the option list. It's possible that this breaks for someone who happened to use ":" as separator. But this was undocumented, and never recommended. Originally, the option treated many other characters in a special way, but this was changed in commit a3d561f950e74fe. I'm, not sure why ":" was explicitly included. Maybe because -the absurd -vf/--af syntax uses ":" as list separator. But "," was always recommended and used in examples for key/value options. Fixes: #8021 (if you consider it a bug)
2020-08-22 18:25:20 +00:00
- key/value list options do not accept ":" as item separator anymore,
only ",". This means ":" is always considered part of the value.
vo_vdpau: remove deprecated/inactive --vo-vdpau-deint option I think this has been dead code for quite a while. It was deprecated anyway.
2020-09-09 13:38:39 +00:00
- remove deprecated --vo-vdpau-deint option
DOCS: correct interface-changes.rst delete-watch-later-config was introduced in mpv 0.33.0 not mpv 0.31.0.
2020-11-08 00:55:03 +00:00
- add `delete-watch-later-config` command to complement
`write-watch-later-config`
Release 0.32.0
2020-01-26 20:31:54 +00:00
--- mpv 0.32.0 ---
options: change option parsing when using a single dash Addresses dumb things like accidentally overwriting a media file with e.g. "mpv --log-file test.mkv" (when the user thought that --log-file was a flag option, when it actually takes a filename). This example will now print an error. It still works with "-log-file overwritten.mkv", but prints a warning. Not sure if I'm being too careful or not "radical" enough. In any case, both the syntax that stops working and the syntax that produces a warning now have been discouraged and were called legacy for almost a decade.
2020-01-07 22:08:45 +00:00
- change behavior when using legacy option syntax with options that start
with two dashes (``--`` instead of a ``-``). Now, using the recommended
syntax is required for options starting with ``--``, which means an option
value must be strictly passed after a ``=``, instead of as separate
argument. For example, ``--log-file f.txt`` was previously accepted and
behaved like ``--log-file=f.txt``, but now causes an error. Use of legacy
syntax that is still supported now prints a deprecation warning.
interface-changes: fixup the location of d3d11-output-csp 0.30.0 is already cut, so +1 it is.
2019-10-30 18:02:08 +00:00
--- mpv 0.31.0 ---
player: Optionally validate st_mtime when restoring playback state I often watch sporting events. On many occasions I get files with the same filename for each session. For example, for F1 I might have the following directory structure: F1/ FP1.mkv FP2.mkv FP3.mkv Qualification.mkv Race.mkv Since usually one simply watches one race after the other, I usually just rsync the new event's files over the old ones, so, for example, Race.mkv will be replaced from the file for the last event with the file from the new event. One problem with this is that I like to use --resume-playback for other kinds of media, so I have it on by default. That works great for, say, a movie, but doesn't work so well with this scheme, because you can trivially forget to pass --no-resume-playback on the command line and end up 2 hours in, watching spoilers as the race results scroll down the screen :-) This patch adds a new option, --resume-playback-check-mtime, which validates that the file's mtime hasn't changed since the watch_later configuration was saved. It does this by setting the watch_later configuration to have the same mtime as the file after it is saved. Switching back and forth between checking mtime and not checking mtime works fine, as we only choose whether to compare based on it, but we update the watch_later configuration mtime regardless of its value.
2019-11-09 18:24:16 +00:00
- add `--resume-playback-check-mtime` to check consistent mtime when
restoring playback state.
vo_gpu/d3d11: add support for configuring swap chain color space By default utilizes the color space of the desktop on which the swap chain is located. If a specific value is defined, it will be instead be utilized. Enables configuration of the PQ color space (BT.2020 primaries, PQ transfer function) for HDR. Additionally, signals the swap chain color space to the renderer, so that the render looks correct without having to specify target-trc or target-prim manually. Due to all of the APIs being Win10+ only, will only work starting with Windows 10.
2018-05-06 00:01:58 +00:00
- add `--d3d11-output-csp` to enable explicit selection of a D3D11
swap chain color space.
DOCS/interface-changes.rst: improve entry about sws changes This was pretty vague. Add some context, and explicitly mention how these options now affect screenshots.
2019-11-03 22:32:59 +00:00
- the --sws- options and similar now affect vo_image and screenshot
conversion (does not matter as much for vo_gpu, which does most of this
with shaders)
- add a builtin "sw-fast" profile, which restores performance settings
for software video conversion. These were switched to higher quality since
mpv 0.30.0 (related to the previous changelog entry). This affects video
outputs like vo_x11 and vo_drm, and screenshots, but not much else.
options: deprecate --input-file I have no idea why this still exists, since we have --input-ipc-server. I think there was something about Windows, but the latter option is implemented even on Windows.
2019-11-16 14:28:18 +00:00
- deprecate --input-file (there are no plans to remove this short-term,
ipc: add --input-ipc-client option While --input-file was removed for justified reasons, wanting to pass down socket FDs this way is legitimate, useful, and easy to implement. One odd thing is that Fixes: #7592
2020-04-08 23:05:51 +00:00
but it will probably eventually go away <- that was a lie)
options: deprecate --video-sync=display-adrop A stupid thing that will probably be in the way.
2019-11-17 01:11:28 +00:00
- deprecate --video-sync=display-adrop (might be removed if it's in the way;
undeprecated or readded if it's not too much of a problem)
manpage: deprecate input section commands These were a bad idea and are obscure. Scripting key mapping support still uses them, but this is not relevant to scripting authors, because the mpv provided helper code (defaults.lua) takes care of this. In addition, the OSC uses a legacy form of this. Hopefully, this input section stuff can be removed, and replaced by a simpler mechanism.
2019-11-19 22:09:59 +00:00
- deprecate all input section commands (these will be changed/removed, as
soon as mpv internals do not require them anymore)
options: remove deprecated --playlist-pos alias This causes problems because it has the same name as a property which behaves differently.
2019-11-24 21:39:47 +00:00
- remove deprecated --playlist-pos alias (use --playlist-start)
command, options: deprecate old --display-fps behavior See changelog and manpage changes. (So much effort to fix an ancient dumb mistake for an option nobody should use anyway.)
2019-11-24 23:47:53 +00:00
- deprecate --display-fps, introduce --override-display-fps. The display-fps
property now is unavailable if no VO exists (or the VO did not return a
display FPS), instead of returning the option value in this case. The
property will keep existing, but writing to it is deprecated.
command: change af/vf property behavior wrt. filter creation failures The behavior is slightly different in a messy way. The change is in line with the option-to-property bridge removal mentioned some commits ago and thus is deemed necessary.
2019-11-25 00:16:03 +00:00
- the vf/af properties now do not reject the set value anymore, even if
filter chain initialization fails. Instead, the vf/af options are always
set to the user's value, even if it does not reflect the "runtime" vf/af
chain.
command: change vid/aid/sid property behavior slightly Again in line with the option-to-property bridge changes. As usual, this causes subtle behavior changes, which may affect some users.
2019-11-25 18:49:09 +00:00
- the vid/aid/sid/secondary-sid properties (and their aliases: "audio",
"video", "sub") will now allow setting any track ID; before this change,
only IDs of actually existing tracks could be set (the restriction was
active the MPV_EVENT_FILE_LOADED/"file-loaded" event was sent). Setting
DOCS/interface-changes.rst: more details about track property changes Another subtle thing that should be mentioned. May or may not matter to someone.
2019-11-27 19:47:43 +00:00
an ID for which no track exists is equivalent to disabling it. Note that
setting the properties to non-existing tracks may report it as selected
track for a small time window, until it's forced back to "no". The exact
details how this is handled may change in the future.
mac: remove Apple Remote support the Apple Remote has long been deprecated and abandoned by Apple. current macs don't come with support for it anymore. support might be re-added with the next commit.
2019-11-16 15:54:07 +00:00
- remove old Apple Remote support, including --input-appleremote
- add MediaPlayer support and remove the old Media Key event tap on macOS.
this possibly also re-adds the Apple Remote support
command: change "edition" property behavior See manpage/changelog changes. The purpose of this change is to removes another case of inconsistent property behavior. At first I wanted to make this go through deprecation before making a technically incompatible change, but then I considered this feature too obscure as that anyone would care.
2019-12-16 00:47:06 +00:00
- the "edition" property now strictly returns the value of the option,
instead of the runtime value. The new "current-edition" property needs to
be queried to read the runtime-chosen edition. This is a breaking change
for any users which expected "edition" to return the runtime-chosen
edition at default settings (--edition=auto).
command: change "window-scale" property behavior This is similar to the "edition" change. I considered making this go through deprecation, but didn't have a good idea how to do that. Maybe it's fine, because this is pretty obscure. But it might break some API users/scripts (it certainly broke stats.lua), and all I have to say is sorry for that.
2019-12-16 01:32:17 +00:00
- the "window-scale" property now strictly returns the value of the option,
instead of the actual size of the window. The new "current-window-scale"
property needs to be queried to read the value as indicated by the current
window size. This is a breaking change.
options: increase consistency between list options and document them Whenever I deal with this, I have to look at the code to make sense of this. And beyond that, there are some strange inconsistencies. (I think this code is cursed. It always was, and maybe always will be.) Although the manpage claimed that using multiple items for -add etc. is deprecated, string list options didn't warn against it. So add the warning, and add something in the changelog (even though nobody will ever read this). The manpage mentioned --vf-append, but this didn't even exist. So add it, I guess. We encourage using -append for the other option types, so for consistency, it should work on filter options. (And I already tricked me into believing it existed when I mentioned it in the manpage.) Make the "operations" table separate for all option types, and mention the option type on every single of the top-level list options.
2019-12-18 04:11:57 +00:00
- explicitly deprecate passing more than 1 item to "-add" suffix in key/value
options (for example --script-opts-add). This was actually always
deprecated, like with other list options, but the option parser did not
print a warning in this particular case.
options: deprecate -del for list options I never liked that these used integer indexes. -remove should have existed from the start. This deprecation is yet another empty threat, though.
2019-12-18 05:57:24 +00:00
- deprecate -del for list options (use -remove instead, which is by content
instead of by integer index)
video/out/x11: add fs-screen fallback Apparently there are two different options for controlling which screen an mpv window goes onto: --fs-screen and --screen. The former explicitly only controls which screen a fullscreened window goes onto, but does not appear to actually care about this option at runtime for X11, so pressing f will always fullscreen to the screen mpv is currently on. This means the option is of questionable usefulness for starters. Making it worse, if you use --screen=1 --fs, mpv will actually fullscreen on screen 0, because --fs-screen isn't set. Instead of doing that, fall back to whatever --screen is set to.
2019-12-22 00:19:53 +00:00
- if `--fs` is used but `--fs-screen` is not set, mpv will now use `--screen`
instead.
vd_lavc: remove hwdec-by-default special case for RPI
2019-12-24 08:24:56 +00:00
- change the default of --hwdec to "no" on RPI. The default used to be "mmal"
specifically if 'Raspberry Pi support' was enabled at configure time
(equivalent to --enable-rpi). Use --hwdec=mmal to get the old behavior.
interface-changes: fixup the location of d3d11-output-csp 0.30.0 is already cut, so +1 it is.
2019-10-30 18:02:08 +00:00
--- mpv 0.30.0 ---
vo_gpu/d3d11: add support for configuring swap chain format Query information on the system output most linked to the swap chain, and either utilize a user-configured format, or either 8bit RGBA or 10bit RGB with 2bit alpha depending on the system output's bit depth.
2019-10-11 21:35:22 +00:00
- add `--d3d11-output-format` to enable explicit selection of a D3D11
swap chain format.
DOCS: Document DVB changes in interface-changes.
2019-10-01 23:05:25 +00:00
- rewrite DVB channel switching to use an integer value
`--dvbin-channel-switch-offset` for switching instead of the old
stream controls which are now gone. Cycling this property up or down will
change the offset to the channel which was initially tuned to.
Example for `input.conf`: `H cycle dvbin-channel-switch-offset up`,
`K cycle dvbin-channel-switch-offset down`.
- adapt `stream_dvb` to support writing to `dvbin-prog` at runtime
and also to consistently use dvbin-configuration over URI parameters
when provided
video/d3d11: add adapter selection by name into d3d11 options This lets the user define an adapter name that can then be passed further into the internals.
2019-04-19 22:26:39 +00:00
- add `--d3d11-adapter` to enable explicit selection of a D3D11 rendering
adapter by name.
drm: rename plane options to better, invariant, names This commit bumps the libmpv version to 1.102 drm-osd-plane -> drm-draw-plane drm-video-plane -> drm-drmprime-video-plane drm-osd-size -> drm-draw-surface-size "draw plane", as in the plane that OpenGL draws to, whether it be video + OSD or just OSD. "drmprime video plane", as in the plane used for hwdec video imported via drmprime. "draw surface size", as in the size of the surface used for the draw plane The new names are invariant whether or not hwdec_drmprime_drm is being used or not. The original naming was very confusing, as when doing regular rendering (swdec or vaapi) the video would be displayed on the "OSD plane", and the "Video plane" would remain unused.
2018-12-01 11:01:17 +00:00
- rename `--drm-osd-plane-id` to `--drm-draw-plane`, `--drm-video-plane-id` to
`--drm-drmprime-video-plane` and `--drm-osd-size` to `--drm-draw-surface-size`
to better reflect what the options actually control, that the values they
accept aren't actually internal DRM ID's (like with similar options in
ffmpeg's KMS support), and that the video plane is only used when the drmprime
overlay hwdec interop is active, with the video being drawn to the draw plane
otherwise.
- in addition to the above, the `--drm-draw-plane` and `--drm-drmprime-video-plane`
drm_atomic: Add general primary/overlay plane option Add general primary/overlay plane option to drm-osd-plane-id and drm-video-plane-id, so that the user can just request any usable primary or overlay plane for either of these two options. This should be somewhat more user-friendly (especially as neither of these two options currently have a useful help function), as usually you would only be interested in the type of the plane, and not exactly which plane gets picked.
2018-06-02 10:54:05 +00:00
options now accept either an integer index, or the values primary or overlay.
drm: rename plane options to better, invariant, names This commit bumps the libmpv version to 1.102 drm-osd-plane -> drm-draw-plane drm-video-plane -> drm-drmprime-video-plane drm-osd-size -> drm-draw-surface-size "draw plane", as in the plane that OpenGL draws to, whether it be video + OSD or just OSD. "drmprime video plane", as in the plane used for hwdec video imported via drmprime. "draw surface size", as in the size of the surface used for the draw plane The new names are invariant whether or not hwdec_drmprime_drm is being used or not. The original naming was very confusing, as when doing regular rendering (swdec or vaapi) the video would be displayed on the "OSD plane", and the "Video plane" would remain unused.
2018-12-01 11:01:17 +00:00
`--drm-draw-plane` now defaults to primary and `--drm-drmprime-video-plane`
drm_atomic: Add general primary/overlay plane option Add general primary/overlay plane option to drm-osd-plane-id and drm-video-plane-id, so that the user can just request any usable primary or overlay plane for either of these two options. This should be somewhat more user-friendly (especially as neither of these two options currently have a useful help function), as usually you would only be interested in the type of the plane, and not exactly which plane gets picked.
2018-06-02 10:54:05 +00:00
defaults to overlay. This should be similar to previous behavior on most drivers
due to how planes are usually sorted.
ao_opensles: update interface-changes
2018-07-25 14:36:57 +00:00
- rename --opensles-frames-per-buffer to --opensles-frames-per-enqueue to
better reflect its purpose. In the past it overrides the buffer size the AO
requests (but not the default/value of the generic --audio-buffer option).
Now it only guarantees that the soft buffer size will not be smaller than
itself while setting the size per Enqueue.
- add --opensles-buffer-size-in-ms, allowing user to tune the soft buffer size.
It overrides the --audio-buffer option unless it's set to 0 (with the default
being 250).
vo_gpu: split --linear-scaling into two separate options Since linear downscaling makes sense to handle independently from linear/sigmoid upscaling, we split this option up. Now, linear-downscaling is its own option that only controls linearization when downscaling and nothing more. Likewise, linear-upscaling / sigmoid-upscaling are two mutually exclusive options (the latter overriding the former) that apply only to upscaling and no longer implicitly enable linear light downscaling as well. The old behavior was very confusing, as evidenced by issues such as #6213. The current behavior should make much more sense, and only minimally breaks backwards compatibility (since using linear-scaling directly was very uncommon - most users got this for free as part of gpu-hq and relied only on that). Closes #6213.
2018-10-17 09:23:16 +00:00
- remove `--linear-scaling`, replaced by `--linear-upscaling` and
`--linear-downscaling`. This means that `--sigmoid-upscaling` no longer
implies linear light downscaling as well, which was confusing.
- the built-in `gpu-hq` profile now includes` --linear-downscaling`.
spirv: remove --spirv-compiler=nvidia This option has been deprecated upstream for a long time, probably doesn't even work anymore, and won't work moving forwards as we replace the vulkan code by libplacebo wrappers. I haven't removed the option completely yet since in theory we could still add support for e.g. a native glslang wrapper in the future. But most likely the future of this code is deletion. As an aside, fix an issue where the man page didn't mention d3d11.
2018-11-24 03:25:30 +00:00
- support for `--spirv-compiler=nvidia` has been removed, leaving `shaderc`
as the only option. The `--spirv-compiler` option itself has been marked
as deprecated, and may be removed in the future.
vo_gpu: improve tone mapping desaturation Instead of desaturating towards luma, we desaturate towards the per-channel tone mapped version. This essentially proves a smooth roll-off towards the "hollywood"-style (non-chromatic) tone mapping algorithm, which works better for bright content, while continuing to use the "linear" style (chromatic) tone mapping algorithm for primarily in-gamut content. We also split up the desaturation algorithm into strength and exponent, which allows users to use less aggressive desaturation settings without affecting the overall curve.
2018-12-27 17:34:19 +00:00
- split up `--tone-mapping-desaturate`` into strength + exponent, instead of
only using a single value (which previously just controlled the exponent).
The strength now linearly blends between the linear and nonlinear tone
mapped versions of a color.
vo_gpu: redesign peak detection algorithm The previous approach of using an FIR with tunable hard threshold for scene changes had several problems: - the FIR involved annoying hard-coded buffer sizes, high VRAM usage, and the FIR sum was prone to numerical overflow which limited the number of frames we could average over. We also totally redesign the scene change detection. - the hard scene change detection was prone to both false positives and false negatives, each with their own (annoying) issues. Scrap this entirely and switch to a dual approach of using a simple single-pole IIR low pass filter to smooth out noise, while using a softer scene change curve (with tunable low and high thresholds), based on `smoothstep`. The IIR filter is extremely simple in its implementation and has an arbitrarily user-tunable cutoff frequency, while the smoothstep-based scene change curve provides a good, tunable tradeoff between adaptation speed and stability - without exhibiting either of the traditional issues associated with the hard cutoff. Another way to think about the new options is that the "low threshold" provides a margin of error within which we don't care about small fluctuations in the scene (which will therefore be smoothed out by the IIR filter).
2019-01-01 06:30:00 +00:00
- add --hdr-peak-decay-rate and --hdr-scene-threshold-low/high
vo_gpu: allow boosting dark scenes when tone mapping In theory our "eye adaptation" algorithm works in both ways, both darkening bright scenes and brightening dark scenes. But I've always just prevented the latter with a hard clamp, since I wanted to avoid blowing up dark scenes into looking funny (and full of noise). But allowing a tiny bit of over-exposure might be a good thing. I won't change the default just yet (better let users test), but a moderate value of 1.2 might be better than the current 1.0 limit. Needs testing especially on dark scenes.
2019-01-02 02:03:38 +00:00
- add --tone-mapping-max-boost
Merge commit '559a400ac36e75a8d73ba263fd7fa6736df1c2da' into wm4-commits--merge-edition This bumps libmpv version to 1.103
2018-12-05 18:02:03 +00:00
- ipc: require that "request_id" fields are integers. Other types are still
accepted for compatibility, but this will stop in the future. Also, if no
request_id is provided, 0 will be assumed.
- mpv_command_node() and mp.command_native() now support named arguments
(see manpage). If you want to use them, use a new version of the manpage
as reference, which lists the definitive names.
- edition and disc title switching will now fully reload playback (may have
consequences for scripts, client API, or when using file-local options)
docs: add removed properties and options to interface-changes.rst
2018-12-06 18:14:14 +00:00
- with the removal of the stream cache, the following properties and options were
dropped: `cache`, `cache-size`, `cache-free`, `cache-used`, `--cache-default`,
`--cache-initial`, `--cache-seek-min`, `--cache-backbuffer`, `--cache-file`,
`--cache-file-size`
DOCS: some corrections around cache options
2019-10-08 16:38:23 +00:00
- the --cache option does not take a number value anymore
DOCS/interface-changes.rst: simplify playback abort change description Although it was not true at the time this was written, both the "program" and "cache-size" are gone now. Since the changelog is for the entire next release, it makes no sense to mention these removed properties. It also happens to make the description of this much simpler, because it's a non-issue now. It's probably not even worth mentioning anymore.
2019-10-05 00:08:19 +00:00
- remove async playback abort hack. This may make it impossible to abort
playback if --demuxer-thread=no is forced.
cocoa-cb: refactor title bar styling half of the materials we used were deprecated with macOS 10.14, broken and not supported by run time changes of the macOS theme. furthermore our styling names were completely inconsistent with the actually look since macOS 10.14, eg ultradark got a lot brighter and couldn't be considered ultradark anymore. i decided to drop the old option --macos-title-bar-style and rework the whole mechanism to allow more freedom. now materials and appearance can be set separately. even if apple changes the look or semantics in the future the new options can be easily adapted.
2019-03-29 19:38:02 +00:00
- remove `--macos-title-bar-style`, replaced by `--macos-title-bar-material`
and `--macos-title-bar-appearance`.
docs: add mentions of the Vulkan rendering abstraction replacement From internal to libplacebo.
2019-04-22 12:58:10 +00:00
- The default for `--vulkan-async-compute` has changed to `yes` from `no`
with the move to libplacebo as the back-end for vulkan rendering.
Remove optical disc fancification layers This removes anything related to DVD/BD/CD that negatively affected the core code. It includes trying to rewrite timestamps (since DVDs and Blurays do not set packet stream timestamps to playback time, and can even have resets mid-stream), export of chapters, stream languages, export of title/track lists, and all that. Only basic seeking is supported. It is very much possible that seeking completely fails on some discs (on some parts of the timeline), because timestamp rewriting was removed. Note that I don't give a shit about optical media. If you want to watch them, rip them. Keeping some bare support for DVD/BD is the most I'm going to do to appease the type of lazy, obnoxious users who will care. There are other players which are better at optical discs.
2019-09-13 14:48:34 +00:00
- Remove "disc-titles", "disc-title", "disc-title-list", and "angle"
properties. dvd:// does not support title ranges anymore.
Remove classic Linux analog TV support, and DVB runtime controls Linux analog TV support (via tv://) was excessively complex, and whenever I attempted to use it (cameras or loopback devices), it didn't work well, or would have required some major work to update it. It's very much stuck in the analog past (my favorite are the frequency tables in frequencies.c for analog TV channels which don't exist anymore). Especially cameras and such work fine with libavdevice and better than tv://, for example: mpv av://v4l2:/dev/video0 (adding --profile=low-latency --untimed even makes it mostly realtime) Adding a new input layer that targets such "modern" uses would be acceptable, if anyone is interested in it. The old TV code is just too focused on actual analog TV. DVB is rather obscure, but has an active maintainer, so don't remove it. However, the demux/stream ctrl layer must go, so remove controls for channel switching. Most of these could be reimplemented by using the normal method for option runtime changes.
2019-09-13 15:16:18 +00:00
- Remove all "tv-..." options and properties, along with the classic Linux
analog TV support.
command, demux: remove program property The "program" property could switch between TS programs. It was rather complex and rather obscure (even if you deal with TS captures, you usually don't need it). If anyone actually needs it (did anyone ever attempt to even use it?), it should be rewritten. The demuxer should export a program list, and the frontend should handle the "cycling" logic.
2019-09-13 15:22:17 +00:00
- remove "program" property (no replacement)
vo_gpu: x11: remove special vdpau probing, use EGL by default Originally, vo_gpu/vo_opengl considered the case of Nvidia proprietary drivers, which required vdpau/GLX, and Intel open source drivers, which require vaapi/EGL. Since window creation and GPU context creation are inseparable in mpv's internal API, it had to pick the correct API very early, or hardware decoding wouldn't work. "x11probe" was introduced for this reason. It created a GLX context (without showing the window yet), and checked whether vdpau was available. If yes, it used GLX, if not, it continued probing x11/EGL. (Obviously it couldn't always fail on GLX without vdpau, which is why it was a separate "probe" backend.) Years passed, and now the situation is different. Vdpau is dead. Nvidia drivers and libavcodec now provide CUDA interop, which requires EGL, and fixes some of the vdpau problems. AMD drivers now provide vaapi, which generally works better than vdpau. Intel didn't change. In particular, vaapi provides working HEVC Main10 support. In theory, it should work on vdpau too, with quality reduction (no 10 bit surfaces), but I couldn't get it to work. So always prefer EGL. And suddenly hardware decoding works. This is actually rather important, because HEVC is unfortunately on the rise, despite shitty encoders and unoptimized decoders. The latter may mean that hardware decoding works better than libavcodec. This should have been done a long, long time ago.
2017-12-27 04:27:00 +00:00
- always prefer EGL over GLX, which helps with AMD/vaapi, but will break
vdpau with --vo=gpu - use --gpu-context=x11 to be able to use vdpau. This
does not affect --vo=vdpau or --hwdec=vdpau-copy.
options: remove --chapter Has been deprecated for almost 3 years. Manpage didn't mention the deprecation, but CLI and release notes did. It wouldn't be much effort to keep this option working, but I just don't see the damn point. --start/--end can specify chapters using special syntax, which is equivalent.
2019-05-25 23:11:54 +00:00
- remove deprecated --chapter option
options: deprecate --stream-record It's inadequate for most uses. There are better mechanisms.
2019-07-13 13:41:42 +00:00
- deprecate --record-file
demux_cue: auto-detect CUE sheet charset
2019-04-07 13:10:52 +00:00
- add `--demuxer-cue-codepage`
player: expose pixel aspect ratio, bitrate and rotation value on tracks
2019-08-01 10:51:13 +00:00
- add ``track-list/N/demux-bitrate``, ``track-list/N/demux-rotation`` and
``track-list/N/demux-par`` property
options: rename --video-aspect to --video-aspect-override The justification for this is the fact that the `video-aspect` property doesn't work well with `cycle_values` commands that include the value "-1". The "video-aspect" property has effectively no change in behavior, but we may want to make it read-only in the future. I think it's probably fine to leave as-is, though. Fixes #6068.
2019-10-04 16:45:37 +00:00
- Deprecate ``--video-aspect`` and add ``--video-aspect-override`` to
replace it. (The `video-aspect` option remains unchanged.)
options: drop some previously deprecated options A release has been made, so drop options deprecated for that release. Also drop some options which have been deprecated a much longer time before. Also fix a typo in client-api-changes.rst.
2017-12-25 10:43:04 +00:00
--- mpv 0.29.0 ---
ao_opensles: remove useless cfg_sample_rate We should always use the ao-neutral --audio-samplerate option.
2018-03-12 19:30:54 +00:00
- drop --opensles-sample-rate, as --audio-samplerate should be used if desired
options: drop some previously deprecated options A release has been made, so drop options deprecated for that release. Also drop some options which have been deprecated a much longer time before. Also fix a typo in client-api-changes.rst.
2017-12-25 10:43:04 +00:00
- drop deprecated --videotoolbox-format, --ff-aid, --ff-vid, --ff-sid,
--ad-spdif-dtshd, --softvol options
player: strictly never autoselect tracks from --external-files Before this commit, some autoselection of tracks coming from files loaded with --external-files was still done. This commit removes all of it, and the only way to select a track is via the explicit stream selection options like --vid/--sid/--aid. I think this was always the original intention. The change could in theory still unintentionally surprise some users, so add a changelog entry. This does not affect --audio-file/--sub-file, even if these contain mismatching track types. E.g. if audio files passed to --audio-file contain subtitles, these should still be selected. Past feature requests indicate that users want this.
2018-01-06 16:49:37 +00:00
- fix --external-files: strictly never select any tracks from them, unless
explicitly selected (this may or may not be expected)
client API: remove ytdl=no default With the recent changes to the script it does not incur a startup delay by default due to starting youtube-dl and waiting for it. This was the main reason for making libmpv have a different default. Starting sub processes from a library can still be a bit fishy, but I think it's ok. Still mention it in the libmpv header. There were already other cases where libmpv would start its own processes, such as the X11 backend calling xdg-screensaver. (The reason why this is fishy is because UNIX process management sucks: SIGCHLD and the wait() syscall make sub processes non-transparent and could potentially introduce conflicts with code trying to use them.)
2018-01-11 22:36:07 +00:00
- --ytdl is now always enabled, even for libmpv
audio: add global options for resampler defaults This is part of trying to get rid of --af-defaults, and the af resample filter. It requires a complicated mechanism to set the defaults on the resample filter for backwards compatibility.
2018-01-12 03:02:55 +00:00
- add a number of --audio-resample-* options, which should from now on be
used instead of --af-defaults=lavrresample:...
options: deprecate --vf-defaults and --af-defaults
2018-01-12 03:07:53 +00:00
- deprecate --vf-defaults and --af-defaults. These didn't work with the
lavfi bridge, so they have very little use left. The only potential use
is with af_lavrresample (going to be deprecated, --audio-resample-... set
its defaults), and various hw deinterlacing filters (like vf_vavpp), for
which you will have to stop using --deinterlace=yes, and instead use the
vf toggle commands and the filter enable/disable flag to customize it.
af_lavrresample: deprecate this filter The future direction might be not having such a user-visible filter at all, similar to how vf_scale went away (or actually, redirects to libavfilter's vf_scale).
2018-01-12 03:16:39 +00:00
- deprecate --af=lavrresample. Use the ``--audio-resample-...`` options to
customize resampling, or the libavfilter ``--af=aresample`` filter.
command: add --osd-on-seek option defaulting to bar Restores behaviour prior to aef2ed5dc13e37dec0670c451b4369b151d5c65f. That change was apparently unpopular. However, given the amount of complaining over how hard it is to change the defaults by rebinding every key, I think the extra option introduced by this commit is justified. Technically not all behaviour is restored, because now --no-osd-bar will not instead display the msg text on seek. I think that feature was a little weird and is now easy enough to remedy with the --osd-on-seek option.
2018-01-21 23:36:08 +00:00
- add --osd-on-seek
video: rewrite filtering glue code Get rid of the old vf.c code. Replace it with a generic filtering framework, which can potentially handle more than just --vf. At least reimplementing --af with this code is planned. This changes some --vf semantics (including runtime behavior and the "vf" command). The most important ones are listed in interface-changes. vf_convert.c is renamed to f_swscale.c. It is now an internal filter that can not be inserted by the user manually. f_lavfi.c is a refactor of player/lavfi.c. The latter will be removed once --lavfi-complex is reimplemented on top of f_lavfi.c. (which is conceptually easy, but a big mess due to the data flow changes). The existing filters are all changed heavily. The data flow of the new filter framework is different. Especially EOF handling changes - EOF is now a "frame" rather than a state, and must be passed through exactly once. Another major thing is that all filters must support dynamic format changes. The filter reconfig() function goes away. (This sounds complex, but since all filters need to handle EOF draining anyway, they can use the same code, and it removes the mess with reconfig() having to predict the output format, which completely breaks with libavfilter anyway.) In addition, there is no automatic format negotiation or conversion. libavfilter's primitive and insufficient API simply doesn't allow us to do this in a reasonable way. Instead, filters can use f_autoconvert as sub-filter, and tell it which formats they support. This filter will in turn add actual conversion filters, such as f_swscale, to perform necessary format changes. vf_vapoursynth.c uses the same basic principle of operation as before, but with worryingly different details in data flow. Still appears to work. The hardware deint filters (vf_vavpp.c, vf_d3d11vpp.c, vf_vdpaupp.c) are heavily changed. Fortunately, they all used refqueue.c, which is for sharing the data flow logic (especially for managing future/past surfaces and such). It turns out it can be used to factor out most of the data flow. Some of these filters accepted software input. Instead of having ad-hoc upload code in each filter, surface upload is now delegated to f_autoconvert, which can use f_hwupload to perform this. Exporting VO capabilities is still a big mess (mp_stream_info stuff). The D3D11 code drops the redundant image formats, and all code uses the hw_subfmt (sw_format in FFmpeg) instead. Although that too seems to be a big mess for now. f_async_queue is unused.
2018-01-16 10:53:44 +00:00
- remove outfmt sub-parameter from "format" video filter (no replacement)
- some behavior changes in the video filter chain, including:
- before, using an incompatible filter with hwdec would disable hwdec;
now it disables the filter at runtime instead
- inserting an incompatible filter with hwdec at runtime would refuse
to insert the filter; now it will add it successfully, but disables
the filter slightly later
audio: rewrite filtering glue code Use the new filtering code for audio too.
2018-01-18 13:44:20 +00:00
- some behavior changes in the audio filter chain, including:
- a manually inserted lavrresample filter is not necessarily used for
sample format conversion anymore, so it's pretty useless
- changing playback speed will not respect --af-defaults anymore
- having libavfilter based filters after the scaletempo or rubberband
filters is not supported anymore, and may desync if playback speed is
changed (libavfilter does not support the metadata for playback speed)
- the lavcac3enc filter does not auto detach itself anymore; instead it
passes through the data after converting it to the sample rate and
channel configuration the ac3 encoder expects; also, if the audio
format changes midstream in a way that causes the filter to switch
between PCM and AC3 output, the audio output won't be reconfigured,
and audio playback will fail due to libswresample being unable to
convert between PCM and AC3 (Note: the responsible developer didn't
DOCS/interface-changes.rst: adjust some audio filter change notes The first change is about spdif - I mostly ignore spdif issues these days, but it seems like the recent changes made handling of it slightly better (but I didn't really test). The second change is about broken libavfilter filters. We won't restore the old behavior, because people were complaining about the old behavior in the past. Possibly we could make libavfilter export this was metadata and use the old behavior if we know they're broken - but it doesn't exist yet.
2018-04-12 16:55:36 +00:00
give a shit. Later changes might have improved or worsened this.)
- inserting a filter that changes the output sample format will not
audio: rewrite filtering glue code Use the new filtering code for audio too.
2018-01-18 13:44:20 +00:00
reconfigure the AO - you need to run an additional "ao-reload"
command to force this if you want that
DOCS/interface-changes.rst: fix typo
2018-02-12 16:31:07 +00:00
- using "strong" gapless audio (--gapless-audio=yes) can fail if the
audio: rewrite filtering glue code Use the new filtering code for audio too.
2018-01-18 13:44:20 +00:00
audio formats are not convertible (such as switching between PCM and
AC3 passthrough)
DOCS/interface-changes: add note about desyncing audio filters For example af_loudnorm is a known filter with this behavior.
2018-03-01 20:09:33 +00:00
- if filters do not pass through PTS values correctly, A/V sync can
DOCS/interface-changes.rst: adjust some audio filter change notes The first change is about spdif - I mostly ignore spdif issues these days, but it seems like the recent changes made handling of it slightly better (but I didn't really test). The second change is about broken libavfilter filters. We won't restore the old behavior, because people were complaining about the old behavior in the past. Possibly we could make libavfilter export this was metadata and use the old behavior if we know they're broken - but it doesn't exist yet.
2018-04-12 16:55:36 +00:00
result over time. Some libavfilter filters are known to be affected by
this, such as af_loudnorm, which can desync over time, depending on
f_lavfi: add an option to use old audio PTS handling for af_lavfi The fix-pts option basically uses the old af_lavfi's (before filter rewrite) timestamp logic. The rest is explained in the manpage.
2018-04-12 20:08:56 +00:00
how the audio track was muxed (af_lavfi's fix-pts suboption can help).
audio: rewrite filtering glue code Use the new filtering code for audio too.
2018-01-18 13:44:20 +00:00
- remove out-format sub-parameter from "format" audio filter (no replacement)
player: replace old lavfi wrapper with new filter code lavfi.c is not necessary anymore, because f_lavfi.c (which was actually converted from it) can be used now.
2018-01-26 03:36:47 +00:00
- --lavfi-complex now requires uniquely named filter pads. In addition,
unconnected filter pads are not allowed anymore (that means every filter
pad must be connected either to another filter, or to a video/audio track
or video/audio output). If they are disconnected at runtime, the stream
will probably stall.
client API: deprecate opengl-cb API and introduce a replacement API The purpose of the new API is to make it useable with other APIs than OpenGL, especially D3D11 and vulkan. In theory it's now possible to support other vo_gpu backends, as well as backends that don't use the vo_gpu code at all. This also aims to get rid of the dumb mpv_get_sub_api() function. The life cycle of the new mpv_render_context is a bit different from mpv_opengl_cb_context, and you explicitly create/destroy the new context, instead of calling init/uninit on an object returned by mpv_get_sub_api(). In other to make the render API generic, it's annoyingly EGL style, and requires you to pass in API-specific objects to generic functions. This is to avoid explicit objects like the internal ra API has, because that sounds more complicated and annoying for an API that's supposed to never change. The opengl_cb API will continue to exist for a bit longer, but internally there are already a few tradeoffs, like reduced thread-safety. Mostly untested. Seems to work fine with mpc-qt.
2018-02-20 12:30:18 +00:00
- rename --vo=opengl-cb to --vo=libmpv (goes in hand with the opengl-cb
API deprecation, see client-api-changes.rst)
cocoa: change deprecation warning from opengl-cb to libmpv
2018-04-18 14:04:27 +00:00
- deprecate the OpenGL cocoa backend, option choice --gpu-context=cocoa
when used with --gpu-api=opengl (use --vo=libmpv)
video: make --deinterlace and HW deinterlace filters always deinterlace Before this, we made deinterlacing dependent on the video codec metadata (AVFrame.interlaced_frame for libavcodec). So even if --deinterlace=yes was set, we skipped deinterlacing if the flag wasn't set. This is very unreliable and there are many streams with flags incorrectly set. The potential problem is that this might upset people who alwase enabled deinterlace and hoped it worked. But it's likely these people were screwed by this setting anyway. The new behavior is less tricky and easier to understand, and this preferable. Maybe one day we could introduce a --deinterlace=auto, which does the right thing, but of course this would be hard to implement (esecially with hwdec). Fixes #5219.
2018-02-12 17:23:22 +00:00
- make --deinterlace=yes always deinterlace, instead of trying to check
certain unreliable video metadata. Also flip the defaults of all builtin
HW deinterlace filters to always deinterlace.
vf_vavpp: select best quality deinterlacing algorithm by default This switches the default away from "bob" to the best algorithm reported as supported by the driver. This is convenient for users, and there is no reason to use something worse by default. Untested.
2018-02-12 17:44:46 +00:00
- change vf_vavpp default to use the best deinterlace algorithm by default
command: remove an old compatibility hack Was removed 3 releases ago and was spamming warning messages that it'll be dropped, so it's fine to remove it now.
2018-03-23 14:33:51 +00:00
- remove a compatibility hack that allowed CLI aliases to be set as property
(such as "sub-file"), deprecated in mpv 0.26.0
client API: add a first class hook API, and deprecate old API As it turns out, there are multiple libmpv users who saw a need to use the hook API. The API is kind of shitty and was never meant to be actually public (it was mostly a hack for the ytdl script). Introduce a proper API and deprecate the old one. The old one will probably continue to work for a few releases, but will be removed eventually. There are some slight changes to the old API, but if a user followed the manual properly, it won't break. Mostly untested. Appears to work with ytdl_hook.
2018-03-23 15:24:49 +00:00
- deprecate the old command based hook API, and introduce a proper C API
(the high level Lua API for this does not change)
config: replace config dir lua-settings/ with dir script-opts/ lua-settings/ is still supported, with deprecation warning.
2017-12-13 17:37:42 +00:00
- rename the the lua-settings/ config directory to script-opts/
scripting: change when/how player waits for scripts being loaded Fundamentally, scripts are loaded asynchronously, but as a feature, there was code to wait until a script is loaded (for a certain arbitrary definition of "loaded"). This was done in scripting.c with the wait_loaded() function. This called mp_idle(), and since there are commands to load/unload scripts, it meant the player core loop could be entered recursively. I think this is a major complication and has some problems. For example, if you had a script that does 'os.execute("sleep inf")', then every time you ran a command to load an instance of the script would add a new stack frame of mp_idle(). This would lead to some sort of reentrancy horror that is hard to debug. Also misc/dispatch.c contains a somewhat tricky mess to support such recursive invocations. There were also some bugs due to this and due to unforeseen interactions with other messes. This scripting stuff was the only thing making use of that reentrancy, and future commands that have "logical" waiting for something should be implemented differently. So get rid of it. Change the code to wait only in the player initialization phase: the only place where it really has to wait is before playback is started, because scripts might want to set options or hooks that interact with playback initialization. Unloading of builtin scripts (can happen with e.g. "set osc no") is left asynchronous; the unloading wasn't too robust anyway, and this change won't make a difference if someone is trying to break it intentionally. Note that this is not in mp_initialize(), because mpv_initialize() uses this by locking the core, which would have the same problem. In the future, commands which logically wait should use different mechanisms. Originally I thought the current approach (that is removed with this commit) should be used, but it's too much of a mess and can't even be used in some cases. Examples are: - "loadfile" should be made blocking (needs to run the normal player code and manually unblock the thread issuing the command) - "add-sub" should not freeze the player until the URL is opened (needs to run opening on a separate thread) Possibly the current scripting behavior could be restored once new mechanisms exist, and if it turns out that anyone needs it. With this commit there should be no further instances of recursive playloop invocations (other than the case in the following commit), since all mp_idle()/mp_wait_events() calls are done strictly from the main thread (and not commands/properties or libmpv client API that "lock" the main thread).
2018-04-15 08:14:00 +00:00
- the way the player waits for scripts getting loaded changes slightly. Now
scripts are loaded in parallel, and block the player from continuing
playback only in the player initialization phase. It could change again in
the future. (This kind of waiting was always a feature to prevent that
playback is started while scripts are only half-loaded.)
encoding: deprecate a bunch of obscure options --audio-delay does not work correctly yet, but hopefully this can be fixed later.
2018-04-19 17:34:52 +00:00
- deprecate --ovoffset, --oaoffset, --ovfirst, --oafirst
encode: remove old timestamp handling This effectively makes --ocopyts the default. The --ocopyts option itself is also removed, because it's redundant.
2018-04-29 00:55:27 +00:00
- remove the following encoding options: --ocopyts (now the default, old
timestamp handling is gone), --oneverdrop (now default), --oharddup (you
need to use --vf=fps=VALUE), --ofps, --oautofps, --omaxfps
options: remove broken --video-stereo-mode option See changelog for minor explanation. Basically, 3D is unused crap and nobody cares.
2018-04-21 11:33:47 +00:00
- remove --video-stereo-mode. This option was broken out of laziness, and
nobody wants to fix it. Automatic 3D down-conversion to 2D is also broken,
although you can just insert the stereo3d filter manually. The obscurity
of 3D content doesn't justify such an option anyway.
command: change cycle-value command behavior Instead of using an internal counter to keep track of the value that was set last, attempt to find the current value of the property/option in the value list, and then set the next value in the list. There are some potential problems. If a property refuses to accept a specific value, the cycle-values command will fail, and start from the same position again. It can't know that it's supposed to skip the next value. The same can happen to properties which behave "strangely", such as the "aspect" property, which will return the current aspect if you write "-1" to it. As a consequence, cycle-values can appear to get "stuck". I still think the new behavior is what users expect more, and which is generally more useful. We won't restore the ability to get the old behavior, unless we decide to revert this commit entirely. Fixes #5772, and hopefully other complaints.
2018-04-28 16:14:43 +00:00
- change cycle-values command to use the current value, instead of an
internal counter that remembered the current position.
player: remove deprecated vo/ao auto profiles These were deprecated almost 2 years ago. Now they happen to be in the way.
2018-05-21 12:58:40 +00:00
- remove deprecated ao/vo auto profiles. Consider using scripts like
auto-profiles.lua instead.
vo_gpu, options: don't return NaN through API Internally, vo_gpu uses NaN for some options to indicate a default value that is different depending on the context (e.g. different scalers). There are 2 problems with this: 1. you couldn't reset the options to their defaults 2. NaN is a damn mess and shouldn't be part of the API The option parser already rejected NaN explicitly, which is why 1. didn't work. Regarding 2., JSON might be a good example, and actually caused a bug report. Fix this by mapping NaN to the special value "default". I think I'd prefer other mechanisms (maybe just having every scaler expose separate options?), but for now this will do. See you in a future commit, which painfully deprecates this and replaces it with something else. I refrained from using "no" (my favorite magic value for "unset" etc.) because then I'd have e.g. make --no-scale-param1 work, which in addition to a lot of effort looks dumb and nobody will use it. Here's also an apology for the shitty added test script. Fixes: #6691
2019-10-24 22:25:05 +00:00
- --[c]scale-[w]param[1|2] and --tone-mapping-param now accept "default",
and if set to that value, reading them as property will also return
"default", instead of float nan as in previous versions
options: remove --heartbeat-cmd and --heartbeat--interval This mechanism uses system() and shouldn't even exist. x11_common.c has its own solution for the original problem (disabling Linux DE screensavers without MPlayer/mpv having to link a dbus lib). If that is not sufficient, you can create a simple Lua script. Incidentally fixes #4888.
2017-09-18 20:54:03 +00:00
--- mpv 0.28.0 ---
hwdec: rename mediacodec to mediacodec-copy
2017-07-06 17:40:40 +00:00
- rename --hwdec=mediacodec option to mediacodec-copy, to reflect
conventions followed by other hardware video decoding APIs
options: remove --heartbeat-cmd and --heartbeat--interval This mechanism uses system() and shouldn't even exist. x11_common.c has its own solution for the original problem (disabling Linux DE screensavers without MPlayer/mpv having to link a dbus lib). If that is not sufficient, you can create a simple Lua script. Incidentally fixes #4888.
2017-09-18 20:54:03 +00:00
- drop previously deprecated --heartbeat-cmd and --heartbeat--interval
options
vo_opengl: refactor into vo_gpu This is done in several steps: 1. refactor MPGLContext -> struct ra_ctx 2. move GL-specific stuff in vo_opengl into opengl/context.c 3. generalize context creation to support other APIs, and add --gpu-api 4. rename all of the --opengl- options that are no longer opengl-specific 5. move all of the stuff from opengl/* that isn't GL-specific into gpu/ (note: opengl/gl_utils.h became opengl/utils.h) 6. rename vo_opengl to vo_gpu 7. to handle window screenshots, the short-term approach was to just add it to ra_swchain_fns. Long term (and for vulkan) this has to be moved to ra itself (and vo_gpu altered to compensate), but this was a stop-gap measure to prevent this commit from getting too big 8. move ra->fns->flush to ra_gl_ctx instead 9. some other minor changes that I've probably already forgotten Note: This is one half of a major refactor, the other half of which is provided by rossy's following commit. This commit enables support for all linux platforms, while his version enables support for all non-linux platforms. Note 2: vo_opengl_cb.c also re-uses ra_gl_ctx so it benefits from the --opengl- options like --opengl-early-flush, --opengl-finish etc. Should be a strict superset of the old functionality. Disclaimer: Since I have no way of compiling mpv on all platforms, some of these ports were done blindly. Specifically, the blind ports included context_mali_fbdev.c and context_rpi.c. Since they're both based on egl_helpers, the port should have gone smoothly without any major changes required. But if somebody complains about a compile error on those platforms (assuming anybody actually uses them), you know where to complain.
2017-09-14 06:04:55 +00:00
- rename --vo=opengl to --vo=gpu
- rename --opengl-backend to --gpu-context
- rename --opengl-shaders to --glsl-shaders
- rename --opengl-shader-cache-dir to --gpu-shader-cache-dir
- rename --opengl-tex-pad-x/y to --gpu-tex-pad-x/y
- rename --opengl-fbo-format to --fbo-format
- rename --opengl-gamma to --gamma-factor
- rename --opengl-debug to --gpu-debug
- rename --opengl-sw to --gpu-sw
- rename --opengl-vsync-fences to --swapchain-depth, and the interpretation
slightly changed. Now defaults to 3.
- rename the built-in profile `opengl-hq` to `gpu-hq`
- the semantics of --opengl-es=yes are slightly changed -> now requires GLES
- remove the (deprecated) alias --gpu-context=drm-egl
- remove the (deprecated) --vo=opengl-hq
- remove --opengl-es=force2 (use --opengl-es=yes --opengl-restrict=300)
DOCS/interface-changes.rst: mention --log-file behavior change See previous commit.
2017-10-05 09:23:33 +00:00
- the --msg-level option now affects --log-file
command: drop "audio-out-detected-device" property Coreaudio stopped setting it a few releases ago (66a958bb4fa). There is not much of a user- or API-visible change, so remove it without deprecation.
2017-10-09 13:48:47 +00:00
- drop "audio-out-detected-device" property - this was unavailable on all
audio output drivers for quite a while (coreaudio used to provide it)
video: make it possible to always override hardware decoding format Mostly an obscure option for testing. But --videotoolbox-format can be deprecated, as it becomes redundant. We rely on the libavutil hwcontext implementation to reject invalid pixfmts, or not to blow up if they are incompatible.
2017-10-16 12:37:28 +00:00
- deprecate --videotoolbox-format (use --hwdec-image-format, which affects
most other hwaccels)
demux: add a back buffer and the ability to seek into it This improves upon the previous commit, and partially rewrites it (and other code). It does: - disable the seeking within cache by default, and add an option to control it - mess with the buffer estimation reporting code, which will most likely lead to funny regressions even if the new features are not enabled - add a back buffer to the packet cache - enhance the seek code so you can seek into the back buffer - unnecessarily change a bunch of other stuff for no reason - fuck up everything and vomit ponies and rainbows This should actually be pretty usable. One thing we should add are some properties to report the proper buffer state. Then the OSC could show a nice buffer range. Also configuration of the buffers could be made simpler. Once this has been tested enough, it can be enabled by default, and might replace the stream cache's byte ringbuffer. In addition it may or may not be possible to keep other buffer ranges when seeking outside of the current range, but that would be much more complex.
2017-10-21 17:26:33 +00:00
- remove deprecated --demuxer-max-packets
DOCS/interface-changes.rst: fix typo
2017-11-30 06:19:30 +00:00
- remove most of the deprecated audio and video filters
DOCS/interface-changes.rst: update according to recent commits
2017-11-29 20:34:08 +00:00
- remove the deprecated --balance option/property
vo_gpu: make it possible to load multiple hwdec interop drivers Make the VO<->decoder interface capable of supporting multiple hwdec APIs at once. The main gain is that this simplifies autoprobing a lot. Before this change, it could happen that the VO loaded the "wrong" hwdec API, and the decoder was stuck with the choice (breaking hw decoding). With the change applied, the VO simply loads all available APIs, so autoprobing trickery is left entirely to the decoder. In the past, we were quite careful about not accidentally loading the wrong interop drivers. This was in part to make sure autoprobing works, but also because libva had this obnoxious bug of dumping garbage to stderr when using the API. libva was fixed, so this is not a problem anymore. The --opengl-hwdec-interop option is changed in various ways (again...), and renamed to --gpu-hwdec-interop. It does not have much use anymore, other than debugging. It's notable that the order in the hwdec interop array ra_hwdec_drivers[] still matters if multiple drivers support the same image formats, so the option can explicitly force one, if that should ever be necessary, or more likely, for debugging. One example are the ra_hwdec_d3d11egl and ra_hwdec_d3d11eglrgb drivers, which both support d3d11 input. vo_gpu now always loads the interop lazily by default, but when it does, it loads them all. vo_opengl_cb now always loads them when the GL context handle is initialized. I don't expect that this causes any problems. It's now possible to do things like changing between vdpau and nvdec decoding at runtime. This is also preparation for cleaning up vd_lavc.c hwdec autoprobing. It's another reason why hwdec_devices_request_all() does not take a hwdec type anymore.
2017-12-01 04:05:00 +00:00
- rename the --opengl-hwdec-interop option to --gpu-hwdec-interop, and
change some of its semantics: extend it take the strings "auto" and
"all". "all" loads all backends. "auto" behaves like "all" for
vo_opengl_cb, while on vo_gpu it loads nothing, but allows on demand
loading by the decoder. The empty string as option value behaves like
"auto". Old --hwdec values do not work anymore.
This option is hereby declared as unstable and may change any time - its
old use is deprecated, and it has very little use outside of debugging
now.
vd_lavc: rewrite how --hwdec is handled Change it from explicit metadata about every hwaccel method to trying to get it from libavcodec. As shown by add_all_hwdec_methods(), this is a quite bumpy road, and a bit worse than expected. This will probably cause a bunch of regressions. In particular I didn't check all the strange decoder wrappers, which all cause some sort of special cases each. You're volunteering for beta testing by using this commit. One interesting thing is that we completely get rid of mp_hwdec_ctx in vd_lavc.c, and that HWDEC_* mostly goes away (some filters still use it, and the VO hwdec interops still have a lot of code to set it up, so it's not going away completely for now).
2017-12-01 20:05:54 +00:00
- change the --hwdec option from a choice to a plain string (affects
introspection of the option/property), also affects some properties
DOCS/interface-changes.rst: fix minor typos
2017-12-26 02:11:35 +00:00
- rename --hwdec=rpi to --hwdec=mmal, same for the -copy variant (no
vd_lavc: rename --hwdec=rpi to --hwdec=mmal Annoying exception that makes no sense to keep. Normally, users or client applications will either use --hwdec=auto, or not set the option at all, which both leads to the expected result.
2017-12-14 18:31:09 +00:00
backwards compatibility)
DOCS/interface-changes.rst: fix minor typos
2017-12-26 02:11:35 +00:00
- deprecate the --ff-aid, --ff-vid, --ff-sid options and properties (there is
options: deprecate --ff- options and properties Some old crap which nobody needs and which probably nobody uses. This relies on a GCC extension: using "## __VA_ARGS__" to remove the comma from the argument list if the va args are empty. It's supported by clang, and there's some chance newer standards will introduce a proper way to do this. (Even if it breaks somewhere, it will be a problem only for 1 release, since I want to drop the deprecated properties immediately.)
2017-12-20 04:50:42 +00:00
no replacement, but you can manually query the track property and use the
"ff-index" field to find the mpv track ID to imitate this behavior)
encode: rename option --ometadata to --ocopy-metadata --copy-metadata describes the result of the option better, (copying metadata from the source file to the output file). Marks the old --no-ometadata OPT_REMOVED with a suggestion for the new --no-ocopy-metadata.
2017-12-16 12:14:26 +00:00
- rename --no-ometadata to --no-ocopy-metadata
options: kill --field-dominance GPL-only author, no chance of relicensing.
2017-07-21 18:00:09 +00:00
--- mpv 0.27.0 ---
- drop previously deprecated --field-dominance option
input: drop deprecated "osd" command Complicated situation due to changes by GPL-only author, but also unnecessary due to newer mechanisms.
2017-07-21 18:02:58 +00:00
- drop previously deprecated "osd" command
client API: drop some compatibility handling See commit e4bc563fd2dcf for more information.
2017-07-21 18:09:22 +00:00
- remove client API compatibility handling for "script", "sub-file",
"audio-file", "external-file" (these cases used to log a deprecation
warning)
options: drop --video-aspect-method=hybrid Remove this code because it could be argued that it contains GPL-only code (see commit 642e963c860 for details). The remaining aspect methods appear to work just as well, are potentially more compatible to other players, and the code becomes much simpler.
2017-07-21 18:19:39 +00:00
- drop deprecated --video-aspect-method=hybrid option choice
vo_opengl: generalize HDR tone mapping to gamut mapping Since this code was already written for HDR, and is now per-channel (because it works better for HDR as well), we can actually reuse this to get very high quality gamut mapping without clipping. The only required change is to move the tone mapping from before the gamut map to after the gamut map. Additonally, we need to also account for changes in the signal range as a result of applying the CMS when we compute ref_peak, which is fortunately pretty easy because we only need to consider the case of primaries mapping to themselves. Since `HDR` no longer really makes sense as a label, rename it to `--tone-mapping` in general. Also fits better with `--tone-mapping-desat` etc. Arguably we could also rename `--hdr-compute-peak`, but that option is basically only useful for HDR content anyway because we don't need information about the signal range for gamut mapping. This (finally!) gives us reasonably high quality gamut mapping even in the absence of an ICC profile / 3DLUT.
2017-08-03 10:46:57 +00:00
- rename --hdr-tone-mapping to --tone-mapping (and generalize it)
vo_opengl: make fbotex helper use ra Further work removing GL dependencies from the actual video renderer, and moving them into ra backends. Use of glInvalidateFramebuffer() falls away. I'd like to keep this, but it's better to readd it once shader runs are in ra.
2017-08-04 11:48:37 +00:00
- --opengl-fbo-format changes from a choice to a string. Also, its value
will be checked only on renderer initialization, rather than when the
option is set.
vo_opengl: further GL API use separation Move multiple GL-specific things from the renderer to other places like vo_opengl.c, vo_opengl_cb.c, and ra_gl.c. The vp_w/vp_h parameters to gl_video_resize() make no sense anymore, and are implicitly part of struct fbodst. Checking the main framebuffer depth is moved to vo_opengl.c. For vo_opengl_cb.c it always assumes 8. The API user now has to override this manually. The previous heuristic didn't make much sense anyway. The only remaining dependency on GL is the hwdec stuff, which is harder to change.
2017-08-07 17:14:18 +00:00
- Using opengl-cb now always assumes 8 bit per component depth, and dithers
to this size. Before, it tried to figure out the depth of the first
framebuffer that was ever passed to the renderer. Having GL framebuffers
with a size larger than 8 bit per component is quite rare. If you need
it, set the --dither-depth option instead.
player: make --lavfi-complex changeable at runtime Tends to be somewhat glitchy if subtitles are enabled, and you enable and disable tracks. On error, this will disable --lavfi-complex, which will result in whatever behavior.
2017-08-12 21:08:48 +00:00
- --lavfi-complex can now be set during runtime. If you set this in
expectation it would be applied only after a reload, you might observe
weird behavior.
player: add --track-auto-selection option I imagine this is useful. Or maybe it isn't.
2017-08-12 21:43:05 +00:00
- add --track-auto-selection to help with scripts/applications that
make exclusive use of --lavfi-complex.
options: change --loop semantics As announced by the previous deprecation.
2017-08-14 18:01:08 +00:00
- undeprecate --loop, and map it from --loop-playlist to --loop-file (the
deprecation was to make sure no API user gets broken by a sudden behavior
change)
vf_eq: remove this filter Both the video equalizer command/option glue, which drives this filter, as well as the filter itself are slightly GPL contaminated. So it goes. After this commit, "--vf=eq" will actually use libavfilter's vf_eq (if FFmpeg was compiled in GPL mode), but it has different options and will not listen to the equalizer VOCTRLs.
2017-08-22 13:58:49 +00:00
- remove previously deprecated vf_eq
video: change --deinterlace behavior This removes all GPL only code from it, and that's the whole purpose. Also happens to be much simpler. The "deinterlace" option still sort of exists, but only as runtime changeable option. The main change in behavior is that the property will not report back the actual deint state. Or in other words, if inserting or initializing the filter fails, the deinterlace property will still return "yes". This is in line with most recent behavior changes to properties and options.
2017-08-22 17:08:07 +00:00
- remove that hardware deinterlace filters (vavpp, d3d11vpp, vdpaupp)
changed their deinterlacing-enabled setting depending on what the
--deinterlace option or property was set to. Now, a filter always does
what its filter options and defaults imply. The --deinterlace option and
property strictly add/remove its own filters. For example, if you run
"mpv --vf=vavpp --deinterlace=yes", this will insert another, redundant
filter, which is probably not what you want. For toggling a deinterlace
filter manually, use the "vf toggle" command, and do not set the
deinterlace option/property. To customize the filter that will be
DOCS/interface-changes.rst: don't suggest @deinterlace label --vf-defaults always applies, and the label is ignored. So don't suggest using it, it would be misleading.
2017-08-23 10:10:51 +00:00
inserted automatically, use --vf-defaults. Details how this works will
probably change in the future.
video: change --deinterlace behavior This removes all GPL only code from it, and that's the whole purpose. Also happens to be much simpler. The "deinterlace" option still sort of exists, but only as runtime changeable option. The main change in behavior is that the property will not report back the actual deint state. Or in other words, if inserting or initializing the filter fails, the deinterlace property will still return "yes". This is in line with most recent behavior changes to properties and options.
2017-08-22 17:08:07 +00:00
- remove deinterlace=auto (this was not deprecated, but had only a very
obscure use that stopped working with the change above. It was also
prone to be confused with a feature not implemented by it: auto did _not_
mean that deinterlacing was enabled on demand.)
input: use mnemonic names for mouse buttons mpv's mouse button numbering is based on X11 button numbering, which allows for an arbitrary number of buttons and includes mouse wheel input as buttons 3-6. This button numbering was used throughout the codebase and exposed in input.conf, and it was difficult to remember which physical button each number actually referred to and which referred to the scroll wheel. In practice, PC mice only have between two and five buttons and one or two scroll wheel axes, which are more or less in the same location and have more or less the same function. This allows us to use names to refer to the buttons instead of numbers, which makes input.conf syntax a lot easier to remember. It also makes the syntax robust to changes in mpv's underlying numbering. The old MOUSE_BTNx names are still understood as deprecated aliases of the named buttons. This changes both the input.conf syntax and the MP_MOUSE_BTNx symbols in the codebase, since I think both would benefit from using names over numbers, especially since some platforms don't use X11 button numbering and handle different mouse buttons in different windowing system events. This also makes the names shorter, since otherwise they would be pretty long, and it removes the high-numbered MOUSE_BTNx_DBL names, since they weren't used. Names are the same as used in Qt: https://doc.qt.io/qt-5/qt.html#MouseButton-enum
2017-08-08 11:34:38 +00:00
- add shortened mnemonic names for mouse button bindings, eg. mbtn_left
the old numeric names (mouse_btn0) are deprecated
- remove mouse_btn3_dbl and up, since they are only generated for buttons
0-2 (these now print an error when sent from the 'mouse' command)
input: merge mouse wheel and axis keycodes Mouse wheel bindings have always been a cause of user confusion. Previously, on Wayland and macOS, precise touchpads would generate AXIS keycodes and notched mouse wheels would generate mouse button keycodes. On Windows, both types of device would generate AXIS keycodes and on X11, both types of device would generate mouse button keycodes. This made it pretty difficult for users to modify their mouse-wheel bindings, since it differed between platforms and in some cases, between devices. To make it more confusing, the keycodes used on Windows were changed in 18a45a42d524 without a deprecation period or adequate communication to users. This change aims to make mouse wheel binds less confusing. Both the mouse button and AXIS keycodes are now deprecated aliases of the new WHEEL keycodes. This will technically break input configs on Wayland and macOS that assign different commands to precise and non-precise scroll events, but this is probably uncommon (if anyone does it at all) and I think it's a fair tradeoff for finally fixing mouse wheel-related confusion on other platforms.
2017-09-02 14:00:52 +00:00
- rename the axis bindings to wheel_up/down/etc. axis scrolling and mouse
wheel scrolling are now conceptually the same thing
the old axis_up/down names remain as deprecated aliases
options: remove remaining deprecated audio device selection options
2017-04-23 15:51:55 +00:00
--- mpv 0.26.0 ---
DOCS/interface-changes.rst: fix typo Pointed out by someone.
2017-04-26 15:00:38 +00:00
- remove remaining deprecated audio device options, like --alsa-device
options: remove remaining deprecated audio device selection options
2017-04-23 15:51:55 +00:00
Some of them were removed in earlier releases.
audio: move replaygain control to top-level options af_volume is deprecated, and so are its replaygain sub-options. To make it possible to use replaygain without deprecated options (and of course to make it available at all after af_volume is dropped), reintroduce them as top-level options. This also means that they are easily changeable at runtime by using them as properties. Change the "volume" property to use the new update mechanism as well. We don't actually bother sharing the implementation between new and deprecated mechanisms, as the deprecated one will simply be deleted. For the from_dB() functions, we mention anders' copyright, although I'm not sure if a mere formula is copyrightable. This will have to be determined later. This whole change is mostly untested. Our distributed human CI will take care of it.
2017-04-26 19:45:50 +00:00
- introduce --replaygain... options, which replace the same functionality
provided by the deprecated --af=volume:replaygain... mechanism.
demux_raw: drop "mp-rawvideo" use This is an old pseudo codec to pass through the pixel format. Setup a suitable AVCodecParameter directly instead, so the "rawvideo" codec can be used.
2017-05-20 09:10:55 +00:00
- drop the internal "mp-rawvideo" codec (used by --demuxer=rawvideo)
options: slight cleanup of --sub-ass-style-override List of changes: 1. Rename `signfs` to `scale`, to better match what it actually does (force --sub-scale to apply to ASS subtitles), and fix the blatantly wrong documentation (it actually specifically does *not* apply to signs) 2. Rename `--sub-ass-style-override` to `--sub-ass-override` to help reduce confusion between it and `--sub-ass-force-style`, as well as pointing out that it doesn't necessarily actually override styles. (The new `scale` option, for example, only sets ASS_OVERRIDE_BIT_FONT_SIZE, but not ASS_OVERRIDE_BIT_STYLE) 3. Mention that `--sub-ass-override` is generally sort of smart about only overriding dialog, not signs.
2017-06-06 20:16:29 +00:00
- rename --sub-ass-style-override to --sub-ass-override, and rename the
`--sub-ass-override=signfs` setting to `--sub-ass-override=scale`.
dec_video: change license to LGPL (almost) "Almost" because this might contain copyright by michael, who agreed with LGPL, but only once the core is LGPL. This is preparation for that to happen. Apart from that, the usual remarks apply. In particular, dec_video.c started out quite chaotic with no modularization, but was later basically gutted, and in general rewritten a bunch of times. Not going to give a history lesson. Special attention needs to be given to 3 patches by cehosos, who did not agree to the relicensing: 240b743ebdf: --field-dominance e32cbbf7dc3: reinit VO if aspect ratio changes 306f6243fdf: use container aspect if codec aspect unset (?) The first patch is pretty clearly still in the current code, and needs to be disabled for LGPL. The functionality of the second patch is still active, but implemented completely different, and as part of general frame parameter changes (at the time of the patch, MPlayer already reinitialized the VO on frame size and pixel format changes - all this was merged into a single check for changing image parameters). The third patch makes me a bit more uncomfortable. It appears the code was moved to dec_video.c in de68b8f23c8c, and further changed in 82f0d373, 0a0bb905, and bf13bd0d. You could claim that cehoyos' copyright still sticks. Fortunately, we implement alternative aspect detection, which is simpler and probably preferable, and which arguably contains none of the original code and logic, and thus should be fully safe. While I don't know if cehoyos' copyright actually still applies, I'm more comfortable with making the code GPL-only for now. Also change the default to use the (in future) plain LGPL code, and deprecate the one associated with the GPL code, so we can eventually remove the GPL code. But it's also possible we decide that the copyright doesn't apply, and undo the deprecation and GPL guards. I expect that users won't notice anything. If you ask me, the old aspect method was probably an accidental bug instead of intentional behavior. Although, the new aspect method was broken too, so I had to fix it.
2017-06-18 16:27:48 +00:00
- change default of --video-aspect-method to "bitstream". The "hybrid"
method (old default) is deprecated.
video: refactor HDR implementation List of changes: 1. Kill nom_peak, since it's a pointless non-field that stores nothing of value and is _always_ derived from ref_white anyway. 2. Kill ref_white/--target-brightness, because the only case it really existed for (PQ) actually doesn't need to be this general: According to ITU-R BT.2100, PQ *always* assumes a reference monitor with a white point of 100 cd/m². 3. Improve documentation and comments surrounding this stuff. 4. Clean up some of the code in general. Move stuff where it belongs.
2017-06-10 12:01:25 +00:00
- remove property "video-params/nom-peak"
- remove option --target-brightness
- replace vf_format's `peak` suboption by `sig-peak`, which is relative to
the reference white level instead of in cd/m^2
csputils: rename HDR curves st2084 and std-b67 are really weird names for PQ and HLG, which is what everybody else (including e.g. the ITU-R) calls them. Follow their example. I decided against naming them bt2020-pq and bt2020-hlg because it's not necessary in this case. The standard name is only used for the other colorspaces etc. because those literally have no other names.
2017-06-13 15:09:02 +00:00
- renamed the TRCs `st2084` and `std-b67` to `pq` and `hlg` respectively
player: deprecate "osd" command It was extended by "seru" in 8d190244. This person could not be reached (or does not reply), and it's in the way of LGPL relicensing. Deprecate it, and mark the (probably) affected parts of the code with HAVE_GPL. To be fair, even though the osd.c parts were refactored from the original code, there's probably no copyright by seru on it. But for now play it save. The mere existence of a 3rd OSD level is certainly not copyrightable, so you still can set osd-level to 3 - just that it does nothing.
2017-06-23 12:27:53 +00:00
- the "osd" command is deprecated (use "cycle osd-level")
options: suggest a replacement for --field-dominance
2017-06-25 16:54:33 +00:00
- --field-dominance is deprecated (use --vf=setfield=bff or tff)
options: remove weird --really-quiet special behavior This was especially grating because it causes problems with the option/property unification, uses as only thing OPT_FLAG_STORE, and behaves weird with the client API or scripts. It can be reimplemented in a much simpler way, although it needs slightly more code. (Simpler because less special cases.)
2017-06-23 18:42:20 +00:00
- --really-quiet subtle behavior change
client API: drop old "no-" option emulation You could do mpv_set_option(h, "no-fs", ""), which would behave like "--no-fs" on the command line. At one point, this had to be emulated for compatibility, and printed a deprecation warning. This was almost a year ago, so remove it.
2017-06-26 17:55:40 +00:00
- the deprecated handling of setting "no-" options via client API is dropped
options: change path list options, and document list options The changes to path list options is basically getting rid of the need to pass multiple paths to a single option. Instead, you can use the option multiple times. The old behavior can be used by using the -set suffix with the option. Change some options to path lists. For example --script is now append by default, and if you use --script-set, you need to use ":"/";" as separator instead of ",". --sub-paths/--audio-file-paths is a deprecated alias now, and will break if the user tries to pass multiple paths to it. I'm assuming that if these are used, most users will pass only 1 path anyway. --opengl-shaders has more compatibility handling, since it's probably rather common that users pass multiple options to it. Also document all that in the manpage. I'll probably regret this later, as it somewhat increases the complexity of the option parser, rather than increasing it.
2017-06-30 14:39:36 +00:00
- the following options change to append-by-default (and possibly separator):
--script
also, the following options are deprecated:
options: change everything again Fucking bullshit.
2017-07-02 14:26:41 +00:00
--sub-paths => --sub-file-paths
the following options are deprecated for setting via API:
"script" (use "scripts")
"sub-file" (use "sub-files")
"audio-file" (use "audio-files")
"external-file" (use "external-files")
(the compatibility hacks for this will be removed after this release)
vo_opengl: refactor vo performance subsystem This replaces `vo-performance` by `vo-passes`, bringing with it a number of changes and improvements: 1. mpv users can now introspect the vo_opengl passes, which is something that has been requested multiple times. 2. performance data is now measured per-pass, which helps both development and debugging. 3. since adding more passes is cheap, we can now report information for more passes (e.g. the blit pass, and the osd pass). Note: we also switch to nanosecond scale, to be able to measure these passes better. 4. `--user-shaders` authors can now describe their own passes, helping users both identify which user shaders are active at any given time as well as helping shader authors identify performance issues. 5. the timing data per pass is now exported as a full list of samples, so projects like Argon-/mpv-stats can immediately read out all of the samples and render a graph without having to manually poll this option constantly. Due to gl_timer's design being complicated (directly reading performance data would block, so we delay the actual read-back until the next _start command), it's vital not to conflate different passes that might be doing different things from one frame to another. To accomplish this, the actual timers are stored as part of the gl_shader_cache's sc_entry, which makes them unique for that exact shader. Starting and stopping the time measurement is easy to unify with the gl_sc architecture, because the existing API already relies on a "generate, render, reset" flow, so we can just put timer_start and timer_stop in sc_generate and sc_reset, respectively. The ugliest thing about this code is that due to the need to keep pass information relatively stable in between frames, we need to distinguish between "new" and "redrawn" frames, which bloats the code somewhat and also feels hacky and vo_opengl-specific. (But then again, this entire thing is vo_opengl-specific)
2017-06-29 15:00:06 +00:00
- remove property `vo-performance`, and add `vo-passes` as a more general
replacement
m_option: deprecate multiple items for -add etc. This is more confusing than it helps, and forces escaping more stuff. For example, for string lists we could remove all need for escaling with -add and -pre. The user can simply use multiple of those options.
2017-07-02 14:46:27 +00:00
- deprecate passing multiple arguments to -add/-pre options (affects the
vf/af commands too)
demux_lavf: remove --demuxer-lavf-cryptokey option Was at least somewhat broken, and is misleading. I don't really have an idea why FFmpeg has two AVOptions here anyway. We don't need to care, and I'm only aware of 1 user trying this option ever. See #4579.
2017-07-06 15:58:26 +00:00
- remove --demuxer-lavf-cryptokey. Use --demux-lavf-o=cryptokey=<hex> or
--demux-lavf-o=decryption_key=<hex> instead (whatever fits your situation).
vo_opengl: rework --opengl-dumb-mode It's now possible to request non-dumb mode as a user, even when not using any non-dumb features. This change is mostly intended for testing, so I can easily switch between dumb and non-dumb mode on default settings. The default behavior is unaffected.
2017-07-07 12:46:46 +00:00
- rename --opengl-dumb-mode=no to --opengl-dumb-mode=auto, and make `no`
always disable it (unless forced on by hardware limitation).
vo_opengl: generalize --scale-clamp etc. This can help fight ringing without completely killing it, thus providing a middle-ground between ringing and aliasing.
2017-07-12 17:08:58 +00:00
- generalize --scale-clamp, --cscale-clamp etc. to accept a float between
0.0 and 1.0 instead of just being a flag. A value of 1.0 corresponds to
the old `yes`, and a value of 0.0 corresponds to the old `no`.
vo_opengl: remove dxva2 dummy hwdec backend This was a hack to let libmpv API users pass a d3d device to mpv. It's not needed anymore for 2 reasons: 1. ANGLE does not have this problem 2. Even native GL via nVidia (where this failed) seems to not require this anymore
2017-02-20 07:39:08 +00:00
--- mpv 0.25.0 ---
- remove opengl-cb dxva2 dummy hwdec interop
(see git "vo_opengl: remove dxva2 dummy hwdec backend")
image_writer: remove useless formats Nobody cares about those.
2017-03-18 13:24:53 +00:00
- remove ppm, pgm, pgmyuv, tga choices from the --screenshot-format and
--vo-image-format options
screenshot: change details of --screenshot-format handling This is just a pointless refactor with the only goal of making image_writer_opts.format a number. The pointless part of it is that instead of using some sort of arbitrary ID (in place of a file extension string), we use a AV_CODEC_ID_. There was also some idea of falling back to the libavcodec MJPEG encoder if mpv was not linked against libjpeg, but this fails. libavcodec insist on having AV_PIX_FMT_YUVJ420P, which we pretend does not exist, and which we always map to AV_PIX_FMT_YUV420P (without the J indicating full range), so encoder init fails. This is pretty dumb, but whatever. The not-caring factor is raised by the fact that we don't know that we should convert to full range, because encoders have no proper way to signal this. (Be reminded that AV_PIX_FMT_YUVJ420P is deprecated.)
2017-03-18 14:03:05 +00:00
- the "jpeg" choice in the option above now leads to a ".jpg" file extension
af_drc: remove Remove low quality drc filter. Anyone whishing to have dynamic range compression should use the much more powerful acompressor ffmpeg filter: mpv --af=lavfi=[acompressor] INPUT Or with parameters: mpv --af=lavfi=[acompressor=threshold=-25dB:ratio=3:makeup=8dB] INPUT Refer to https://ffmpeg.org/ffmpeg-filters.html#acompressor for a full list of supported parameters. Signed-off-by: wm4 <wm4@nowhere>
2017-03-17 15:49:28 +00:00
- --af=drc is gone (you can use e.g. lavfi/acompressor instead)
vo_opengl: replace uniform variable image_size with input_size input_size can be the size of a cropped image Signed-off-by: wm4 <wm4@nowhere>
2017-03-19 14:13:51 +00:00
- remove image_size predefined uniform from OpenGL user shaders. Use
input_size instead
sub: add SDH subtitle filter Add subtitle filter to remove additions for deaf or hard-of-hearing (SDH). This is for English, but may in part work for others too. This is an ASS filter and the intention is that it can always be enabled as it by default do not remove parts that may be normal text. Harder filtering can be enabled with an additional option. Signed-off-by: wm4 <wm4@nowhere>
2017-02-02 09:53:19 +00:00
- add --sub-filter-sdh
- add --sub-filter-sdh-harder
osx: fix key input in certain circumstances for a reason i can just assume some key events can vanish from the event chain and mpv seems unresponsive. after quite some testing i could confirm that the events are present at the first entry point of the event chain, the sendEvent method of the Application, and that they vanish at a point afterwards. now we use that entry point to grab keyDown and keyUp events. we also stop propagating those key events to prevent the no key input' error sound. if we ever need the key events somewhere down the event chain we need to start propagating them again. though this is not necessary currently.
2017-03-26 18:32:04 +00:00
- remove --input-app-events option (macOS)
DOCS/interface-changes.rst: document --vf/--af deprecations And also future directions. Basically, it tells the user that he can't hope for perfect forward-compatibility.
2017-04-04 15:16:54 +00:00
- deprecate most --vf and --af filters. Only some filters not in libavfilter
will be kept.
Also, you can use libavfilter filters directly (e.g. you can use
--vf=name=opts instead of --vf=lavfi=[name=opts]), as long as the
libavfilter filter's name doesn't clash with a mpv builtin filter.
In the long term, --vf/--af syntax might change again, but if it does, it
will switch to libavfilter's native syntax. (The above mentioned direct
support for lavfi filters still has some differences, such as how strings
are escaped.) If this happens, the non-deprecated builtin filters might be
moved to "somewhere else" syntax-wise.
options: deprecate --loop Also "announce" the plans to undeprecate it with changed semantics later. The deprecation period is needed to warn script authors and client API users (etc.) of the change. This is done because everyone seems to expect --loop to loop the current file, not the playlist. Even in cases when only 1 file is on the playlist, the --loop-file semantics seem to be preferred.
2017-04-10 19:19:13 +00:00
- deprecate --loop - after a deprecation period, it will be undeprecated,
but changed to alias --loop-file
player: add --keep-open-pause=no option Instead of pausing if --keep-open is active, stop at end but continue playing if seeking backwards. And then stop again when end is reached. Signed-off-by: wm4 <wm4@nowhere> Over the PR, the option was renamed, and the manpage additions were slightly changed/enhanced.
2017-03-27 09:34:02 +00:00
- add --keep-open-pause=no
demux: estimate total packet size, deprecate packet number limits It's all explained in the DOCS changes. Although this option was always kind of obscure and pointless. Until it is removed, the only reason for setting it would be to raise the static default limit, so change its default to INT_MAX so that it does nothing by default.
2017-04-14 17:19:44 +00:00
- deprecate --demuxer-max-packets
options: change --audio-file-auto default to not to load any files There have been user complaints, and I'm annoyed by this behavior myself.
2017-04-20 03:29:04 +00:00
- change --audio-file-auto default from "exact" to "no" (mpv won't load
files with the same filename as the video, but different extension, as
audio track anymore)
vo_opengl, vo_opengl_cb: better hwdec interop backend selection Introduce the --opengl-hwdec-interop option, which replaces --hwdec-preload. The new option allows explicit selection of the interop backend. This is relatively complex, and I would have preferred not to add this, but it's probably useful to debug certain problems. In exchange, the "new" option documents that pretty much any but the simplest use of it will not be forward compatible.
2017-01-17 13:51:08 +00:00
--- mpv 0.24.0 ---
- deprecate --hwdec-api and replace it with --opengl-hwdec-interop.
The new option accepts both --hwdec values, as well as named backends.
A minor difference is that --hwdec-api=no (which used to be the default)
now actually does not preload any interop layer, while the new default
("") uses the value of --hwdec.
options: drop deprecated --vd/--ad codecs selection features Only simple selection works now. Using "-" to terminate codec selection remains in the code (might get undeprecated).
2017-01-19 14:38:58 +00:00
- drop deprecated --ad/--vd features
options: drop deprecated --sub-codepage syntax
2017-01-19 14:44:49 +00:00
- drop deprecated --sub-codepage syntax
command: rename framedrop properties "drop-frame-count" -> "decoder-frame-drop-count" "vo-drop-frame-count" -> "frame-drop-count" This gets rid of the backwards "drop-frame" part in the name. Maybe calling the new property "frame-drops" would be better, but there are already a bunch of similar properties that end in "-count".
2017-01-20 16:01:29 +00:00
- rename properties:
- "drop-frame-count" to "decoder-frame-drop-count"
- "vo-drop-frame-count" to "frame-drop-count"
The old names still work, but are deprecated.
player: remove --stream-capture option/property This was excessively useless, and I want my time back that was needed to explain users why they don't want to use it. It captured the byte stream only, and even for types of streams it was designed for (like transport streams), it was rather questionable. As part of the removal, un-inline demux_run_on_thread() (which has only 1 call-site now), and sort of reimplement --stream-dump to write the data directly instead of using the removed capture code. (--stream-dump is also very useless, and I struggled coming up with an explanation for it in the manpage.)
2017-01-21 16:19:01 +00:00
- remove the --stream-capture option and property. No replacement.
manpage: fix incorrect option name for --record-file Also the one in interface-changes.rst. Fixes #4121.
2017-02-08 05:54:47 +00:00
(--record-file might serve as alternative)
sub: add justify of subtitles To make it easier for the eyes, multi line subtitles should be left justified (for most languages). This adds an option to define how subtitles are to be justified inpendently of how they are aligned. Also add option to enable --sub-justify to be applied on ASS subtitles.
2017-02-01 12:19:09 +00:00
- add --sub-justify
- add --sub-ass-justify
player: different way to auto-enable the demuxer cache Instead of enabling it only when a stream-cache is enabled, also try to enable it independently from that if the demuxer is marked as is_network. Also add some code to the EDL code, so EDLs containing network streams are automatically cached this way. Extend the OSD info line so that it shows the demuxer cache in this case (more or less). I didn't find where or whether options.rst describes how the demuxer cache is enabled, so no changes there.
2017-02-02 17:38:16 +00:00
- internally there's a different way to enable the demuxer cache now
it can be auto-enabled even if the stream cache remains disabled
vf_vdpaurb: remove this filter Was deprecated, superseded by --hwdec=vdpau-copy.
2016-11-22 13:57:34 +00:00
--- mpv 0.23.0 ---
- remove deprecated vf_vdpaurb (use "--hwdec=vdpau-copy" instead)
command: redefine some deprecated properties As threatened by the API changes document. We can actually keep the deprecated --playlist-pos and --cache options, since they are aliases and not used by the corresponding properties. They are inconsistent, but do no harm. Keep them for now for the sake of the command line user. mpv_identify.sh partially stopped working, because it was never updated. The shell magic can't deal with property names that contain "/", so we can't replace "samplerate" with "audio-params/samplerate" - just remove these properties. (How about you use ffprobe?)
2016-11-22 14:38:01 +00:00
- the following properties now have new semantics:
- "demuxer" (use "current-demuxer")
- "fps" (use "container-fps")
- "idle" (use "idle-active")
- "cache" (use "cache-percent")
- "audio-samplerate" (use "audio-params/samplerate")
- "audio-channels" (use "audio-params/channel-count")
- "audio-format" (use "audio-codec-name")
(the properties equivalent to the old semantics are in parentheses)
options: remove deprecated sub-option handling for --vo and --ao Long planned. Leads to some sanity. There still are some rather gross things. Especially g_groups is ugly, and a hack that can hopefully be removed. (There is a plan for it, but whether it's implemented depends on how much energy is left.)
2016-11-25 20:00:39 +00:00
- remove deprecated --vo and --ao sub-options (like --vo=opengl:...), and
replace them with global options. A somewhat complete list can be found
here: https://github.com/mpv-player/mpv/wiki/Option-replacement-list#mpv-0210
- remove --vo-defaults and --ao-defaults as well
options: remove legacy global sub-option syntax A bit of sanity, although a very small one. --vo sub-options are not affected by this yet.
2016-11-22 14:52:55 +00:00
- remove deprecated global sub-options (like -demuxer-rawaudio format=...),
use flat options (like --demuxer-rawaudio-format=...)
charset_conv: simplify and change --sub-codepage option As documented in interface-changes.rst. This makes it much easier to follow what the heck is going on. Whether this is adequate for real-world use is unknown.
2016-12-09 18:51:29 +00:00
- the --sub-codepage option changes in incompatible ways:
- detector-selection and fallback syntax is deprecated
- enca/libguess are removed and deprecated (behaves as if they hadn't
been compiled-in)
- --sub-codepage=<codepage> does not force the codepage anymore
(this requires different and new syntax)
cocoa: fullscreen refactoring this replaces the old fullscreen with the native macOS fullscreen. additional the --fs-black-out-screens was removed since the new API doesn't support it in a way the old one did. it can possibly be re-added if done manually. Fixes #2857 #3272 #1352 #2062 #3864
2016-12-04 21:52:14 +00:00
- remove --fs-black-out-screens option for macOS
audio: change how spdif codecs are selected Remove ad_spdif from the normal codec list, and select it explicitly. One goal was to decouple this from the normal codec selection, so they're less entangled and the decoder selection code can be simplified in the far future. This means spdif codec selection is now done explicitly via select_spdif_codec(). We can also remove the weird requirements on "dts" and "dts-hd" for the --audio-spdif option, and it can just do the right thing. Now both video and audio codecs consist of a single codec family each, vd_lavc and ad_lavc.
2016-12-23 17:03:16 +00:00
- change how spdif codecs are selected. You can't enable spdif passthrough
with --ad anymore. This was deprecated; use --audio-spdif instead.
options: deprecate codec family selection in --vd/--ad Useless now, so get rid of it. Also affects some user-visible display things (like reported codec in use).
2016-12-23 17:12:29 +00:00
- deprecate the "family" selection with --ad/--vd
options: deprecate some other complex --ad/--vd features Who even needs those? Once these deprecations are gone, --ad/--vd are simple lists without any kind of complex matching.
2016-12-23 17:18:17 +00:00
forcing/excluding codecs with "+", "-", "-" is deprecated as well
options: explicitly deprecate --ad-spdif-dtshd Has been less formally deprecated for a longer time.
2016-12-23 17:12:54 +00:00
- explicitly mark --ad-spdif-dtshd as deprecated (it was done so a long time
ago, but it didn't complain when using the option)
DOCS: update interface changes
2016-11-20 16:37:22 +00:00
--- mpv 0.22.0 ---
- the "audio-device-list" property now sets empty device description to the
device name as a fallback
- add --hidpi-window-scale option for macOS
- add audiounit audio output for iOS
- make --start-time work with --rebase-start-time=no
- add --opengl-early-flush=auto mode
- add --hwdec=vdpau-copy, deprecate vf_vdpaurb
- add tct video output for true-color and 256-color terminals
m_config: handle --no-... options differently Instead of adding "no-"-prefixed aliases to the internal option list, which will act like normal options, do it in the parsing stage. This turns out to be simpler (and cheaper), and avoids adding aliased options.
2016-08-31 14:45:58 +00:00
--- mpv 0.21.0 ---
DOCS/interface-changes.rst: reword a line Try to make it sound a bit less weird. Probably still sounds weird, so feel free to propose further changes.
2016-11-15 22:45:57 +00:00
- unlike in older versions, setting options at runtime will now take effect
immediately (see for example issue #3281). On the other hand, it will also
options: take care of propertly updating options on runtime changes All option write accesses are now put through the property interface, which means runtime option value verification and runtime updates are applied. This is done even for command line arguments and config files. This has many subtle and not-so-subtle consequences. The potential for unintended and intended subtle or not-subtle behavior changes is very large. Architecturally, this is us literally jumping through hoops. It really should work the other way around, with options being able to have callbacks for value verification and applying runtime updates. But this would require rewriting the entirety of command.c. This change is more practical, and if anything will at least allow incremental changes. Some options are too incompatible for this to work - these are excluded with an explicit blacklist. This change fixes many issues caused by the mismatch between properties and options. For example, this fixes #3281.
2016-09-17 18:48:22 +00:00
do runtime verification and reject option changes that do not work
(example: setting the "vf" option to a filter during playback, which fails
to initialize - the option value will remain at its old value). In general,
"set name value" should be mostly equivalent to "set options/name value"
in cases where the "name" property is not deprecated and "options/name"
exists - deviations from this are either bugs, or documented as caveats
in the "Inconsistencies between options and properties" manpage section.
options: deprecate suboptions for the remaining AO/VOs
2016-09-05 19:07:03 +00:00
- deprecate _all_ --vo and --ao suboptions. Generally, all suboptions are
replaced by global options, which do exactly the same. For example,
"--vo=opengl:scale=nearest" turns into "--scale=nearest". In some cases,
DOCS/interface-changes.rst: minor cleanup Edit the 0.21.0 section: remove the redundant vo_opengl items, move some up. Move the additions (which are less important and which aren't documented completely anyway) below the incompatible changes/deprecations.
2016-09-13 08:02:27 +00:00
the global option is prefixed, e.g. "--vo=opengl:pbo" turns into
"--opengl-pbo".
DOCS/interface-changes.rst: list exact sub-option replacements Actually, only link to a wiki page doing that, because these are too many options.
2016-09-06 18:10:05 +00:00
Most of the exact replacements are documented here:
https://github.com/mpv-player/mpv/wiki/Option-replacement-list
DOCS/interface-changes.rst: minor cleanup Edit the 0.21.0 section: remove the redundant vo_opengl items, move some up. Move the additions (which are less important and which aren't documented completely anyway) below the incompatible changes/deprecations.
2016-09-13 08:02:27 +00:00
- remove --vo=opengl-hq. Set --profile=opengl-hq instead. Note that this
profile does not force the VO. This means if you use the --vo option to
set another VO, it won't work. But this also means it can be used with
opengl-cb.
- remove the --vo=opengl "pre-shaders", "post-shaders" and "scale-shader"
sub-options: they were deprecated in favor of "user-shaders"
- deprecate --vo-defaults (no replacement)
- remove the vo-cmdline command. You can set OpenGL renderer options
directly via properties instead.
audio/out: deprecate device sub-options We have --audio-device, which can force the device. Also add something describing to this extent to the manpage.
2016-09-05 19:07:30 +00:00
- deprecate the device/sink options on all AOs. Use --audio-device instead.
audio/out: deprecate "exclusive" sub-options And introduce a global option which does this. Or more precisely, this deprecates the global wasapi and coreaudio options, and adds a new one that merges their functionality. (Due to the way the sub-option deprecation mechanism works, this is simpler.)
2016-09-05 19:07:34 +00:00
- deprecate "--ao=wasapi:exclusive" and "--ao=coreaudio:exclusive",
use --audio-exclusive instead.
m_config: handle --no-... options differently Instead of adding "no-"-prefixed aliases to the internal option list, which will act like normal options, do it in the parsing stage. This turns out to be simpler (and cheaper), and avoids adding aliased options.
2016-08-31 14:45:58 +00:00
- subtle changes in how "--no-..." options are treated mean that they are
not accessible under "options/..." anymore (instead, these are resolved
at parsing time). This does not affect options which start with "--no-",
but do not use the mechanism for negation options.
client API: deprecate "no-..." option handling The client API can do this (and there are apparently some libmpv using projects which rely on this). But it's just unnecessary bloat as it requires a separate code path from the option parser. It would be better to remove this code. Formally deprecate it, including API bump and warning in the API changes file to make it really clear.
2016-08-31 15:28:42 +00:00
(Also see client API change for API version 1.23.)
command: rename/deprecate some conflicting property names These conflict with options of the same name, and prevent a "full" unification. Not addressed is the "cache" property, and possibly a few properties that behave differently from their equivalent options.
2016-09-01 18:01:02 +00:00
- rename the following properties
- "demuxer" -> "current-demuxer"
- "fps" -> "container-fps"
- "idle" -> "idle-active"
command: deprecate "cache" property, replace with "cache-percent" The --cache option and cache property conflict, so one of them has to be renamed. The option is probably used frequently, so initiate deprecation/rename of the property.
2016-09-02 07:42:19 +00:00
- "cache" -> "cache-percent"
Fix some future release version numbers Since the recent release was named 0.22.0 instead of 0.21.1, bump all mentions of 0.22.0 to 0.23.0. These were planned removals of deprecated versions, which obviously didn't happen in 0.22.0.
2016-11-21 19:17:41 +00:00
the old names are deprecated and will change behavior in mpv 0.23.0.
command: remove 2 deprecated properties They were delcared to be removed in mpv 0.20.0, and the next release will be 0.21.0.
2016-09-01 18:01:29 +00:00
- remove deprecated "hwdec-active" and "hwdec-detected" properties
config: deprecate ao and vo auto-profiles These never made any sense. They checked the --vo/--ao option, and applied the profile corresponding to the first entry. So the only way to get any use of those was to use the --ao or --vo option explicitly. You can get the same functionality by making a manual profile, making these force the ao/vo, and then using --profile on command line instead of --vo/--ao.
2016-09-03 10:46:26 +00:00
- deprecate the ao and vo auto-profiles (they never made any sense)
vo_direct3d: deprecate direct3d_shaders alias And remove the difference between the aliases. This is needed to make the sub-option changes less painful.
2016-09-05 19:05:31 +00:00
- deprecate "--vo=direct3d_shaders" - use "--vo=direct3d" instead.
Change "--vo=direct3d" to always use shaders by default.
options: rename/deprecate --playlist-pos Conflicts with the "playlist-pos" property. They're really a bit too different, and since the --playlist-pos option is relatively new and obscure, just rename it to get this out of the way.
2016-09-18 11:38:45 +00:00
- deprecate --playlist-pos option, renamed to --playlist-start
player: more option/property consistency fixes Some properties had a different type from their equivalent options (such as mute, volume, deinterlace, edition). This wasn't really sane, as raw option values should be always within their bounds. On the other hand, these properties use a different type to reflect runtime limits (such as range of available editions), or simply to improve the "UI" (you don't want to cycle throuhg the completely useless "auto" value when cycling the "mute" property). Handle this by making them always return the option type, but also allowing them to provide a "constricted" type, which is used for UI purposes. All M_PROPERTY_GET_CONSTRICTED_TYPE changes are related to this. One consequence is that you can set the volume property to arbitrary high values just like with the --volume option, but using the "add" command it still restricts it to the --volume-max range. Also deprecate --chapter, as it is grossly incompatible to the chapter property. We pondered renaming it to --chapters, or introducing a more powerful --range option, but concluded that --start --end is actually enough. These changes appear to take care of the last gross property/option incompatibilities, although there might still be a few lurking.
2016-09-18 14:06:12 +00:00
- deprecate the --chapter option, as it is redundant with --start/--end,
and conflicts with the semantics of the "chapter" property
options: rename subtitle options Rename the text subtitle options from --sub-text- to --sub- and --ass- options to --sub-ass-. The intention is to common sub options to prefixed --sub- and special ASS option be seen as a special version of sub options. The OSD options that work like the --sub- options are still named --osd-. Man page updated including a short note about renamed --sub-text-* and --ass-* options to --sub-* and --sub-ass-*.
2016-10-02 15:08:14 +00:00
- rename --sub-text-* to --sub-* and --ass-* to --sub-ass-* (old options
deprecated)
stream_cdda: remove weird option parsing stuff Mostly untested. This is not compatible. It removes the URL fields for track range and cdrom speed (what did this even do). The device is not not to be prefixed with an additional "/" if it's put into the URL. I can't be bothered to keep these things compatible, just rip your damn CDs instead.
2016-09-09 15:39:22 +00:00
- incompatible change to cdda:// protocol options: the part after cdda://
now always sets the device, not the span or speed to be played. No
separating extra "/" is needed. The hidden --cdda-device options is also
deleted (it was redundant with the documented --cdrom-device).
Fix some future release version numbers Since the recent release was named 0.22.0 instead of 0.21.1, bump all mentions of 0.22.0 to 0.23.0. These were planned removals of deprecated versions, which obviously didn't happen in 0.22.0.
2016-11-21 19:17:41 +00:00
- deprecate --vo=rpi. It will be removed in mpv 0.23.0. Its functionality
vo_rpi: deprecate this VO
2016-09-12 17:58:06 +00:00
was folded into --vo=opengl, which now uses RPI hardware decoding by
treating it as a hardware overlay (without applying GL filtering). Also
Fix some future release version numbers Since the recent release was named 0.22.0 instead of 0.21.1, bump all mentions of 0.22.0 to 0.23.0. These were planned removals of deprecated versions, which obviously didn't happen in 0.22.0.
2016-11-21 19:17:41 +00:00
to be changed in 0.23.0: the --fs flag will be reset to "no" by default
vo_rpi: deprecate this VO
2016-09-12 17:58:06 +00:00
(like on the other platforms).
options: actually deprecate --mute=auto Also, make it internally actually an alias to "no".
2016-09-18 09:58:24 +00:00
- deprecate --mute=auto (informally has been since 0.18.1)
client API: declare mpv_suspend/mpv_resume deprecated They're useless, and I have no idea what they're actually supposed to do (wrt. pending input processing changes). Also remove their implicit uses from the IPC handlers.
2016-09-16 12:24:31 +00:00
- deprecate "resume" and "suspend" IPC commands. They will be completely
Fix some future release version numbers Since the recent release was named 0.22.0 instead of 0.21.1, bump all mentions of 0.22.0 to 0.23.0. These were planned removals of deprecated versions, which obviously didn't happen in 0.22.0.
2016-11-21 19:17:41 +00:00
removed in 0.23.0.
client API: declare mpv_suspend/mpv_resume deprecated They're useless, and I have no idea what they're actually supposed to do (wrt. pending input processing changes). Also remove their implicit uses from the IPC handlers.
2016-09-16 12:24:31 +00:00
- deprecate mp.suspend(), mp.resume(), mp.resume_all() Lua scripting
commands, as well as setting mp.use_suspend. They will be completely
Fix some future release version numbers Since the recent release was named 0.22.0 instead of 0.21.1, bump all mentions of 0.22.0 to 0.23.0. These were planned removals of deprecated versions, which obviously didn't happen in 0.22.0.
2016-11-21 19:17:41 +00:00
removed in 0.23.0.
DOCS/interface-changes.rst: mention seek command change This is potentially incompatible if a program used negative timestamps to deal with timestamp resets, which would potentially lead to mpv producing and using negative timestamps.
2016-10-03 13:49:53 +00:00
- the "seek" command's absolute seek mode will now interpret negative
seek times as relative from the end of the file (and clamps seeks that
still go before 0)
DOCS/interface-changes.rst: minor cleanup Edit the 0.21.0 section: remove the redundant vo_opengl items, move some up. Move the additions (which are less important and which aren't documented completely anyway) below the incompatible changes/deprecations.
2016-09-13 08:02:27 +00:00
- add almost all options to the property list, meaning you can change
options without adding "options/" to the property name (a new section
has been added to the manpage describing some conflicting behavior
between options and properties)
- implement changing sub-speed during playback
player: make --osc/--ytdl settable during playback Setting the osc or ytdl properties will now load/unload the associated scripts. (For ytdl this does not mean the currently played URL will be reloaded.) Also add a changelog entry for this, which also covers the preceding work for --terminal.
2016-09-19 22:59:54 +00:00
- make many previously fixed options changeable at runtime (for example
--terminal, --osc, --ytdl, can all be enable/disabled after
mpv_initialize() - this can be extended to other still fixed options
on user requests)
player: add option to control duration of image display The --image-display-duration option controls how long an image is displayed. It's also possible to display the image forever (until manual user interaction stops playback). With this, the core drops the old method to "drain" video (i.e. waiting for the last frame duration on end of playback). Instead, we reuse MPContext.time_frame. The old mechanism was disabled for non-images anyway. Fixes #3425.
2016-08-17 20:45:44 +00:00
--- mpv 0.20.0 ---
- add --image-display-duration option - this also means that image duration
is not influenced by --mf-fps anymore in the general case (this is an
incompatible change)
DOCS: Update version
2016-08-15 14:16:17 +00:00
--- mpv 0.19.0 ---
audio: refactor mixer code and delete mixer.c mixer.c didn't really deserve to be separate anymore, as half of its contents were unnecessary glue code after recent changes. It also created a weird split between audio.c and af.c due to the fact that mixer.c could insert audio filters. With the code being in audio.c directly, together with other code that unserts filters during runtime, it will be possible to cleanup this code a bit and make it work like the video filter code. As part of this change, make the balance code work like the volume code, and add an option to back the current balance value. Also, since the balance semantics are unexpected for most users (panning between the audio channels, instead of just changing the relative volume), and there are some other volumes, formally deprecate both the old property and the new option.
2016-07-17 17:21:28 +00:00
- deprecate "balance" option/property (no replacement)
options: deprecate --heartbeat-cmd It's useless. --heartbeat-interval is also considered deprecated, but this is not made explicit.
2016-06-29 16:10:15 +00:00
--- mpv 0.18.1 ---
- deprecate --heartbeat-cmd
audio: drop --softvol=no and --softvol=auto Drop the code for switching the volume options and properties between af_volume and AO volume controls. interface-changes.rst mentions the changes in detail. Do this because this was exceedingly complex and had other problems as well. It was also very hard to test. It's just not worth the trouble. Some leftovers like AOCONTROL_HAS_PER_APP_VOLUME will be removed at a later point. Fixes #3322.
2016-07-09 16:31:18 +00:00
- remove --softvol=no capability:
- deprecate --softvol, it now does nothing
manpage: minor fix Also fix some other type in interface-changes.rst.
2016-07-10 12:30:02 +00:00
- --volume, --mute, and the corresponding properties now always control
audio: drop --softvol=no and --softvol=auto Drop the code for switching the volume options and properties between af_volume and AO volume controls. interface-changes.rst mentions the changes in detail. Do this because this was exceedingly complex and had other problems as well. It was also very hard to test. It's just not worth the trouble. Some leftovers like AOCONTROL_HAS_PER_APP_VOLUME will be removed at a later point. Fixes #3322.
2016-07-09 16:31:18 +00:00
softvol, and behave as expected without surprises (e.g. you can set
them normally while no audio is initialized)
- rename --softvol-max to --volume-max (deprecated alias is added)
- the --volume-restore-data option and property are removed without
replacement. They were _always_ internal, and used for watch-later
resume/restore. Now --volume/--mute are saved directly instead.
- the previous point means resuming files with older watch-later configs
will print an error about missing --volume-restore-data (which you can
ignore), and will not restore the previous value
- as a consequence, volume controls will no longer control PulseAudio
per-application value, or use the system mixer's per-application
volume processing
- system or per-application volume can still be controlled with the
ao-volume and ao-mute properties (there are no command line options)
DOCS: change version references from 0.17.1 to 0.18.0 0.17.1 was never released, so the actual 0.18.0 release takes its place.
2016-06-25 10:39:08 +00:00
--- mpv 0.18.0 ---
command: if only ab-loop-b is set, loop from start of file Commit 382bafcb changed the behavior for ab-loop-a. This commit changes ab-loop-b so that the behavior is symmetric. Adjust the OSD rendering accordingly to the two changes. Also fix mentions of the "ab_loop" command to the now preferred "ab-loop".
2016-04-21 20:15:17 +00:00
- now ab-loops are active even if one of the "ab-loop-a"/"-b" properties is
unset ("no"), in which case the start of the file is used if the A loop
docs: fix some typos
2016-05-23 16:43:49 +00:00
point is unset, and the end of the file for an unset B loop point
sd_add: replace --sub-ass=no with --ass-style-override=strip --sub-ass=no / --ass=no still work, but --ass-style-override=strip is preferred now. With this change, --ass-style-override can control all the types of style overriding.
2016-04-30 12:25:23 +00:00
- deprecate --sub-ass=no option by --ass-style-override=strip
(also needs --embeddedfonts=no)
command: change some hwdec properties Introduce hwdec-current and hwdec-interop properties. Deprecate hwdec-detected, which never made a lot of sense, and which is replaced by the new properties. hwdec-active also becomes useless, as hwdec-current is a superset, so it's deprecated too (for now).
2016-05-04 14:55:26 +00:00
- add "hwdec-interop" and "hwdec-current" properties
- deprecated "hwdec-active" and "hwdec-detected" properties (to be removed
DOCS: change version references from 0.17.1 to 0.18.0 0.17.1 was never released, so the actual 0.18.0 release takes its place.
2016-06-25 10:39:08 +00:00
in mpv 0.20.0)
client API: access choices as flags if appropriate Options/properties that are choices, and which include "yes" or "no" values (or both) can now be read and written as MPV_FORMAT_FLAG. For write access, rejecting flags in these cases was obnoxiously unintuitive and inconvenient. For read access, the value of this is less convincing, and actually it's a major API change. At this point I probably have to admit that the finer details of the client API are very unstable.
2016-05-04 15:37:54 +00:00
- choice option/property values that are "yes" or "no" will now be returned
as booleans when using the mpv_node functions in the client API, the
"native" property accessors in Lua, and the JSON API. They can be set as
such as well.
vo_opengl: remove non-working rgb/rgba FBO formats Following commit 84ccebd9, the internal helpers don't allow GL_RGB and GL_RGBA as internal formats for FBO attachments anymore. While OpenGL itself is perfectly fine with it, I don't see much of a reason to bother, and mixing sized and unsized internal formats is confusing anyway. Just remove these formats.
2016-05-20 21:21:43 +00:00
- the VO opengl fbo-format sub-option does not accept "rgb" or "rgba"
anymore
vo_opengl: remove prescaling framework with superxbr prescaler Signed-off-by: wm4 <wm4@nowhere>
2016-06-10 12:35:09 +00:00
- all VO opengl prescalers have been removed (replaced by user scripts)
command: export more information under track-list Export a number of container fields, which may or may not be useful in some scenarios. They are explicitly marked as originating from the demuxer, in order to make it explicit that they might be unreliable. I'd actually like to remove all other cases where container information is exported, but those numerous cases are going to be somewhat hard to deprecate. Also, not directly related, export the description of the currently active decoder. (This has been requested before.)
2016-02-29 19:55:44 +00:00
--- mpv 0.17.0 ---
- deprecate "track-list/N/audio-channels" property (use
"track-list/N/demux-channel-count" instead)
command: change stream-pos semantics Changing the byte stream position without cooperation of the demuxer seems a bit insane, and is certainly useless. A user should do factor seeks instead. For formats like ts, this will actually translate to byte seeks, while treating the rest of the playback chain a bit more gracefully. With this argument, remove write access to this property. If someone really complains, proper byte seeks could be added as seek mode (although I'm going to need a convincing argument for this). Read access changes too, but in a more subtle way.
2016-03-09 22:34:04 +00:00
- remove write access to "stream-pos", and change semantics for read access
lua: don't suspend core by default during script execution This changes behavior somewhat. The old behavior can be restored by running "mp.use_suspend=true". It was originally introduced for the OSC, but I can't reproduce whatever misbehavior I was seeing. (See mp.suspend()/resume() for explanations what the suspend mechanism does.)
2016-03-18 21:03:04 +00:00
- Lua scripts now don't suspend mpv by default while script code is run
command: add cache-speed property Should reflect I/O speed. This could go into the terminal status line. But I'm not sure how to put it there, since it already uses too much space, so it's not there yet.
2016-03-20 18:48:55 +00:00
- add "cache-speed" property
DOCS/interface-changes: mention --input-ipc-server change
2016-03-24 18:24:40 +00:00
- rename --input-unix-socket to --input-ipc-server, and make it work on
Windows too
aspect: make video-zoom logarithmic The past behavior was a bit weird, especially when zooming out. There was no simple way to zoom in or out in consistent increments using keybindings alone. The new behavior preserves most of the old behavior's semantics but scales out to infinity better. It coincidentally also makes it really easy to get clean power of 2 ratios (e.g. 2x, 4x, 8x and their inverses). Fixes #3004.
2016-04-03 11:55:37 +00:00
- change the exact behavior of the "video-zoom" property
aspect: rework --video-unscaled In the past, --video-unscaled also disabled zooming and aspect ratio corrections. But this didn't make much sense in terms of being a useful option. The new behavior just sets the initial video size to be unscaled, but it's still affected by zoom commands and aspect ratio corrections. To get the old behavior back, --video-aspect=0 --video-zoom=0 need to be added as well (in the general case). Most of the time it should not make a difference though. Also, there seems to have been some additional dst_rect clamping code inside src_dst_split_scaling that didn't seem to either be necessary nor ever get triggered. (The code immediately above it already makes sure to crop the video if it's larger than the dst_rect) No idea why it was there, but I just removed it.
2016-04-10 15:26:32 +00:00
- --video-unscaled no longer disables --video-zoom and --video-aspect
To force the old behavior, set --video-zoom=0 and --video-aspect=0
audio: change --audio-channels default back to stereo Too many problems. Well, actually it's just Linux audio systems which cause problems, and exclusive audio access on other platforms. In any case, it seems you have to do some manual configuration if you want multichannel audio output.
2016-01-20 16:12:08 +00:00
--- mpv 0.16.0 ---
- change --audio-channels default to stereo (use --audio-channels=auto to
get the old default)
audio: change downmix behavior, add --audio-normalize-downmix This is probably the 3rd time the user-visible behavior changes. This time, switch back because not normalizing seems to be the more expected behavior from users.
2016-01-20 16:14:04 +00:00
- add --audio-normalize-downmix
- change the default downmix behavior (--audio-normalize-downmix=yes to get
the old default)
vo_opengl: rename custom shader entrypoint from sample to sample_pixel "sample" is a reserved identifier at least in GLES ES. Suggestions for a better name than "sample_pixel" are still welcome. Fixes #2733.
2016-01-25 19:24:41 +00:00
- VO opengl custom shaders must now use "sample_pixel" as function name,
instead of "sample"
vo_opengl: default scaler-resizes-only sub-option to yes Often requested. The main argument, that prominent scalers like sharpen change the image even if no scaling happens, disappeared anyway. ("sharpen", unsharp masking, is neither prominent nor a scaler anymore. This is an artifact from MPlayer, which fuses unsharp masking with bilinear scaling in order to make it single-pass, or so.)
2016-01-25 20:35:39 +00:00
- change VO opengl scaler-resizes-only default to enabled
vo_opengl: replace tscale-interpolates-only with interpolation-threshold The previous approach was too naive, and can e.g. ruin playback if scheduling switches e.g. between 1 and 2 vsync per frame.
2016-01-27 20:07:17 +00:00
- add VO opengl "interpolation-threshold" suboption (introduces new default
behavior, which can change e.g. ``--video-sync=display-vdrop`` to the
worse, but is usually what you want)
command: always allow setting volume/mute properties This seems generally easier when using libmpv (and was already requested and implemented before: see commit 327a779a; it was reverted some time later). With the weird internal logic we have to deal with, in particular the --softvol=no case (using system volume), and using the audio API's mixer (--softvol=auto on some systems), we still can't avoid all glitches and corner cases that complicate this issue so much. The API user is either recommended to use --softvol=yes or auto, or to watch the new mixer-active property, and assume the volume/mute properties have significant values if the mixer is active. Remaining glitches: - changing the volume/mute properties has no effect if no internal mixer is used (--softvol=no) and the mixer is not active; the actual mixer controls do not change, only the property values - --volume/--mute do not have an effect on the volume/mute properties before mixer initialization (the options strictly are only applied during mixer init) - volume-max is 100 while the mixer is not active
2016-01-26 14:12:42 +00:00
- make "volume" and "mute" properties changeable even if no audio output is
active (this gives not-ideal behavior if --softvol=no is used)
- add "volume-max" and "mixer-active" properties
input: ignore --input-cursor for events injected by input commands Apparently useful for window embedding. Fixes #2750.
2016-02-04 22:01:15 +00:00
- ignore --input-cursor option for events injected by input commands like
"mouse", "keydown", etc.
vf_yadif: change defaults This is for the sake of command.c and the "deinterlace" option/property. Instead of forcing certain "better" defaults when inserting yadif, change the actual "yadif" defaults. I pondered not changing vf_yadif, and instead adding a trivial "yadif- auto" wrapper filter, which would merely have different defaults. But thinking about it, it doesn't make any sense for "deinterlace" to have different defaults from vf_yadif, with vf_yadif having the "worse" defaults. If someone wants the old behavior, the old behavior can be forced in a backward and forward compatible way by setting the suboptions. Fixes #2539 (kind of).
2015-12-21 21:04:53 +00:00
--- mpv 0.15.0 ---
- change "yadif" video filter defaults
command: add vsync-ratio property This is very "illustrative", unlike the video-speed-correction property, and thus useful. It can also be used to observe scheduling errors, which are not detected by the core. (These happen due to rounding errors; possibly not evne our fault, but coming from files with rounded timestamps and so on.)
2015-11-13 21:48:32 +00:00
--- mpv 0.14.0 ---
DOCS/interface-changes: add some recent changes
2015-11-29 12:07:04 +00:00
- vo_opengl interpolation now requires --video-sync=display-... to be set
- change some vo_opengl defaults (including changing tscale)
- add "vsync-ratio", "estimated-display-fps" properties
player: handle rebasing start time differently Most of this is explained in the DOCS additions. This gives us slightly more sanity, because there is less interaction between the various parts. The goal is getting rid of the video_offset entirely. The simplification extends to the user API. In particular, we don't need to fix missing parts in the API, such as the lack for a seek command that seeks relatively to the start time. All these things are now transparent. (If someone really wants to know the real timestamps/start time, new properties would have to be added.)
2015-11-16 21:47:17 +00:00
- add --rebase-start-time option
This is a breaking change to start time handling. Instead of making start
time handling an aspect of different options and properties (like
"time-pos" vs. "playback-time"), make it dependent on the new option. For
compatibility, the "time-start" property now always returns 0, so code
which attempted to handle rebasing manually will not break.
vo_opengl_cb: make operation more similar to normal VOs vo_opengl_cb is a special case, because we somehow have to render video asynchronously, all while "trusting" the API user to do it correctly. This didn't quite work, and a while ago a compromise using a timeout to prevent theoretically possible deadlocks was added. Make it even more synchronous. Basically, go all the way, and synchronize rendering between VO and user renderer thread to the full extent possible. This means the silly frame queue is dropped, and we event attempt to synchronize the GL SwapBuffer call (via mpv_opengl_cb_report_flip()). The changes introduced with commit dc33eb56 are effectively dropped. I don't even remember if they mattered. In the future, we might make all VOs fetch asynchronously from a frame queue, which would mostly remove the differences between vo_opengl and vo_opengl_cb, but this will take a while (if it will even be done).
2015-11-09 19:49:30 +00:00
--- mpv 0.13.0 ---
- remove VO opengl-cb frame queue suboptions (no replacement)
vo_opengl: remove sharpen scalers, add sharpen sub-option This turns the old scalers (inherited from MPlayer) into a pre- processing step (after color conversion and before scaling). The code for the "sharpen5" scaler is reused for this. The main reason MPlayer implemented this as scalers was perhaps because FBOs were too expensive, and making it a scaler allowed to implement this in 1 pass. But unsharp masking is not really a scaler, and I would guess the result is more like combining bilinear scaling and unsharp masking.
2015-09-23 20:43:27 +00:00
--- mpv 0.12.0 ---
options: remove --use-text-osd
2015-10-24 17:09:35 +00:00
- remove --use-text-osd (useless; fontconfig isn't a requirement anymore,
and text rendering is also lazily initialized)
command: make time properties unavailable if timestamp is unknown Let's hope this doesn't confuse client API users too much. It's still the best solution to get rid of corner cases where it actually return the wrong timestamp on start, and then suddenly jump.
2015-10-16 14:16:10 +00:00
- some time properties (at least "playback-time", "time-pos",
"time-remaining", "playtime-remaining") now are unavailable if the time
is unknown, instead of just assuming that the internal playback position
is 0
audio: add option for falling back to ao_null The manpage entry explains this. (Maybe this option could be always enabled and removed. I don't quite remember what valid use-cases there are for just disabling audio entirely, other than that this is also needed for audio decoder init failure.)
2015-10-05 16:53:02 +00:00
- add --audio-fallback-to-null option
video: replace vf_format outputlevels option with global option The vf_format suboption is replaced with --video-output-levels (a global option and property). In particular, the parameter is removed from mp_image_params. The mechanism is moved to the "video equalizer", which also handles common video output customization like brightness and contrast controls. The new code is slightly cleaner, and the top-level option is slightly more user-friendly than as vf_format sub-option.
2015-09-29 19:12:26 +00:00
- replace vf_format outputlevels suboption with "video-output-levels" global
property/option; also remove "colormatrix-output-range" property
vo_opengl: remove sharpen scalers, add sharpen sub-option This turns the old scalers (inherited from MPlayer) into a pre- processing step (after color conversion and before scaling). The code for the "sharpen5" scaler is reused for this. The main reason MPlayer implemented this as scalers was perhaps because FBOs were too expensive, and making it a scaler allowed to implement this in 1 pass. But unsharp masking is not really a scaler, and I would guess the result is more like combining bilinear scaling and unsharp masking.
2015-09-23 20:43:27 +00:00
- vo_opengl: remove sharpen3/sharpen5 scale filters, add sharpen sub-option
af_lavfi: implement af-metadata property Works like vf-metadata. Unfortunately requires some code duplication (even though it's not much). Fixes #2311.
2015-09-11 21:04:02 +00:00
--- mpv 0.11.0 ---
- add "af-metadata" property
DOCS: cleanup API changes version markers Make it so that they don't need to be edited on release (no change in tense). Also, move the "stray" changes after client API version 1.19 to 1.19 itself.
2015-09-10 12:08:10 +00:00
--- mpv 0.10.0 ---
video: make container vs. bitstream aspect ratio configurable Utterly idiotic bullshit. Fixes #2259.
2015-08-30 21:01:46 +00:00
- add --video-aspect-method option
player: add --playlist-pos option Oddly often requested.
2015-08-22 20:08:17 +00:00
- add --playlist-pos option
player: add display sync mode If this mode is enabled, the player tries to strictly synchronize video to display refresh. It will adjust playback speed to match the display, so if you play 23.976 fps video on a 24 Hz screen, playback speed is increased by approximately 1/1000. Audio wll be resampled to keep up with playback. This is different from the default sync mode, which will sync video to audio, with the consequence that video might skip or repeat a frame once in a while to make video keep up with audio. This is still unpolished. There are some major problems as well; in particular, mkv VFR files won't work well. The reason is that Matroska is terrible and rounds timestamps to milliseconds. This makes it rather hard to guess the framerate of a section of video that is playing. We could probably fix this by just accepting jittery timestamps (instead of explicitly disabling the sync code in this case), but I'm not ready to accept such a solution yet. Another issue is that we are extremely reliant on OS video and audio APIs working in an expected manner, which of course is not too often the case. Consequently, the new sync mode is a bit fragile.
2015-08-10 16:43:25 +00:00
- add --video-sync* options
"display-sync-active" property
"vo-missed-frame-count" property
"audio-speed-correction" and "video-speed-correction" properties
demux: remove options to control minimum packet queue size Remove --demuxer-readahead-packets and --demuxer-readahead-bytes. These were a bit useless. They could force a minimum packet queue size, but controlling the queue size with --demuxer-readahead-secs is much nicer. It's fairly certain nobody ever used these options.
2015-08-05 21:38:23 +00:00
- remove --demuxer-readahead-packets and --demuxer-readahead-bytes
demux: add options to control maximum queue size Add --demuxer-max-packets and --demuxer-max-bytes, which control the maximum size of the packet queue. These can be helpful to avoid excessive memory usage. Memory usage is the reason why there's a limit in the first place. If a file is more or less broken, and audio and video don't line up, the decoders will fill up the packet queue trying to read more audio or video, and the maximum sizes are required to avoid unbounded memory allocation. Being able to override the maximum sizes is useful; either for restricting memory usage further, or enlarging the sizes when attempting to play various broken files.
2015-08-05 21:41:29 +00:00
add --demuxer-max-packets and --demuxer-max-bytes
(the new options are not replacement and have very different semantics)
DOCS: document video-aspect behavior change Forgotten in commit ae2f8fd0.
2015-08-05 19:29:09 +00:00
- change "video-aspect" property: always settable, even if no video is
running; always return the override - if no override is set, return
the video's aspect ratio
player: remove higher-level remains of DVD/BD menu support Nobody wanted to restore this, so it gets the boot. If anyone still wants to volunteer to restore menu support, this would be welcome. (I might even try it myself if I feel masochistic and like wasting a lot of time for nothing.) But if it does get restored, it should be done differently. There were many stupid things about how it was done. For example, it somehow tried to pull mp_nav_events through all the layers (including needing to "buffer" them in the demuxer), which was needlessly complicated. It could be done simpler. This code was already inactive, so this commit actually changes nothing. Also keep in mind that normal DVD/BD playback still works.
2015-08-03 21:33:03 +00:00
- remove disc-nav (DVD, BD) related properties and commands
command: add property indicating per-file options Fixes #2165, more or less.
2015-07-23 20:59:04 +00:00
- add "option-info/<name>/set-locally" property
cache: make backbuffer size configurable Allow setting an arbitrary amount, instead of the fixed 50%. This is nto striclty backwards compatible. The defaults don't change, but the --cache/--cache-default options now set the readahead portion. So in practice, users who configured this until now will see the double amount of cache being used, _plus_ the 75MB default backbuffer will be in use.
2015-07-22 21:38:45 +00:00
- add --cache-backbuffer; change --cache-default default to 75MB
the new total cache size is the sum of backbuffer and the cache size
specified by --cache-default or --cache
command: add track-list/N/audio-channels property Signed-off-by: wm4 <wm4@nowhere> (With some heavy modifications from the original patch.)
2015-07-03 00:33:54 +00:00
- add ``track-list/N/audio-channels`` property
screenshot: don't write PNG colorspace tags by default Generates too much discussion and confusion. Fixes #2051.
2015-07-18 16:33:54 +00:00
- change --screenshot-tag-colorspace default value
sub: add option for stretching image subtitles to screen Probably makes users happy who want bitmap subtitles to show up in the screen margins, and stops them from doing idiotic crap with vf_expand. Fixes #2098.
2015-07-18 12:36:17 +00:00
- add --stretch-image-subs-to-screen
player: parse and expose m3u playlist titles Requested. Closes #2100.
2015-07-10 19:22:35 +00:00
- add "playlist/N/title" property
video: add a way to disable automatic stereo conversion Fixes #2111.
2015-07-10 16:04:34 +00:00
- add --video-stereo-mode=no to disable auto-conversions
player: disable seeking even if the cache is enabled Until now, if a stream wasn't seekable, but the stream cache was enabled (--cache), we've enabled seeking anyway. The idea was that at least short seeks would typically fall within the cache. And if not, the user was out of luck and terrible things happened. In other words, it was unreliable. Be stricter about it and remove this behavior. Effectively, this will for example disable seeking in piped data. Instead of trying to be clever, add an --force-seekable option, which will always enable seeking if the user really wants it.
2015-07-08 20:04:35 +00:00
- add --force-seekable, and change default seekability in some cases
vf_vdpaupp: don't attempt to deinterlace progressive frames
2015-07-08 13:14:38 +00:00
- add vf yadif/vavpp/vdpaupp interlaced-only suboptions
Also, the option is enabled by default (Except vf_yadif, which has
it enabled only if it's inserted by the deinterlace property.)
vo_opengl_cb, vo_opengl: add option for preloading hwdec context See manpage additions. This is mainly useful for vo_opengl_cb, but can also be applied to vo_opengl. On a side note, gl_hwdec_load_api() should stop using a name string, and instead always use the IDs. This should be cleaned up another time.
2015-07-07 12:53:58 +00:00
- add --hwdec-preload
ao_coreaudio: add exclusive suboption
2015-07-03 17:21:22 +00:00
- add ao coreaudio exclusive suboption
DOCS: fix recent typos Pointed out by a certain wiiaboo.
2015-06-28 11:23:16 +00:00
- add ``track-list/N/forced`` property
audio: output human-readable channel layouts too This gets you the "logical" channel layout, instead of the exact thing we're sending to the AO. (Tired of the cryptic shit ALSA gives me.)
2015-06-25 17:10:24 +00:00
- add audio-params/channel-count and ``audio-params-out/channel-count props.
DOCS: document some recent interface additions
2015-06-24 12:40:03 +00:00
- add af volume replaygain-fallback suboption
- add video-params/stereo-in property
command: add keypress, keydown, and keyup commands. These commands are used to simulate keypresses using the key names from input.conf.
2015-06-10 23:56:56 +00:00
- add "keypress", "keydown", and "keyup" commands
audio: add --audio-spdif as new method for enabling passthrough This provides a new method for enabling spdif passthrough. The old method via --ad (--ad=spdif:ac3 etc.) is deprecated. The deprecated method will probably stop working at some point. This also supports PCM fallback. One caveat is that it will lose at least 1 audio packet in doing so. (I don't care enough to prevent this.) (This is named after the old S/PDIF connector, because it uses the same underlying technology as far as the higher level protoco is concerned. Also, the user should be renamed that passthrough is backwards.)
2015-06-05 20:35:43 +00:00
- deprecate --ad-spdif-dtshd and enabling passthrough via --ad
add --audio-spdif as replacement
command: remove deprecated get_property command This command has been deprecated in the 0.8.x and 0.9.x releases - get rid of it. Its only point ever was MPlayer compatibility, which broke years ago anyway.
2015-05-27 16:08:02 +00:00
- remove "get_property" command
options: remove --slave-broken It has been deprecated for ages.
2015-05-27 16:01:26 +00:00
- remove --slave-broken
DOCS: interface-changes: mention recent vo_opengl additions
2015-05-27 09:28:21 +00:00
- add vo opengl custom shader suboptions (source-shader, scale-shader,
pre-shaders, post-shaders)
command: change the hwdec properties Another very minor step towards property/option unification. Not bothering with interface compatibility here.
2015-05-25 19:44:48 +00:00
- completely change how the hwdec properties work:
- "hwdec" now reflects the --hwdec option
- "hwdec-detected" does partially what the old "hwdec" property did
(and also, "detected-hwdec" is removed)
- "hwdec-active" is added
command: add protocol-list property Fixes #1972.
2015-05-23 13:26:55 +00:00
- add protocol-list property
command: deprecate audio-samplerate Also replace their implementation with the recently introduced properties. One significant difference is that audio-channels using OSD formatting does not print the channel layout. The user can just use the replacement property instead.
2015-05-22 18:28:20 +00:00
- deprecate audio-samplerate and audio-channels properties
(audio-params sub-properties are the replacement)
command: add audio-params and audio-out-params properties
2015-05-22 18:23:47 +00:00
- add audio-params and audio-out-params properties
command: rename audio-format property Clashes with the option.
2015-05-22 18:05:04 +00:00
- deprecate "audio-format" property, replaced with "audio-codec-name"
options: rename --media-title option Conflicts with the property.
2015-05-22 18:03:14 +00:00
- deprecate --media-title, replaced with --force-media-title
command: deprecate the "length" property It collides with the --length option.
2015-05-22 18:02:47 +00:00
- deprecate "length" property, replaced with "duration"
DOCS: add a changelog for option/command/property changes All these make up both user interface and API. It's a good idea to actually keep track of changes to it.
2015-05-22 17:00:13 +00:00
- change volume property:
- the value 100 is now always "unchanged volume" - with softvol, the
range is 0 to --softvol-max, without it is 0-100
- the minimum value of --softvol-max is raised to 100
- remove vo opengl npot suboption
- add relative seeking by percentage to "seek" command
- add playlist_shuffle command
- add --force-window=immediate
- add ao coreaudio change-physical-format suboption
- remove vo opengl icc-cache suboption, add icc-cache-dir suboption
- add --screenshot-directory
- add --screenshot-high-bit-depth
- add --screenshot-jpeg-source-chroma
- default action for "rescan_external_files" command changes
DOCS: cleanup API changes version markers Make it so that they don't need to be edited on release (no change in tense). Also, move the "stray" changes after client API version 1.19 to 1.19 itself.
2015-09-10 12:08:10 +00:00
--- mpv 0.9.0 ---
Reference in New Issue Copy Permalink