lumelix wrote:Hi
I try out something with the papywizard import module and found a funny thing:
The two images above are in landscape orientation but you shoot them in portrait orientation.
It's because you have deactivated the camera inclination sensor.
Now if I rotate them directly into the papywizard module then I get a completely wrong FOV and focal lenght in APG. It calculates over 300 mm focal lenght and the FOV is much to small for a 20mm WW.
If I import the images as they are and rotate the pano into APG everything looks ok. FOV is 100º and focal lenght is above 20mm.
lumelix wrote:Hi Klaus
For selecting the images in Papywizard Module do you use the system fileexplorer or the one of APG ?
I have seen that there is a new option in the settings "Allgemein - Thema" where we can select this.
I use always the system fileexplorer.
Then there is an Option while installing to install APGs file context functions in the fileexplorer.
I don't do this because I don't use context functions for APG.
Maybe this can have an influence how APG is "reading" the input files?
The best will be to clean install APG on one machine and then test it again
lumelix wrote:Hi Klaus
What I will say with this is that it seems that there is going something wrong in the papywizard import tool when rotating there the landscape images.
The resulting FOV and calculated focal length in APG are totally wrong.
When importing without rotating them, these values are ok but the pano must be rotated then in APG.
Below are my general settings in APG.
Note the setting about using the system file-explorer, this is not default.
And I don't use one of these EXIF-settings. This could be your problem here.
lumelix wrote:Have you also test this "Verwende System Dateibrowser" setting ?
klausesser wrote:The problem seems to be: the importer doesn´t seem to distinguish "use xml focus" and "use image focus". BOTH show the SAME values when selected.
No matter i chose "use xml focal length" or i chose "use image focal lenth": in both cases the importer sets the xml focal length - but declares it as "fisheye".
mediavets wrote:
Are you sure your images don't have EXIF?
klausesser wrote:mediavets wrote:
Are you sure your images don't have EXIF?
Of course they have! But none from the lens! The only lens-informations which can be in the EXIFs are the ones i
typed into the D800: focal length and max. aperture.
best, Klaus
mediavets wrote:klausesser wrote:mediavets wrote:
Are you sure your images don't have EXIF?
Of course they have! But none from the lens! The only lens-informations which can be in the EXIFs are the ones i
typed into the D800: focal length and max. aperture.
best, Klaus
AFAIK APG is only interested in focal length, and iis obvioulsy reading the focal length from the EXIF correctly.
ThomasV wrote:Hello,
From what I understand, there are 2 issues here.
First, as martin, mediavets and I cannot reproduce the issue, there is an issue with APG settings or usage on your side Klauss.
The second issue is on APG side. It indeed seems that the lens type is badly imported from the xml (and almost not imported at all). This must be fixed on software side.
Issue #2713 opened for that.
Thanks for reporting this bug.
Thomas
klausesser wrote:ThomasV wrote:Hello,
From what I understand, there are 2 issues here.
First, as martin, mediavets and I cannot reproduce the issue, there is an issue with APG settings or usage on your side Klauss.
The second issue is on APG side. It indeed seems that the lens type is badly imported from the xml (and almost not imported at all). This must be fixed on software side.
Issue #2713 opened for that.
Thanks for reporting this bug.
Thomas
Sounds like a contradiction, don´t you think?
My usage is: i use a work-around by setting "force x x" in the prefs. THEN the import uses the lens i set by "force x x"
So the only "issue on my side" rises when i forget to set "force x x" and rely on the importer to do what it´s supposed to do . .
There´s no other "issue in my use" at all, Thomas.
Again: the issue does not rise in PTGui and also not in APG 3.0.7 . . . it only appears in 3.0.8.
In the jimport-window clicking on "use xml focal" or clicking on "use image focal" makes no difference at all - both do not react.
Nevertheless teh xml focal lengths is taken - but interpreted as "fisheye".
That´s all.
When i set "force xx" in the prefs of APG everything works fine: the importer takes the focal-lengths and lens-model i set in the prefs by "force xx".
Hope i could make it clearer in the end . .![]()
best, Klaus
mediavets wrote:So it seems your settings - and/or usage - are different from ours.
mediavets wrote:Next two posts show 5 screenshots - APG 3.08 on Windows 8.1 - and yes mine look different to yours Klaus.
For me it sees all images as portrait orientation, so no rotating in the import module.
klausesser wrote:mediavets wrote:Next two posts show 5 screenshots - APG 3.08 on Windows 8.1 - and yes mine look different to yours Klaus.
For me it sees all images as portrait orientation, so no rotating in the import module.
Andrew: i use the same procedere for some years now. With images from my 5D2 and now from my D800.
Always i need to rotate the images before starting the stitch. But that ha no meaning - it works very well when i do not rotate them.
I then just rotate the stitch in the editor-window. No problem.
NEVER i was told my lenses - 20, 35, 85 mm - are "fisheyes" . . .
best, Klaus
PS: you might think i´m hallucinating . . . but you see the screenshots.
Users browsing this forum: No registered users and 0 guests