diff options
| author | Rishikesh Donadkar <rishikeshdonadkar@gmail.com> | 2022-09-15 17:17:33 +0530 |
|---|---|---|
| committer | Umang Jain <umang.jain@ideasonboard.com> | 2022-11-12 00:14:52 +0530 |
| commit | 872588301fe6badb4b22cd8d16ab094753138b52 (patch) | |
| tree | 4937d3e2d471cfec0b7dbca8d54238bbc44a186c /src/py/examples/simple-capture.py | |
| parent | 86735b12ec60567c12305a5231d0aeb3fae218fc (diff) | |
gstreamer: Do not expose the caps before configuring the camera
Configure the camera before exposing the caps valid controls values
(and bounds) are available. These control values might be of interest
to be exposed on the capabilites, which otherwise, would not be
available if the camera is configured after the update caps event.
For instance, the FrameDurationLimits are computed by RPi's IPA in
its configure(). Hence, we need to Camera::configure() to happen in
order to know the FrameDurationLimits, that can be exposed in the caps.
This ties into the framerate support for libcamerasrc which will happen
in a follow-up commit.
Signed-off-by: Rishikesh Donadkar <rishikeshdonadkar@gmail.com>
Signed-off-by: Umang Jain <umang.jain@ideasonboard.com>
Tested-by: Umang Jain <umang.jain@ideasonboard.com>
Reviewed-by: Umang Jain <umang.jain@ideasonboard.com>
Reviewed-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
Diffstat (limited to 'src/py/examples/simple-capture.py')
0 files changed, 0 insertions, 0 deletions