Long filenames report not found

[thany]

Windows happily supports very long filenames, let's get that out of the way. Due to legacy API's, a lot of software is blissfully unaware of paths longer than 260 characters. Since a very long time, paths of up to 32K characters have been possible.

Exiftool, when it is fed a filename whose path is longer than the aforementioned 260 characters, will say

Code Select Expand


Error: File not found - (repeats the filename back at me)


Not only is this an incorrect error message, it is also completely fixable. I don't know how, but it is definitely possible. More and more software can deal with these files.

And no, I cannot rename these files before processing them in exiftool. The filenames contain tags, and I'm looking to keep them there until I've found a way to transplant them into their metadata.

[Phil Harvey]

I don't know how to fix this.  It is a limitation of the version of Perl for Windows that ExifTool is using.

- Phil

[obetz]

even running ExifTool with 64 bit Strawberry Perl doesn't help.

[herb]

Hello Phil, hello obetz,

accidentally I found this: https://metacpan.org/pod/Win32::LongPath

Best regards
herb