It's been there for a while and it is still in 3.0 alpha 3
When I shoot a pano with the VRdrive it produces a XML-file in which the focal is written like this <lens type="rectilinear"> <focal>12</focal> </lens> This is correct, the lens is 12mm f2.0 The camera, E-M5, has a cropfactor of 2.0
In the Papywizard plugin (and the VRdrive2) the EXIF is used to identify the camera, it finds it and finds that the crop is 2.0 Then the 35mm equivalent focal is calculated and the result is 24mm.
The bug/annoyance is the red sign (which normally means an error) saying "Focal length difference between EXIF and XML" This is wrong ! The XML says 12mm and the EXIF says 12mm. The calculated 35mm equivalent focal is used instead of EXIF focal, and this results in the red warning. I think I will call it a bug.
.lets see who changes first....I'd put my money on the Papywizard or Kolor team.....reprogramming an embedded app is a lot more difficult then reprogramming PC/Mac source code. Though IMHO if you build an interface to a standard well you build an interface to a standard (I know I've build more the
I bet that Seitz changes first.
The Papywizard XML data file standard long pre-dates Seitz attempt at implementing the Papywizard-compatible data file recording feature...and they (Seitz) somehow seem to have got it wrong.
Kolor didn't write the Papywizard software and may well not wish to touch/'hack' it.
Andrew Stephens Nikon D40, Nikkor 10.5mm fisheye, Sigma 8mm f3.5 fisheye, Nikkor 18-55/50/35mm lenses, Nodal Ninja 5 Lite, Nodal Ninja 4 with R-D16, Agno's MrotatorTCS short. Nikon P5100, CP5000, CP995, FC-E8, WC-E63,WC-E68, TC-E2, Kaidan Kiwi 995, Bophoto pano bracket, Agno's MrotatorA. Merlin/Orion robotic pano head + Papywizard on Nokia 770/N800/N810 and Windows 8/XP/2K.