-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v4l2ctl:
Parameters being skipped, even though the device supports all parameters
#284
Comments
You are just using it wrong. In our docs you can find an example: https://crowsnest.mainsail.xyz/configuration/cam-section#v4l2ctl |
I'm not trying to change it something other than MJPG, I'm trying to change it to something other than YUYV. I do have |
How should I be using it then? ustreamer is in JPEG format, yet v4l2ctl is stuck in YUYV and I'd like to change it to MPJEG, using
|
Please use the appropriate channels for help. Either our discussions or our Discord. |
It doesn't matter in what |
What happened
When setting
v4l2ctl:
to--device=/dev/video0 --set-fmt-video=width=1920,height=1080,pixelformat=MJPG
orwidth=1920,height=1080,pixelformat=MJPG
crowsnest skips over the parameters with a "not available for" in it's logsThe width, height, and pixel format are all supported according to
crowsnest.log
Yet for some reason the parameters are skipped and my logitech c920 remains stuck in YUYV pixel format, nothing in my
v4l2ctl:
appears to work.When using
v4l2-ctl --device=/dev/video0 --set-fmt-video=width=1920,height=1080,pixelformat=MJPG
directly while crowsnest is stopped, v4l2-ctl accepts it and my C920 is configured as expectedWhat did you expect to happen
Logitech C920 v4l2 configuration switching to the passed flags in the
v4l2ctl:
config fieldHow to reproduce
v4l2ctl:
to something basic/simple, like changing the pixel formatAdditional information
Almost seems like crowsnest is parsing what only the capabilities of what the camera is currently set to, YUYV only supports 5fps for my camera
The text was updated successfully, but these errors were encountered: