<font size="2"><font face="trebuchet ms,sans-serif">its in is personal todo list already ;) <br>I already punish him for that :D <br><br>cheers,<br><br>F.<br></font></font><br><br><br><br><div class="gmail_quote">2011/8/17 Ejner Fergo <span dir="ltr"><<a href="mailto:ejnersan@gmail.com">ejnersan@gmail.com</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 Sergey!<br>
<br>
I was happy to see that you included the sensor patch into Tomato, but<br>
having tried a newer build I see that you made some changes (removed<br>
sensor height and vertical FOV).<br>
<br>
I understand by one of your weekly GSOC mails that you wanted to<br>
simplify the camera data workflow, but I feel disapointed that you<br>
removed the option to acces the vertical FOV ('data.angle_y') through<br>
the camera properties. As I have tried to explain many times on the<br>
patch-tracker, the vertical FOV is important for exporting the camera,<br>
and for importing cameras from other apps. During my tests and writing<br>
the Channel (.chan) importer/exporter, and atleast with FBX (most<br>
likely Collada too), 'data.angle_y' is essential to get the correct<br>
focal length with both export and import. Now this is removed.<br>
<br>
Blender is in many ways a complete pipeline tool, but realistically it<br>
is/will be included in existing pipelines among other tools, and here<br>
sharing camera data is very important, like Blender <-> Nuke (which is<br>
why I wrote the chan script, and hacked on Matt's sensor patch).<br>
Removing these settings (sensor height and thereby the vertical FOV)<br>
seems too much of a sacrifies, to simplify the workflow during<br>
tracking.<br>
<br>
It's fair enough you want to simplify the sensor settings during<br>
tracking, but then why not just include the 'data.sensor_width' in the<br>
camera data settings as you do now, and have both sensor dimensions<br>
(plus angle_x/angle_y) in the camera properties? What is the deal with<br>
removing the sensor_height anyway? If people find these values<br>
confusing, isn't that why we have all these camera presets now? Also<br>
why is there 2 preset folders for camera data?<br>
<br>
I hope you will reconsider the removal of sensor height and vertical<br>
FOV, as this is not just about making camera info seem simple, but how<br>
Blender will fit in mixed software pipelines, and generally be more<br>
complete.<br>
<br>
Sincerly,<br>
<font color="#888888"><br>
Ejner Fergo<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>