Sharing knowledge around Autopano
You are not logged in.
EXIF output in a rendered panorama. We can think of many information to be stored back in the rendered panorama.
So I propose a discussion about that.
Here's some comment I grabbed from customers :
> As my picture archive program (photoshop elements 4.0) sorts
> pictures by DATE it is anoying that the stiched pictures get
> the ACTUAL date and time --> therefor an OPTION in the
> settings / render menu would be VERY NICE to have:
> set date and time...
> to ACTUAL time
> to time of first/earliest picture in this panorama
> to time of last/latest picture in this panorama
Proposal
For the following value :
- EXIF_MAKER ( 0x010F )
- EXIF_MODEL ( 0x0110 )
- EXIF_EXPOSURETIME ( 0x829A )
- EXIF_FNUMBER ( 0x829D )
- EXIF_SHUTTERSPEED ( 0x9201 )
- EXIF_APERTURE ( 0x9202 )
- EXIF_DATETIME_ORIGINAL ( 0x9003 )
We could set the real value if all input value where the same or an average value for numerical entries.
Focal length :
- EXIF_FOCALLENGTH ( 0x920A )
Should this be relative to input files (focal of input files) or be relative to panorama (focal calculated out of the fov of the panorama ) ?
Software :
- EXIF_SOFTWARE (0x0131) => "Autopano Pro v1.*"
Date :
- EXIF_DATEMODIFIED ( 0x0132 ) => date of panorama creation
Kolor Markernotes :
- int : Projection Type (rectangular, cylindrical, spherical, mercator, etc )
- 2 floats : angular size of the panorama ( 135.25° width, 78.75° height )
- 2 floats : horizon (where is the infinite point of view in picture coordinates )
If we setup something to store theses values, it could be used by an online viewer to switch automatically to the right mode of projection. And it will clamp directly the windows to the maximum angular view (as when you do by hand to your create partial QTVR).
Last edited by AlexandreJ (2006-07-11 18:24:15)
Offline
Focal lenght (teoretical for actual FOV)
Explosure (if youcan find common)
All common parameters from the images
Manufacturer information (not Canon, Nikon etc - Autopano pro, of course)
Offline
If there is a possibility to write non-statndar information with textual description - write information about pano settings and source images
for source images write fixed aperture/speed range (if case of fixed aperture), or exposure range
Offline
I'm also using Elements 4.0 and I've encountered the problem myself. I'd set the date and time of last image in the set in EXIF without prompting the user. I think this "earliest picture"/"latest picture" options are useless and over-complication of the problem.
Also, filling the EXIF with non-standard data is not a good thing - the main purpose of metadata is to make data understandable for the computer. If no software is going to use it (or it's not compatible with it), why fill the files with useless metadata?
Offline
2 bo: Your answer is incorrect. The main purpose of metadata is to make data understandable for the computer OR FOR PEOPLE ![]()
First way, for people - fill 'image description' tag textual information about panorama.
Second way - define Kolor makernote, publish specification and wait for the support of this in famous software
Better is going by the both ways
Last edited by Panorama fanatic (2006-07-11 12:22:54)
Offline
Some related points
A panorama corresponds to a file set. On my hard-disks those files are often scattered in various locations (especially when using APP which likes to save files on the desktop !o) In most cases the final result is difficult to discern from the previous intermediate or failed versions.
Finding the project file which corresponds to a given stitched panorama is useful (when the project file still exists and was kept unchanged.)
- finding the source image files which correspond to a given project is useful (when those files still exist and were kept unchanged.)
I suppose a perfect solution would require host file system having a major revamp!
My opinion is that the project file is the best place to store infos about the corresponding panorama. I have a probably unacceptable opinion about that: the whole project file should be included in the resulting panorama file header. Yes, this looks like an outrageous idea, but mind this: the JPEG file size of a panorama often amounts in MB while the .pano project file amounts in KB.)
Besides that, having lots of data in EXIF is not the actual goal.
Offline
Would be nice if the program could keep track of the exif data for you and then copy it over to the final version. I usually output in adobe photoshop format edit them then output from there into JPG or TIFF format. WOuld be nice if I could embed the exif data from say the first file of the series onto the final outputed file after I am done all my editing. For now I just embed the date taken back onto the photo using finepixviewer.
Offline
Here are my wishes for EXIF tag propagation:
1. for the EXIF tag
EXIF_DATETIME_ORIGINAL ( 0x9003 )
I would recommend to set one second before the first photo in the panorama
(or one second after the last photo). This way sorting by original time puts the pano in the right place, independent from specific naming of the panorama.
2. GPS-related tags (latitude, longitude, height) should be taken to the panorama.
Offline
how about the color space (sRGB, ProPhoto, etc)?
Adding an indication of dynamic range may be useful when HDR is added, and possibly some indication of how much the range was compressed.
Would it help to have the RMS of the pano added as a markernote? Don't know how I'd use it, except to compare two different versions of the same pano.
I think all the parameters you can set to create a filename (blender, etc) should be added as markernotes.
The HFOV and VFOV should be added, but the effective lens length is problematic: what is the effective lens length for a sperical pano?
Offline