<br><br><div class="gmail_quote">On Wed, Oct 5, 2011 at 7:55 AM, François T. <span dir="ltr"><<a href="mailto:francoistarlier@gmail.com">francoistarlier@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br><div><font color="#666666" face="'trebuchet ms', sans-serif">Gray flow : </font></div><div><font color="#666666" face="'trebuchet ms', sans-serif">it could be use when you are not planning on doing much compositing at the end or very thigh schedules :p. </font></div>
<div><font color="#666666" face="'trebuchet ms', sans-serif">I guess this would use some sort of Lens Shader in the render engine (pretty much like did LaMaison porting 3DEqualizer lens model to MentalRay for XSI <a href="http://www.alamaison.fr/3d/lmWarpDistort/lmWarpDistort.htm" target="_blank">http://www.alamaison.fr/3d/lmWarpDistort/lmWarpDistort.htm</a>)</font><br>
</div></blockquote></div><br>Honestly, I wouldn't even bother talking about this case. Lens distortion should be done in comp - coding resources will be better spent on implementing reliable overscan rendering with proper implementation of separated display windows/data windows throughout the pipeline.<br>
<br>Matt<br>