On Sep 15, 1:58 am, Yuval Levy <goo...@levy.ch> wrote:
> On September 14, 2010 01:52:17 am Eric O'Brien wrote:
> Has anybody here thought of pointing the fingers to the TIFF-producing tools?
>
> Why don't they give the consumer an option not to store the unnecessary
> pages?
> ...
> There surely is tiffsplit,...
tiffsplit is actually a fast and convenient way to split a multi-image
tiff file into several single-image ones. I use it on the files my
canon raw converter produces (they are with a preview image and I
haven't found a way to avoid that). But just tiffsplit is not enough,
since tiffsplit also removes all exif information from the file, and I
make EXIF-TIFFs to use the information in hugin and elsewhere. So I've
written a little shell script to deal with the issue. It's a bash
script (the bourne-again shell) and I run it on Windows under msys,
the environment that goes along with minGw. I am sure that a
corresponding Windows script could easily be written, but I have a
strong dislike of Windows scripting (maybe from the old MSDOS days,
when you had to spend days to get something done in a batch file that
you could get done with a unix one-liner) - being pragmatic, though, I
still use Windows, just with a little help from the 'other side'. But
I shan't waffle on, here's the (trivial) script (that certainly could
be improved upon):
#! /bin/bash
# this little shell script keeps only the first layer
# of each tiff file it is invoked with and replaces
# the original file with it.
for picture in $*
do
echo -n 'processing' $picture '.... '
tiffsplit $picture layer_ &&
exiftool -overwrite_original_in_place -TagsFromFile $picture -
exif:all layer_aaa.tif &&
mv layer_aaa.tif $picture &&
echo 'done'
done
rm -f layer_???.tif
# end of script
This lives as 'no_thumb' in my /bin directory.
The script throws stuff out of the original file and overwrites it
without warning, but mostly it does just what I want.
Of course, having to run an extra two processes per image (and all the
disk activity envolved) costs time and one does indeed wish there was
a way to tell TIFF-consuming programs straight away that one only
cares for one of the several images in the input only, but if one
really only does care for just the one image, one might as well throw
the other(s) out straight away - and then enjoy the gimp opening
without the dialog that asks which of the images one wants to load, as
well as having the droplets and enfuse function as one often intends.
I also feel that the preview image should be an option in the TIFF-
generating software, and I also feel that the choice to have enfuse do
what it does is legitimate, and that the workaround needed until
someone maybe makes the effort to include additional syntax into
enfuse is not really a great bother.
With regards
KFJ
--
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
