<!-- Some styling for better description lists --><style type='text/css'>dt { font-weight: bold;float: left;display:inline;margin-right: 1em} dd { display:block; margin-left: 2em}</style> cristian_c: <u>ndufresne</u>: I've analyzed the pp3 files <br> <u>ndufresne</u>: they include details about captured frames ndufresne: I had a big week last week, and somehow, I forgot what we were discussing before cristian_c: np, I should calculate <br> I should calculate size of buffer <br> so, I've captured a frame by rawthreapee <br> the .pp3 file shows info about exposure, color channels, data about black&white, luminance, sharpening, vibrance, white balance, shadows and other parameters <br> I can see data about width and height in Crop section <br> 633x473 <br> and ratio 3:2 <br> so, I should calculate the expected size of the buffer for the v4l device <br> <u>ndufresne</u>: what parameters are needed in order to calculate that? ndufresne: ok, I see <br> 633x473 is quite strange, but you said it's a crop rectangle ? cristian_c: yeah ndufresne: memory whise, you'll need to figure-out some allocation size parameter <br> Most HW can't deal with odd size buffers cristian_c: I''ve opened the .raw grabbed frame ndufresne: So you have to find the stride, which is the width of a line in bytes <br> so from 633 width, how many bytes is added per lines in order to satisfy the HW requirement <br> In general, for one HW it's fixed cristian_c: of course, the grabbed frame is totally black <br> the second frame I grabbed is 'green' but crop properties don't change, btw <br> just one info, the .pp3 file shows also a Resize section <br> width x height is 900 x 900, but Enabled=false <br> Scale=1 and AppliesTo=Cropped area <br> so, it's not important hverkuil: <u>ndufresne</u>: Tuesday, 11 am at the Linux Foundation registration desk. ndufresne: hverkuil, thanks ! <br> I'll be there hverkuil: I'll figure out tomorrow where to sit and if things change then I'll send an email, so check your mail Tuesday morning.