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

Hi Martin!

I´m not quite sure what´s your point . . . I´m acting this way for years without any issue.

I always shoot in portrait-orientation. The importer always imports them as landscapes. I always rotate them to portrait in the importer.Usually no problems at all.

I´m just about to shoot a sphere in the backyard - deleting all entries in the camera regarding focal/aperture-values of my non-exif-lenses. Mayne it´s something in this entries thePapyWizard import-module in APG gets confused by. As said: PTGui handles it WITHOUT any error.

best, Klaus

Last edited by klausesser on Mon Oct 21, 2013 12:41 pm, edited 1 time in total.

lumelix wrote:Hi KlausFor 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

Hi Martin!

I do the import the same way as ever . . don´t exactly know what you mean!?

Using the PW import there´s only one way to select images.

But what i realized minutes ago: usually there´s a difference between "use xml-focal length" and "use image focal length".Selecting "use xml focal length" sets the values which are in the XML.Selecting "use image focal length" sets the values which are set in the APG´s prefs or - maybe - come from the image´s EXIFs (my lenses don´t provide EXIFs).

I always set "use xml focal length" - and never had a problem with it. Until 3.0.8 came.

Funny: makes no differences whether i choose "use xml focal lenth" or when i choose "use image focal lenth" . . . in both cases the the xml focal-length is set!(makes me crazy trying to put images into a logical order with the uploader . . .)

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.

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.

Hi Martin!

I use the import like i use it for years without any issue. I used it util 3.0.8 came out - in 3.0.7 there is NO issue.

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

So in my eyes it´s clearly a bug in the importer.

Fact is - to name it again: 1) this issue came up since i use 3.0.8 it´s NOT in 3.0.7 - ONLY in 3.0.82) PTGui does NOT show this issue.

IF it were in the xml or in the EXIFs PTGui would show the same issue, don´t you think?

best, Klaus

PS: i did what you also did - i did set no values in the presets regarding focal lenth or lens-type.Nevertheless it´s the same issue.

Hi KlausBut I can't reproduce this "fisheye"-bug !?On my Win7x64-machine the papywizard import your images as it should - as standard lens with 20mm focal lenght.The only problem I could find ist this funny thing with wrong FOV and focal lenght if I rotate the images just in the importer.But the pano is created well nevertheless.

So I guess the problem must have something to do with your installations or settings ?That the problem has occurred since you have installed version 3.0.8 suggest this.Or perhaps it depends only at the MAC-version, which I can not test.

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.

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

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

The difference is - none of us needs to use the workaround for it to work correctly. No need for 'Force xx' in the settings/preferences.

Hi allI try out these two downloads from Klaus also on Win7x64 with APG 3.0.8 (64bit).And it's clear that there is something misterious in this papywizard module !But who wonders: it's logo is the hat from Merlin

My first try was with my general settings for testing giga-panos and end up in a totally mess, see below:As you can see, the papywizard reads the XML correctly but shows no focal length from the EXIF.This is ok because all this images have no EXIF inside, no ones from the D800 also (?).All images are in portrait orientation without rotating them. The preview in the wizard is funnybecause there are gigantic gaps between this overlapping images. This calculation is clearly wrong.But now, APG starts with a focal length of 1mm (one !!!) and the pano was a completely mess.But: The lens is declared as "STANDARD"

Then I close APG and start it again, first I set all general settings to the default values. Then the papywizard shows me again the XML data but no EXIF focal length.

And now - APG starts - magically - with a standard 20mm lens and the pano is ok.So, what happends that it works now?

I try to reconfigurate my settings as they was and try to replicate the first case.With no success. But with the forth try APG hangs up while optimize the controll points. I have - for the first time - to shut down APG !

For me it's clear: This wizard has some strange quirks and idiosyncrasies that need to be addressed. The XML import is important for all who work with motorized heads, and must work correctly with and without EXIF data in each case, and on each machine, PC or MAC. And with fisheye and wide angles.

On the other hand I know as an IT-specialist that there aren't two exactly identical computer on the world. My recommendation for Klaus is completely reinstall APG and then try using the default settings again. Maybe it helps.