lil update out of the agenda because i'm so in love with this project
nevermind the interpolation function between min and max values of a given control. custom definitions of + and - for each one is way better. i even set ExposureTime for the standard 1/250 1/500 ... 1/4000 and beyond
so i'm creating this function where we cycle through these FPS options: 5, 15, 24, 30, 60![:geek:]( "Geek")
heck easy but i also wanted a fps_mode, which we update the camera FPS (at a click, not at a loop) based on ExposureTime. so far so good but i noticed the never gets the right exposure past 16000 (60 fps). the only way to get the actual correct value is by checking for the ExposureTime on my dictionary data. OR start the function withthere's some other way to accomplish that faster? i would like to rely on the camera get metadata instead of my dictionary or this last example...
here's a sneak peek on the camera at 0.06 FPS preview
i was reading my post and i got the idea of why not a loop running this function till the ExposureTime repeats itself (thus reaching the true value set by set_controls)
edit: well, i tried a loop jumping through multiple Exposures in increment but the slower fps = 0.05 to check the thing once feels faster... i opted for limiting this fps_mode at manual modes (ptm (photo manual), tlm (timelapse manual) and vdm (video)). so we can check directly on each mode's dict which contain Exposure, as we rely on that for showing information at the screen
nevermind the interpolation function between min and max values of a given control. custom definitions of + and - for each one is way better. i even set ExposureTime for the standard 1/250 1/500 ... 1/4000 and beyond
so i'm creating this function where we cycle through these FPS options: 5, 15, 24, 30, 60
heck easy but i also wanted a fps_mode, which we update the camera FPS (at a click, not at a loop) based on ExposureTime. so far so good but i noticed the Code:
picam2.capture_metadata()['ExposureTime']Code:
cam.stop()fps = 0.05 # gives time to sensor check Exposure correctly for our maximum exposure of ~ 15 secondscam_config() # configure the cam (shared function among other stuff)cam.start()then the logic of calculating the fps = 1000000 / Exposurehere's a sneak peek on the camera at 0.06 FPS preview
edit: well, i tried a loop jumping through multiple Exposures in increment but the slower fps = 0.05 to check the thing once feels faster... i opted for limiting this fps_mode at manual modes (ptm (photo manual), tlm (timelapse manual) and vdm (video)). so we can check directly on each mode's dict which contain Exposure, as we rely on that for showing information at the screen
Statistics: Posted by luqtas — Wed Jul 30, 2025 11:21 pm