<br><br><div class="gmail_quote">On Fri, Oct 21, 2011 at 3:38 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 class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
That the sensor_width becomes sensor_height in portrait, is as<br>
Francois writes,</blockquote></div><div><br>NO ! I was actually saying that the sensor width NEVER becomes the sensor height. portrait mode is a rotation of the camera itself. You should never intervert those parameter<br>
</div></div></blockquote><div><br>I'm not convinced by this reasoning (any time the sensor height > width represents a camera rotation). Firstly not all camera formats are landscape - some are square, some are portrait. We're not just talking about tracking here (which I agree most of the time is done with landscape formats), but we're talking about blender's camera model in general, and this should be more flexible. I should be able to use blender to match output from my 6x6 mamiya or my half-frame olympus pen! ;)<br>
<br>The other thing is that bringing the idea of a camera rotation into blender's camera model complicates and confuses the issue - rotation is a property of the object and has nothing to do with the lens/film back.<br>
<br>If my memory is correct, the main reason this is up for discussion is because of a (mostly convenient) peculiarity of blender, where the aspect ratio is determined by the resolution, and decisions are made in the camera model based on what edge (vertical/horizontal) of the final frame is longer. I think it would be better to just make this explicit, with 3 FOV calculation modes:<br>
* Auto - the default, same as is now<br>* Horizontal priority - always use horizontal sensor size for FOV calculation<br>* Vertical priority - always use vertical sensor size for FOV calculation<br></div></div><br>This could probably affect what is editable in the UI too - if Horizontal priority is selected, the vertical sensor size could be greyed out, and vice versa.<br>
<br>cheers<br><br>Matt<br>