6by9

If you'd make the ```--native``` option of buildme set the new flag it'd be appreciated.

I don't follow your issue. vc.ril.rawcam will accept an buffers. It will write them with incoming data, and return 2 buffers with the same timestamp each time it receives a...

errorcode -2 is that it can't allocate an image buffer for the new camera frame. By the looks of it the video_encode has been passed frames and isn't producing output...

I don't believe this is totally down to a faulty camera. You are correct that it will stall under those conditions @JamesH65 up to you whether you want to know...

It's possible that there is a memory leak, but I'd . I420 2592x1944 is 7.5MB per buffer, so not insignificant. Opaque buffers are (IIRC) about 64bytes! Even dropping to 1080P...

port_format_commit shouldn't change the buffer_num or buffer_size fields, but it will change buffer_num_min, buffer_num_recommended and buffer_size_min to reflect the requirements of the new format Buffer size for RGBA > RGB565...

I only use MMAL, I didn't write it ;-) I thought that port_format_commit didn't change things, but it does appear to set the size and num to at least the...

Old issue, but I'm hoping I've fixed this in the latest firmware. https://github.com/Hexxeh/rpi-firmware/commit/a1621d67b20f04acdac602d0b24923ec3cdbfb66 "firmware: MMAL: reset buffer recommended values on switching back to raw pixels"

As referenced above, I did put in a change for this that was released in https://github.com/Hexxeh/rpi-firmware/commit/a1621d67b20f04acdac602d0b24923ec3cdbfb66 Hopefully buffer_num_recommended and buffer_size_recommended are now reset to sensible values when switching back from...

(I can relate - mine has her 1st birthday this week!) That sounds like we still have an issue. At the IL level (hiding below MMAL), a buffer count of...