Closed zlorfi closed 3 years ago
Your journalctl log contains information about available video controls and mapping between v4l2 and UVC.
camera control V4L2_CID_BRIGHTNESS is available and is mapped to UVC_PU_BRIGHTNESS_CONTROL V4L2: Supported control Brightness (V4L2_CID_BRIGHTNESS = UVC_PU_BRIGHTNESS_CONTROL)
range of values available for V4L2_CID_BRIGHTNESS V4L2: V4L2: min: 0, max: 100, step: 1, default: 50, value: 50
range of values propagated to host computer if UVC_PU_BRIGHTNESS_CONTROL is requested. V4L2: UVC: min: 0, max: 100, step: 1, default: 50, value: 50
If host computer need to change brightness, then tou can see in log messages like this - UVC: PROCESSING_UNIT - GET_CUR - UVC_PU_BRIGHTNESS_CONTROL UVC: PROCESSING_UNIT - GET_CUR - UVC_PU_BRIGHTNESS_CONTROL UVC: PROCESSING_UNIT - SET_CUR - UVC_PU_BRIGHTNESS_CONTROL UVC: Control CONTROL_UNDEFINED, length: 2 DEVICE_UVC: V4L2_CID_BRIGHTNESS changed value (V4L2: 54, UVC: 54)
Your journalctl doesn't contain a message like "DEVICE_UVC: V4L2_CID_BRIGHTNESS changed value (V4L2: 54, UVC: 54)", so uvc-gadget don't change brightness.
I'm encountering the same problem. Other settings in the camera.txt are being honored, but the 'brightness' value is ignored. I have to set it manually using the serial interface each time I connect the webcam.
In branch new-code https://github.com/peterbay/uvc-gadget/tree/feat/new-code is now added argument -z for ignoring controls from v4l2 source device and host computer.
After writing
/boot/camera.txt
withthe
auto_expose_bias
value is being honoured, but not thebrightness
value.Any idea how to fix this problem? In order to have the brightness at
55
after a reboot, I have to set it manually via/usr/bin/v4l2-ctl -c brightness=55
which seems to work until the next reboot.This is the
journalctl
output:I see, that the brightness is being set, but the output stays the same at 50.