Re: [hugin-ptx] TIF compression

2010-04-20 Thread Harry van der Wolf
Hi Battle and others,

Some inevitable history to start this reply.

In April/May/June 2009 I worked on patched tiff libraries for enblend/enfuse
to overcome the 4GB limit for tiffs on OSX. I brought some of these binaries
in the open for testing and a dutch profesional photographer (nickname
Jannes), making huge panos, has tested these builds. At that moment there
were problems with big images (tiff, jpg, png) having horizontal and
vertical lines in them and that patched tiff development road stopped more
or less. It doesn't make sense to create 4+ GB tiffs as the tiffs below that
limit already are unusable for another reason.
Second, and for me most important reason, was that my MacBook was fried
early July 2009 (which most users of this community might remember) and I
decided to go back to (cheap) Linux which I had used for many years (since
1993 partly and since 2000 completely until 2007). However, after 2 months I
decided to buy a Mac again as nothing can beat the MacOSX (this despite the
fact that I hate all the semi-religional, apple-protectionism marketing spam
from prophet Steve Jobs).

This 4GB+ panos are only for the very few among us. For me it's not a
priority at all especially as I won't use them myself (and you may call that
selfish). Now that I have built the several enblend/enfuse versions I might
as well build another 64bit tiff patched enblend/enfuse in the near future.
I don't promise anything, maybe I will.

Hoi,
Harry



2010/4/19 Battle battlebr...@gmail.com

 Does anyone know how the file compression works in hugin.  TIFs are
 limited to 4GB, but there are compression options in hugin -- LZW,
 deflate, packbits.  They yield pretty good compressions around 50 to
 75% reduction.  Does this reduction happen prior of the final image
 TIF assembly, or after.  In other words if I'm generating a a 3gb tiff
 uncompressed and it ends up as 1GB, can I safely triple the size of
 the panorama or will that cause problems because the final output tif
 is generated first and then compressed.  In this example that would be
 a 9GB uncompressed over double the limit before compression.

 And in a related question if I switched to PNG or JPG ouput, when are
 those files generated and does this get me past the 4GB TIF file size
 limit?

 Thanks
 Battle

 --
 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.comhugin-ptx%2bunsubscr...@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.
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

Re: [hugin-ptx] TIF compression

2010-04-20 Thread Bruno Postle

On Mon 19-Apr-2010 at 14:24 -0700, Battle wrote:
Does anyone know how the file compression works in hugin.  TIFs 
are limited to 4GB, but there are compression options in hugin


In other words if I'm generating a a 3gb tiff uncompressed and it 
ends up as 1GB, can I safely triple the size of the panorama or 
will that cause problems because the final output tif is generated 
first and then compressed.


You should be ok, the TIFF files are written directly to disk, and 
the limitation is on the file size and not the size of the image.


And in a related question if I switched to PNG or JPG ouput, when 
are those files generated and does this get me past the 4GB TIF 
file size limit?


As far as I know PNG doesn't have this limitation.  Hugin still uses 
TIFF for the intermediate remapped files, but if they are 'cropped' 
TIFF (the default) this shouldn't be a problem until you are doing 
_really_ big panoramas.


--
Bruno

--
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


[hugin-ptx] TIF compression

2010-04-19 Thread Battle
Does anyone know how the file compression works in hugin.  TIFs are
limited to 4GB, but there are compression options in hugin -- LZW,
deflate, packbits.  They yield pretty good compressions around 50 to
75% reduction.  Does this reduction happen prior of the final image
TIF assembly, or after.  In other words if I'm generating a a 3gb tiff
uncompressed and it ends up as 1GB, can I safely triple the size of
the panorama or will that cause problems because the final output tif
is generated first and then compressed.  In this example that would be
a 9GB uncompressed over double the limit before compression.

And in a related question if I switched to PNG or JPG ouput, when are
those files generated and does this get me past the 4GB TIF file size
limit?

Thanks
Battle

-- 
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