Hmm. So what am I doing wrong? For my test, I took the first image (only) and added a variety of caption and title tags such as these:
Image Description : Monument at Place de la Bastille, where a remnant of the prison sits
User Comment : Monument at Place de la Bastille, where a remnant of the prison sits
Title : The Bastille
Description : Monument at Place de la Bastille, where a remnant of the prison sits
Object Name : The Bastille
Caption-Abstract : Monument at Place de la Bastille, where a remnant of the prison sits
Comment : Monument at Place de la Bastille, where a remnant of the prison sits
None of them propagated through to the resulting rendered pano. Do I need to put the caption on every single image to make it propagate through? How does it choose which image to get tags from that propagate? Having to tag every image defeats the purpose of this functionality, we want it to be easy to assign such tags on our panos that persist from render to render. A possible correct action, if there are multple different versions of an exif tag on the source images would be to either take the first -- though "first" can be hard to be exact about -- or perhaps take the longest. Certainly if all but one are null, take the one that is not null.
In addition, as I noted, the renderer puts the stitching data in the user comment, even though I had an image with a different user comment.
As noted, perhaps an ideal behaviour (though it requires more code) is:
a) Examine source images for various freeform text tags. If all are the same, take that. If they differ, take the longest.
b) Store that resulting value in the .pano file and keep it as a user editable parameter. Flag it as user-edited or auto-generated.
c) Have a UI to let the user see what APP extracted and change it. If they change it, it now overrides what APP extracts, even if the underlying image captions change.
However, lesser UIs are certainly suitable.
Last edited by bradtem on Fri Oct 12, 2012 4:31 pm, edited 1 time in total.