We "know" that gstreamer supports different modes for synchronization and queue handling.
However, soon, we will need deep understandings in this area.
Some people (at least two! :) ) should be familiar enough with this topic so that he can let us know how to:
construct stream pipeline with queues or inter-element connections dropping frames whenever "next" frame comes while the "previous" frame is still being processed.
at tensor_mux or tensor_merge, use the most recent tensor frame for each sink-pad, dropping any "obsolete" frame and keeping "recent" frame EVEN if it is already processed and sent away to next element.
Issue by myungjoo-ham Thursday Jul 26, 2018 at 11:40 GMT Originally opened as https://github.sec.samsung.net/STAR/nnstreamer/issues/349
We "know" that gstreamer supports different modes for synchronization and queue handling.
However, soon, we will need deep understandings in this area.
Some people (at least two! :) ) should be familiar enough with this topic so that he can let us know how to: