From e5f2072364ac450e0f593f534ddee2ae1a8f2176 Mon Sep 17 00:00:00 2001 From: wm4 Date: Sat, 10 Jan 2015 19:11:28 +0100 Subject: command: change properties added in previous commit Make their meaning more exact, and don't pretend that there's a reasonable definition for "bits-per-pixel". Also make unset fields unavailable. average_depth still might be inconsistent: for example, 10 bit 4:2:0 is identified as 24 bits, but RGB 4:4:4 as 12 bits. So YUV formats seemingly drop the per-component padding, while RGB formats do not. Internally it's consistent though: 10 bit YUV components are read as 16 bit, and the padding must be 0 (it's basically like an odd fixed- point representation, rather than a bitfield). --- DOCS/man/input.rst | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) (limited to 'DOCS') diff --git a/DOCS/man/input.rst b/DOCS/man/input.rst index d044923654..ede28b07bf 100644 --- a/DOCS/man/input.rst +++ b/DOCS/man/input.rst @@ -1119,11 +1119,15 @@ Property list The pixel format as string. This uses the same names as used in other places of mpv. - ``video-params/bpp`` - Bits-per-pixel as integer. - - ``video-params/depth`` - Bit depth for each color component as integer. + ``video-params/average_bpp`` + Average bits-per-pixel as integer. Subsampled planar formats use a + different resolution, which is the reason this value can sometimes be + odd or confusing. Can be unavailable with some formats. + + ``video-params/plane_depth`` + Bit depth for each color component as integer. This is only exposed + for planar or single-component formats, and is unavailable for other + formats. ``video-params/w``, ``video-params/h`` Video size as integers, with no aspect correction applied. -- cgit v1.2.3