Just clarifying: the remapped intermediate images are always written to the working directory regardless of whether they are 'temporary' (i.e. even when Hugin deletes them afterwards).
This is how Hugin has worked since the Makefile stitching system was implemented, but there are good reasons to change it: The temp directory could be on a larger partition, or it could be on a faster partition such a ramdisk. Fixing this would require creating a secure folder in the temp directory and writing any intermediate files that the user hasn't asked to keep in this folder. i.e. if the user asks to keep all temporary files then the behaviour would be the same as currently. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/678632 Title: Current directory used for temporary files Status in Hugin - Panorama Tools GUI: Incomplete Status in Hugin default series: Incomplete Bug description: I've tried to use hugin and enblend with TIF output. However, this generated two TIF files with more than 100MB, which filled up my /home partition. However, I have a few gigabytes free at another partition. A similar issue could arise if /home was a network-mounted filesystem. Even though I would want to operate on files from that filesystem and save the final result there, those huge temporary files should be stored elsewhere (/tmp or any user-defined place). My suggestion: allow the user to specify an alternate temporary directory. _______________________________________________ Mailing list: https://launchpad.net/~hugin-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
