Hello Chris, 2010/5/16 cspiel <[email protected]>
> Harry - > > On May 13, 11:47 pm, Harry van der Wolf <[email protected]> wrote: > > For the others in this list, the repeated warnings are: > > "TIFF library warning tiff module: TIFFReadDirectory" > > It would be terribly helpful to know > which program issues this message, wouldn't it? > > You are completely right. The message originated from a private mail which I redirected to the hugin mailing list. As it was a very long mail (containing a crash log) I copied only the "necessary" parts, but indeed too brief. When running external binaries like enblend/enfuse, Hugin redirects stdout and sterr messages and displays them in a progress window. That's where the tiff warnings are displayed. Binaries exiting with 0 (no error) make the progress window close nicely, warnings and everything else are displayed as a warning/error message, after having closed the progress window. In this case a warning error was displayed when Hugin was reading the tiff images, that is before enblend and/or enfuse are being used. > > > I'm sure that your tiffs are created from a DSLR (a canon or nikon?) > either > > directly, or via the RAW convertor delivered with your camera. If you > open > > such a tiff in OSX Preview you will see that it has 2 images. A full > > resolution 16bit tiff, most probably with an alpha-mask, and a small > preview > > tiff. > > Again some definitive answer would be > appropriate, e.g., what does tiffinfo(1) say > about the image files? > > > I agree but please note that most Mac users do not have the tiff libraries/tools on their Mac. I wanted to ask Micah to privately send me one/some of his tiffs for further analysis, but I have been busy the last days with both ImageFuser and PTBatcherGui/Hugin builds, and as the warnings were only warnings and not (fatal) errors I put the priority a bit lower. To be continued. > > If have seen this also with enfuse often. Enfuse can't handle these tiffs > > and crashes on it. I had to write a patch for my ImageFuser(1) program to > > overcome that behavior from enfuse. > > Enfuse (and Enblend) ought to process > multi-directory TIFF files. In particular they > should not crash. If fact, there never has been > any failure reported on multi-layer images. > > My wording is not accurate (or plain incorrect actually). Enfuse and enblend don't crash, but both enfuse and enblend exit with error messages. For the user that's the same. He/She has tiff images most programs handle without problem, either because most of them don't recognise them as such like in this case align_image_stack and nona, or they do recognise them properly and act accordingly (macs preview, photoshop, etc.). But enblend and enfuse don't. Again: I know the difference, but the user either doesn't know or doesn't care. > Of course it is utter nonsense to feed a > 2-directory TIFF image as described above (full > quality image plus thumbnail) into Enfuse (or > Enblend for that matter), because the different > layers are not meant to be fused (or blended), > whereas both Enblend and Enfuse process all > directories. This behavior is documented in > Section 1, "Overview", of the Enblend and the > Enfuse manual. > > I agree as such that these single image files containing mulit-tiffs are not meant at all to be fused or blended, but I think we should not close our eyes and ignore the existence of these images. More and more cameras and raw-convertors create these images and they are slowly becoming the new tiff standard creared by DSLR and high-range compact cameras (my view on the near future). Based on the size difference of the "original" and the preview, and the fact that the original has an alpha-mask and the preview not, it should be possible to recognise these kind of tiffs. Unfortunately I lack the knowledge to write a patch for this, let alone that enblends/enfuses current behavior is "by design" to handle these tiffs now. The mentioned ImageFuser patch is nothing more than letting sips, a command-line tool comparable to ImageMagick convert and available on every mac, split the images. I fully understand your point and the implications of implementing the functionality to try to handle these images. And most probably new exceptions and thereby "(end user) bugs" will arise when it should be implemented. > > > Even more: I think that the only reason that hugin does not crash (on all > > platforms) when having to handle these kind of tiffs in stacked panos, is > > because nona (and align_image_stack) are not that intelligent and just > grab > > the first image in the tiff that they encounter. And then they deliver a > > single (cropped) tiff to enfuse and enblend which than can handle these > new > > intermediate "single tiff" images. > > > > Please let me know whether I'm correct in my analysis of the tiff > behavior. > > Many applications ignore all but the > first directory in a TIFF file. > > Agreed. See my comments above. > However, the true support of multi-directory > TIFFs implies quite an extra effort. We have > not even reached a conclusion on the syntax to > process multi-layer images for Enblend and > Enfuse! See, e.g. the brief "discussions" at > > > http://sourceforge.net/tracker/?func=detail&aid=2885858&group_id=123407&atid=696409 > > http://sourceforge.net/tracker/?func=detail&aid=2977905&group_id=123407&atid=696412 > > > /Chris > > I understand and respect your opinion. For the time being it remains an inconvenient and unsatisfactory situation for the users. Sometimes I behave like a user in this mailing list, sometimes as a "builder" or troubleshooter (hardly ever as a developer as I'm simply not). This double role sometimes causes mails that are "easy" for the end user (at least I hope so) and might be unclear or incorrect to the developer. Even though I try to be as accurate as possible I might (will?) generate more of these unclarities in the future due to my double role. best, Harry -- 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
