On Tue, Mar 08, 2011 at 02:36:30PM +0100, Stefan Peter wrote:
> Am 08.03.2011 10:36, schrieb Gnome Nomad:
> > kfj wrote:
> >>
> >> On 8 Mrz., 09:54, Henk Tijdink <[email protected]> wrote:
> >>> The same happens on my system (Windows XP) with 2010.4 and 2011 beta
> >>> 2.
> >>> Noticed it when fusing a pano, saving it in JPEG.
> >>> The problem is not in Hugin, but Enblend.
> >>> Enblend gives that error message, but still works. I see it as a
> >>> warning from enblend. Enblend doesn't crash.
> >>
> >> I never save or read JPEG, only TIFF. But I guess TIFF is using some
> >> JPEG tech as well?
> >
> > JPEG is a compression method that TIFF can use, but I have mine set to
> > use LZW.
> >
> > I use JPEG for my input photos, I've always used that format. But when
> > enblend is running, it's taking the TIFF files generated by nona and
> > outputting a TIFF file.
> >
> > Bizarre.
> >
>
> Nona does issue these messages, too. At least when used under Ubuntu
> 10.10 as in
> nona -z LZW -r ldr -m TIFF_m -o test21 -i 15 /tmp/huginpto_yiPXtQ
> you will get the
> OJPEGSetupEncode: OJPEG encoding not supported; use new-style JPEG
> compression instead.
I read the situation as follows.
OJPEG
stands for oldjpeg.
When nona specifies
TIFF_OPTION_COMPRESS_LZW
the library understands
TIFF_OPTION_COMPRESS_OJPEG
and does
TIFF_OPTION_COMPRESS_NONE
because some dork changed the header file that defined
#define TIFF_OPTION_COMPRESS_LZW 2
#define TIFF_OPTION_COMPRESS_JPG 3
into
#define TIFF_OPTION_COMPRESS_OJPG 2
#define TIFF_OPTION_COMPRESS_LZW 3
#define TIFF_OPTION_COMPRESS_JPG 4
or something like that.
So that when compiled against the first header file, the library will
think the second case...
It is a mismatch of the compile-time header that differs from the
compile time header that the library used....
This will work on the developer's workstation because there the
versions will match.
Library developers should take care not to make such incompatible
changes.... Apparently someone screwed up.
Roger.
> The message seems to stem from recent libtiff versions. See
> http://trac.imagemagick.org/browser/tiff/trunk/libtiff/tif_ojpeg.c?rev=1
> for further information.
>
> The source files where jpeg, but I don't think that this matters.
>
> It may be more interesting that tiffinfo reported "Compression Scheme:
> None" on the resulting tiff output files, although LZW was requested
> according to the command line. Even the exif information states
> "Uncompressed" for the Compression tag. This was further confirmed by
> using tiffcp -c lzw on the file from above. The resulting output
> significantly smaller than the source.
>
> With kind regards
>
> Stefan Peter
>
> --
> In theory there is no difference between theory and practice. In
> practice there is.
>
> --
> 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 [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at http://groups.google.com/group/hugin-ptx
--
** [email protected] ** http://www.BitWizard.nl/ ** +31-15-2600998 **
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement.
Does it sit on the couch all day? Is it unemployed? Please be specific!
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ
--
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
