Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
hugin and other free panoramic software
Home
+ new post
About this group
Join this group
Message from discussion Might this idea work? scripting process
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Gnome Nomad  
View profile  
 More options Nov 9 2012, 10:26 pm
From: Gnome Nomad <gnomeno...@gmail.com>
Date: Fri, 09 Nov 2012 17:26:02 -1000
Local: Fri, Nov 9 2012 10:26 pm
Subject: Re: [hugin-ptx] Re: Might this idea work? scripting process
Print | View thread | Show original | Report this message | Find messages by this author
On 11/09/2012 01:52 AM, dex Otaku wrote:

> Salut alouest,

> On Thursday, 8 November 2012 14:01:32 UTC-6, alouest wrote:

>     'm using a sotware which can export RGB tiff and 32 bit tiff. I can
>     produce panoramic with hugin of the RGB but not of the 32 bit tiff.
>     If I extract both RGB and 32 bit tiff, then I create my panorama
>     from the RGB pictures and save the project file.
>     Would I be able to use all the settings (and control points,
>     basically everything) used before and apply them to my 32 bit tiff
>     that hugin see totally blank?
>     I tried quickly with nona but it crashed.

>     To summary could hugin or another tool could apply the settings from
>     a working panoramic creation into empty tiff (they off course have
>     the exact same extent).

>     Is that crazy or that could work?

> To my knowledge, Hugin and its included tools only work with TIFF images
> that:
> * use 16 bits per colour channel or less [no 32bpc TIFF, no floating
> point TIFF],
> * are RGB or RGBA [no CMYK support],
> * use only a single image layer [no multi-layers TIFF support],
> * and must be <4GB in file size [a limitation of base-standard TIFF]

Yes. I understand there's an effort to come up with a TIFF standard that
allows larger sizes.

> What are you using that creates 32-bit [I assume that's per colour
> channel] output? HDR images from something?

I don't know what the original poster means by it. Windows claims a
32-bit image format, but I think it's actually 8-bit RGB with 8-bit
alpha-transparency.

> Is there a practical reason to maintain that bit depth as far in your
> processing chain as Hugin? Chances are, even if you're going to be
> post-processing the images after stitching, 16 bits per channel will be
> sufficient.

I get better color when I stitch using 48-bit TIF (16-bit per channel).
I convert them from my camera's 48-bit RAW files. 48-bit is minimal HDR,
because 16-bits per channel gives a greater color gamut than can be
displayed or printed with existing technology.

> My suggestion [which is probably your only option with Hugin, Nona,
> etc.]: reduce the bit depth of the images to 16bpc or less and use those
> with Hugin. If you require >16 bit per channel image support, you may
> need to find other tools to use.

I know of one Hugin tool that doesn't work with 16-bit per channel
images: linefind. Unless that's been fixed in the new release?

> Cheers,
> D

--
Gnome Nomad
gnomeno...@gmail.com
wandering the landscape of god
http://www.clanjones.org/david/
http://dancing-treefrog.deviantart.com/
http://www.cafepress.com/otherend/

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google