I thought I'd better open a semi-official Q&A thread on the new Sony IMX219 8MP camera.
Can I remind people at the outset that whilst it is an official Pi product and has support from Pi Towers, people such as myself supporting it do so on a voluntary basis and have full time jobs elsewhere. If something is hideously broken we will fix it as soon as possible, but making unreasonable demands because feature X isn't exposed is unlikely to be well received.
There are some features still in progress, but the basics are:
- Sony IMX219 8MPix sensor.
- Fixed lens.
- Various readout modes defined off the sensor. I haven't been directly involved in these, but reading out from the driver source, these are in order:
edit: As of rpi-update from 13/5/16, and raspbian update of 16/5/16, the mode list has been altered to more closely match the ordering on OV5647, and also to improve FOV for some modes.
- 1 - 1080P30 cropped (680 pixels off left/right, 692 pixels off top/bottom), up to 30fps
- 2 - 3240x2464 Full 4:3, up to 15fps
- 3 - 3240x2464 Full 4:3, up to 15fps (identical to 2)
- 4 - 1640x1232 binned 4:3, up 40fps
- 5 - 1640x922 2x2 binned 16:9 (310 pixels off top/bottom before binning), up to 40fps
- 6 - 720P binned and cropped (360 pixels off left/right, 512 pixels off top/bottom before binning), 40 to 90fps (120fps if overclocked)
- 7 - VGA binned and cropped (1000 pixels off left/right, 752 pixels off top/bottom before binning), 40 to 90fps (120fps if overclocked)
Modes 1-5 should all allow up to 10second exposure times if you request appropriate frame rates.
Prior to those releases, the mode list was:
- 1280x720 binned(? may be skipping) and cropped, at 60-120 fps. Please note that the H264 encoder will not be able to consume video at above 720P60, although we're looking into where the limit actually sits. Currently the codec will enforce a max of level 4, which is 720P at max 68.3fps (see https://en.wikipedia.org/wiki/H.264/MPE ... Levels). I'm not expecting to be able to claim 4.2 and 720P145 even with mega overclocking, but we'll try to push the limits.
- 1080P cropped up to 30fps.
- 1640x1232 full FOV binned mode, up to 30fps.
- 3280x2464 full FOV, allegedly 0.1fps to 15fps. (Yes, that in theory means 10second exposures).
edit: The H264 encoder will now allow the app to request level 4.2, but will only achieve any significant gain with overclocking. An update to raspivid is in order to allow > 720P68. 720P120 is almost working reliably but requires a significant overclock (achieved on a Pi3, but not on a Pi2 yet). Settings for how much overclocking, and any other trade-offs that can be made, are still being determined.
- The camera LED appears to have been removed.
- Firmware has supported the sensor for a while, but there have been updates in the last couple of days. Raspistill app and V4L2 driver have been updated to ask the GPU what the max sensor resolution is and set default/max resolutions appropriately - source repos are both updated.
- It does work on the Compute Module in stereoscopic mode, and the CM and software should also work correctly with one IMX219 and one OV5647 connected. (Fixed as of 8th June 2016 firmware update)
- HDR is NOT supported. The ISP doesn't have suitable processing to implement it.
- For obvious reasons, the size of the raw data captured using "raspistill --raw" has changed. There is an updated version of dcraw in my test repo at https://github.com/6by9/RPiTest/tree/master/dcraw. You will need to rebuild it manually as I haven't updated the binary in there.
- My rawcam code for capturing the raw Bayer data has not been updated, and again register sets are under NDA. Support will come eventually, or may be added via V4L2 instead.
If your Pi isn't critical, then "sudo rpi-update" will get the absolute latest, but that also bumps the kernel to 4.4 which has a few minor issues at present.
Please ensure you apt-get upgrade to get the best from the sensor. Ideally use the 16th May Raspbian update to raspberrypi-bootloader.
I think that covers the main points. If other useful items come out of questions then I'll update that list.
(Updated 10/6/16 as one OV5647 and one IMX219 on the Compute Module is now working).