arv_stream_start_thread() and arv_stream_stop_thread() functions have been
removed in favor of [method@Aravis.Stream.start_acquisition] and
[method@Aravis.Stream.stop_acquisition]. The main difference is acquisition is
not started automatically at stream creation, but should be done afterward. This
maps better with GenAPI, where buffers must be pushed to DataStream objects
before DataStream acquisition is started.
[method@Aravis.Camera.start_acquisition] and
[method@Aravis.Camera.stop_acquisition] do the calls for you, but if you are
using the ArvDevice API directly, you have to call the start/stop acquisition
functions.
xinyuli1204
commented
1 month ago
In official aravis
Acquisition control
right order
arv_stream_start_thread()andarv_stream_stop_thread()functions have been removed in favor of [method@Aravis.Stream.start_acquisition] and [method@Aravis.Stream.stop_acquisition]. The main difference is acquisition is not started automatically at stream creation, but should be done afterward. This maps better with GenAPI, where buffers must be pushed to DataStream objects before DataStream acquisition is started. [method@Aravis.Camera.start_acquisition] and [method@Aravis.Camera.stop_acquisition] do the calls for you, but if you are using theArvDeviceAPI directly, you have to call the start/stop acquisition functions.Camera v1.2
due to hardware issue , libusb_submit_transfer will throw out error.
and we need to do it reversely
reversed order
but arv-tool still use the previous order, so the error still exists when user want to keep using arv tool
Camera v1.0
due to hardware issue , asnc mode is not supported automatically change back to sync mode