Best TIFF format for Hugin?

[Donald Johnston]

Hi, i’m working on a workflow to take my Canon raw files to TIFF and then into align_image_stack, and enfuse.

Raw Photo Processor offers: Lab TIFF 16-bit, RGB TIFF 16-bit (BetaRGB), RGB TIFF 16-bit (L*), or (L*, perceptual), (ECI-RGB), (sRGB), (-studio swing), and Raw RGB TIFF 16-bit. It has other 8-bit and 32-bit formats but my camera uses a 14-bit ADC so I plan to use 16-bit TIFF.

Which of that plethora of options would be best for the hugin parts of this workflow?

[Terry Duell]

Hello Donald,

In the absence of any other response, I'll offer a less than expert
opinion.
I think as a general rule, hugin passes on the input profile. There was
some discussion a couple of years ago as to what would happen if different
images had different profiles, and I think the profile from the first
image was passed on.
Regarding enfuse, it seems that if there is no profile, sRGB is assumed. I
am not sure, but guess that an input profile is passed on.
I would also guess that align_image_stack would mimic the general hugin
behaviour...I haven't found anything that says one way or another.
Looking at the notes accompanying DCRaw (a respected raw file converter),
it defaults to sRGB.
So, I would reckon sRGB would be a safe choice.
Having said that, those that know better can now correct me :-)

Cheers,
--
Regards,
Terry Duell

[Carl von Einem]

Hi,

Terry Duell schrieb am 08.11.13 04:07:

> Hello Donald,
>
> On Fri, 08 Nov 2013 08:21:26 +1100, Donald Johnston
> <dgjoh...@accesscomm.ca> wrote:
>

>> Hi, i�m working on a workflow to take my Canon raw files to TIFF and

>> then into align_image_stack, and enfuse.
>>
>> Raw Photo Processor offers: Lab TIFF 16-bit, RGB TIFF 16-bit
>> (BetaRGB), RGB TIFF 16-bit (L*), or (L*, perceptual), (ECI-RGB),
>> (sRGB), (-studio swing), and Raw RGB TIFF 16-bit. It has other 8-bit
>> and 32-bit formats but my camera uses a 14-bit ADC so I plan to use
>> 16-bit TIFF.
>>
>> Which of that plethora of options would be best for the hugin parts of
>> this workflow?
>
> In the absence of any other response, I'll offer a less than expert
> opinion.
> I think as a general rule, hugin passes on the input profile. There was
> some discussion a couple of years ago as to what would happen if
> different images had different profiles, and I think the profile from
> the first image was passed on.
> Regarding enfuse, it seems that if there is no profile, sRGB is assumed.
> I am not sure, but guess that an input profile is passed on.
> I would also guess that align_image_stack would mimic the general hugin
> behaviour...I haven't found anything that says one way or another.
> Looking at the notes accompanying DCRaw (a respected raw file
> converter), it defaults to sRGB.
> So, I would reckon sRGB would be a safe choice.
> Having said that, those that know better can now correct me :-)

I usually use sRGB only for output on unknown printers and displays.
It's the minimal (standard) color space that can be displayed in
browsers on calibrated or not so calibrated systems.

As a working space for editing and also archival purposes a color space
with a wider gamut is usually recommended. Is your system calibrated,
which profiles are available in your system / workflow? This is usually
a can of worms when you start diving into this topic.

An overview is maybe
http://en.wikipedia.org/wiki/Color_management

Check out the "Getting Started" tab on http://www.color.org/

In Raw Photo Processor ("RPP", a "Mac only" application) I usually
default to ECI-RGB when I'm heading for CMYK print output. Here is more
information about that profile:
http://www.eci.org/en/colourstandards/workingcolorspaces

If I remember correctly RPP's own choice is BetaRGB, see also
http://pavelkosenko.wordpress.com/2012/05/24/rpp-for-begginers/

Also read the "RPP User Manual" PDF (page 11) that comes with your
latest version of RPP. There you find a link to
http://brucelindbloom.com/index.html?BetaRGB.html

If you use Photoshop CS6 (or CC) also try the built-in raw converter.

Cheers,
Carl

[Donald Johnston]

Carl, thanks for the information.  I use the Spyder4Pro to calibrate my two screens: MacBook Pro and acer X203W.  I also use the colour profile for my printer (an HP) and the company that I usually use for prints.  I’ve read through your various links below; thanks for the information.  From hugin’s point of view (align_image_stack and enfuse) what colour (color) space to they work best with?

On Nov 8, 2013, at 1:49 AM, Carl von Einem <ca...@einem.net> wrote:

Hi,

Terry Duell schrieb am 08.11.13 04:07:

Hello Donald,

On Fri, 08 Nov 2013 08:21:26 +1100, Donald Johnston
<dgjoh...@accesscomm.ca> wrote:

Hi, i’m working on a workflow to take my Canon raw files to TIFF and

Also read the "RPP User Manual" PDF (page 11) that comes with your latest version of RPP. There you find a link tohttp://brucelindbloom.com/index.html?BetaRGB.html

If you use Photoshop CS6 (or CC) also try the built-in raw converter.

Cheers,
Carl

-- 
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
--- 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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/527C9789.8090808%40einem.net.
For more options, visit https://groups.google.com/groups/opt_out.

[Carl von Einem]

Hugin et al will pass on the profile you use in your workflow, so just
use the one you're happy with.

Carl

Donald Johnston schrieb am 09.11.13 20:52:

> Carl, thanks for the information. I use the Spyder4Pro to calibrate my
> two screens: MacBook Pro and acer X203W. I also use the colour profile
> for my printer (an HP) and the company that I usually use for prints.

> I�ve read through your various links below; thanks for the
> information. From hugin�s point of view (align_image_stack and enfuse)

[Carl von Einem]

Just one quick addition: in case the profile of your input images is
ignored by some software and not embedded in the output file the next
color profile aware application (like Photoshop) will ask you how it
should interpret the file. Since you know the original profile you
should _apply_ that one on opening the file, instead of _converting_
which will alter the color information.

Carl von Einem schrieb am 11.11.13 09:31: