I've said it before, but I'll say it again: I think we need a "file type" that also tiles the images. There should be a lot less strain on the OS if there is, for example, a folder with an extension (e.g, MyImage.tiles), and within that, a directory structure to implement tiling. The most simple approach would be to choose a standard tile size (e.g, 1024x1024) and then dissect the image into tiles of that size, with the right-most column and bottom row perhaps not being entirely used.
Optional support for caching down-sized tiles to speed up viewing could be added. I just don't like the idea of multi-GB TIFF files, because many programs operate on the assumption that the whole, decompressed image will fit into memory. Also, if something like this already exists, let me know! Ryan On May 1, 12:53 pm, Matthias Kabel <[email protected]> wrote: > * rew ([email protected]) [090501 20:02]: > > > 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. > > Hm, I'm creating panoramas with a resulting tif (with LZW compression) > between 2.3 GB and 2.6 GB. Debian 64bit Linux. Works fine here. The blending > process swaps een with 8GB of RAm, but it's working here. > > Kind regards > Matthias --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
