enblend: input image UINT8 but previousUINT16

Bug #679602 reported by ll0zz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Enblend
New
Undecided
Unassigned
Hugin
Incomplete
Undecided
Unassigned

Bug Description

Hi,
I tried to use Hugin on 7 Tiff16 images from my EOS5D camera.
Process can't complete (see below).
I'm using Hugin 2010.0.0.5045 (in french) with Ubuntu64 10.10
All images have been converted the same way from raw (.CR2) to TIFF16 using Ufraw 0.16

Tiffs generated by Hugin seem to be indeed different, the first (panoQuaix100000.tif) is 38.6Mio whereas others (panoQuaix10000n.tif) are around 23.2Mio

Regards,
GB

--output:
Checking nona...[OK]
Checking enblend...[OK]
Checking enfuse...[OK]
Checking hugin_hdrmerge...[OK]
Checking exiftool...[OK]
nona -z PACKBITS -r ldr -m TIFF_m -o panoQuaix10 -i 0 /tmp/huginpto_VPgHbk
OJPEGSetupEncode: OJPEG encoding not supported; use new-style JPEG compression instead.
nona -z PACKBITS -r ldr -m TIFF_m -o panoQuaix10 -i 1 /tmp/huginpto_VPgHbk
OJPEGSetupEncode: OJPEG encoding not supported; use new-style JPEG compression instead.
nona -z PACKBITS -r ldr -m TIFF_m -o panoQuaix10 -i 2 /tmp/huginpto_VPgHbk
OJPEGSetupEncode: OJPEG encoding not supported; use new-style JPEG compression instead.
nona -z PACKBITS -r ldr -m TIFF_m -o panoQuaix10 -i 3 /tmp/huginpto_VPgHbk
OJPEGSetupEncode: OJPEG encoding not supported; use new-style JPEG compression instead.
nona -z PACKBITS -r ldr -m TIFF_m -o panoQuaix10 -i 4 /tmp/huginpto_VPgHbk
OJPEGSetupEncode: OJPEG encoding not supported; use new-style JPEG compression instead.
nona -z PACKBITS -r ldr -m TIFF_m -o panoQuaix10 -i 5 /tmp/huginpto_VPgHbk
OJPEGSetupEncode: OJPEG encoding not supported; use new-style JPEG compression instead.
nona -z PACKBITS -r ldr -m TIFF_m -o panoQuaix10 -i 6 /tmp/huginpto_VPgHbk
OJPEGSetupEncode: OJPEG encoding not supported; use new-style JPEG compression instead.
enblend --compression NONE -f13010x1833+558+366 -o panoQuaix10.tif panoQuaix100000.tif panoQuaix100001.tif panoQuaix100002.tif panoQuaix100003.tif panoQuaix100004.tif panoQuaix100005.tif panoQuaix100006.tif
enblend: input image "panoQuaix100001.tif" has pixel type UINT8,
enblend: but previous images have pixel type UINT16
make: *** [panoQuaix10.tif] Erreur 1

Revision history for this message
Bruno Postle (brunopostle) wrote :

Can you install tiffinfo, run it on all the input photos and send the result here?

Unfortunately Hugin (or rather enblend) doesn't support mixing 8bit and 16bit photos. If Hugin has somehow created a mixture of 8bit and 16bit files from uniform 16bit input photos then this would be a bug.

Revision history for this message
ll0zz (ll0zz) wrote :

Thank you for the tip about tiffinfo, exactly what I was missing to check if the files were Tiff16 or Tiff8.
And indeed it seems I had trouble with Ufraw that memorize some settings between two images, and doesn't for some others, so I ended with mixed Tiff8 and Tiff16.
So this was not a bug.
But maybe Hugin could warn user he's mixing 8 and 16 bits images, or enblend show a more explicit message ?

Nevertheless, thank you for your time and your work.

Revision history for this message
Bruno Postle (brunopostle) wrote :

What version of enblend do you have? a comment in an earlier report (Bug #679094 (sf-2549583)) for this issue says it is fixed in enblend.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.