Emmanuel Pacaud
Emmanuel Pacaud
In libusb async mode, the reported number of underruns is systematically high. This is because the async thread asks for buffers before actually receiving data, unlike the sync code. May...
Randomization of test order can help to detect strange camera behaviour or camera configuration issues in the ArvCamera helpers (set_trigger, set_frame_rate...)
In arv-test, we should add a test that exercises the Genicam range check feature. As for cache policy, we probably needs an API that reports the number of failed check...
Documentation does not make clear the API in arv.h is not thread safe.
Being either in the stream callback, or in the new-buffer signal callback.
We should be able to easily set a persistent IP address easily using arv-tool. It is probably possible currently, but by setting manually the right features.
arv_gv_device_auto_packet_size doesn't work with this device, while GevSCPSFireTestPacket seems to be supported and to work at least once: ```sh Sources/aravis/build on wip/packet-size-check [$] took 3s ❯ ./tests/arv-camera-test -d device...
See https://aravis-project.discourse.group/t/stability-and-the-0-8-release/110/2
Explanations here: https://aravis-project.discourse.group/t/port-knocking-for-streaming-from-different-subnets/113