Hey all. Trying to set up my webcam with v4l2 settings to throw into crowsnest to stop swinging the exposure so aggressively when my LEDs turn on and off just for nicer stuff on startup. However whenever I set exposure_auto=1 and exposure_absoulte=X (x=any number I was using 99 for my use case but any number does it) I get what looks like a conflict between the FPS and the webcam's refresh cycle as shown in this GIF. Is there something I configured wrong? I have also included the -l output as a screenshot because neither CMD or Powershell handle whitespace on copy well thanks Winblows.
#Webcam bars when setting exposure
28 messages · Page 1 of 1 (latest)
you can set your power line frequenz. you just see your light...
I figured since this only started happening when I tried to manually set exposure that that wasnt what was going on.
Like if I swap it back to auto exposure 3 it goes away. And changing power line freq to 2 for USA's 60hz does not change the video output.
I am sure you using led and use pwm for them so you need to match these both. It could be that 50Hz work better
Okay but if that was the case my initial post shows that the settings were using Freq=1 which is 50
what do you mean by PWM affecting it? i am running these LEDs at 50% because 100 is just way too much light
my cycle_time is currently 0.01
That flickering is quite normal especially if you start playing around with exposure. And as your led have there own frequency it does not matter where you live
So you could try to change that to 0.02 (50Hz) or 0.01667 (60Hz) and see if it gets better
You can not go faster for a software based pwm pin
well........ that did solve the flickering problem I set both the LED and the Camera to 60Hz but it seems like it isnt properly taking the values I set in the config for the exposure_absolute. I tried setting it to 99 and I just keep getting different random values when I restart crowsnest.
v4l2ctl: focus_auto=0,focus_absolute=50,power_line_frequency=2,exposure_auto=1,exposure_absolute=99
exposure_auto 0x009a0901 (menu) : min=0 max=3 default=3 value=1
1: Manual Mode
3: Aperture Priority Mode
exposure_absolute 0x009a0902 (int) : min=3 max=2047 step=1 default=250 value=312
Let’s bet it’s a Logitech C9xx cam?
920 yeah
We still debugging it https://discord.com/channels/758059413700345988/1064030033552867358
It seams that Logitech cams have problem with that and need special treatment. There are also reports in the internet about that
well thats weird since doing it manually through the CLI works seemingly without issue
although
if I try doing it through the CLI the bars return
just very slowly moving down the image instead of quickly
Yes we know 🙈. It seams to have to do when you do it relative to starting the stream
so long story short better off just sucking it up and using auto exposure and dealing with that
Currently yes
😦 ok