Skip to main content

A note of mental ray/iray camera terminology.


The original mental ray camera is a pinhole camera. Therefore, some of the terminology differs with a normal camera. I will write them down here.

aperture: This is the film width size. This has no relationship with lens aperture/opening. mental ray's camera was a pinhole camera, there is no lens aperture.

focal: This is the distance from lens to the film (sensor). Pinhole camera always focused, so there is no focal length meaning. But using parameters aperture and focal length, we can compute the horizontal field of view. I think these two parameters exist for this purpose.

aspect ratio: This is film(sensor)'s aspect ratio. There is no relationship with pixel resolution and camera geometry.  aspect ratio = film width/film height. Note: If we use aperture, focal, and aspect ratio, we can compute the vertical field of view.

mental ray/iray camera model (pinhole camera) without lens shader


Current mental ray/iray can have depth of field effect, etc., this terminology is confusing. For the depth of field effect, some lens shaders have parameters like lens_radius and focus_plane_distance.

I recommend to read Andy Kopra's Writing mental ray Shaders, chapter 24 to know about the camera model.

By the way, mental images has completely integrated with NVidia. (http://www.mentalimages.com) The name, mental images, has been changed to NVidia ARC (NVidia Advanced Rendering Center).

At this year's SIGGRAPH, NVidia announced they will support the mental images products (http://www.nvidia.com/object/siggraph-2011.html) and enhance the products with more GPU/cloud support. But, it is a bit sad for me that there is no company called mental images anymore.

Comments

Popular posts from this blog

What is mental ray shader?

mental ray shader is C/C++ code that is invoked by the mental ray core when a ray hits an object. The name ``shader'' is used by hysterical reason, I think ``Plugin'' is much better word nowadays. mental ray shader gives us a lot of freedom for users, but, I think we do not need to write a custom shader in most of the cases. The meaning of 'gives us a lot of freedom' is when a ray hit an object, a user could almost everything by a shader. For example, when a ray hit an object, mental ray can send an email from the shader. (I believe that mental ray designer does not recommended this kind of side effect usage, but, a shader is just a plugin and it should be possible.) You can do anything means also it is difficult to handle the shaders. mental ray was developed for a long time and takes care of backward compatibility, this contributed for its complexity.

Using stand alone mental ray

If you render a scene using Maya, 3dsMax, XSI, and so on, you can skip this part of article. If you have your own shaders or you are managing a render firm, then this might help you a bit. References of mental ray The following mental ray references are the important ones. Thomas Driemeyer, Rendering with mental ray, 3nd Ed. (Mental Ray Handbooks 1), ISBN-13: 978-3211228753 Thomas Driemeyer and Rolf Herken, Programming mental ray, (Mental Ray Handbooks 2), ISBN-13: 978-3211838518 Andy Kopra, Writing Mental Ray Shaders: A Perceptual Introduction (Mental Ray Handbooks 3), ISBN-13: 978-3211489642 These are advanced documentation and there are some more introductory documents around. Among these three books, I think Andy Korpa's book is easier to read. There is also a support page of the book http://www.writingshaders.com/ . Getting mental ray In my case, I use mental ray at my company. Therefore, I have no problem to get mental ray. However, if you want to have mental ray in private,