[Hugin-devs] [Bug 679512] Re: Enblend fails from Hugin, works from cmd line
** Changed in: hugin Milestone: None = 2011.4beta1 ** Changed in: hugin Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679512 Title: Enblend fails from Hugin, works from cmd line Status in Hugin - Panorama Tools GUI: Fix Released Bug description: This bug has actually been reported a number of times, but closed out because people assumed it was simply a problem of not enough disk space. I have a case that proves this is not the case... and have added some information that will hopefully help diagnose the real problem. My bottom line: Enblend works from command prompt, not from Hugin, and I suspect the issue is that Hugin may not be properly setting environment variables before launching Enblend. ERROR SEEN (during stitching, when directly run by Hugin): enblend: info: loading next image: pLTRR.tif 1/1 enblend: info: loading next image: pLTRR0001.tif 1/1 enblend: an exception occured enblend: enblend: unable to create image swap file name. enblend: info: remove invalid output image pLTRR.tif make: *** [pLTRR.tif] Error 1 HOWEVER: there is no error if the exact command listed in the Hugin window is run from command line! i.e., I copy the command, open a command prompt, go to the project folder f: cd \photos\pLTRR ...and paste in the enblend command: C:/apps/photo/Hugin/bin/enblend --compression LZW -w -f12764x5389 -o pLTRR.tif pLTRR.tif pLTRR0001.tif pLTRR0002.tif pLTRR0003.tif pLTRR0004.tif pLTRR0005.tif pLTRR0006.tif pLTRR0007.tif pLTRR0008.tif pLTRR0009.tif pLTRR0010.tif pLTRR0011.tif pLTRR0012.tif pLTRR0013.tif pLTRR0014.tif pLTRR0015.tif pLTRR0016.tif pLTRR0017.tif pLTRR0018.tif pLTRR0019.tif pLTRR0020.tif pLTRR0021.tif pLTRR0022.tif pLTRR0023.tif pLTRR0024.tif pLTRR0025.tif pLTRR0026.tif pLTRR0027.tif pLTRR0028.tif pLTRR0029.tif pLTRR0030.tif pLTRR0031.tif pLTRR0032.tif pLTRR0033.tif pLTRR0034.tif pLTRR0035.tif pLTRR0036.tif pLTRR0037.tif pLTRR0038.tif pLTRR0039.tif pLTRR0040.tif pLTRR0041.tif pLTRR0042.tif ENVIRONMENT WinXP SP3, Hugin 2010.1.0.5161 built by Zoran C: drive does NOT have enough space F: drive has plenty of space (30+GB free) Project is on F:; TMP and TEMP vars point to f:\temp\WinTmp Hugin temp setting points to f:\temp\HuginTmp SI FILEMON MONITOR LOG shows... From the command prompt, Enblend uses F:\temp\WinTmp as it should. From within Hugin, Enblend dies without attempting to create a temp file at all! THE BIG QUESTION What is different between calling Enblend from the command prompt vs from Hugin? My strong suspicion: Hugin improperly sets environment variables before launching Enblend To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/679512/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679512] Re: Enblend fails from Hugin, works from cmd line
Fixed quoting of TMP variable in makefile in default branch ** Changed in: hugin Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679512 Title: Enblend fails from Hugin, works from cmd line Status in Hugin - Panorama Tools GUI: Fix Committed Bug description: This bug has actually been reported a number of times, but closed out because people assumed it was simply a problem of not enough disk space. I have a case that proves this is not the case... and have added some information that will hopefully help diagnose the real problem. My bottom line: Enblend works from command prompt, not from Hugin, and I suspect the issue is that Hugin may not be properly setting environment variables before launching Enblend. ERROR SEEN (during stitching, when directly run by Hugin): enblend: info: loading next image: pLTRR.tif 1/1 enblend: info: loading next image: pLTRR0001.tif 1/1 enblend: an exception occured enblend: enblend: unable to create image swap file name. enblend: info: remove invalid output image pLTRR.tif make: *** [pLTRR.tif] Error 1 HOWEVER: there is no error if the exact command listed in the Hugin window is run from command line! i.e., I copy the command, open a command prompt, go to the project folder f: cd \photos\pLTRR ...and paste in the enblend command: C:/apps/photo/Hugin/bin/enblend --compression LZW -w -f12764x5389 -o pLTRR.tif pLTRR.tif pLTRR0001.tif pLTRR0002.tif pLTRR0003.tif pLTRR0004.tif pLTRR0005.tif pLTRR0006.tif pLTRR0007.tif pLTRR0008.tif pLTRR0009.tif pLTRR0010.tif pLTRR0011.tif pLTRR0012.tif pLTRR0013.tif pLTRR0014.tif pLTRR0015.tif pLTRR0016.tif pLTRR0017.tif pLTRR0018.tif pLTRR0019.tif pLTRR0020.tif pLTRR0021.tif pLTRR0022.tif pLTRR0023.tif pLTRR0024.tif pLTRR0025.tif pLTRR0026.tif pLTRR0027.tif pLTRR0028.tif pLTRR0029.tif pLTRR0030.tif pLTRR0031.tif pLTRR0032.tif pLTRR0033.tif pLTRR0034.tif pLTRR0035.tif pLTRR0036.tif pLTRR0037.tif pLTRR0038.tif pLTRR0039.tif pLTRR0040.tif pLTRR0041.tif pLTRR0042.tif ENVIRONMENT WinXP SP3, Hugin 2010.1.0.5161 built by Zoran C: drive does NOT have enough space F: drive has plenty of space (30+GB free) Project is on F:; TMP and TEMP vars point to f:\temp\WinTmp Hugin temp setting points to f:\temp\HuginTmp SI FILEMON MONITOR LOG shows... From the command prompt, Enblend uses F:\temp\WinTmp as it should. From within Hugin, Enblend dies without attempting to create a temp file at all! THE BIG QUESTION What is different between calling Enblend from the command prompt vs from Hugin? My strong suspicion: Hugin improperly sets environment variables before launching Enblend To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/679512/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679512] Re: Enblend fails from Hugin, works from cmd line
I have the same problem. Temp directory is not on C: because of low space so i moved it to D: ** Attachment added: logfile.log https://bugs.launchpad.net/hugin/+bug/679512/+attachment/2351868/+files/logfile.log -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679512 Title: Enblend fails from Hugin, works from cmd line Status in Hugin - Panorama Tools GUI: Confirmed Bug description: This bug has actually been reported a number of times, but closed out because people assumed it was simply a problem of not enough disk space. I have a case that proves this is not the case... and have added some information that will hopefully help diagnose the real problem. My bottom line: Enblend works from command prompt, not from Hugin, and I suspect the issue is that Hugin may not be properly setting environment variables before launching Enblend. ERROR SEEN (during stitching, when directly run by Hugin): enblend: info: loading next image: pLTRR.tif 1/1 enblend: info: loading next image: pLTRR0001.tif 1/1 enblend: an exception occured enblend: enblend: unable to create image swap file name. enblend: info: remove invalid output image pLTRR.tif make: *** [pLTRR.tif] Error 1 HOWEVER: there is no error if the exact command listed in the Hugin window is run from command line! i.e., I copy the command, open a command prompt, go to the project folder f: cd \photos\pLTRR ...and paste in the enblend command: C:/apps/photo/Hugin/bin/enblend --compression LZW -w -f12764x5389 -o pLTRR.tif pLTRR.tif pLTRR0001.tif pLTRR0002.tif pLTRR0003.tif pLTRR0004.tif pLTRR0005.tif pLTRR0006.tif pLTRR0007.tif pLTRR0008.tif pLTRR0009.tif pLTRR0010.tif pLTRR0011.tif pLTRR0012.tif pLTRR0013.tif pLTRR0014.tif pLTRR0015.tif pLTRR0016.tif pLTRR0017.tif pLTRR0018.tif pLTRR0019.tif pLTRR0020.tif pLTRR0021.tif pLTRR0022.tif pLTRR0023.tif pLTRR0024.tif pLTRR0025.tif pLTRR0026.tif pLTRR0027.tif pLTRR0028.tif pLTRR0029.tif pLTRR0030.tif pLTRR0031.tif pLTRR0032.tif pLTRR0033.tif pLTRR0034.tif pLTRR0035.tif pLTRR0036.tif pLTRR0037.tif pLTRR0038.tif pLTRR0039.tif pLTRR0040.tif pLTRR0041.tif pLTRR0042.tif ENVIRONMENT WinXP SP3, Hugin 2010.1.0.5161 built by Zoran C: drive does NOT have enough space F: drive has plenty of space (30+GB free) Project is on F:; TMP and TEMP vars point to f:\temp\WinTmp Hugin temp setting points to f:\temp\HuginTmp SI FILEMON MONITOR LOG shows... From the command prompt, Enblend uses F:\temp\WinTmp as it should. From within Hugin, Enblend dies without attempting to create a temp file at all! THE BIG QUESTION What is different between calling Enblend from the command prompt vs from Hugin? My strong suspicion: Hugin improperly sets environment variables before launching Enblend To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/679512/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679512] Re: Enblend fails from Hugin, works from cmd line
I installed Hugin 2011.0.0.0f9fdaf56720 built by Matthew Petroff on my PC, running under Win 7 Prof-64 bit and 4GB RAM. The system partition is a SSD with 60GB, so the images are located on a USB-drive with 160GB free. Possibly this is a hint: Interestingly the error doesn't depend on the size of the target image: some images, that are much larger than others, are enblended without any problem. Some, containing only 2 images of 12 MPx, don't work. The eroor occurs oin several panos (on several not..) If you are interested in the system architecture, tell me, what you want to know - possibly you have a workaround for me?? -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679512 Title: Enblend fails from Hugin, works from cmd line Status in Hugin - Panorama Tools GUI: Confirmed Bug description: This bug has actually been reported a number of times, but closed out because people assumed it was simply a problem of not enough disk space. I have a case that proves this is not the case... and have added some information that will hopefully help diagnose the real problem. My bottom line: Enblend works from command prompt, not from Hugin, and I suspect the issue is that Hugin may not be properly setting environment variables before launching Enblend. ERROR SEEN (during stitching, when directly run by Hugin): enblend: info: loading next image: pLTRR.tif 1/1 enblend: info: loading next image: pLTRR0001.tif 1/1 enblend: an exception occured enblend: enblend: unable to create image swap file name. enblend: info: remove invalid output image pLTRR.tif make: *** [pLTRR.tif] Error 1 HOWEVER: there is no error if the exact command listed in the Hugin window is run from command line! i.e., I copy the command, open a command prompt, go to the project folder f: cd \photos\pLTRR ...and paste in the enblend command: C:/apps/photo/Hugin/bin/enblend --compression LZW -w -f12764x5389 -o pLTRR.tif pLTRR.tif pLTRR0001.tif pLTRR0002.tif pLTRR0003.tif pLTRR0004.tif pLTRR0005.tif pLTRR0006.tif pLTRR0007.tif pLTRR0008.tif pLTRR0009.tif pLTRR0010.tif pLTRR0011.tif pLTRR0012.tif pLTRR0013.tif pLTRR0014.tif pLTRR0015.tif pLTRR0016.tif pLTRR0017.tif pLTRR0018.tif pLTRR0019.tif pLTRR0020.tif pLTRR0021.tif pLTRR0022.tif pLTRR0023.tif pLTRR0024.tif pLTRR0025.tif pLTRR0026.tif pLTRR0027.tif pLTRR0028.tif pLTRR0029.tif pLTRR0030.tif pLTRR0031.tif pLTRR0032.tif pLTRR0033.tif pLTRR0034.tif pLTRR0035.tif pLTRR0036.tif pLTRR0037.tif pLTRR0038.tif pLTRR0039.tif pLTRR0040.tif pLTRR0041.tif pLTRR0042.tif ENVIRONMENT WinXP SP3, Hugin 2010.1.0.5161 built by Zoran C: drive does NOT have enough space F: drive has plenty of space (30+GB free) Project is on F:; TMP and TEMP vars point to f:\temp\WinTmp Hugin temp setting points to f:\temp\HuginTmp SI FILEMON MONITOR LOG shows... From the command prompt, Enblend uses F:\temp\WinTmp as it should. From within Hugin, Enblend dies without attempting to create a temp file at all! THE BIG QUESTION What is different between calling Enblend from the command prompt vs from Hugin? My strong suspicion: Hugin improperly sets environment variables before launching Enblend To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/679512/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679512] Re: Enblend fails from Hugin, works from cmd line
I have no access to Windows and can not help much, but I think this report deserves at least to be re-opened and investigated after it has been recently confirmed by two users, one of whom even provides a workaround. What interest me is: what triggers this bug? if it was a generalized bug, we would see many more reports. I would call Hugin for Windows broken if it consistently failed all stitching attempt at the blending stage. So what is it that makes your case different from the general public? Do you have a Temporary dir set in the Hugin's preferences, or is it empty (system default)? Try going to the Preferences menu, General tab, and hit the Load Defaults button. See if a simple stitch (two images only) works. If it is not in Hugin's preferences, maybe it is a system environment variable that points to a non-default temp location? If you can find what is it that trigger the condition, we can have a look if it can be improved in the code. Since it does not seem to affect the vast majority of Windows users, I am not inclined to fiddle with not adding the quotes as suggested in comment #6. Maybe the solution will be not adding the quotes *if* That condition that makes your system different from the default system, needs to be identified, and side-effects on the default settings must be considered before making the change. ** Changed in: hugin Status: Fix Released = Confirmed -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679512 Title: Enblend fails from Hugin, works from cmd line Status in Hugin - Panorama Tools GUI: Confirmed Bug description: This bug has actually been reported a number of times, but closed out because people assumed it was simply a problem of not enough disk space. I have a case that proves this is not the case... and have added some information that will hopefully help diagnose the real problem. My bottom line: Enblend works from command prompt, not from Hugin, and I suspect the issue is that Hugin may not be properly setting environment variables before launching Enblend. ERROR SEEN (during stitching, when directly run by Hugin): enblend: info: loading next image: pLTRR.tif 1/1 enblend: info: loading next image: pLTRR0001.tif 1/1 enblend: an exception occured enblend: enblend: unable to create image swap file name. enblend: info: remove invalid output image pLTRR.tif make: *** [pLTRR.tif] Error 1 HOWEVER: there is no error if the exact command listed in the Hugin window is run from command line! i.e., I copy the command, open a command prompt, go to the project folder f: cd \photos\pLTRR ...and paste in the enblend command: C:/apps/photo/Hugin/bin/enblend --compression LZW -w -f12764x5389 -o pLTRR.tif pLTRR.tif pLTRR0001.tif pLTRR0002.tif pLTRR0003.tif pLTRR0004.tif pLTRR0005.tif pLTRR0006.tif pLTRR0007.tif pLTRR0008.tif pLTRR0009.tif pLTRR0010.tif pLTRR0011.tif pLTRR0012.tif pLTRR0013.tif pLTRR0014.tif pLTRR0015.tif pLTRR0016.tif pLTRR0017.tif pLTRR0018.tif pLTRR0019.tif pLTRR0020.tif pLTRR0021.tif pLTRR0022.tif pLTRR0023.tif pLTRR0024.tif pLTRR0025.tif pLTRR0026.tif pLTRR0027.tif pLTRR0028.tif pLTRR0029.tif pLTRR0030.tif pLTRR0031.tif pLTRR0032.tif pLTRR0033.tif pLTRR0034.tif pLTRR0035.tif pLTRR0036.tif pLTRR0037.tif pLTRR0038.tif pLTRR0039.tif pLTRR0040.tif pLTRR0041.tif pLTRR0042.tif ENVIRONMENT WinXP SP3, Hugin 2010.1.0.5161 built by Zoran C: drive does NOT have enough space F: drive has plenty of space (30+GB free) Project is on F:; TMP and TEMP vars point to f:\temp\WinTmp Hugin temp setting points to f:\temp\HuginTmp SI FILEMON MONITOR LOG shows... From the command prompt, Enblend uses F:\temp\WinTmp as it should. From within Hugin, Enblend dies without attempting to create a temp file at all! THE BIG QUESTION What is different between calling Enblend from the command prompt vs from Hugin? My strong suspicion: Hugin improperly sets environment variables before launching Enblend To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/679512/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679512] Re: Enblend fails from Hugin, works from cmd line
I also duplicated this error. My system is also windows 7 64-bit, though i'm not sure that makes a difference, since i resolved this by using a script to remove the quotes that hugin is adding to the values of TEMP and TMP environment variables. I suspect the windows api calls in enblend.exe to retrieve value of TEMP folder don't tolerate quotes in the path. WORKAROUND: create a script in your C:\Program Files (x86)\Hugin\bin called enblend.cmd with the contents: if defined TEMP set TEMP=%TEMP:=% if defined TMP set TMP=%TMP:=% %~dp0\enblend.exe %* (you might have to open notepad with run as administrator rights to modify/create files in program files under windows 7). then change the preferences in hugin to choose the C:\Program Files (x86)\Hugin\bin\enblend.cmd instead of the enblend.exe. (under File, preferences, stitching tab, use alternative enblend program) Maybe the resolution will be to change hugin not to add the quotes? Be curious if this workaround works consistently for everyone else... I'm new to trying hugin but have unsuccessful at creating a stitched .exr hdr type panorama.. still trying... I resorted to 32 bit hugin because i was having issues with 64-bit not creating any HDR exr output either... -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679512 Title: Enblend fails from Hugin, works from cmd line Status in Hugin - Panorama Tools GUI: Fix Released Bug description: This bug has actually been reported a number of times, but closed out because people assumed it was simply a problem of not enough disk space. I have a case that proves this is not the case... and have added some information that will hopefully help diagnose the real problem. My bottom line: Enblend works from command prompt, not from Hugin, and I suspect the issue is that Hugin may not be properly setting environment variables before launching Enblend. ERROR SEEN (during stitching, when directly run by Hugin): enblend: info: loading next image: pLTRR.tif 1/1 enblend: info: loading next image: pLTRR0001.tif 1/1 enblend: an exception occured enblend: enblend: unable to create image swap file name. enblend: info: remove invalid output image pLTRR.tif make: *** [pLTRR.tif] Error 1 HOWEVER: there is no error if the exact command listed in the Hugin window is run from command line! i.e., I copy the command, open a command prompt, go to the project folder f: cd \photos\pLTRR ...and paste in the enblend command: C:/apps/photo/Hugin/bin/enblend --compression LZW -w -f12764x5389 -o pLTRR.tif pLTRR.tif pLTRR0001.tif pLTRR0002.tif pLTRR0003.tif pLTRR0004.tif pLTRR0005.tif pLTRR0006.tif pLTRR0007.tif pLTRR0008.tif pLTRR0009.tif pLTRR0010.tif pLTRR0011.tif pLTRR0012.tif pLTRR0013.tif pLTRR0014.tif pLTRR0015.tif pLTRR0016.tif pLTRR0017.tif pLTRR0018.tif pLTRR0019.tif pLTRR0020.tif pLTRR0021.tif pLTRR0022.tif pLTRR0023.tif pLTRR0024.tif pLTRR0025.tif pLTRR0026.tif pLTRR0027.tif pLTRR0028.tif pLTRR0029.tif pLTRR0030.tif pLTRR0031.tif pLTRR0032.tif pLTRR0033.tif pLTRR0034.tif pLTRR0035.tif pLTRR0036.tif pLTRR0037.tif pLTRR0038.tif pLTRR0039.tif pLTRR0040.tif pLTRR0041.tif pLTRR0042.tif ENVIRONMENT WinXP SP3, Hugin 2010.1.0.5161 built by Zoran C: drive does NOT have enough space F: drive has plenty of space (30+GB free) Project is on F:; TMP and TEMP vars point to f:\temp\WinTmp Hugin temp setting points to f:\temp\HuginTmp SI FILEMON MONITOR LOG shows... From the command prompt, Enblend uses F:\temp\WinTmp as it should. From within Hugin, Enblend dies without attempting to create a temp file at all! THE BIG QUESTION What is different between calling Enblend from the command prompt vs from Hugin? My strong suspicion: Hugin improperly sets environment variables before launching Enblend To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/679512/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679512] Re: Enblend fails from Hugin, works from cmd line
An further update. Am now now having this problem when I run the make file from the command line. Not sure if it relevant: I got the LZW compression is not available due to Unisys patent enforcement error from Enblend. Does this mean its using uncompressed files and running out of memory? System info: C and E drive are partitions on the same physical disk. C has 1GB free, E has 600GB free. source files are located on E: and destination file goes there too. Scratch drive is G: (separate physical drive with 1300GB free). Scratch is set correctly in makefile, hugin preferences, and system variables. System has 8GB RAM supplemented by 2x4GB Readyboost devices. OS is windows 7 Ultimate 64 bit Hugin version 2010.4 64bit. I got further through the stitch process using -m6500 parameter for enblend. Doing the same for enfuse got me even further. The project is a 3 Exposure HDR 360x180 spherical panorama stitched at 12000x6000 pixels. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679512 Title: Enblend fails from Hugin, works from cmd line Status in Hugin - Panorama Tools GUI: Fix Released Bug description: This bug has actually been reported a number of times, but closed out because people assumed it was simply a problem of not enough disk space. I have a case that proves this is not the case... and have added some information that will hopefully help diagnose the real problem. My bottom line: Enblend works from command prompt, not from Hugin, and I suspect the issue is that Hugin may not be properly setting environment variables before launching Enblend. ERROR SEEN (during stitching, when directly run by Hugin): enblend: info: loading next image: pLTRR.tif 1/1 enblend: info: loading next image: pLTRR0001.tif 1/1 enblend: an exception occured enblend: enblend: unable to create image swap file name. enblend: info: remove invalid output image pLTRR.tif make: *** [pLTRR.tif] Error 1 HOWEVER: there is no error if the exact command listed in the Hugin window is run from command line! i.e., I copy the command, open a command prompt, go to the project folder f: cd \photos\pLTRR ...and paste in the enblend command: C:/apps/photo/Hugin/bin/enblend --compression LZW -w -f12764x5389 -o pLTRR.tif pLTRR.tif pLTRR0001.tif pLTRR0002.tif pLTRR0003.tif pLTRR0004.tif pLTRR0005.tif pLTRR0006.tif pLTRR0007.tif pLTRR0008.tif pLTRR0009.tif pLTRR0010.tif pLTRR0011.tif pLTRR0012.tif pLTRR0013.tif pLTRR0014.tif pLTRR0015.tif pLTRR0016.tif pLTRR0017.tif pLTRR0018.tif pLTRR0019.tif pLTRR0020.tif pLTRR0021.tif pLTRR0022.tif pLTRR0023.tif pLTRR0024.tif pLTRR0025.tif pLTRR0026.tif pLTRR0027.tif pLTRR0028.tif pLTRR0029.tif pLTRR0030.tif pLTRR0031.tif pLTRR0032.tif pLTRR0033.tif pLTRR0034.tif pLTRR0035.tif pLTRR0036.tif pLTRR0037.tif pLTRR0038.tif pLTRR0039.tif pLTRR0040.tif pLTRR0041.tif pLTRR0042.tif ENVIRONMENT WinXP SP3, Hugin 2010.1.0.5161 built by Zoran C: drive does NOT have enough space F: drive has plenty of space (30+GB free) Project is on F:; TMP and TEMP vars point to f:\temp\WinTmp Hugin temp setting points to f:\temp\HuginTmp SI FILEMON MONITOR LOG shows... From the command prompt, Enblend uses F:\temp\WinTmp as it should. From within Hugin, Enblend dies without attempting to create a temp file at all! THE BIG QUESTION What is different between calling Enblend from the command prompt vs from Hugin? My strong suspicion: Hugin improperly sets environment variables before launching Enblend To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/679512/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679512] Re: Enblend fails from Hugin, works from cmd line
Just ran into the issue again. This time I copied the failed enblend command from the error log and ran it on the command line. It worked without any problems. Is this information helpful? Enblend failed when it encountered the first image that wrapped around the 0-360 degree boundary. Could be a coincidence. I will check future errors to see if this is a recurring aspect. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679512 Title: Enblend fails from Hugin, works from cmd line Status in Hugin - Panorama Tools GUI: Fix Released Bug description: This bug has actually been reported a number of times, but closed out because people assumed it was simply a problem of not enough disk space. I have a case that proves this is not the case... and have added some information that will hopefully help diagnose the real problem. My bottom line: Enblend works from command prompt, not from Hugin, and I suspect the issue is that Hugin may not be properly setting environment variables before launching Enblend. ERROR SEEN (during stitching, when directly run by Hugin): enblend: info: loading next image: pLTRR.tif 1/1 enblend: info: loading next image: pLTRR0001.tif 1/1 enblend: an exception occured enblend: enblend: unable to create image swap file name. enblend: info: remove invalid output image pLTRR.tif make: *** [pLTRR.tif] Error 1 HOWEVER: there is no error if the exact command listed in the Hugin window is run from command line! i.e., I copy the command, open a command prompt, go to the project folder f: cd \photos\pLTRR ...and paste in the enblend command: C:/apps/photo/Hugin/bin/enblend --compression LZW -w -f12764x5389 -o pLTRR.tif pLTRR.tif pLTRR0001.tif pLTRR0002.tif pLTRR0003.tif pLTRR0004.tif pLTRR0005.tif pLTRR0006.tif pLTRR0007.tif pLTRR0008.tif pLTRR0009.tif pLTRR0010.tif pLTRR0011.tif pLTRR0012.tif pLTRR0013.tif pLTRR0014.tif pLTRR0015.tif pLTRR0016.tif pLTRR0017.tif pLTRR0018.tif pLTRR0019.tif pLTRR0020.tif pLTRR0021.tif pLTRR0022.tif pLTRR0023.tif pLTRR0024.tif pLTRR0025.tif pLTRR0026.tif pLTRR0027.tif pLTRR0028.tif pLTRR0029.tif pLTRR0030.tif pLTRR0031.tif pLTRR0032.tif pLTRR0033.tif pLTRR0034.tif pLTRR0035.tif pLTRR0036.tif pLTRR0037.tif pLTRR0038.tif pLTRR0039.tif pLTRR0040.tif pLTRR0041.tif pLTRR0042.tif ENVIRONMENT WinXP SP3, Hugin 2010.1.0.5161 built by Zoran C: drive does NOT have enough space F: drive has plenty of space (30+GB free) Project is on F:; TMP and TEMP vars point to f:\temp\WinTmp Hugin temp setting points to f:\temp\HuginTmp SI FILEMON MONITOR LOG shows... From the command prompt, Enblend uses F:\temp\WinTmp as it should. From within Hugin, Enblend dies without attempting to create a temp file at all! THE BIG QUESTION What is different between calling Enblend from the command prompt vs from Hugin? My strong suspicion: Hugin improperly sets environment variables before launching Enblend To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/679512/+subscriptions ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 679512] Re: Enblend fails from Hugin, works from cmd line
enblend got the composition of the TMPDIR variable wrong. IIRC this has been fixed or is being fixed. Please check that it still happens on 2010.4. It fails to make the tmp file NAME. Not that the disk fills after writing a little bit to the temp file ** Tags added: enblend tmpdir ** Changed in: hugin Status: New = Fix Released ** Changed in: hugin Importance: Undecided = Low -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679512 Title: Enblend fails from Hugin, works from cmd line Status in Hugin - Panorama Tools GUI: Fix Released Bug description: This bug has actually been reported a number of times, but closed out because people assumed it was simply a problem of not enough disk space. I have a case that proves this is not the case... and have added some information that will hopefully help diagnose the real problem. My bottom line: Enblend works from command prompt, not from Hugin, and I suspect the issue is that Hugin may not be properly setting environment variables before launching Enblend. ERROR SEEN (during stitching, when directly run by Hugin): enblend: info: loading next image: pLTRR.tif 1/1 enblend: info: loading next image: pLTRR0001.tif 1/1 enblend: an exception occured enblend: enblend: unable to create image swap file name. enblend: info: remove invalid output image pLTRR.tif make: *** [pLTRR.tif] Error 1 HOWEVER: there is no error if the exact command listed in the Hugin window is run from command line! i.e., I copy the command, open a command prompt, go to the project folder f: cd \photos\pLTRR ...and paste in the enblend command: C:/apps/photo/Hugin/bin/enblend --compression LZW -w -f12764x5389 -o pLTRR.tif pLTRR.tif pLTRR0001.tif pLTRR0002.tif pLTRR0003.tif pLTRR0004.tif pLTRR0005.tif pLTRR0006.tif pLTRR0007.tif pLTRR0008.tif pLTRR0009.tif pLTRR0010.tif pLTRR0011.tif pLTRR0012.tif pLTRR0013.tif pLTRR0014.tif pLTRR0015.tif pLTRR0016.tif pLTRR0017.tif pLTRR0018.tif pLTRR0019.tif pLTRR0020.tif pLTRR0021.tif pLTRR0022.tif pLTRR0023.tif pLTRR0024.tif pLTRR0025.tif pLTRR0026.tif pLTRR0027.tif pLTRR0028.tif pLTRR0029.tif pLTRR0030.tif pLTRR0031.tif pLTRR0032.tif pLTRR0033.tif pLTRR0034.tif pLTRR0035.tif pLTRR0036.tif pLTRR0037.tif pLTRR0038.tif pLTRR0039.tif pLTRR0040.tif pLTRR0041.tif pLTRR0042.tif ENVIRONMENT WinXP SP3, Hugin 2010.1.0.5161 built by Zoran C: drive does NOT have enough space F: drive has plenty of space (30+GB free) Project is on F:; TMP and TEMP vars point to f:\temp\WinTmp Hugin temp setting points to f:\temp\HuginTmp SI FILEMON MONITOR LOG shows... From the command prompt, Enblend uses F:\temp\WinTmp as it should. From within Hugin, Enblend dies without attempting to create a temp file at all! THE BIG QUESTION What is different between calling Enblend from the command prompt vs from Hugin? My strong suspicion: Hugin improperly sets environment variables before launching Enblend ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
