There are OS projects that try to make universal camera sensor profiles that work with multiple ISPs (libcamera for one), but it is still early days. In addition every single ISP has its own proprietary format for those profiles. The modern ISP is a "black box" even with source code for the drivers. I wanted <20ms as I could encode 720p h264 frames in 7ms,unfortunately I got stuck with ISP (image signal processor) adding 40ms of latency even when in pass through mode. I needed high fps video (I managed to get 120fps 720p - I think I could push it further to 140 perhaps, but this was OK for now) and as low latency as I could get. I've spent few weeks of my (spare) time improving a Sony imx219 driver for a Rockchip rk3566 cpu that is used in few pine devices I own.
Without a very good profile even a good camera sensor output will look like crap. The profile specifies how to debayer, denoise, sharpen, color correct, adjust brightness and autofocus of the chip.
It is a proprietary component that is essentially a black box controlled with a "profile" for specific camera chip.
ISP is an imaging signal processor, a component of most mobile SOCs that sits between the camera and the rest of the system. The reason why modern smartphones have such good camera picture quality is primarily thanks to the ISP profiles developed by teams of people for the particular sensor in use.
0 kommentar(er)
