Thank you AlexandreJ.
APG is supposed to be 32bit
I don't know what you're quoting exactly, but I wage APG has a complete 32-bit per channel pipeline.
Why would you want to stitch "real" HDR-images anyway?
- Most importantly, because you require a stitched HDR image
For HDRI lighting etc.
In no particular order:
- To save the full panorama straight to a HDR format without requiring HDR creation software.
- For correct global tone-mapping operators. Some tone-mapping operators are strictly local, others are global, in that they require knowledge of the luminance and other parameters of the whole image, which in this case would be the whole panorama, and not a subset of the whole image, which in this case would be a stack.
- Easier workflow assuming your hardware and software can manage a large high bit-depth image.
- Autopano does not reuse blending seams across layers, a very old issue, which means you cannot render layers and merge them to HDR later without having to deal with Autopano-created ghosts (OK, last time I tested this was 3.0 or 3.1, not 3.6.1, but I don't recall seeing info about it in the changelog). Besides, not all HDR creation software supports de-ghosting efficiently or at all.
- Less images and layers in APG,
Why OpenEXR at all?
- It's open.
- Supports more features than Radiance RGBE, e.g. metadata.
- Other software support.
- Other compression methods.
- http://www.hdrlabs.com/cgi-bin/forum/Ya ... 655637/1#1
- Autopano already supports it, though not in the requested form.