summaryrefslogtreecommitdiffstats
path: root/DOCS/man/input.rst
Commit message (Collapse)AuthorAgeFilesLines
* player: add on_preloaded hookwm42016-02-151-0/+11
| | | | (Limited usefulness.)
* command: always allow setting volume/mute propertieswm42016-01-261-2/+21
| | | | | | | | | | | | | | | | | | | | | | | 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
* manpage: adjust vf/af-command descriptionwm42016-01-221-1/+4
|
* command: add af-command commandwm42016-01-221-0/+3
| | | | Similar to vf-command. Requested. Untested.
* command: add vf-command commandwm42016-01-221-0/+6
|
* man: input: document new DVB bindings and properties.Oliver Freyermuth2016-01-141-0/+9
| | | | | There is now H and K for DVB-channel switching, and the properties dvb-channel (W) and dvb-channel-name (RW).
* input: add a catch-all "unmapped" commandwm42015-12-231-0/+6
| | | | | | This can be used to grab all unmapped keys. Fixes #2612.
* input: add key name to script-binding command responsewm42015-12-231-8/+14
| | | | | | | | | | | | | | | | The "script-binding" command is used by the Lua scripting wrapper to register key bindings on the fly. It's also the only way to get fine- grained information about key events (such as separate key up/down events). This information is sent via a "key-binding" message when the state of a key changes. Extend it to send name of the mapped key itself. Previously, it was assumed that the user just uses an unique identifier for the binding's name, so it wasn't needed. With this change, a user can map exactly the same command to multiple keys, which is useful especially with the next commit. Part of #2612.
* man: fix grammar issuesMartin Herkt2015-12-191-8/+7
|
* manpage: reflect recent subtitle changeswm42015-12-061-3/+3
|
* manpage: explain behavior of "path" propertywm42015-11-291-1/+5
| | | | | | | This seems to confuse users pretty often, but I'm not going to change its behavior. See e.g. #2541.
* command, vo: add estimated-display-fps propertywm42015-11-251-0/+8
| | | | | | | | | | This is simply the average refresh rate. Including "bad" samples is actually an advantage, because the property exists only for informational purposes, and will reflect problems such as the driver skipping a vsync. Also export the standard deviation of the vsync frame duration (normalized to the range 0-1) as vsync-jitter property.
* command: export some per-video-frame informationwm42015-11-221-0/+13
| | | | Utterly useless, but requested. Fixes #2444.
* player: handle rebasing start time differentlywm42015-11-161-5/+8
| | | | | | | | | | | | | | | | 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.)
* command: add vsync-ratio propertywm42015-11-131-0/+7
| | | | | | | | 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.)
* command: rename vo-missed-frame-count propertywm42015-11-131-0/+5
| | | | | | | | | "Missed" implies the frame was dropped, but what really happens is that the following frame will be shown later than intended (due to the current frame skipping a vsync). (As of this commit, this property is still inactive and always returns 0. See git blame for details.)
* command: make display-fps property writablewm42015-11-091-1/+1
| | | | | | | Has the same function as setting the option. This commit changes the property in a bunch of other ways. For example if the VO is not created, it will return the option value.
* command: add mistimed-frame-count propertywm42015-10-301-0/+8
| | | | | Does what the manpage says. This is a replacement incrementing the dropped frame counter (see previous commit).
* video: remove user-controllable PTS sorting (--pts-association-mode)wm42015-10-061-3/+0
| | | | | | | | | Useless. Sometimes it might be useful to make some extremely broken files work, but on the other hand --no-correct-pts is sufficient for these cases. While we still need some of the code for AVI, the "auto" mode in particular inflated the size of the code.
* video: replace vf_format outputlevels option with global optionwm42015-09-291-2/+2
| | | | | | | | | | | 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.
* af_lavfi: implement af-metadata propertywm42015-09-111-0/+3
| | | | | | | Works like vf-metadata. Unfortunately requires some code duplication (even though it's not much). Fixes #2311.
* cache: do not include backbuffer size in total stream cache sizewm42015-09-101-1/+3
| | | | | | | | | This causes weirdness with the "cache-size" property and option. Only the read handler of the property included the backbuffer, while all others did not. Make it consistent, and subtract the backbuffer size from the cache size. Fixes #2305.
* command: make the playback-time property writablewm42015-08-211-2/+4
| | | | | | | Provides a simplistic way to seek without having to care about weird situations like timestamp vs. playback time. This is good, because the seek command is currently timestamp based, so when using the seek command the user _does_ have to care.
* manpage: fix typowm42015-08-181-1/+1
| | | | Actually, this was unintentionally changed in commit 70e0bc1e.
* player: add display sync modewm42015-08-101-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* player: separate controls for user and video controlled speedwm42015-08-101-0/+4
| | | | | | | | | | For video sync, we want separate playback speed controls for user- requested speed and the "correction" speed for video timing. Further, we use this separation to make sure only a resampler is inserted if playback speed is only changed for video sync correction. As of this commit, this is basically inactive code. It's just preparation for the video sync code (the following commit).
* manpage: use - as separator for the remaining commandswm42015-08-061-22/+22
| | | | | See commit 289705da. These manpage parts were just forgotten when updating the command descriptions.
* lua: implement input_enable_section/input_disable_section via commandswm42015-08-061-4/+13
| | | | | | | | | | | | | | | Removes some more internal API calls from the Lua scripting backend. Which is good, because ideally the scripting backend would use libmpv functions only. One awkwardness is that mouse sections are still not supported by the public commands (and probably will never), so flags like allow-hide- cursor make no sense to an outside user. Also, the way flags are passed to the Lua function changes. But that's ok, because they're only undocumented internal functions, and not supposed to be used by script users. osc.lua only does due to historical reasons.
* command: define-section with empty contents removes a sectionwm42015-08-061-0/+2
|
* command: add a command for defining input bindingswm42015-08-061-0/+20
| | | | | | This was requested. It was more or less present internally already and used for Lua scripting. Lua will switch to the "public" functions in the following commits.
* player: remove higher-level remains of DVD/BD menu supportwm42015-08-031-22/+0
| | | | | | | | | | | | | | | 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.
* command: add property indicating per-file optionswm42015-07-231-0/+6
| | | | Fixes #2165, more or less.
* command: add track-list/N/audio-channels propertydeuiore2015-07-181-0/+5
| | | | | | Signed-off-by: wm4 <wm4@nowhere> (With some heavy modifications from the original patch.)
* player: parse and expose m3u playlist titleswm42015-07-101-0/+6
| | | | Requested. Closes #2100.
* manpage: fix copy&paste mistakeswm42015-06-301-22/+20
| | | | | | | These are definitely not per-track. (Maybe we should just provide a script or such which pretty-prints "native" property output.
* DOCS/man: fix some grammar errorsDaniel Bergmann2015-06-291-1/+1
| | | | Signed-off-by: wm4 <wm4@nowhere>
* DOCS: fix recent typoswm42015-06-281-1/+1
| | | | Pointed out by a certain wiiaboo.
* demux: export forced flagwm42015-06-271-0/+5
| | | | | | At least Matroska files have a "forced" flag (in addition to the "default" flag). Export this flag. Treat it almost like the default flag, but with slightly higher priority.
* audio: output human-readable channel layouts toowm42015-06-251-0/+6
| | | | | 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.)
* manpage: minor fixeswm42015-06-231-1/+2
|
* command: export stereo 3D tagswm42015-06-231-0/+3
| | | | Fixes #2066.
* Various spelling fixesMarcin Kurczewski2015-06-181-1/+1
| | | | Signed-off-by: wm4 <wm4@nowhere>
* DOCS/manpage: fix typosrrooij2015-06-171-2/+2
| | | | | | | Fix some errors in the man pages by spell checking them. Most of them were typos. Signed-off-by: wm4 <wm4@nowhere>
* command: add keypress, keydown, and keyup commands.torque2015-06-111-0/+17
| | | | | These commands are used to simulate keypresses using the key names from input.conf.
* command: remove deprecated get_property commandwm42015-05-271-1/+1
| | | | | | 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.
* input: allow - as separator between commands, instead of _wm42015-05-251-40/+40
| | | | | | | | | | Wnile it seems quite logical to me that commands use _ as word separator, while properties use -, I can't really explain the difference, and it tends to confuse users as well. So always prefer - as separator for everything. Using _ still works, and will probably forever. Not doing so would probably create too much chaos and confusion.
* command: change the hwdec propertieswm42015-05-251-19/+23
| | | | | | Another very minor step towards property/option unification. Not bothering with interface compatibility here.
* command: add protocol-list propertywm42015-05-231-0/+6
| | | | Fixes #1972.
* command: deprecate audio-sampleratewm42015-05-221-7/+0
| | | | | | | 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.
* command: add audio-params and audio-out-params propertieswm42015-05-221-0/+36
|
* command: rename audio-format propertywm42015-05-221-3/+3
| | | | Clashes with the option.
* command: deprecate the "length" propertywm42015-05-221-2/+5
| | | | It collides with the --length option.
* audio: change range of volume option/propertywm42015-05-221-1/+1
| | | | | | | | | Now --volume takes an absolute volume, meaning it doesn't depend on --softvol-max. 0 is still silence, and 100 now always means unchanged volume. The OSD and the "volume" property are changed accordingly. Also raise the minimum value of --softvol-max. A value below 100 makes no sense and breaks the OSD.
* input: add relative percentage seekrrooij2015-05-191-1/+3
| | | | | | | | | | | Only absolute percentage seeking was permitted first. It is now also possible to seek by relative percentage. MPSEEK_FACTOR is used as seek_type. Fixes #1950. Signed-off-by: wm4 <wm4@nowhere>
* command: add playlist_shuffle commandwm42015-05-171-0/+4
| | | | Fixes #965.
* manpage: explain some property expansion restrictionswm42015-05-131-1/+4
|
* manpage: remove stray newlinewm42015-05-131-1/+0
|
* command: change the default action for rescan_external_fileswm42015-04-281-5/+5
| | | | | | | | Now the rescan_external_files command will by default reselect the audio and subtitle streams. This should be more intuitive. Client API users and Lua scripts might break, but can be fixed in a backward-compatible way by setting the mode explicitly.
* manpage: update colormatrix property descriptionwm42015-04-271-8/+9
|
* manpage: document ff-index sub-propertywm42015-04-231-0/+7
|
* command: demuxer-cache-time propertyxylosper2015-04-211-0/+5
| | | | | | | | Approximate time of video buffered in the demuxer, in seconds. Same as `demuxer-cache-duration` but returns the last timestamp of bufferred data in demuxer. Signed-off-by: wm4 <wm4@nowhere>
* client API: add a screenshot_raw commandwm42015-04-201-0/+9
| | | | | | | | | Requested. The wild code for setting up the mpv_node probably deserves to be cleaned up later. Fixes #1800.
* player: change video-bitrate and audio-bitrate propertieswm42015-04-201-7/+22
| | | | | | | | | | | | | | Remove the old implementation for these properties. It was never very good, often returned very innaccurate values or just 0, and was static even if the source was variable bitrate. Replace it with the implementation of "packet-video-bitrate". Mark the "packet-..." properties as deprecated. (The effective difference is different formatting, and returning the raw value in bits instead of kilobits.) Also extend the documentation a little. It appears at least some decoders (sipr?) need the AVCodecContext.bit_rate field set, so this one is still passed through.
* command: disc-mouse-on-button propertyxylosper2015-04-211-0/+4
| | | | | This property indicates whether mouse cursor is located on button or not for disc naviation.
* command: let screenshot_to_file command overwrite fileswm42015-04-161-2/+1
| | | | | | | The old behavior does not make too much sense after all. If you don't want to file to be overwritten, the user can check this manually. This is a change in behavior - let's hope nobody actually relied on it.
* command: new subproperty for video-params: gammaNiklas Haas2015-04-041-0/+3
|
* command: add property returning current working directorywm42015-03-241-0/+4
| | | | Requested; fixes #1717.
* command: display-fps is the display FPS as assumed by the VOwm42015-03-121-3/+3
| | | | | | | | | Requested change in behavior. Note that we set the assumed "infinite" display_fps to 1e6, which conveniently lets vo_get_vsync_interval() return a dummy value of 1, which can be easily checked against, and still avoids doing math with float INFs.
* command: add display-fps propertywm42015-03-101-0/+7