Error using TIFF_multilayer with nona on command line

57 views
Skip to first unread message

Greg Rafalski

unread,
Jul 26, 2013, 1:07:39 PM7/26/13
to hugi...@googlegroups.com
I've searched around a lot, but I can't find any other instances of this error.

When I try to create a multilayer TIFF with all the input images to help touch up the final panorama, I get this error:
"
C:\>"Program Files\Hugin\bin\nona.exe" -v -m TIFF_multilayer -o E:\wf_layers "E:\Working_Photos\Panoramics\20110702 Whiteface\20110702 Whiteface_tif.pto"

Remapping (remapping DSC_1454.tif)4% E:\wf_layers.tif: Error writing data for field "ICC Profile".
Remapping (remapping DSC_1455.tif)7% E:\wf_layers.tif: Error writing data for field "ICC Profile".
.
.  (lines removed for redundancy)
.
Remapping (remapping DSC_1480.tif):96% E:\wf_layers.tif: Error writing data for field "ICC Profile".
Remapping (remapping DSC_1481.tif): 100% E:\wf_layers.tif: Error writing data for field "ICC Profile".
"

In this case I was trying from TIF input images but it had the same result with JPGs whether or not I started with the JPGs from the camera or ran the RAW files through photoshop.

I was able to use the TIFF_multilayer option for a panoramic I took using my old point-and-shoot, as opposed to the rest which were taken with my Nikon D80. I also get no error if I use nona from the command line without the multilayer option.

Attached is one file from a panorama that gives me the error (DSC_1454.jpg) and one that doesn't (2007_0512_184828.JPG). I couldn't upload the full resolution files, hopefully the metadata didn't get changed too much to be relevant.

Any ideas?
Thanks

Other information:
Windows 7 x64
HuginSetup_2012.0.0_64bit_Windows
2007_0512_184828.jpg
DSC_1454.jpg

Greg Rafalski

unread,
Jul 26, 2013, 2:01:49 PM7/26/13
to hugi...@googlegroups.com
I forgot to mention that the resulting output image can't be opened in any program I have.

Greg Rafalski

unread,
Aug 4, 2013, 9:41:59 PM8/4/13
to hugi...@googlegroups.com
My brother is more familiar with coding than I am, and he said the actual error message is coming from Libtiff. Here to be more specific. Anyone else having this, or know how to avoid it?
Reply all
Reply to author
Forward
0 new messages