Corruption when frame size changes

[cedricve]

Corruption when frame size changes

[cedricve]

Does it work with the default width and height?

[mcemilg]

This is what happens if I do not call any set function;

But if i call setters with default values like the folloowing;

cap->set(CV_CAP_PROP_FRAME_WIDTH , 2592);
cap->set(CV_CAP_PROP_FRAME_HEIGHT, 1944);

I am getting this frame, this is corrupted but not as much as the others;

[benrules2]

Are you repeatedly getting a new frame, or just grabbing one? My live feed looks like this sometimes when the camera has just started, but fixes itself. Maybe a 5s sleep before grabbing the image would help.

[dennisss]

I am also getting this issue with the the non-opencv video version.

By adding the line: Camera.setCaptureSize(1640, 1232); to simpletest_raspicam.cpp the following image is produced:

Hardware is Raspberry Pi 3 and Camera v2. The default resolution works fine, but I'm trying to get a higher resolution. Both picamera and raspivid are able to output this resolution, so I'm not sure what's different with this library.

Any ideas? Thanks!

[FirstCaptain]

I am having the exact same issue. Has anyone found out a work around or how to fix it yet?

[dennisss]

@FirstCaptain yes, I've found the solution and have a rough patch on my branch (https://github.com/dennisss/raspicam/) implemented for video only right now though.

I've tested it with grayscale on the RPi Camera v2, but I think it should work for RGB and BGR as well. YUV needs more work.

The main issue is that if the width and height is not aligned to 32 x 16 blocks, mmal internally pads each row up to that alignment point.
So the fix is basically to change the routine that copies the buffer to do it row by row and skip the padding: https://github.com/dennisss/raspicam/blob/master/src/private/private_impl.cpp#L766

[cedricve]

awesome @dennisss can we merge upstream?