<font size="2"><font face="trebuchet ms,sans-serif">I'm using DJV a lot which does have this kind of on-the-fly proxy stuff you can set. </font></font><div><font size="2"><font face="trebuchet ms,sans-serif">Nuke also have this ability where you can set the resolution of the proxy you want to. </font></font></div>
<div><font size="2"><font face="trebuchet ms,sans-serif"><br></font></font></div><div><font size="2"><font face="trebuchet ms,sans-serif">But for tracking, as a rule of thumb, we never downsample the footage, but track on the one which would be final (even if it's 4k and very slow :p). The reason for that is because downsampling could cause some slight shifting in the pixels which would cause a mismatch when applying the solve (which I've been done on the downsampling) onto the final 4K. Might not make a huge difference for most people, but it usually does for the one who is working on it, and we usually try to have a subpixel accurancy. </font></font></div>
<div><font size="2"><font face="trebuchet ms,sans-serif">Actually even the inverse (resample to create a better resolution) is available in most the matchmove packages (Syntheyes for instance has it). I only use it on really poor footages or fast moving camera, because those kind of resample would create thick edges which usually doesn't match the original footage. </font></font></div>
<div><font size="2"><font face="trebuchet ms,sans-serif">On a 64bit computer with 4/6 gb of memory, you can put a few seconds in RAM which is usually enough for tracking. </font></font></div><div><font size="2"><font face="trebuchet ms,sans-serif">I'm sorry if that doesn't sounds very clear :( . tell me if you need more explanation. </font></font></div>
<div><font size="2"><font face="trebuchet ms,sans-serif"><br></font></font></div><div><font size="2"><font face="trebuchet ms,sans-serif">Cheers, </font></font></div><div><font size="2"><font face="trebuchet ms,sans-serif"><br>
</font></font></div><div><font size="2"><font face="trebuchet ms,sans-serif">F.</font></font></div><div><br><div class="gmail_quote">2011/6/7 Peter Schlaile <span dir="ltr"><<a href="mailto:peter@schlaile.de">peter@schlaile.de</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi Sergey,<br>
<br>
you might want to take a look at the vse-proxies branch, which I want to<br>
merge very soon into trunk.<br>
<br>
<a href="http://lists.blender.org/pipermail/bf-committers/2011-May/032152.html" target="_blank">http://lists.blender.org/pipermail/bf-committers/2011-May/032152.html</a><br>
<br>
It's working on ImBuf-level, so you could use it directly in other parts<br>
of blender, if you like.<br>
<br>
Cheers,<br>
Peter<br>
<div><div></div><div class="h5"><br>
> I'm still working under camera tracking integration and need some help.<br>
><br>
> One of goals is to be able to deal with 4K footage. But to deal with it<br>
> fine, there should be some stuff which would reduce resolution to make<br>
> playback faster. Such transparent resolution changing is called proxying in<br>
> our development stuff.<br>
><br>
> So, questions are:<br>
> - How proxying should happen? Should it be slider to specify quality of<br>
> footage or it should be determined automatically using current zoom level,<br>
> space clip size and so?<br>
> - Should it be able to specify tracker which footage to use: original 4K or<br>
> proxied?<br>
> - Should user really care about this proxies or they should be totally<br>
> transparent for him?<br>
><br>
> --<br>
> With best regards, Sergey I. Sharybin<br>
<br>
</div></div>----<br>
<font color="#888888">Peter Schlaile<br>
_______________________________________________<br>
Bf-vfx mailing list<br>
<a href="mailto:Bf-vfx@blender.org">Bf-vfx@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-vfx" target="_blank">http://lists.blender.org/mailman/listinfo/bf-vfx</a><br>
</font></blockquote></div><br><br clear="all"><br>-- <br>____________________<br>François Tarlier<br><a href="http://www.francois-tarlier.com">www.francois-tarlier.com</a><br><a href="http://www.linkedin.com/in/francoistarlier">www.linkedin.com/in/francoistarlier</a><br>
</div>