<div class="gmail_quote">On Mon, May 9, 2011 at 1:25 PM, Sergey I. Sharybin <span dir="ltr"><<a href="mailto:g.ulairi@gmail.com">g.ulairi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#ffffff" text="#000000"><div class="im">
<small>Ton Roosendaal wrote:</small><br>
<blockquote type="cite">
<pre>- allow realtime playback of clips
(could become "Render -> Play Anim" as well)
</pre>
</blockquote>
</div><small>Not sure what does it mean (about Render -> Play anim).</small><br>
<br>
<small>And I've been imaging quite the same picture (except
curves/masks. haven't thought about them much due to tried to
solve more "nearest" issues).<br>
<br>
I'm trying to understand which data libmv supports/requires,
where/how it sohuld be stored and so on to prepare more detailed
data structure schema. Also, investigation of current codebase is
still in progress. Maybe something could be re-used.</small></div></blockquote><div><br></div><div>For now, just a void* marker_data will do the trick. I plan on reorganizing the libmv 2D tracker code this weekend, so this will change anyway.</div>
<div><br></div><div>At a high level, what libmv will need for each frame is a "preprocessed" version (which libmv can compute) that has e.g. the image filtered with edge detectors and whatnot. Each bundle (not just marker) typically has a image patch ("pattern") associated with it that is from the first frame of that track.</div>
<div><br></div><div>Keir</div></div>