Hmm, I shoot 16-bit/channel RAW files (both for HDR and non-HDR stuff).
Process them into similarly 16-bit/channel TIFFs that I then stitch
and/or align using Hugin. At the end of the process, I have
16-bit/channel TIFFs. No values being "clamped" to 8-bit anywhere in the
chain or the final output. Puzzled where you get that idea ...
I used to do the image swap trick you mention in 1 (below), when Hugin's
vertical line fine was unable to function on 16-bit/channel TIFFs. I'd
generate a set of 16-bit TIFFs, then generate a set of 8-bit TIFFs in a
separate folder. Then I'd use the 8-bit TIFFs to create and finalize the
Hugin project. Then I'd copy the resulting PTO file into the folder with
the 16-bit TIFFs, and either stitch it, or reoptimize exposure and then
stitch.
I do believe Hugin has a way to merge different exposures into a single
image. I've done it but don't presently recall how.
On 05/28/2013 07:21 AM, byex...@gmail.com wrote:
Ouch, I meant what was the point of having 16bits when values were being
clamped to the max of 8bit (255)
I will have another go at it, I have some feedback on it but not sure
where to post it so I'll stick it in here, I can create a separate
thread if needed.
1 - It would be great to be able to swap images or specify proxies,
imagine the following scenario, you have a some huge HDR images that you
want to stitch together, ideally one would resize them to a different
size or to some 8bit format, say jpeg to make working with them faster,
then swap them when you're about to stitch the panorama.
2 - Hugin doesn't seem to have a way to merge different exposures into
one image? This would definitely help a lot of vfx people to turn to
Hugin rather than relying on propietary tools, probably getting some
donations from small studios to help out with the project?
On Friday, May 24, 2013 8:25:58 AM UTC+1, Bruno Postle wrote:
On May 23, 2013 10:47 PM, <bye...@gmail.com> wrote:
>
> I am a programmer and I am fully aware of what the crash error
means, when I have the time I will have a look at the source and try
to figure out why is crashing but I just wanted to check if this is
even being looked at, as it makes Hugin literally useless.
This must be a library error as I don't see it on Linux.
> Exporting 16bit tiffs is still an option, but they seem to be
clamped to 1, so I am not entirely sure what is the point of having
8bits if every value is going to be clamped to 255 anyway.
The TIFF output when you feed it HDR input is actually full HDR
32bit float. So until EXR is fixed you should be able use TIFF instead.
--
Bruno
--
David W. Jones
gnomeno...@gmail.com
wandering the landscape of god
http://dancingtreefrog.com
http://www.clanjones.org/david/
http://dancing-treefrog.deviantart.com/
http://www.cafepress.com/otherend/
--
--
You received this message because you are subscribed to the Google Groups "Hugin and
other free panoramic software" group.
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to hugin-ptx+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
