<div><font size="2"><font face="trebuchet ms,sans-serif">once again about all the hidden parameters (height, image ratio, ...) , I still don't see the big deal of having them. at least accessible via API if you don't want it in the UI, so people who wants it, needs it for any reason we have mention (export, check values, import, blablabla,...) can make his tool and everybody is happy. </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">landscape or portrait, the width is the still the width (x axis of the camera sensor in the space of the camera), you turn the camera, you don't "turn" the sensor the camera</font></font></div>
<font size="2"><font face="trebuchet ms,sans-serif"><div><font size="2"><font face="trebuchet ms,sans-serif"><br></font></font></div>concerning the presets. Everything is saved (filmgate, focal, distortion) which at some point does make sense, since you would probably more likely create lens profile rather than camera profile.<br>
But right now, the design of the preset is only suited for prime lens. Maybe it would be better to make it work for zoom lens as well, meaning one profile contain several focal and for each focal there is a distortion value.</font></font><div>
<font class="Apple-style-span" face="'trebuchet ms', sans-serif"><br></font></div><div><font class="Apple-style-span" face="'trebuchet ms', sans-serif">To create a zoom profile you would take videos at different step of focal (24mm, 28mm, 30mm, ... 70mm). then compute distortion for each step. This will give you a graph of the distortion (interpolation) so you would have some kind of approximation of distortion of in-between. (which you might even refine, when you computed the lens correctly and want to fine tune the distortion a little bit.</font></div>
<div><font size="2"><font face="trebuchet ms,sans-serif">
<br>otherwise it could be pending until tomato supports zoom lens, but I figure it might be better to do it in the first place. (not really the topic, but I lost the mail with the code review) </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"><br></font></font></div><div><font size="2"><font face="trebuchet ms,sans-serif">F.<br><br><br></font></font><div><font size="2"><font face="trebuchet ms,sans-serif"><br>
</font></font></div><div><font size="2"><font face="trebuchet ms,sans-serif"><br>
</font></font><br><div class="gmail_quote">2011/10/19 Brecht Van Lommel <span dir="ltr"><<a href="mailto:brechtvanlommel@pandora.be" target="_blank">brechtvanlommel@pandora.be</a>></span><br><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
Hi all,<br>
<br>
I think it would be good to get the full sensor size patch in 2.61 and<br>
I can review it, Sergey can concentrate on the tracking aspect of it.<br>
After trying the full patch and reading this thread, it leaves me with<br>
some questions though.<br>
<br>
There's this patch from the tomato branch, which has just the sensor<br>
width. Even there it's confusing me as it seems it's actually the<br>
sensor height when rendering in 'portrait' instead of 'landscape'<br>
aspect ratio. Is this the intended behavior, and if so, why?<br>
<a href="http://codereview.appspot.com/5274047/" target="_blank">http://codereview.appspot.com/5274047/</a><br>
<br>
I don't object to a sensor height property that doesn't affect blender<br>
internal. The resolution gate image linked here explained to me why it<br>
can be useful, and especially if it can be visualized in the<br>
viewport. But I don't understand how it's correct to use the sensor<br>
width as sensor height in some cases, I'm trying to understand if it's<br>
a particular case of resolution gate fitting but I don't see it. How<br>
would you export the 'portrait' case to get matching renders in other<br>
applications?<br>
<font color="#888888"><br>
Brecht.<br>
</font><div><div></div><div>_______________________________________________<br>
Bf-vfx mailing list<br>
<a href="mailto:Bf-vfx@blender.org" target="_blank">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>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>____________________<br>François Tarlier<br><a href="http://www.francois-tarlier.com" target="_blank">www.francois-tarlier.com</a><br><a href="http://www.linkedin.com/in/francoistarlier" target="_blank">www.linkedin.com/in/francoistarlier</a><br>
</div></div>