The interface that argus_camera uses is significantly different so somewhat difficult to change the existing application.
The ioctl and VIDIOC_DQBUF method is used in the “12_camera_v4l2_cuda” and “v4l2cuda” samples so I assume that this method is still somewhat recommended. These samples exhibit the same problem when the frame rate is below 5 fps. Any suggestion on buffering issue through this interface?
My application requires simultaneous capture on three cameras with 12-bit bayer format. The required processing prevents me from directly using the ISP.
If I need to rewrite the front end of the acquisition to this different method, I have a few questions:
Does this API attempt to use the ISP for each camera (which would be a problem for three cameras)?
Any problems with getting the raw 12-bit data?
Does this API have the same 3 image ring buffer issue mentioned in The timestamp of vi5 capture dqueue is always two frames later than capture enqueue.