summaryrefslogtreecommitdiffstats
path: root/DOCS
diff options
context:
space:
mode:
authorarpi <arpi@b3059339-0415-0410-9bf9-f77b7e298cf2>2002-03-24 18:44:15 +0000
committerarpi <arpi@b3059339-0415-0410-9bf9-f77b7e298cf2>2002-03-24 18:44:15 +0000
commit7d29c3856a8f220d269813e532760dae7e258709 (patch)
treedc1a61af3aad4cd9ab4f73b82a820024c8468336 /DOCS
parentac51a1e4116f1a3ed400c3dc21e4682d3ecc17cf (diff)
downloadmpv-7d29c3856a8f220d269813e532760dae7e258709.tar.bz2
mpv-7d29c3856a8f220d269813e532760dae7e258709.tar.xz
fixes, extended by mplayer's planes[]
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@5315 b3059339-0415-0410-9bf9-f77b7e298cf2
Diffstat (limited to 'DOCS')
-rw-r--r--DOCS/tech/colorspaces.txt9
1 files changed, 7 insertions, 2 deletions
diff --git a/DOCS/tech/colorspaces.txt b/DOCS/tech/colorspaces.txt
index f64311ace8..b1d7d6f22e 100644
--- a/DOCS/tech/colorspaces.txt
+++ b/DOCS/tech/colorspaces.txt
@@ -33,12 +33,17 @@ note: this formule doesn't contain the +128 offsets of U,V values!
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!