Mercurial > mplayer.hg
changeset 5314:ba5c92e64c5d
fixes, extended by mplayer's planes[]
| author | arpi |
|---|---|
| date | Sun, 24 Mar 2002 18:44:15 +0000 |
| parents | 0b7229832d2a |
| children | 75092614a37d |
| files | DOCS/tech/colorspaces.txt |
| diffstat | 1 files changed, 7 insertions(+), 2 deletions(-) [+] |
line wrap: on
line diff
--- a/DOCS/tech/colorspaces.txt Sun Mar 24 18:42:27 2002 +0000 +++ b/DOCS/tech/colorspaces.txt Sun Mar 24 18:44:15 2002 +0000 @@ -33,12 +33,17 @@ Conclusion: Y = luminance, the weighted average of R G B components. (0=black 255=white) U = Cb = blue component (0=green 128=grey 255=blue) -V = Cv = red component (0=green 128=grey 255=red) +V = Cr = red component (0=green 128=grey 255=red) MPlayer side: ============= In MPlayer, we usually have 3 pointers to the Y, U and V planes, so it -doesn't matter what is they order in memory. +doesn't matter what is they order in memory: + for mp_image_t and libvo's draw_slice(): + planes[0] = Y = luminance + planes[1] = U = Cb = blue + planes[2] = V = Cr = red + But there are some codecs (vfw, dshow) and vo drivers (xv) ignoring the 2nd and 3rd pointer, and use only a single pointer to the planar yuv image. In this case we must know the right order and alignment of planes in the memory!