diff options
| author | wm4 <wm4@nowhere> | 2012-10-21 17:12:42 +0200 |
|---|---|---|
| committer | wm4 <wm4@nowhere> | 2012-10-24 21:56:34 +0200 |
| commit | 6bea013e27c705ad0bc39f7da22b4ac4eabd7890 (patch) | |
| tree | 86b7b907dc908e64211fbe6efdc2d0f5010e11e2 /DOCS | |
| parent | 4b4e4b56909a07f1738d75c0f3fc1739990adfc9 (diff) | |
| download | mpv-6bea013e27c705ad0bc39f7da22b4ac4eabd7890.tar.bz2 mpv-6bea013e27c705ad0bc39f7da22b4ac4eabd7890.tar.xz | |
screenshot: hack against w/width confusion
struct mp_image has two sets of size members: width/height and w/h. It's
not even sure which one of these is the ACTUAL dimension, and which is
the "stored" or "visible" dimension. vf_get_image() (a core function for
video filters) does something confusing with the sizes, and often sets
up cropped versions of other filter's image buffers. The screenshot code
uses w/h to store the display size for anamorphic video, while
width/height is the size of the pixel data. The draw_bmp.c code, as well
as sws_utils.c, always use w/h for the size of the pixel data.
It's an unholy mess, and the screenshot code potentially breaks it even
more. Work that around with a hack, until we hopefully clean up
mp_image and the video filter code.
Diffstat (limited to 'DOCS')
0 files changed, 0 insertions, 0 deletions