Using latest release 0.8.28 on on Ubuntu 18.04, I did not receive callbacks ARV_STREAM_CALLBACK_TYPE_BUFFER_DONE, however I receive ARV_STREAM_CALLBACK_TYPE_INIT. I realised that default for this release was changed to async and changing back to sync fix the issue. I have libusb 1.0.21.
With 5 buffers pushed, I have these traces:
[17:11:19.193] 🅸 stream-thread> Start async USB3Vision stream thread
[17:11:19.193] 🅳 stream-thread> leader_size = 1024
[17:11:19.193] 🅳 stream-thread> payload_size = 1048576
[17:11:19.193] 🅳 stream-thread> trailer_size = 1024
[17:11:19.203] 🅳 stream-thread> Stream buffer context not found for buffer 0x55bb0fe54150, creating…
Image acquisition started
[17:11:19.226] 🅳 stream-thread> Stream buffer context not found for buffer 0x55bb0fe541e0, creating…
[17:11:19.244] 🅳 stream-thread> Total payload: 15925248 bytes
[17:11:19.428] 🅳 stream-thread> Stream buffer context not found for buffer 0x55bb0fe54270, creating…
[17:11:19.448] 🅳 stream-thread> Total payload: 15925248 bytes
[17:11:19.628] 🅳 stream-thread> Stream buffer context not found for buffer 0x55bb0fe54300, creating…
[17:11:19.647] 🅳 stream-thread> Total payload: 15925248 bytes
[17:11:19.828] 🅳 stream-thread> Stream buffer context not found for buffer 0x55bb0fe54390, creating…
[17:11:19.847] 🅳 stream-thread> Total payload: 15925248 bytes
[17:11:20.048] 🅳 stream-thread> Total payload: 15925248 bytes
There is nothing wrong in the traces. Stream buffer context not found for buffer 0x55bb0fe54150, creating… is expected for each buffer you pushed. What is the output of arv-camera-test-0.8 --duration=5 -d all ?
I know that the traces are correct, but my understanding is we receive images and I’m expecting the stream callback to be called with ‘buffer done’ but it is not.
For camera-test, I can not give you the output now as I’m no longer in the office, but it was working. However it registers the callback differently as a kind of slot.