summaryrefslogtreecommitdiffstats
path: root/options.h
diff options
context:
space:
mode:
authorwm4 <wm4@mplayer2.org>2011-11-27 19:58:04 +0100
committerwm4 <wm4@mplayer2.org>2012-03-17 21:06:30 +0100
commit7c6a4e1e98c29ea853c6f7fdf9a3e5a3668006b5 (patch)
treed41d98a0c0c4492be4466a72f205145ab58c1f52 /options.h
parentd813a4ede8b9fcd5e06d808be794061d7183b36d (diff)
downloadmpv-7c6a4e1e98c29ea853c6f7fdf9a3e5a3668006b5.tar.bz2
mpv-7c6a4e1e98c29ea853c6f7fdf9a3e5a3668006b5.tar.xz
vo_direct3d: implement screenshots
There are 4 code paths when taking a screenshot: - textured rendering mode - StretchRect rendering mode with planar formats - StretchRect with packed formats - full-window screenshot mode The implementation of the full-window mode (capturing the window contents, instead of the video) is very inefficient: it will create a surface of desktop size, copy the desktop contents, allocate a new memory image, and copy in the window contents. The code in screenshot.c will (as of now) allocate and convert the image from BGR to RGB, and allocate a destination buffer for the libavcodec PNG writer. If parts of the mplayer window are obscured, the full-window mode wil contain these parts as seen on the screen. Parts of the window that are outside the bounds of the desktop are clipped away. It is not known whether full-window mode works on multi-monitor setups.
Diffstat (limited to 'options.h')
0 files changed, 0 insertions, 0 deletions