Our default tunings tend to be quite "punchy", mostly because we think that's what casual users tend to like, and that folks who care about such things wouldn't mind tweaking a few settings to better match their preferences. We very much encourage people to do so! On the subject of sharpening, if you still want the block to operate, just a bit more "sympathetically", at a first stab I would set "threshold" to 2.0, and "slope" and "limit" to 0.5 and see how it looks. Note that libcamera has a runtime control called just "sharpness" which you could set to, say, 0.5 and it would adjust exactly those parameters for you in a similar way.
The ISP does quite a lot, but wouldn't say there's any "hidden" processing on the Pi 5 either there or in software. Indeed we've gone to fairly great lengths to describe exactly what it does (see here)! Perhaps that's too much information, but the diagrams on page 18 (the Front End) and pages 64 and 67 (the Back End) give a pretty good idea what's in there.
As I said previously, you can disable other blocks in the tuning file. You probably want to leave black level in there, and the demosaic will be enabled automatically when the software detects a Bayer sensor, but I really don't think there's much else. You can disable stuff programmatically by loading the JSON file and editing it before starting the camera system too, though that's really just doing the same thing.
A lot of this stuff doesn't have runtime controls, because libcamera prefers only to expose what it regards as "standard" camera controls, that can work on any platform. These days, however, there is such a thing as vendor specific controls, sothere could be scope for adding some specialised controls of our own if there were a need.
The ISP does quite a lot, but wouldn't say there's any "hidden" processing on the Pi 5 either there or in software. Indeed we've gone to fairly great lengths to describe exactly what it does (see here)! Perhaps that's too much information, but the diagrams on page 18 (the Front End) and pages 64 and 67 (the Back End) give a pretty good idea what's in there.
As I said previously, you can disable other blocks in the tuning file. You probably want to leave black level in there, and the demosaic will be enabled automatically when the software detects a Bayer sensor, but I really don't think there's much else. You can disable stuff programmatically by loading the JSON file and editing it before starting the camera system too, though that's really just doing the same thing.
A lot of this stuff doesn't have runtime controls, because libcamera prefers only to expose what it regards as "standard" camera controls, that can work on any platform. These days, however, there is such a thing as vendor specific controls, sothere could be scope for adding some specialised controls of our own if there were a need.
Statistics: Posted by therealdavidp — Fri Nov 01, 2024 9:25 am