diff options
author | wm4 <wm4@nowhere> | 2017-07-10 17:56:43 +0200 |
---|---|---|
committer | wm4 <wm4@nowhere> | 2017-07-10 17:56:43 +0200 |
commit | 26f56b5a5d1f8d004d756ee8cc8552ca7de00f34 (patch) | |
tree | 5978a1913dc3b0ad3099e5c14b61232b929bfae7 /osdep/terminal-win.c | |
parent | b016760a286a190e5134c177672472aa8f2e42d8 (diff) | |
download | mpv-26f56b5a5d1f8d004d756ee8cc8552ca7de00f34.tar.bz2 mpv-26f56b5a5d1f8d004d756ee8cc8552ca7de00f34.tar.xz |
vo_opengl: don't make assumptions about plane order
The renderer code doesn't list a fixed set of supported formats, but
supports anything that is described by AVPixFmtDescriptor and follows a
number of constraints.
Plane order is not included in those constraints. This means the planes
could be in random order, rather than what the vo_opengl renderer
happens to assume. For example, it assumes that the 4th plane is alpha,
even though alpha could be on any plane. Likewise it assumes that plane
0 was always luma, and planes 2/3 chroma. (In earlier iterations of
format support, this was guaranteed by MP_IMGFLAG_YUV_P, but this is not
used anymore.)
Explicitly set the plane semantics (enum plane_type) by the component
descriptors and the used colorspace. The behavior should mostly not
change, but it's less likely to break when FFmpeg adds new pixel
formats.
Diffstat (limited to 'osdep/terminal-win.c')
0 files changed, 0 insertions, 0 deletions