hugin-devs team mailing list archive

[Matthew Petroff <685899@xxxxxxxxxxxxxxxxxx>]

Enblend 4.0-6e6f573e57be exhibits the same behavior for me under Windows
XP.

** Changed in: enblend
       Status: New => Confirmed

** Changed in: enblend
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/685899

Title:
  windows: enblend: short filename directory error

Status in Enblend:
  Confirmed

Bug description:
  enblend 4.0-6e6f573e57be
Windows XP32 SP3

-- input --
enblend.exe --output=test.tif C:\THISIS~1\1.TIF C:\THISIS~1\2.TIF C:\THISIS~1\3.TIF
-- /input --

-- error output --
enblend: cannot load image "C:\THISIS~1\1.tif", because the
enblend:     format of the file is unrecognized or unknown
-- /error output --

"C:\THISIS~1\" expands to the LFN "C:\This is a long path\".  If specifying the LFN rather than the SFN, no error occurs.

Oddly enough, specifying the SFN for source file images' filenames appears to be fine (e.g. "c:\This is a long path\THISIS~1.TIF") - it's when the directory contains a SFN that an error occurs.

Ran into this after PTGui stated that Enblend failed with 'Error 1' without further details after upgrading to Enblend 4 (from Enblend 3, which was fine).  Turns out the temporary file path used by PTGui was so old that it was still set to SFN.  Re-selecting the directory (folder) in PTGui so that it would grab the LFN fixed the problem.