 |
|
|
|
|
|
 |
| ||||||||
 |
 
|
|
|
|
|
|
|
|
|
| ||||||||
|
|
| 
| User list | Rules | You are not logged in.
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.
After the import everything is OK.
leifs
Last edited by leifs (2012-09-06 21:06:58)
Offline
do I miss some info?
you write about "VRdrive2" and "papywizzard plugin"... why not using the VRdrive2 import plugin instead?
Georg
Offline
Artisan S. wrote:
That in fact is a bug in your VR drive software
You are wrong.
As I wrote the lens is a 12mm f2.0
The XML from the head is right:
<lens type="rectilinear">
<focal>12</focal>
</lens>
leifs
Offline
gkaefer wrote:
do I miss some info?
you write about "VRdrive2" and "papywizzard plugin"... why not using the VRdrive2 import plugin instead?
Georg
As far as I can see the VRdrive2 plugin is identical with the Papywizard plugin except for the addition of an automated path for HDR's.
If I shoot non-HDR the plugins do the same thing.
leifs
Offline
issue 1497 opened ( I've asked Seitz for some details about xml generation )
Offline
AlexandreJ wrote:
issue 1497 opened ( I've asked Seitz for some details about xml generation )
I've noted before that the XML file written by the Seitz VRDrive does not appear to be fully compliant with the Papywizard XML data file standard.
Amongst other things it writes the data for bracketed shots data incorrectly.
Online
Artisan S. wrote:
.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.
Online
Seitz will update their firmware to add the missing part ( aka : <sensor coef="1.6" ratio="3:2"/> part with the right value ).
So no more red warning should happen during the VRDrive2 plugin.
Offline
AlexandreJ wrote:
Seitz will update their firmware to add the missing part ( aka : <sensor coef="1.6" ratio="3:2"/> part with the right value ).
So no more red warning should happen during the VRDrive2 plugin.
Alex,
Did you ask 'em to fix the way they record bracketed shots too so that it complies with the Papywizard standard?
Online
I like this :
a problem is described
the fix is identified
now it's up to Seitz to deliver
then: solved !
in the meantime I will just add the fix by hand, insert the
<sensor coef="2.0" ratio="4:3"/>
leifs 
Offline
mediavets wrote:
Did you ask 'em to fix the way they record bracketed shots too so that it complies with the Papywizard standard?
I didn't found anything wrong here. Could you highlight me ?
Offline
