<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
David Kuehling wrote:<br>
<blockquote cite="mid87k6393ojy.fsf@snail.Pool" type="cite">
<blockquote type="cite">
<pre wrap="">Can't you grab directly in YUV ? ( like V4L2_PIX_FMT_YUV420 )
</pre>
</blockquote>
<pre wrap=""><!---->In my experience the least-common denominator for V4L2 capture would be
V4L2_PIX_FMT_YUYV. Which is twice as many chroma data as YUV420. </pre>
</blockquote>
<br>
You can choose any colorspace you like but if you convert it to YUV I
don't think the extra chroma data will count.<br>
<br>
I use V4L2_PIX_FMT_YUV420 because in this way I can use ffmpeg's
PIX_FMT_YUV420P or ogg's OC_PF_420 directly ;)<br>
( and also SDL overlays almost directly )<br>
<br>
<blockquote cite="mid87k6393ojy.fsf@snail.Pool" type="cite">
<pre wrap="">But reducing that shouldn't take much cpu power.
</pre>
</blockquote>
<br>
In this way you can skip a post processing function on every frame you
grab... I think it can help the CPU.<br>
And you were asking about RGB to YUV conversion in these posts...<br>
<br>
BTW, if I remember correctly in ffmpeg there should be a
img_convert() function to convert the frames between different
colorspaces<br>
<br>
</body>
</html>