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
In the initial Sensor Settings, Absolute Exposure Time is adjustable while the Auto Exposure Mode is aperture priority mode (Absolute Exposure Time should not be adjustable in this case).
If the Auto Exposure Mode is switched to other mode and then switched back to the aperture priority mode, Absolute Exposure Time is then no longer adjustable.
If the Auto Exposure Mode is switched from aperture priority mode to manual mode, the value shown above the Absolute Exposure Time slider is not automatically applied to UVC until some setting (e.g. Resolution, Frame rate...) is reconfigured.
shutter priority mode and auto mode are actually not valid Auto Exposure Modes. If one just click on one of those, there is warning message, but the Auto Exposure Mode Selector still shows the invalid mode, instead of the current actual Auto Exposure Mode. This may be misleading.
The text was updated successfully, but these errors were encountered:
In the initial Sensor Settings,
Absolute Exposure Time
is adjustable while theAuto Exposure Mode
isaperture priority mode
(Absolute Exposure Time
should not be adjustable in this case).If the
Auto Exposure Mode
is switched to other mode and then switched back to theaperture priority mode
,Absolute Exposure Time
is then no longer adjustable.If the
Auto Exposure Mode
is switched fromaperture priority mode
tomanual mode
, the value shown above theAbsolute Exposure Time
slider is not automatically applied to UVC until some setting (e.g. Resolution, Frame rate...) is reconfigured.shutter priority mode
andauto mode
are actually not valid Auto Exposure Modes. If one just click on one of those, there is warning message, but theAuto Exposure Mode
Selector still shows the invalid mode, instead of the current actual Auto Exposure Mode. This may be misleading.The text was updated successfully, but these errors were encountered: