Page 1 of 1

FOV in detail description of .pano file

PostPosted: Wed Sep 28, 2011 10:43 am
by vklaffehn
Hi!
When rendering a large pano to KRO RAW, there's no metadata for PTP, and to find out the FOV of the Pano I have to open it in APG again, but 'unimportant' details like used blender etc. can be seen if i rightclick the pano file and look at the details... Maybe it's possible to add the FOV there, too?

MfG
V.Klaffehn

PostPosted: Wed Sep 28, 2011 12:21 pm
by AlexandreJ
If you are on windows, the shell extension parses the .pano and display these information as tooltips.
You can also open the .pano with a text editor and you'll find something like that :

<Projection>
<Type> 2 </Type>
<ThetaMin> -0.802458 </ThetaMin>
<ThetaMax> 0.802458 </ThetaMax>
<PhiMin> -0.347454 </PhiMin>
<PhiMax> 0.288683 </PhiMax>
<FitMode> 1 </FitMode>
</Projection>

Type -> projection mode
ThetaMin/Max, PhiMin/Max => fov

PostPosted: Wed Sep 28, 2011 12:45 pm
by vklaffehn
Hi!

I attached screenshots of what I can get out of my pano file. Opening it in a texteditor and calculating the FOV is a possibility, but it's not really faster than opening it in APG and just look :-) As you can see theres nothing shown about the FOV on my system, oh just found a bug? In my screenshots it says 'planar projection' but it's spherical?

btw. I'm using APG 2.6b2 on intel Q8200 with 8GB RAM and NVIDIA GTX460

PostPosted: Wed Sep 28, 2011 1:09 pm
by AlexandreJ
Oups. Sorry. The shell explorer doesn't display the fov. But when opening the .pano with autopano, it does, of course : 77.65° horizontal by 45.88° vertical.
You'll still need to vertical offset which is (phiMax-phiMin)/2. You can calculate this value by opening the editor, and in the status bar, you'll have phiMax and phiMin.

PostPosted: Wed Sep 28, 2011 1:23 pm
by vklaffehn
No Problem .-)

I found an easy way, just ad %f to the filename in the renderer, as far as I see it will append the FOV and also the vertical offset.

thanks alot!

Btw., I dehazed the 806 images, now image quality is much better, and for the fun of it I imported the images through the gigapan importer in APG 26b2 and 2.5.2, with (as far as I know) identical settings, and in 2.5.2 I have a RMS of 3.93 and in 2.6b2 its above 10? I also discovered a heavy alignmend error somewhere and a single missrotated ble sky image in 2.6b2?

PostPosted: Wed Sep 28, 2011 1:49 pm
by AlexandreJ
Yes, 2.6 beta 2 has a lot of issues and this is one of them.