:: :: > I'm not quite sure what YUV2 is but ordinary MPEG2 YUV (more properly, :: > Y, Cb, Cr) is such that U and V are subsampled x2 horizontally w.r.t. Y and :: > that is how you get "16 bits". :: :: I'am far from xpert at this area - so maybe i'am wrong at this ml anyway :: mayself ;-)
I'm an image/signal processing researcher. As I've demonstrated several times on this list, I know next to nothing about X, itself, except as a simple user who wants to learn. You're probably on the right list. But the real xperts would be a better judge of that. :: > Bit chopping does not, technically speaking, result in loss of resolution. :: > Instead you get various "contouring" and other artifacts due to the :: :: Exactly that is what i see! :: :: But what to do now? Is there a way to support more ximage input formats? This is a question for the Xperts. I can't help you. I can only explain why you see what you see :-) :: But, this is going OT now - as it was about Xvideo docs. Still got no :: detailed explanation why i should use the XvPutVideo() function call at all, :: which i thought would solve btw, the problem of the high CPU-load (at least :: reported to me with V3K + NVIDIA + Matrox cards). Comments from the Xperts? Dean _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
