Any progress? Are the camera drivers and device tree open source so that we can get more eyes on this?
1 Like
+1 wanted to add my support for this to be doneâŚItâs a great camera, great board, made kind of useless by the fact we canât control it.
Please check here: common_drivers/drivers/amlisp at khadas-vims-5.15.y ¡ khadas/common_drivers ¡ GitHub
Iâve been testing the OS08A10 on the new (NPU) VIM4.
The ghosting problem only seems to happen when the camera is in 1080p mode - it looks fine in 4k.
(Has anyone tested the imx414 on the new VIM4 - does it work better ?)
We also see the problem that v4l2-ctl doesnât work in any useful wayâŚ
@steely-glint I donât seem to have the same luck as you. At both 1920x1080 and 3840x2160 I can see the ghosting. I am in a relatively low light, not out in the bright daylight. However, even when I turn on a bright light I can still see this blurry ghosting but maybe it is a little less.
I am using the command provided above as prescribed by @numbqq :
gst-launch-1.0 -v v4l2src device=/dev/media0 io-mode=mmap ! video/x-raw,format=NV12,width=3840,height=2160,framerate=30/1 ! videoconvert ! waylandsink
I would really like to be able to use this camera considering I bought 3 of them for a prototype application. Now I have buyers remorse.
I played with this camera some more in a bright full sun setting. This ghosting problem is not present in a bright setting. This tells me that the problem is probably related to exposure. In a dark setting the ISP may be allowing the exposure to go higher than the frame rate will allow. At 60Hz the exposure and readout time need to be below 16.6ms, 33.3ms at 30Hz.
Has anyone revisited this? I was just running the camera again the other day and the ghosting problem is definitely still there. I own 3 of these cameras and 3 VIM4, it would be great if they were usable. @numbqq ?
Hello @DoomMonkey
Could you check with the latest 1.7.4 version? We have a patch to fix this issue.
Yes, just confirmed that I do not see ghosting with the latest build 1.7.4.
Did we ever get to the point that we could control these cameras? v4l2-ctl does not appear to make any changes for exposure settings.
We see that it is better then before on our side, do you use it in the dark envoronment? Could you take a photo of it ?
Nevermind the lawn destroyed by corgies. The ghosting problem is gone, but the image feels flat, soft, lacking range. I know this sensor is supposed to be HDR. What is the best way to get higher bit-depth data from the sensor?
Also, I was hoping to have some controls over exposure and other camera parameters much like we do on a Raspberry Pi with an IMX477 or other USB cameras.