Currently the receiving thread of the device is completely independent and uncoupled from the processing pipeline. Both of them run different frame rates and the messages are lying in the buffers. The latter causes a major latency in the whole pipeline. By emitting a message received event the pipeline update process could be triggered which reduces the buffer time to a minimum. However, this couples the two threads and I dont know if that is thread safe.
Description
Description
Event Timeline
Comment Actions
Hi there! 🙂
This task was auto-closed according to our Task Lifecycle Management.
Please follow this link for more information and don't forget that you are encouraged to reasonable re-open tasks to revive them. 🚑
Best wishes,
The MITK devs