My MNT camera arrived today and wow is the fish eye lens cool!
Like every other MNT product I’ve received so far, the build quality is superb and I’m super satisfied.
That being said, I’m only getting 640x480 resolution although the product page says the resolution should be 2592x1994.
I tried to change the resolution of the camera using this command: v4l2-ctl --device=/dev/video1 --set-fmt-video=width=2592,height=1994.
When I run lsusb and inspect the device it’s only showing it’s capable of 640x480 as well, so it makes sense that the above command wouldn’t work.
FWIW I did use the USB cable the camera came with, and tried on a CM4 reform, LS1028A reform, and standard intel workstation also running debian.
I realize that with USB 2.0 the resolution may be lower, but I’d still expect to get something greater than 640x480. I did try with both 3.0 & 2.0 ports. Assuming the cable it came with is 3.0.
If anyone has encountered this as well / has suggestion please let me know. Once again, super cool product, and can’t wait to use it during work calls.
Furthermore, I’m curious about the pixel format / how to rotate the image. I had to flip the webcam upside down as the mount it comes on doesn’t expect the camera to be tilted much. This is fine on the reform, but when using it on my main monitor I need a more aggressive tilt.
Another bit of feedback / question is why does the camera light stay on even when I’m not using it? It’s fine, but a bit distracting. I don’t want to have to go an unplug it each time I don’t want the light on.
Alright, was able to flip the image with this command.
Surprisingly google meets picks up the dummy device and it can be selected. Seems like it will be app specific, but for now that is good enough for my use-case.
About the low resolution, this normally happens if a USB3 connection cannot be established and it falls back to USB2. Do other USB3 devices work on this machine and are recognized as SuperSpeed devices (you can see that in dmesg or with lsusb -v)? Please note that RCM4 is USB2 only.
About the LED, it is hardwired to the power of the camera for security reasons. That way you know when the camera is powered and it cannot be masked in software.
Actually never-mind. It’s still frozen after a short period of time again. False alarm. If anyone else has one of these things and encounters this let me know.
Also happy to dump logs, but not sure what to share.
Alright, it seems that it only happens when the resolution is over 1920x1080p. At least after leaving cheese on for the last hour or so set at that resolution, the issue doesn’t happen.
I’ll try to manually set the resolution using the v4l2 command to 1920x1080p. However, it would be great to use the full resolution and actually make use of the fish-eye affect.