[Bf-committers] Sensor Size

[Matt Ebb]

Hi guys, sorry to have not been keeping track of this stuff, I've been busy.
I'll try to make time to look at the updated patch on the weekend
(hopefully). As far as I can see right now from a cursory glance, all that's
needed is to make blender's internal camera respect the vertical/horizontal
FOV settings - from memory right now it's done automatically based on the
longest render dimension.

btw, this pixel space focal length is a bit of a red herring - it's
unecessary for blender and is a bit of a distraction from the issue at hand,
which is making it possible to convert real world lens units into a final
FOV inside blender.

cheers

Matt


On Wed, Jun 15, 2011 at 2:26 AM, Lars Krueger <lars_e_krueger at gmx.de> wrote:

>
> > @Lars
> >
> > Hi again!
> >
> > > Yes, it does: The sensor size that is currently fixed at 32 units.
> > Otherwise we already have all the data:
> > > - image size (nx,ny) are required for the size of the output image
> > > - focal length (f) is a property of the camera
> >
> > This patch only adds a variable sensor size, and changes the focal/fov
> > accordingly. So to me it looks like adding the variable sensor size
> > (dx/dy) is the first step to implement focal length units in pixels.
> > Or am I missing the point?
>
> Input info should be all there now. Depending on how the rest of the
> projection code is implemented you're either done or have to change all
> computations that use the focal length.
>
> Simple test: make a test scene, double the image size and leave everything
> else constant. The object in the image should be half as wide/high as before
> because all you pixels increased in size.
>
> --
> Dr. Lars Krueger
>
>
> Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
> belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>