picamera *should* work fine with older firmwares but I don't explicitly test them (the test suite already takes a good 30+ minutes to run!)JTeagle wrote:Thanks Dave, I'll try that.waveform80 wrote: Try "rgba" instead. There is an MMAL setting for "argb" but for some reason it doesn't work with the resizer output which I use for raw captures (just as the "rgb" and "bgr" don't (directly) work - but I figured those were important enough to write an emulation for, which is why they're so slow as the processing's been done on the CPU).
Quick question, seeing mention of firmware updates... will the later versions of the picamera library work with older firmwares as well as newer ones, or is it important to keep firmware on the cameras up-to-date? How is the camera firmware updated - through apt-get update (if so, what is the name of the module)?
Generally speaking, firmware updates are only important if you care about new functionality or bug fixes introduced by them. To give a brief run down of stuff that firmware updates have fixed in the past: lockups with long exposure times, correct setting of exposure compensation, fixed white balance, full FoV in most resolutions (except 1080p), frame rates above 30fps, and so on. Unfortunately I don't think there's a simple list of which revision fixes what so a bit of guess-work may be involved.
Firmware updates are applied (and can be rolled back) with "sudo rpi-update" rather than "sudo apt-get".