Intel® Integrated Performance Primitives
Deliberate problems developing high-performance vision, signal, security, and storage applications.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
6814 Discussions

Splitter::SetTimePosition and need to flush frame data

franknatoli
New Contributor I
‎09-16-2008 02:54 PM
383 Views
It appears that Splitter::SetTimePosition does not completely flush the video frame pipeline. I observe that GetNextData after SetTimePosition obtains at least one more video frame from the time sequence prior to the SetTimePosition change. The next call to GetNextData gets a video frame correct for the SetTimePosition change.

Is this indeed how SetTimePosition and GetNextData are expected to behave?

Is there any way to completely flush out of sequence data after calling SetTimePosition?

This is not an academic problem. My application implements synchronization of multiple concurrent streams. If a reposition is requested, but an out of sequence frame is obtained, the code will sleep until the master synchronization clock catches up to the out of sequence frame. This is undesirable behavior. But there appears to be no way to tell which video frames originated before SetTimePosition and which originated after.

Thanks for your time.
0 Kudos

Link Copied

0 Replies
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.