while working/improving on some tracking patches for interactive tables i discovered that there are severall sources for a bad latency. to test latency of the vvvv-freeframewrapper i tried to chain up a freefframedummie that does nothing, it just passes the videosignal. result: latency keeps low as long you just use one or two chained plugins. with the third an forth plugin the latency becomes worse noticeable.
this is the node chain i played around with:
the final tracking patch(or engine) should be able to work on diffused illumination so stuff like blur, dillate/errode, highpass and contour tracker is needed.
-what is the best way to keep latency low?
-where does that latency come from? is the ffwrapper itself somehow inneffecient? or is it something in the plugincode?
-is it a good idea to keep all the imageprocessing in one freeframeplugin? i mean a combined plugin which does the filtering plus the tracking i one go…
-is it possible to bypass the freeframewrapper by writing directshow filters (like the undistortion one) for the tracking. how would that compare in performance/latency to freeframe?
other things/problems to consider?
-would it be possible to do the tracking as a csharp plug? i know that it isnt possible to pass textures or videostreams to v4, but that isnt necessary right? just pass the values of the tracker over…
lots of questions, hope that someone can help to clear up things