I'm giving up. The resulting file is 3.4Gb. Apparently it got written ok, but all "readers" have trouble. This is probably because the IFD is beyond the 2Gb mark. (I've followed flow of code through tifftopnm, and it SHOULD fail if it doesn't mmap the file. In practise however it does mmap the file, and still fails. I haven't figured out why yet.)
What we need is a file format that has 64-bit offsets allowing much larger files. I would suggest that just modifying tiff to have 8-byte pointers in a few places would be the best way to go. I'd call it bigtiff. Problem is.... It already exists. http://www.awaresystems.be/imaging/tiff/bigtiff.html http://www.remotesensing.org/libtiff/BigTIFFProposal.html So... has anybody tried compiling the hugin toolset with bigtiff support? I think I'm going to try. libtiff-4.0.0b3 has been compiled, seems to work. (and its tool ppm2tiff doesn't generate bigtiff files. :-( ) Roger. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
