|
|
Adding image file. 2023-04-16_130859.jpg (286,826 bytes) |
|
|
The problem "Filename encoding not specified" is due to the fact that an instruction like "-charset filename=latin" is missing. I have already asked to be able to add instructions when reading exiftool tags (see 2509) |
|
|
Thanks, but, I think "-charset filename=latin" will not resolve the situation, because the target filename is already in Latin, and, CR2 files (in Latin) does not have the problem. |
|
|
@TaK: Either the file name or the path contains accented characters: the problem does not come from GeoSetter but from Exiftool which is used be GeoSetter to retrieve the metadata |
|
|
Test the following line with and without "-charset filename=latin" exiftool -a -G1 -s -charset filename=latin "FullPathFile" |
|
|
>Either the file name or the path contains accented characters: Aha! I used Kanji (one of UTF-8 character set) for the path. So, I tested moving the file in a folder in English, BUT, it did not work! See the attached picture. The EXIFTool error is gone! However, the captioned problem persists. So, my problem differs from your problem. (Also, CR2 files and JPG files are OK even if in a Kanji name folder. And Aperture or Focal Length data is retrieved even if CR3 files. Those facts demonstrate that file/folder name is not the cause in my case.)
2023-04-17_073000.jpg (163,122 bytes) |
|
|
My intervention is only for the Warning message of the Exiftool tool not for the other errors. Sorry |
|
|
I have the exact same problem: In all CR3 Pictures (from R6, new firmware) there is no date displayed (so I can not match with GPS logfile). Other programs (like XnView) display the date of CR3 correct. In the corresponding JPG-files are all data correct. It makes my process VERY complicated if I want to have GPS-Data also in my CR3-files (resp. XML sidecar-files)! Is there a solution?! |
|
|
@Erik: Could the software "www.routeconverter.com" be useful to you? |
|
|
> "www.routeconverter.com" be useful to you? Nop. |
- Anonymous
