erik
Thanks for clarification.
Quick question for your non-/blocking statement, "if host-side queue fills up and is blocking, it will start blocking device-side nodes". I believe, in that way, when the host-side queue has available spot, the old data will be sent from device-side queue, because the old data sits there until it gets used. IIRC, this is the case I encountered while using the oak-d poe pro. I didn't like this queue configuration as I only want the latest image data. If my understanding is wrong, please correct me.
Another question. You mentioned that, "(if they are configured to blocking as well)". But, I haven't found a way to configure the queue on device side so far. My understanding is that I only can change the queue's size/ behavior on host side. Please correct me if I am wrong.
I would much appreciate your clarification.
Thank you