You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After further analysis I have found out that the problem comes with the release 1.11.
If you want to get the current sensor_mode with camera.sensor_mode it always returns 0 but the method configure_camera(...) is correctly invoked and sets the given sensor_mode. It seems so that the parameter MMAL_PARAMETER_CAMERA_CUSTOM_SENSOR_CONFIG is wrong, but on the same firmware with release 1.10 it's working.
After the upgrade from version 1.09 to 1.12 has setting the
sensor_mode
no effect anymore (same behavior on 6 pi's).Example:
If I take a picture with
raspistill
it's working (raspistill -w 1920 -h 1080 -md 2 -o test.jpg
).Problem on:
4.4.20-v7+ #908 SMP Wed Sep 7 14:44:27 BST 2016 armv7l GNU/Linux
(Raspberry 3)4.4.20+ #908 Wed Sep 7 14:35:04 BST 2016 armv6l GNU/Linux
(Raspberry B, B+, 2)Edit:
sensor_mode
has only no effect if the parameteruse_video_port
with the valueTrue
is given.The text was updated successfully, but these errors were encountered: