[Bf-vfx] Tomato camera sensor changes

[François T.]

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.

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

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.
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.

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.

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)


F.





2011/10/19 Brecht Van Lommel <brechtvanlommel at pandora.be>

> Hi all,
>
> I think it would be good to get the full sensor size patch in 2.61 and
> I can review it, Sergey can concentrate on the tracking aspect of it.
> After trying the full patch and reading this thread, it leaves me with
> some questions though.
>
> There's this patch from the tomato branch, which has just the sensor
> width. Even there it's confusing me as it seems it's actually the
> sensor height when rendering in 'portrait' instead of 'landscape'
> aspect ratio. Is this the intended behavior, and if so, why?
> http://codereview.appspot.com/5274047/
>
> I don't object to a sensor height property that doesn't affect blender
> internal. The resolution gate image linked here explained to me why it
> can be useful, and  especially if it can be visualized in the
> viewport. But I don't understand how it's correct to use the sensor
> width as sensor height in some cases, I'm trying to understand if it's
> a particular case of resolution gate fitting but I don't see it. How
> would you export the 'portrait' case to get matching renders in other
> applications?
>
> Brecht.
> _______________________________________________
> Bf-vfx mailing list
> Bf-vfx at blender.org
> http://lists.blender.org/mailman/listinfo/bf-vfx
>



-- 
____________________
François Tarlier
www.francois-tarlier.com
www.linkedin.com/in/francoistarlier
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-vfx/attachments/20111019/2fad047e/attachment.htm