This seems to be a 6.4 x 4.8 mms sensor, so it's 6.4 mms for film width. When you use 26mm as focal width it should produce the given fov.
However, if you want to be on the safe side use 78.8 degs for fov instead of focal width since this is what the lens effectively sees.
As for matching... not sure but I guess matching apps should be able to use exif data correctly nowadays and have a lens database to correct for any distortion. In any case, don't use Photoshop's correction, it crops images (changing the effective fov) and produces wrong results if the lens is not included in their database. I would go without any lens correction and only try if the match is obviously wrong.
Thank you! Well, so now I know that this 1/2.3" sensor should go into the Filmd Width slot. But I still don't understand the relation of it with the other values (FOV and Focal Length). At first, I inserted the 78.8° in the FOV of my CoronaCamera, like the drone specs told me, but the matching was wrong. So with a little help of the Perspective Match tool in 3DS Max I was able to get a very good matching. But the surprise is that the resulting FOV was around 65°.
But then I inserted the Filmd Width of 6.4mm like you told, based on the sensor. I know this will only affect the DoF, not the projection, so it makes no difference for me now, but somehow, when I modify the Film Width with my FOV selected and setted, the greyed out Focal Length changes to around 5mm. I don't understando very well the relation between those values, how one affects the others. And if I'm using the FOV option, the greyed out Focal Length has no influence in the camera, right?
If you can point me to some docs or tutorials that explain this better, I would appreciete. Been getting a lot of jobs lately that require real footage matching, for stills and animations.
Show Posts