View Issue Details

IDProjectCategoryView StatusLast Update
0002547GeoSetterUser Interfacepublic2024-11-12 00:24
ReporterWilfriedB Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status newResolutionopen 
PlatformThinkPadOSWindows 10OS Version23H2 Build 19045
Product Version 
Target VersionFixed in Version 
Summary0002547: Exiftool 12.88 and 12.89 brings error "could not find .... exiGeoSetter_beta\tools\ftool_files\perl5*.dll"
DescriptionAfter installing Exiftool 12.88, I cannot save any changed files, but get this message
TagsNo tags attached.

Activities

WilfriedB

2024-07-13 16:30

reporter  

grafik.png (30,262 bytes)
grafik.png (30,262 bytes)

EdiSagi

2024-07-13 17:03

reporter   ~0004830

Had the same error. The folder "\exiftool_files\" does not exist. I created this folder and copied the files from the downloaded file "exiftool-12.89_32.zip\exiftool-12.89_32\exiftool_files" to it. I suspect EXIFTOOLS has changed its folder structure.

WilfriedB

2024-07-13 20:12

reporter   ~0004831

Thanks a lot @EdiSagi. Seems to work. I didn't find exiftool-12.89_32.zip but moved all new files from \tools\ to the new \exiftool_files folder. Hopefully, it didn't create some other problems.

xyzzy

2024-07-16 18:23

reporter   ~0004832

For my part, I use ExifTool outside of GeoSetter.
So I created a directory (d:\ExifTool\Current) and I placed any new version of ExifTool there.
For GeoSetter, in the file "config.ini" section "[ExifTool]",
 I configured this line
CustomPath=D:\exiftool\current

zava

2024-07-16 22:58

reporter   ~0004833

Had same problem after update.
This seems to add one more shaky patch to keep GS going... which is one next step towards reducing usability, since GS appears to face no new developments, corrections, versions or even maintenance in any foreseeable future...

zava

2024-07-16 23:28

reporter   ~0004834

I tried the same solution suggested by EdiSagi; in my case, although I had clicked "install" latest exiftool version, no exiftool files or folders or zips were created anywhere relating to the most recent versions.
So I made the requested folder and copied there all exiftool files from the latest version I could find which was in C:\Users\Username\AppData\Roaming\GeoSetter_beta\tools
(plus probably several spurious files that were in the same folder).
This probably duplicated a lot of files but apparently worked.
But I guess there will be problems with all future exiftool versions...
One more crack in our beloved GS building...

WilfriedB

2024-07-17 19:00

reporter   ~0004835

@zava and @xyzzy the problem was reported a second time and @othmarmarti suggested a better workaround here: https://www.geosetter.de/mantis/view.php?id=2548

xyzzy

2024-07-19 00:20

reporter   ~0004836

@WilfriedB:
It all depends on each person’s goals.
Personally, I prefer to separate ExifTool installations and its updates independently from other software that uses it.
I agree with you that GeoSetter should follow the evolution of ExifTool.
But as we no longer have any news from @Friedemann on these next developments, we have to "deal with it".
:(

ceroni

2024-07-24 23:36

reporter   ~0004837

The solution by https://geosetter.de/mantis/view_user_page.php?id=2742 (https://geosetter.de/mantis/view.php?id=2547#c4832) works perfectly for me. This way one can keep a centralized ExifTooll installation that is easy to update. Also, I have some scripts that use ExifTool to do various things (rename files according to CreateDate, inject metadata into video files, etc).

John_Lam

2024-09-01 02:29

reporter   ~0004841

thanks @EdiSagi and @xyzzy on the idea to work around the problem

Just for anyone that pull the ExifTool package through WinGet (winget install -e --id OliverBetz.ExifTool)

ExifTools install path will be inside the localappdata
C:\Users\<UserName>\AppData\Local\Programs\ExifTool
%localappdata%\Programs\ExifTool

just testing with the config.ini file and confirm that it doesn't take the environment variables path so will need to use the full path
for successful example: CustomPath=C:\Users\<UserName>\AppData\Local\Programs\ExifTool
for failure example: CustomPath=%localappdata%\Programs\ExifTool

dydxdx

2024-11-10 23:38

reporter   ~0004842

Same problem with exiftool_files....suggested solutions don't work for me. Think I've corrupted the proggie with all the tinkering, uninstall/reinstall: "Can't locate strict.pm in @INC "

dydxdx

2024-11-12 00:24

reporter   ~0004843

The work-around that works for me: rollback to GS-Beta v4.0.47 which installs exiftool 12.56 in the correct folder...ignore update nag screen on opening. I'll live with missing the fixes to 4.0.49.

Issue History

Date Modified Username Field Change
2024-07-13 16:30 WilfriedB New Issue
2024-07-13 16:30 WilfriedB File Added: grafik.png
2024-07-13 17:03 EdiSagi Note Added: 0004830
2024-07-13 20:12 WilfriedB Note Added: 0004831
2024-07-16 18:23 xyzzy Note Added: 0004832
2024-07-16 22:58 zava Note Added: 0004833
2024-07-16 23:28 zava Note Added: 0004834
2024-07-17 19:00 WilfriedB Note Added: 0004835
2024-07-19 00:20 xyzzy Note Added: 0004836
2024-07-24 23:36 ceroni Note Added: 0004837
2024-09-01 02:29 John_Lam Note Added: 0004841
2024-11-10 23:38 dydxdx Note Added: 0004842
2024-11-12 00:24 dydxdx Note Added: 0004843