You might find it useful to read this article:
http://www.autopano.net/wiki-en/action/ … d_panorama
You might use http://www.hdrlabs.com/picturenaut/index.html who are Autopano promotional parthner, and offer a great tone mapping, and HDRi soft Picturenaut. You can also simply merge to HDRi in photoshop starting with CS3 version i believe.
At this point in time APP, rather then producing true HDRi, uses HDRi techniques to make differently exposed images look good in a pano. You would need to generate two or more different files (see first link above) to produce a true HDR 32 bit floating image. But do not abandon APP as it does something unique by using all of the bracketed images for alignment, so all of the layers shot at the different shutter speeds will have a perfect registration.
When making three or more layers in APP make sure to actually turn off color correction. But that would mean making 2 or more sets of images covering the entire scene with different but the same for each set shutter speeds.
Good luck.

streameru wrote:

But what if APP doesn't "see" the bracketed images, as bracketed images?  There were shot as a bracketed set using "AEB" on my canon.  Tested this feature on both Mac and Windows, neither platform show a BKT tag.  Using APP to look at the EXIF data, "eV:" field changes, but the "eV Bias value:" stays the same for all images.

Is there a way to force APP to treat this photos as a bracketed set?

I was going to say 'no' - but thinking about it I suppose the answer may be 'yes'.

Use an EXIF editor edit the eV bias values?

Last edited by mediavets (2010-03-10 09:07:14)

streameru wrote:

You know of one that will allow me to edit those values? 

Been through a few of them, none allow me to edit 'eV bias' values.

Try Opanda PowerEXIF if you are using Windows.:
http://www.opanda.com/en/pe/index.html

If you are not using Windows then I fear you are beyond any form of help that I can offer.

Shouldn't APP read the EXIF data from canon correctly?  Even from a camera raw file?

My friend that is testing APP with his Nikon, doesn't appear to have the problem.

I'm new to the software, but this does seem like a bit of a bug.

I think that by now you have perhaps finally understood that APP/APG's BKT feature - assigning bracketed images to 'stacks' - only works via the eV bias value in the EXIF. If your camera's AEB function - or whatever other means of bracketing you choose to use - does not reflect the bracketing in the eV bias data in the EXIF then APP/APG will not automatically assign the bracketed images to 'stacks'.

Is this a bug? No, because the way it works (and why it works this way) has been described by Kolor developers.

Is it adequate? No, it's definitely not good enough, IMO.

Last edited by mediavets (2010-03-11 09:15:31)

Brianb50 wrote:

What about Gigapan?

Errr...what about Gigapan?

I am uncertain as to your question?

mediavets wrote:

Shouldn't APP read the EXIF data from canon correctly?  Even from a camera raw file?

My friend that is testing APP with his Nikon, doesn't appear to have the problem.

I'm new to the software, but this does seem like a bit of a bug.

I think that by now you have perhaps finally understood that APP/APG's BKT feature - assigning bracketed images to 'stacks' - only works via the eV bias value in the EXIF. If your camera's AEB function - or whatever other means of bracketing you choose to use - does not reflect the bracketing in the eV bias data in the EXIF then APP/APG will not automatically assign the bracketed images to 'stacks'.

Is this a bug? No, because the way it works (and why it works this way) has been described by Kolor developers.

Is it adequate? No, it's definitely not good enough, IMO.

I was struggling with this as well; I have a camera with very good dynamic range, such that I can usually get decent HDR just by outputting TIFF from RAW at +2 & -2 EV or more, then feeding the 3 resulting TIFFs to an HDR program like Photomatix.

I have a 13-image pano that stitches to about 175MP, unfortunately that's too big for Photomatix to swallow so I'll be trying Picturenaut later.

Anyway, I overlooked the layer capability on my first try and I can attest to the fact that rendering separate panos will indeed lead to registration issues. 10 hours of render and setup time down the tubes. Obviously, when outputting 3 images from a single RAW, the EXIFs are all identical. I think my solution might be something that you could try.

What I did was, in the editor window, I changed the shutter speeds for all images to indicate the EV difference. So, the 0EV images were at 1/20. The -2EV images I set to 1/80 sec. The +3EV images I set to 1/2 sec(The dialog would not accept 1/2.5). I then clicked the button to separate out layers by shutter speed, changed the color correction so that each layer used the same anchor image, and set it to work. Oh, I took some tips about outputting individual layers as files from here.

It's been churning away for about 4 hours, when I get home from work I'll see how it's doing. Hopefully it won't have crashed, I have followed every recommendation about preventing crashes in 2.0.6, and I don't know if it's any more likely to crash rendering 39 files as 3 layers vs 13 files as a single layer.