Exiftool and Google Drive sync issues?

[ribtoks]

Hello

I've been using exiftool for a while for reading metadata in Xpiks (https://github.com/ribtoks/xpiks) on-par with exiv2 library. Users are reporting (https://groups.google.com/forum/#!topic/xpiks-support/ZnwDmJoadYU) issues with reading metadata when using exiftool if their files are stored at Google Drive. However strangely enough this issue does not repro if using exiv2 library.

From experience I know there were issues if using memory-mapping techniques and Google Drive so I have questions:
1. Is this issue know or any known workarounds? (google hasn't found anything useful)
2. Does exiftool uses memory-mapping? If yes, is there an option to turn it off?

Thanks

[Phil Harvey]

From a quick look over the other thread, I'm guessing that the problem is (yet again) due to Unicode characters in the file/directory names.  What encoding are you using for the file names?  Are you using the -charset filename=XXX option to tell exiftool what character set you are using?

- Phil

[ribtoks]

From a quick look over the other thread, I'm guessing that the problem is (yet again) due to Unicode characters in the file/directory names.  What encoding are you using for the file names?  Are you using the -charset filename=XXX option to tell exiftool what character set you are using?

- Phil

Hello Phil

First of all, excuse me for the super very late reply. [excuse list] I didn't receive notifications from the thread and forgot to check myself [\]

No, I've learned to use exiftool with unicode filepaths correctly already some time ago, so this should not be the case

I'm using

Code Select Expand

arguments << "-charset" << "FileName=UTF8";.

I know there're issues with Windows-ported memory mapping functions so I was afraid that could be the case with exiftool.
These issues are more or less easily reproduced when using > 40 files. That's why I thought it could be a known issue.

[Phil Harvey]

I don't remember anything about memory mapping problems, but there is a command-line-length limitation in Windows which is easy to exceed, but I presume you are using -@ to get around this (based on the "<<" in your example).

You say it is easy to reproduce.  Can you detail the steps so I can reproduce this?

- Phil