"A long time ago in a galaxy far, far away....", I wrote pyExifToolGUI (a python/pyside graphical frontend for exiftool). In the past 6/7 years I had some major changes and hiccups in my life, but in 2019 I wanted to pick up again. However, pyside/QT went through some major software and license changes. Next to that: pyside is almost dead. As I had started writing in Android java, I decided to rebuild it in "pc" java, hence j(ava)ExifToolGUI. Also because building a graphical cross-platform tool in java is so much easier when it comes to OS dependencies.
I started one year ago, completely stopped in June 2019, and continued again this year in June.
(https://raw.githubusercontent.com/hvdwolf/jExifToolGUI/master/images/multi-platform-1280.jpg)
I just released 0.99-beta.
I tested it on several Linuxes incl. Chromebook Linux Beta, on Windows 10 and MacOS.
You can find a Readme here (https://github.com/hvdwolf/jExifToolGUI/blob/master/README.md).
A temporary website here (https://hvdwolf.github.io/jExifToolGUI/).
And the (binary) releases here (https://github.com/hvdwolf/jExifToolGUI/releases).
Some short "installation" instructions are here (https://hvdwolf.github.io/jExifToolGUI/installing.html)
Let me know what you think.
Note: Development on this project has stopped. (read here) (https://exiftool.org/forum/index.php?msg=82898)
This look promising, but I'm going to have to look into what is involved with upgrading to Java V11, and what it will break if I do this.
- Phil
Like mentioned on the releases page. There is the "jExifToolGUI-0.99-beta-win-x86_64.zip: A windows 64-bit executable including java V11. Unzip with paths!"
So that one has the V11 jre in the same folder as the exe. No need to install another java version.
So if you unzip that zip file, you get in "some" folder:
LICENSE <- text file (default GPL-3 license)
jExifToolGUI-1.00.exe <- executable
jre <- folder containing the V11 jre
And o so stupid: my packaging script did not rename the exe to 0.99-beta. Well, I already mentioned it was a beta ::)
Ah, right thanks. I'm on MacOS and see you have a bundle for it too.
- Phil
I released the following version: 1.00-betaThose who have the checkbox "Check for new jExifToolGUI version on program start" switched on in the Preferences will get an automatic popup.
Changelog 10 July 2020:
- Add "Edit lens tab". Enables to save (additional) lens data and to create and save lens configurations for future use.
- Add SQLite database with exiftool tags, groups, families.
- Reconfigure menu.
- Make compatible again with java 8. Split MacOS and Windows in a "with jre" and a "without jre" package (for those downloads with included jre, the jre version is still V 11).
- Add "lens data" view option under "Common Tags".
- Add exiftool supported languages for displaying metadata tags (also in "export metadata"). See under Preferences.
Meaning that java 8 is now supported again, also means that many Windows and MacOS users can now download the version without the extra JRE (java runtime environment) as on most Windows 7/8/10 and MacOS versions "of the last years", this java version 8 (actually 1.8_xyz)* is installed.
You can find the binary releases here (https://github.com/hvdwolf/jExifToolGUI/releases).
A readme here (https://github.com/hvdwolf/jExifToolGUI/blob/master/README.md).
A temporary website here (https://hvdwolf.github.io/jExifToolGUI/).
Some short "installation" instructions are here (https://hvdwolf.github.io/jExifToolGUI/installing.html) (but these need to be adapted now for the macos/windows "without jre" packages.)
ToDo?:- Custom views and Edits: A Maintenance screen for users to create a view with their desired tags for viewing (all tags possible), and for editing (only writable tags).
- Translations? Do users want that? Requires translators to help in translating.
*:
Java changed the naming conventions for their versions. Everything below version 9 is 1.8_xyz (or 1.7, 1.6, etc.). As of 9 they are called version 9, 10, 11, etc.
Release of version 1.01-betaThis is a bug fix. :(
Changelog 1.01, 11 July 2020:
- Fix (stupid) mistake in parameters for gps and location view
Download here (https://github.com/hvdwolf/jExifToolGUI/releases).
See post above for other links.
Version 1.1.0releases: https://github.com/hvdwolf/jExifToolGUI/releases
Changelog
- Add work-around for displaying RAW images in the left panel based on Thumbnail/PreviewImage.
- add: Extract all previews/thumbs from selected image(s): "(menu) Other -> Export all previews/thumbs from selected".
- housekeeping: (re)create temp work folder on program start and delete (incl. contents) on program exit.
- Add splash screen to Linux and Mac versions. (Windows versions crash for some reason)
- Fix: debian .deb package. Icon name incorrect in jexiftoolgui.desktop.
- Internal: Go back to good old Linux/Unix versioning scheme.
I can't find a "Thumbs up" or "+1" or "Thank you" for your great work.
Highly appreciated!
Thank you.
I still have a long ToDo list:
- Add "load directory" next to "load images"*
- Add option to add RAW image viewer to preferences (and optionally make it default for all images as well)
- Make xmp & iptc & "sub"-xmp keywords/subjects/PersonInImage more dedicated (Known error: I currently do the PersonInImage wrong: as one string instead of String+)
- Custom views/Edits.
- slideshow with all metadata (full-screen) left-right pane image/info (or vice versa).
- Make "Quick Reference Guide".
- Translate application??? (requires translators, so only when volunteers do that. Next to Dutch and English, I do speak French, German, Danish but not enough to make good translations)
*: But did you know that if you open a folder, click an image and do Ctrl-A/Cmd-A, you can select all images at once in that folder? Likewise multi-select options with Ctl-Select/Cmd-Select and/or Shift-Select.
Version 1.3.0releases: https://github.com/hvdwolf/jExifToolGUI/releases
Changelog
- Add "XMP_IPTC_Strings+" tab. Currently contains Keywords, Subject and PersonInImage. Allows for more fine-grained options when compared to simple "overwrite" in XMP-tab (and might be extended with more).
- Add "simple"xmp-pdf:keywords to XMP tab
- Fix: multiple errors in XMP tab
- Add xmp:credit to the defaults.
- Under Help menu: add "System/Program Info" to show some info (in case we need to troubleshoot).
- Fix: Copy defaults on Exif & XMP (copy Artist/Creator, Credit and Copyrights back in if somehow removed)
- embed splash screen in jar; also works on windows
Version 1.2 (not released)
- Add button "Load Directory" and (menu) "File -> Directory"
- Issue #32 (https://github.com/hvdwolf/jExifToolGUI/issues/32): First remark -> field size.
Released version 1.4.0releases: https://github.com/hvdwolf/jExifToolGUI/releases
website: https://hvdwolf.github.io/jExifToolGUI/
full changelog: https://github.com/hvdwolf/jExifToolGUI/blob/master/Changelog.md
Changelog 1.4.0- Add "add favorites/load favorites" to "Your Commands" tab and to "Exiftool Database" tab. You can save your favorite exiftool commands and/or queries to the database.
- Add option to configure and use RAW image viewer: For all images (clunky on McOS as MacOS wants it own viewer), or only for raw images. Other formats (txt/audio/video/etc) will be opened according mime-type with their default app (if installed).
- Linux: Set default font to SansSerif instead of Linux/java default Dialog bold. (Will be configurable for MacOS/Windows/Linux in 1.5)
- Fix: Issue #36 (https://github.com/hvdwolf/jExifToolGUI/issues/36): Fix linewrap in exif:description and xmp:description.
- Fix: Issue #37 (https://github.com/hvdwolf/jExifToolGUI/issues/37): Tif(f) files not previewed. They are now differently handled based on java version.
- tiff images with preview/thumbnail images inside are displayed (this was already working).
- tiff images without preview/thumbnail inside can only be displayed on java V11 or higher. Use a "full jre" version (comes with V11) or install V11 or newer.
- Add "update" function. This new 1.4 does an extension on the database. You don't want to lose your user data (currently only lens configs if applicable).
- Internal: add program icon to all windows (top-left)(not on MacOS as MacOS does not allow it).
- Internal: DB diagram was displayed in external browser window. Is now displayed in internal scroll panel. It is "uncoupled" from the main window so you can keep it open.
Thank you very much @hvdwolf for taking up this wonderful tool!
also many thanks to Phil, for so many years of hard work ;-)
Count with me for the translation to ES !
best
martin
Released version 1.5.0releases: https://github.com/hvdwolf/jExifToolGUI/releases
website: https://hvdwolf.github.io/jExifToolGUI/
full changelog: https://github.com/hvdwolf/jExifToolGUI/blob/master/Changelog.md
Changelog 1.5.0- Make app translatable: Change (almost) all "fixed" texts to "property based" translatable texts.
- Translated into German => Big thanks to Karsten Günther.
- Translated into Spanish => Big thanks to Martin Gersbach.
- Translated into Dutch.
- Preferences Language tab: Select your language of preference. By default in English if jExifToolGUI is not translated for your language yet. But you can select Spanish, German or Dutch if your system is in Chinese ;)
- Preferences -> Look & Feel tab: File dialog (open/select files/folder) Option to select JFileChooser (shows same dialog on all systems) and Awt Filedialog (looks more "native Operating system" like but less flexible)
- Added the TwelveMonkeys imageIO library. Adds (additional) display support for bmp/jpeg/jpeg-2000/PNM (PBM/PGM/PPM/PAM)/PSD/TIFF/HDR/IFF/PCX/PICT/SGI/TGA/SVG/WMF
- Complete rewrite of previews (with correct aspect ratio and rotation) and image view. Change default viewer to internal java viewer ("Display Image" or double-click preview). It will show the image resized to full-screen (unless smaller). RAW images are displayed in "external" RAW Image viewer (if configured in Preferences).
- MacOS: Use sips on "High Sierra" and newer to convert heic to a jpg preview (and image view). This is very alpha and mostly doesn't work.
- Preferences window now "tabbed". Currently pretty empty but supposed to grow.
- Fix: issue #53 (https://github.com/hvdwolf/jExifToolGUI/issues/53) xmpexport missing? Over the years this has changed to "Sidecar exports". Now added under (menu) Metadata: "Export Exif sidecar file(s)" and "Export XMP sidecar file(s)".(Known shortcoming: currently only works on paths and images without spaces. Comparable exiftool functions do work on other places: why not here? something in exiftool or me doing something wrong?)
- Fix: Issue #54 (https://github.com/hvdwolf/jExifToolGUI/issues/54) Repair csv output (export metadata).
- Request implemented Issue #51 (https://github.com/hvdwolf/jExifToolGUI/issues/51) Reverse buttons in Rename Photos window
- Fix (MacOS): Issue #40 (https://github.com/hvdwolf/jExifToolGUI/issues/40) Load directory don't work on OSX.
- Request implemented Issue #43 (https://github.com/hvdwolf/jExifToolGUI/issues/43) Edit Data->Gpano layout
- Fix: RAW viewer could not be called correctly when path or file name contains spaces.
- Fix: UTF-8 was not used in Preferences dropdown for "Language to use to display metadata tag names/descriptions".
- Fix: UTF-8 was not used for output in "View data" tab in the table and neither in "Your commands".
wow! good news!
The community is very grateful that you decided to port ExifToolGUI to Java
best,
Martin
Quote from: hvdwolf on August 15, 2020, 08:32:06 AM
Released version 1.5.0
releases: https://github.com/hvdwolf/jExifToolGUI/releases
website: https://hvdwolf.github.io/jExifToolGUI/
full changelog: https://github.com/hvdwolf/jExifToolGUI/blob/master/Changelog.md
Changelog 1.5.0
- Make app translatable: Change (almost) all "fixed" texts to "property based" translatable texts.
- Translated into German => Big thanks to Karsten Günther.
- Translated into Spanish => Big thanks to Martin Gersbach.
- Translated into Dutch.
- Preferences Language tab: Select your language of preference. By default in English if jExifToolGUI is not translated for your language yet. But you can select Spanish, German or Dutch if your system is in Chinese ;)
- Preferences -> Look & Feel tab: File dialog (open/select files/folder) Option to select JFileChooser (shows same dialog on all systems) and Awt Filedialog (looks more "native Operating system" like but less flexible)
- Added the TwelveMonkeys imageIO library. Adds (additional) display support for bmp/jpeg/jpeg-2000/PNM (PBM/PGM/PPM/PAM)/PSD/TIFF/HDR/IFF/PCX/PICT/SGI/TGA/SVG/WMF
- Complete rewrite of previews (with correct aspect ratio and rotation) and image view. Change default viewer to internal java viewer ("Display Image" or double-click preview). It will show the image resized to full-screen (unless smaller). RAW images are displayed in "external" RAW Image viewer (if configured in Preferences).
- MacOS: Use sips on "High Sierra" and newer to convert heic to a jpg preview (and image view). This is very alpha and mostly doesn't work.
- Preferences window now "tabbed". Currently pretty empty but supposed to grow.
- Fix: issue #53 (https://github.com/hvdwolf/jExifToolGUI/issues/53) xmpexport missing? Over the years this has changed to "Sidecar exports". Now added under (menu) Metadata: "Export Exif sidecar file(s)" and "Export XMP sidecar file(s)".(Known shortcoming: currently only works on paths and images without spaces. Comparable exiftool functions do work on other places: why not here? something in exiftool or me doing something wrong?)
- Fix: Issue #54 (https://github.com/hvdwolf/jExifToolGUI/issues/54) Repair csv output (export metadata).
- Request implemented Issue #51 (https://github.com/hvdwolf/jExifToolGUI/issues/51) Reverse buttons in Rename Photos window
- Fix (MacOS): Issue #40 (https://github.com/hvdwolf/jExifToolGUI/issues/40) Load directory don't work on OSX.
- Request implemented Issue #43 (https://github.com/hvdwolf/jExifToolGUI/issues/43) Edit Data->Gpano layout
- Fix: RAW viewer could not be called correctly when path or file name contains spaces.
- Fix: UTF-8 was not used in Preferences dropdown for "Language to use to display metadata tag names/descriptions".
- Fix: UTF-8 was not used for output in "View data" tab in the table and neither in "Your commands".
Hello!
Congratulations for this work!
I've installed the version 1.5 on macOS Catalina, but this version don't Load Directory nor Load Images... I click on these options, but nothing happens.
My macbook is too old to run Catalina, but I will check with another user.
And maybe other users will react as well.
Released version 1.5.2releases: https://github.com/hvdwolf/jExifToolGUI/releases
website: https://hvdwolf.github.io/jExifToolGUI/
full changelog: https://github.com/hvdwolf/jExifToolGUI/blob/master/Changelog.md
Changelog 1.5.2
- Fix: (old) error in exiftool detection when exiftool is removed or moved to other folder.
- "Fix" (Linux KDE/QT): KDE/QT based window managers deliver "strange" strings for imagewidth and imageheight out of exiftool. The values are not integers and can't be converted to integers either. Now using java based approach, and better "error trapping" in case it still errors out.
- Logging to file enabled. In the folder where jExifToolGUI is started, a folder "logs" is created where log files are stored per jExifToolGUI session. This does not work for MacOS bundles. Therefore the logs are written inside a logs folder into the user HOME folder. Also the linux deb version writes to the user HOME folder. In case of issues extensive logging can be started to pinpoint the issue.
Another user recommended I try jExifToolGUI and I visited the link but cannot seem to get it installed or working on my MBP running Catalina. The folder jExifToolGUI-master downloads and unzips, but I do not see any executable file to launch the GUI, only a Terminal window. I feel I must be doing something wrong. Please advise.
Andy
I don't have any experience with macs, but if you downloaded the jExifToolGUI-x86_64-macos-1.5.2-with_jre.dmg.zip file, then one with the runtimes built in, you should be able to run it with either the jexiftoolgui file or jExifToolGUI.jar file.
I downloaded the ZIP from https://github.com/hvdwolf/jExifToolGUI/tree/1.5.2
which unzipped itself into a folder named jExifToolGUI-1.5.2
Within that folder, the only executable file is gradlew.
Digging around (5 subfolder levels) revealed an executable file named jexiftoolgui, but that only opened a Terminal window with this output:
Last login: Wed Sep 9 12:31:51 on ttys001
/Users/andy/Downloads/jExifToolGUI-1.5.2/packaging/macos/jExifToolGUI.app.base/Contents/MacOS/jexiftoolgui ; exit;
The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
ANDYS-MBP:~ andy$ /Users/andy/Downloads/jExifToolGUI-1.5.2/packaging/macos/jExifToolGUI.app.base/Contents/MacOS/jexiftoolgui ; exit;
logout
/Users/andy/Downloads/jExifToolGUI-1.5.2/packaging/macos/jExifToolGUI.app.base/Contents/MacOS/jexiftoolgui: line 6: /Users/andy/Downloads/jExifToolGUI-1.5.2/packaging/macos/jExifToolGUI.app.base/Contents/MacOS/jre/Contents/Home/bin/java: No such file or directory
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
[Process completed]
Try grabbing the jExifToolGUI-x86_64-macos-1.5.2-with_jre.dmg.zip file from the releases page (https://github.com/hvdwolf/jExifToolGUI/releases/tag/1.5.2).
That gets me a little farther, but still isn't launching the program. The icon splashes on the screen for a moment and Java launches, but then both disappear.
Stargeek pointed you to the right place: the releases page.
Your first download was the source code.
This is a java application which means it needs java to be able to run.
Did you really download the jExifToolGUI-x86_64-macos-1.5.2-with_jre.dmg.zip?
or did you download the jExifToolGUI-x86_64-macos-1.5.2.dmg?
The first one ("with_jre") comes with java embedded inside the bundle.
The second one (jExifToolGUI-x86_64-macos-1.5.2.dmg) is only the bundle. It means that you need to have java version 8 or newer installed on your system.
If you open a terminal and type java -version, you immedediately see if you have java installed and which version.
If it is not available, or too old: Simply download the jExifToolGUI-x86_64-macos-1.5.2-with_jre.dmg.zip.
Did you also take a look at the "short "installation" instructions (https://hvdwolf.github.io/jExifToolGUI/installing.html)" which are mentioned with every release?
(Anyway: For the "simple" bundle I should build in some error trapping that detects there is no java installed, or a too old version on the system)
Yes, I mistakenly downloaded the source code the first time, then after StarGeek pointed me back to the releases page, I scrolled down and found both links to the MacOS zip files. I do have Java running (and checked to confirm) and I did follow the "short installation instructions." I do then get the dmg and the icon for jexiftoolgui, but when I click on it, Java runs momentarily, then disappears, and the application does not open.
Quote from: acnomad on September 09, 2020, 03:56:49 PM
Yes, I mistakenly downloaded the source code the first time, then after StarGeek pointed me back to the releases page, I scrolled down and found both links to the MacOS zip files. I do have Java running (and checked to confirm) and I did follow the "short installation instructions." I do then get the dmg and the icon for jexiftoolgui, but when I click on it, Java runs momentarily, then disappears, and the application does not open.
Please mention which version you downloaded ("both links"? Does that mean you tried both?)
and which java version you are running. You do not mention that.
That makes it really hard to troubleshoot.
I downloaded:
jExifToolGUI-x86_64-macos-1.5.2-with_jre.dmg.zip
jExifToolGUI-x86_64-macos-1.5.2.dmg
I already had Java 14.0.2 installed
I am running macOS Catalina 10.15.6 on a MBP 15-inch mid-2015
Did you allow jExifToolGUI to run?
Safety/Security on MacOS is normally that only programs downloaded from the app store are allowed to run.
(Maybe something I should add to the installation (micro) instructions)
Yes. As you pointed out, Mac doesn't like third party software, but I did right click to open and manually permitted the app to run. It did begin to launch, with the app graphic splashing momentarily on the screen, and I also noticed that Java activated briefly, but then nothing happened beyond that.
There should be logs file in your <home>/logs folder. Normally jExifToolGUI writes "light" logs, but that can be extended.
Anyway, the log files are named jexiftoolgui_YYYYmmDD-HHMM.log like for example jexiftoolgui_20200910-1608.log.
Is there anything usefull in it? Can you attach one or more logs, if there is/are any? (maybe the program exits before the first log line is written)
Here are the four most recent logs.
I can see where it "seems to" stop, but I have no idea why. I have a test user with seemingly the same configuration and it works fine for him.
I will compile another version with extensive logging.
I'm currently on holiday returning home this weekend. Most probably Sunday I will deliver a new version (which will be a 1.6.0-beta as well). It has no use going back to 1.5.2 when 1.6.0 is almost ready (and which might even function directly).
@acnomad
Please find a link for a 1.6.0-beta3 version: https://mega.nz/file/0UlhVboL#nEI4uxUTPs57CjKsw3iQ6WCP0pYoJZ4YgvMu6E3mX1s
It has functionality for setting the log level which is normally at a light level (among more new functionality which will be mentioned on release).
This version is hard-coded to the highest loglevel (if it still does not complete starting on your system, you will never be able to change it to higher log level)
Please collect the logs again and please add to a post.
Note: Normally bugs can be reported at: https://github.com/hvdwolf/jExifToolGUI/issues
Note to other users: Do not use this beta. It is hard-coded to the highest log level, which will create large log files and will slow down the application due to the extensive logging.
Same issue.
I've attached the log file.
Thanks.
This is not a jExifToolGUI issue but an ExifTool installation issue.
16:57:25.551 [AWT-EventQueue-0] DEBUG o.h.j.controllers.CommandRunner - commandrunner [/Users/andy/exiftool, -ver]
16:57:25.551 [AWT-EventQueue-0] TRACE o.h.j.controllers.CommandRunner - Did ProcessBuilder builder = new ProcessBuilder(cmdparams);
16:57:25.560 [AWT-EventQueue-0] TRACE o.h.j.controllers.CommandRunner - tasklist: Can't locate Image/ExifTool.pm in @INC (you may need to install the Image::ExifTool module) (@INC contains: /Users/andy/lib /Library/Perl/5.18/darwin-thread-multi-2level /Library/Perl/5.18 /Network/Library/Perl/5.18/darwin-thread-multi-2level /Network/Library/Perl/5.18 /Library/Perl/Updates/5.18.4 /System/Library/Perl/5.18/darwin-thread-multi-2level /System/Library/Perl/5.18 /System/Library/Perl/Extras/5.18/darwin-thread-multi-2level /System/Library/Perl/Extras/5.18 .) at /Users/andy/exiftool line 37.
16:57:25.560 [AWT-EventQueue-0] TRACE o.h.j.controllers.CommandRunner - tasklist: BEGIN failed--compilation aborted at /Users/andy/exiftool line 37.
16:57:25.561 [AWT-EventQueue-0] TRACE org.hvdw.jexiftoolgui.mainScreen - raw exiftool version: Can't locate Image/ExifTool.pm in @INC (you may need to install the Image::ExifTool module) (@INC contains: /Users/andy/lib /Library/Perl/5.18/darwin-thread-multi-2level /Library/Perl/5.18 /Network/Library/Perl/5.18/darwin-thread-multi-2level /Network/Library/Perl/5.18 /Library/Perl/Updates/5.18.4 /System/Library/Perl/5.18/darwin-thread-multi-2level /System/Library/Perl/5.18 /System/Library/Perl/Extras/5.18/darwin-thread-multi-2level /System/Library/Perl/Extras/5.18 .) at /Users/andy/exiftool line 37.
BEGIN failed--compilation aborted at /Users/andy/exiftool line 37.
From the logs it seems you installed Exiftool inside your users home folder, but that version is not correct/complete. How did you install ExifTool? It seems you did not do this from the MacOS dmg.
Please remove the incorrect version in your homefolder.
Please install the MacOS version from the exiftool.org (https://exiftool.org/) home page (currently ExifTool-12.06.dmg).
jExifToolGUI will detect the deleted configured (and incorrect) exiftool and will search the PATH for a valid one. It will then find the installed version inside /usr/local/bin. If it can't find it, it will ask you where you installed exiftool.
Edit: I will try to catch these kind of errors as well. I do catch errors but had not looked at exiftool installation errors (yet).
Released version 1.6.0releases: https://github.com/hvdwolf/jExifToolGUI/releases (https://github.com/hvdwolf/jExifToolGUI/releases)
website: https://hvdwolf.github.io/jExifToolGUI/ (https://hvdwolf.github.io/jExifToolGUI/)
full changelog: https://github.com/hvdwolf/jExifToolGUI/blob/master/Changelog.md (https://github.com/hvdwolf/jExifToolGUI/blob/master/Changelog.md)
Changelog
- New menu "Tools"
- User defined Metadata combis
- delete Lenses
- delete Favorites
- Add option to create your own combination of tags in "Tools -> User defined Metadata combis" to write to your images (see help page here (https://hvdwolf.github.io/jExifToolGUI/manual/jexiftoolgui_usercombis.html) or via the help button. This has been extended with the option to also use tags that are not known to Exiftool via a custom config file: Create your custom config file, Create your own custom tag combination and add the config file when saving your combination. This allows for example, to add your own set of tags to XMP, Exif, IPTC, Composite, etc. Exiftool and jExifToolGUI will displays the tags, but you need to have the custom config file to write them as well. As examples: see the Exiftool example (https://exiftool.org/config.html) or see the isadg-struct.cfg (https://raw.githubusercontent.com/hvdwolf/jExifToolGUI/master/src/main/resources/isadg-struct.cfg) online to add ISAD(g) data to the XMP set as new category xmp-isadg. (ISAD(G) is General International Standard Archival Description)
- "pre-installed" custom metadata sets (for use, as example and for modification (save as)):
- isadg: like above mentioned
- gps_location: All gps and location tags in the 3 categories EXIF,XMP and IPTC.
- Google Photos: All tags that Google Photos uses or recognizes.
- Common Tags in the View Tab now also include your own defined "User defined Metadata combis" by name.
- Note: If you added your custom tags under one of the existing categories like XMP, Exif, IPTC, etcetera, they will also be displayed there.
- Export Metadata (Menu Metadata -> Export Metadata) now supports the export by category (exif, xmp, etc.) but also from our user defined metadata combi set.
- Add drag & drop of images. Drop them anywhere on the main program window and they will be loaded into the application.
- Preferences -> System: "Show coordinates in decimal degrees (Exiftool defaults to Deg Min Sec)"
- System: "Use G1 group instead of G for viewing": G will show main category like EXIF or XMP. G1 will show sub groups like for EXIF it will show ExifIFD, IFD0, etc. and for XMP like XMP-x, XMP-exif, XMP-dc, etcetera.
- Preferences -> System: Make log level user definable for troubleshooting.
- In the tab "Your commands": If you specify "-h" or "-htmlFormat", the output will switch to html instead of "plain text"
- MacOS: Apple likes it big. The application starts with a bigger window on MacOS to show all GUI components.
- Feature request: issue #66 (https://github.com/hvdwolf/jExifToolGUI/issues/66): images count. An image counter is now displayed in the bottom left showing how much images have been loaded.
- (Internal) Better separation between Gui elements and program logic.
- Fix: issue #60 (https://github.com/hvdwolf/jExifToolGUI/issues/60) Fix 2 combined errors. There was a check whether exiftool "delivers" data, but not if the first line contains a warning or error in case of faulty metadata data. This resulted in "hanging" on loading a file, or hanging when requesting specific info from a file.
- Fix: fix export metadata (again).
Version 1.6.1 releasedreleases: https://github.com/hvdwolf/jExifToolGUI/releases
website: https://hvdwolf.github.io/jExifToolGUI/
(growing) online manual: https://hvdwolf.github.io/jExifToolGUI/manual/index.html
full changelog: https://github.com/hvdwolf/jExifToolGUI/blob/master/Changelog.md
Changelog- (Menu) Help -> Online manual added. I'm slowly working on an online manual (https://hvdwolf.github.io/jExifToolGUI/manual/index.html) (in English).
- Added sidecar exports of MIE ("The only metadata format that doesn't suck" ;) (https://exiftool.org/commentary.html)) and EXV (next to already available XMP and EXIF).
(All Sidecar files can be read as "images". This makes it possible to read (for example) a .mie file together with a number of images. You use the .mie metadata file as "Copy from selected image" and use it to populate one or more images. For this reason there is no import function for these Sidecar files as you can use them as just described.) - Fix Preferences screen: Somehow 2 options were "falling off the screen": "Credits" under "Always add.." and "Check for new jExifToolGUI version on program start" (under System).
This will be the last "large, spamming" post. Possible next posts will be oneliners linking to releases page and changelog (unless users want it otherwise)
Version 1.6.2 released: Release page (https://github.com/hvdwolf/jExifToolGUI/releases); Changelog (https://github.com/hvdwolf/jExifToolGUI/blob/master/Changelog.md)
I've made this topic sticky so it will always appear at the top. But I'm not sure that the "exiftool" Application board is the best location. What would people think if I moved it to the ExifToolGUI board and somehow broadened that board description to encompass other GUI's?
- Phil
Quote from: Phil Harvey on October 01, 2020, 04:19:16 PM
I've made this topic sticky so it will always appear at the top. But I'm not sure that the "exiftool" Application board is the best location. What would people think if I moved it to the ExifToolGUI board and somehow broadened that board description to encompass other GUI's?
Heh, I was actually thinking of bringing up this idea this morning.
But moving it to the ExifToolGUI might cause confusion, since there's years of posts there about the old GUI and no real way to indicate that they're not related to this GUI.
Thanks.
Just to mix in.
I think that a new subforum like "Graphical Interfaces for Exiftool" might cover it better (and I've noticed that to some/many people the abbreviation GUI is unknown). Having a broader "general" GUI sub-forum will indeed enable it for other apps as well, be it multi-platform, Linux, Windows, MacOS, Android, IOS, etc. In that case the users also get the choice as one app might be more suited for their needs than others.
And ExifTool GUI can either be part of it, or left on its own. It has indeed many posts and was for a very long time the most popular one.
Could the ExiftoolGUI subforum be made into a sub-subforum?
Quote from: StarGeek on October 01, 2020, 05:28:17 PM
Could the ExiftoolGUI subforum be made into a sub-subforum?
Yes it could be. But I was thinking of combining the two at least initially, and then splitting off jExifToolGUI posts into a separate board if there were enough of them. (I don't want to create a new board for a very small number of posts.) However, I'm a bit worried that people could get confused between the different GUI's.
- Phil
Thursday, October 01, 2020, 9:05 p.m.
I was pointed in this direction re your GUI EXIF tool and I downloaded the Mac Versions but upon clicking the dmg file nothing seems to happen. I am using Mac OS 10.13 (High Sierra). You frontend to Phil Harvey's tool seems to be just the thing I need to find the EXIF data in my Fuji image files. I am not very computer literate and thus terminal commands are way above my head. SO, when I looked at you frontend text and schematics this is totally what I would like to use on my image files.
Can you suggest anything I should try to install your app?
I downloaded both the Mac versions of your app and they are just sitting in the download folder.
Don J J Carrol
Quote from: djjc on October 01, 2020, 08:10:30 PM
I downloaded the Mac Versions but upon clicking the dmg file nothing seems to happen.
It is not an auto-installing app. If you double-click the zip it will be unpacked in the same folder giving you a (big) dmg.
If you double-click a dmg, which is actually a virtual disk, it will appear in the left navigation panel in your Finder. If you then click that "disk" in the left panel of the finder, you will find the app bundle inside. I mentioned that in Versions and Installation (https://hvdwolf.github.io/jExifToolGUI/manual/index.html#Installation), but I guess I need to add another line/sentence describing how to deal with dmg files ;)
Note that, just as with a USB-stick, you need to click the "up-arrow" next to it to safely "disconnect" it.
Dear hvdwolf,
I would be extremely thankful if you could clarify me about how to use the GUI version gently suggested to me by StarGeek. It is not clear to me how to open raw files (in particular Fujifilm's RAF) on the left panel. I tried both by the Load Directory/Images without success. Does the app work for that kind of file? On preferences I noticed we should type the image directory and also RAW viewer location -what I fulfilled-, but nothing happened when I clicked to open the files... Could you tell me if I am doing correctly?
My intention is to change Fujifilm camera model name from x-t2 to x-t4 on the EXIF tags of my RAF files... Is it possible to do that using the GUI version?
Thanks very much in advance!
Quote from: Cassio Duarte on October 03, 2020, 01:13:58 PMIt is not clear to me how to open raw files (in particular Fujifilm%u2019s RAF) on the left panel. I tried both by the Load Directory/Images without success. Does the app work for that kind of file? On preferences I noticed we should type the image directory and also RAW viewer location -what I fulfilled-, but nothing happened when I clicked to open the files%u2026 Could you tell me if I am doing correctly?
My intention is to change Fujifilm camera model name from x-t2 to x-t4 on the EXIF tags of my RAF files%u2026 Is it possible to do that using the GUI version?
I do not know if you are doing it correctly :)
Please download and see attached short movie.
It is made on Linux and not on MacOS, but the "workflow" is identical. (I did not have a screen recorder on my Mac)
See attached image of the settings to configure a Raw Viewer (and this is on MacOS). Once done you either double-click an image, or you select it and click the "display Image" button.
Dear hdvwolf,
Thanks for your prompt answer! I attached some print screens in order you can see. My OS is Windows but I suppose there would not be too much difference, am I correct?
First, on File>Preferences I filled the first three spaces and saved the settings. I suppose Capture One.exe can be included on the RAW viewer location, isn't it?
Then, after clicking on Load Images nothing happened. On the low right corner it appears "Loading images..." but strangely no folder appears.
Am I doing something wrong? Is it necessary to configure something before?
Thanks very much once again for your kind attention!
Sorry, I mixed you with the previous user who was on MacOS.
You are now the 3rd person reporting this issue: 1 on MacOS, 1 on Manjaro Linux and now you. And I can't reproduce it, not on any of my systems.
Can you make a copy of the screen under Help -> System / Program Info?
Can you go into Preferences -> System and set the log level to "trace", and restart jExifToolGUI?
Then try again, both the buttons and the menu options under File. After closing please attach the (zipped) log file(s) to a post. These logs are in the folder logs "next to" the program and ordered by jexiftoolgui_YYYYMMDD-HHMM.log.
And afterwards you can/should reduce the log level again to Info or lower.
Edit: jTG supports drag& drop, so please try to drag & drop the RAF files from the file manager onto the program. At least that should work.
Edit 2: I installed Capture One (30 days trial; what an annoying privacy violating program). When double-clicking RAF files or other RAW images from jTG, they are opened in Capture One. Strange thing is that older RAF files, like from the E-550 and FinePix X-100, are not recognized and need to be manually imported into Capture One. Other (open source) Raw viewers/editors like Raw Therapee and Nomacs have no problem with these older RAFs.
Version 1.6.3 released: Release page (https://github.com/hvdwolf/jExifToolGUI/releases); Changelog (https://github.com/hvdwolf/jExifToolGUI/blob/master/Changelog.md)
The next release (1.7.0) will take (much) longer as I will work on "bigger" things.
I will be out if home until Thursday. As soon as I can I will follow your instructions and I will let you know.
Thanks very much!
Dear hvdwolf,
I followed your instructions step by step (please see the attached files you requested) – I just did not understand how "to reduce the log level again to Info or lower" – but in the end I still could not open the files through the Load Images button...
However, this time I was successful opening a raw file through dragging and dropping it directly to the left panel – although I could not do the same thing with the folder with the image (see my print screen "Dragging and Dropping a folder"). I did the same operations you showed on your video and after I could open on Capture One my RAF file as X-T4 one. Thanks very much! 8)
If you discover how to make the GUI version fully operable through the opening of files it would be even more perfect. I am already fully grateful for all your help!
Hi, going back to your first post.
Quote from: Cassio Duarte on October 03, 2020, 01:13:58 PM
It is not clear to me how to open raw files (in particular Fujifilm%u2019s RAF) on the left panel. I tried both by the Load Directory/Images without success. Does the app work for that kind of file? On preferences I noticed we should type the image directory and also RAW viewer location -what I fulfilled-, but nothing happened when I clicked to open the files%u2026 Could you tell me if I am doing correctly?
(I should have asked this before) You say you can't load images via
Load images or
Load Folder. What does (or does not) happen?
- Does the file chooser open or not?
- Can you navigate (go up and down) through folder structures?
- When you want to open a folder: do you "double-click" it or single-click and then using the button Open. Double-clicking a folder, on any OS, will simply open that folder for further drill-down and navigation. Single-clicking the folder and use the "Open" button is what should be done (in any program on any OS).
And you mentioned that you configured the RAW viewer and then:
but nothing happened when I clicked to open the filesPlease explain: If you can't load files, how can you then double-click them from the program to try to open them in the raw viewer?
Quote from: Cassio Duarte on October 03, 2020, 01:13:58 PMI just did not understand how %u201Cto reduce the log level again to Info or lower%u201D
Go to
Preferences -> System and set the loglevel to Warn (or Info or Error or Off).
Dragging and dropping a folder does not work, at least not now (I had not even thought of that, to be honest). Only files can be dragged & dropped. I will have to dive into the possibility whether that is a possibility at all (and then next: what about subfolders: with or without recursion? You might want to load 10.000 folders/images at a time).
Quote from: Cassio Duarte on October 03, 2020, 01:13:58 PMIf you discover how to make the GUI version fully operable through the opening of files it would be even more perfect.
Ho, ho :). It might not work for you, which we should try to solve, but it does work for many other users. The program IS fully operable!!
(and I tried it now on a win7, a win8.1, a Win8.1 tablet (took a little more effort) and several Win10 laptops/PCs.)
Hi hvdwolf!
I'm not used to the language of these forums and I don't know how to highlight your questions as you did with mine. I will do it the way I know:
"(I should have asked this before) You say you can't load images via Load images or Load Folder. What does (or does not) happen?"
No folder was opened either by the buttons Load Directory / Load Images or through File> Load Images / Load Directory.
And a third observation: nothing appears written on the third button
"And you mentioned that you configured the RAW viewer and then:
but nothing happened when I clicked to open the filesPlease explain: If you can't load files, how can you then double-click them from the program to try to open them in the raw viewer?"
As nothing opened, I thought it might be due to not having indicated the program to open RAF files before ... But nothing has changed and I was unable to access any folder with the files.
"Dragging and dropping a folder does not work, at least not now (I had not even thought of that, to be honest). Only files can be dragged & dropped. I will have to dive into the possibility whether that is a possibility at all (and then next: what about subfolders: with or without recursion? You might want to load 10.000 folders/images at a time)."
Well, I probably would not need so much... Even one by one is already working and I am very grateful for all your efforts!
"Ho, ho . It might not work for you, which we should try to solve, but it does work for many other users. The program IS fully operable!!
(and I tried it now on a win7, a win8.1, a Win8.1 tablet (took a little more effort) and several Win10 laptops/PCs.)"
I totally believe in you and I'm used to being a victim of Murphy's Law! And I, who barely know how it all works, find myself in the position to explain details of what is happening to those who understand ...
Quote from: Cassio Duarte on October 09, 2020, 09:47:07 PM
I'm not used to the language of these forums and I don't know how to highlight your questions as you did with mine. I will do it the way I know:
In the top right of every post in this forum you have a "Quote" button/icon. Using that one gives you the options to quote/copy other posts. Copying begin and end quote codes around portions of the text gives you the option to split it into multiple sections and you can even make multi-level quotes (quote in a quote): see bottom one.
Quote from: Cassio Duarte on October 09, 2020, 09:47:07 PMNo folder was opened either by the buttons Load Directory / Load Images or through File> Load Images / Load Directory.
And a third observation: nothing appears written on the third button
A folder will not directly open. It is not that a complete filemanager will start. A file dialog popup should open enabling you so select a folder or files. Just like in Word or Excel when you want to open a file.
So, do you mean that no popup window at all is opening (allowing you to select files/folders)?
Or do you mean that a popup is opening, but it's not functional? (the logs don't show that as there is no error)
The 3rd button ("Display Image") only gets active when images are loaded. Otherwise there is nothing to display. (Anyway: in 1.7.0 the GUI might change considerably)
Quote from: Cassio Duarte on October 09, 2020, 09:47:07 PMQuote from: hvdwolf on October 09, 2020, 03:00:34 AMAnd you mentioned that you configured the RAW viewer and then: but nothing happened when I clicked to open the files
Please explain: If you can't load files, how can you then double-click them from the program to try to open them in the raw viewer?
As nothing opened, I thought it might be due to not having indicated the program to open RAF files before ... But nothing has changed and I was unable to access any folder with the files.
OK. So you mean that you configured the RAW viewer to see if you could open/select files/folder.
There is no link between that. The loading of files/folders should always work. And when you want to see full screen images of RAW thumbnails (which are actually embedded jpeg previews/thumbnails taken from the RAW image), then you need a RAW viewer.
MacOS: Why does the jExifToolGUI app bundle close immediately after the Splash screen when I have double-clicked it from the Finder?
As incidents/issues are now registered due to this Apple behavior, I will mention it now here and I will also add it also to the Releases page. It is already in the manual under Installation (https://hvdwolf.github.io/jExifToolGUI/manual/#Installation) in the MacOS section. (Unfortunately I can't modify my first post anymore. Phil or Stargeek perhaps?)
I am an "unidentified" developer" and by default MacOS (the gatekeeper software) does not open apps from "unidentified" developers as the app bundle could contain malware (and next to that: Apple doesn't like it if there is a developer that is not registered with them with "all" his/her personal information, much more than for the Apple ID. And I don't like that Apple "big brother is watching you" behavior).
These 2 links show you how you can add my app bundle (and other app bundles from other "unidentified" developers) to the list of exceptions in Gatekeeper:
Apple support: https://support.apple.com/guide/mac-help/open-a-mac-app-from-an-unidentified-developer-mh40616/mac
How-To Geek: https://www.howtogeek.com/205393/gatekeeper-101-why-your-mac-only-allows-apple-approved-software-by-default/
(note: as ExifTool is a binary and not an app bundle, this is not relevant for Exiftool (so an app bundle can be malicious, but an executable is not and can always simply be executed? Is that security? ::) )
Quote from: hvdwolf on October 11, 2020, 07:18:48 AM
(Unfortunately I can't modify my first post anymore. Phil or Stargeek perhaps?)
Tell me exactly what to want to change and I'll do it for you.
- Phil
Between the dashes the sentence(s) I would like to add as last sentence(s) of post 1:
--
I am not a registered Apple developer. Apple/MacOS users facing immediate closure of the app bundle after double-click to open it, please see below Apple support article.
https://support.apple.com/guide/mac-help/open-a-mac-app-from-an-unidentified-developer-mh40616/mac
--
Thank you
Bugfix release 1.6.3.1
One line from the changelog:
* Fix: the default translations file contained a number of incorrect characters which made it impossible to use the "Load Images" and "Load Folder" options on all systems NOT running English, German, Spanish or Dutch. This seems like some sort of text file corruption but I do not know how it occurred and which is not visible in a "normal" text editor. It is fixed now.
@Cassio Duarte: I assume this is also your problem.
To overcome this in 1.5.2 to 1.6.3: Open jTG, goto Preferences->Language and set to "en_US". Restart.
Quote from: hvdwolf on October 03, 2020, 01:46:50 PM
(I did not have a screen recorder on my Mac)
Quicktime player --> new screen recording
@hvdwolf
You hit the target! Finally I could open the file with RAF files through the button.
Congratulations and thank you very much!
Quote from: Alan Clifford on October 23, 2020, 12:29:30 PM
Quote from: hvdwolf on October 03, 2020, 01:46:50 PM
(I did not have a screen recorder on my Mac)
Quicktime player --> new screen recording
Yes, thanks. I found it by now. After my post I googled for a screen capture app and then it turned out to be so simple :)
Version 1.7.0 released Release page (https://github.com/hvdwolf/jExifToolGUI/releases); Changelog (https://github.com/hvdwolf/jExifToolGUI/blob/master/Changelog.md)
Version 1.8.0 released Releases page (https://github.com/hvdwolf/jExifToolGUI/releases) Changelog (https://github.com/hvdwolf/jExifToolGUI/blob/master/Changelog.md)
I only found out about jExifTool Today and tried it as soon as I could. I have read many posts in this forum, and read everything I can find online. Yet I am confused and perhapos disappointed! I assumed it would be an updated version of ExifTollGUI, but it's so different. I am so very dependant on seeing files listed vertically on the left and metadata columns listed horizontally at the top so basically everything is sideways for me. I have not yet figured out if it's even possible to view things the way I need to - similar to File Explorer or Directory Opus.
Perhaps this application meets other people's needs very well. I wonder if I am missing somethinmg basic!??
Are they just very different deliberately for some reason I don't know?
Thank you.
I am sorry to hear this, but exiftoolgui and jExifToolGUI have no relation whatsoever, apart from the fact thay they both try to offer a graphic user interface for exiftool.
exiftoolgui was written as closed source for windows.
jExifToolGUI is an open source cross-platform java application and the successor of my previous open-source cross-platform program pyExifToolGUI which started in 2011 or so. (Being a MacOS/Linux user I did not even know about the existence of exiftoolgui until I came here for my pyexiftoolgui)
As jexiftoolgui and exiftoolgui are both graphic user intefaces on top of Phils ExifTool, they both have a lot in common in functionality.
exiftoolgui and jexiftoolgui(and pyexiftoolgui) have a completely different design basis. Just like many other image programs like shotwell, digikam, etc. more or less look the same, but have a different UI and user experience as well and require some adaptation.
So you either need to adapt or find something else that better suits your needs.
And even if jExifToolgui was somehow an update for exiftoolgui: Don't blame the open-source developer for something you yourself didn't do. If they don't make Windows 3.11 anymore, don't blame another for creating something completely else like Linux or MacOS.
Note with regard to design principal for my jtg: Unlike exiftoolgui and fastfototagger, my intentions were always to show as much and detailed metadata as the image had to offer. You watch (and enjoy) your images in a viewer and metadata edit your images in a tool that shows as much metadata as possible. That requires a different ui setup especially in 2011/2012 where screen resolutions were varying from 1200x800 / 1366x768 to max. 1600x900 for macbook pros.
Thank you for clarifying. I am grateful fut the work you've done. My assumption was obviously wrong.
I'm not sure if this is the correct place to post more questions, but there doesn't seem to be a better place! Where should I post my questions?
If I want to see the metadata of several photos at once, the only way I've figured out how to do that is by selecting them in the left panel, then clicking 'Compare'. Is that the only way?
Thank you.
Hi,
Yes. That is how it should be done.
I want to expand this function further "at some time" to also display the differences between the images for the displayed Tags.
Quote from: Phil Harvey on October 01, 2020, 04:19:16 PM
... What would people think if I moved it to the ExifToolGUI board and somehow broadened that board description to encompass other GUI's?
Yes, this really would be a good idea. I am afraid, special questions to this GUI would get lost in this single thread.
I just installed the GUI on Win 10 and started exploring it. Nice GUI! One question about modifying the metadata: Is it correct, that all metadata fields are empty when I select a picture? Wouldn't it be more convenient, if the filled metadata fields of the picture would be displayed? This would it make much easier to see which fields need to be modified and which are already correct.
Martin
Quote from: Birdman on February 27, 2021, 07:17:48 AM
Is it correct, that all metadata fields are empty when I select a picture? Wouldn't it be more convenient, if the filled metadata fields of the picture would be displayed? This would it make much easier to see which fields need to be modified and which are already correct.
Yes, you are correct that the fields are empty. You can display the metadata in the view tab.
But I like your idea, especially if you want to modify your images one by one.
And if you want to bulk modify your images with the tags fn one of your images (that was my design), you can still copy from one image, select 10 (or 30 or 50), and save to all at once.
But there are some complications here:
If you select a number of images, should the program display the metadata from the first or the last image or not at all?
And if you have 30 images selected (or so), how do you decide/select from which image to copy?
Or should you first select one image and copy the metadata from it, and then select the images you want to "save to selected images" from your first selected image. This 3rd one is the current flow and how I do my modifications.
(my previous pyExifToolGUI had a right-click option where you could copy from one image, then select any number of images, and copy the metadata from that one right-clicked image to your selected images. Combinations of selection options in tables work different in java swing and right-click still doesn't work).
I want to release a new version in 2~3 weeks, and this will not be part of it.
But I will think about it. It should lso be very clear to the user what he/she is actually doing.
Thanks for your work. I just downloaded the application to try it but it has some difficulties when there are more than one item in path that contains exiftool.
I have -besides the path where exiftool is located- the path to Advanced Renamer too and that app also comes with an exiftool executable bundled so it seems (by the logs) that your app is trying to execute exiftool by combining both paths, this is what I have in the log:
java.io.IOException: Cannot run program "C:/Programs/Exiftool/exiftool.exeC:/Programs/Advanced Renamer/exiftool.exe": CreateProcess error=2, El sistema no puede encontrar el archivo especificado
I guess the app should just use one of the paths (the first one) when it detects more than one item.
Hi,
This is an issue with windows security. An app that has not been downloaded from the app store, can't execute a program from c:\Programs (c:\Program Files or c:\windows) . This "could" be a serious attack on your system. That's why.
I will not add my app to the store. The fact that you see 2 entries (or 10) is not that it tries both (or 10) at the same time, but that it can't execute either of them.
By now this becomes a serious issue as more and more users use the alternative installer, or copy exiftool in c:\programs or c:\windows, as Phil suggests (and that is easier if you use exiftool only as command line tool). And next to that you also have programs that also come with exiftool.
In the next release I will incorporate exiftool as well to overcome these issues. Then JTG will first check in it's own folder for exiftool and use that one, unless you specify something else in the preferences.
Quote from: hvdwolf on May 30, 2021, 03:43:42 AM
This is an issue with windows security. An app that has not been downloaded from the app store, can't execute a program from c:\Programs (c:\Program Files or c:\windows)
I can't believe this. Would you mind to provide more information?
And you don't answer PersistentPacifier's observation about concatenation of two path entries. BTW: "El sistema no puede encontrar el archivo especificado" means "The system cannot find the specified file" which is obvious for "C:/Programs/Exiftool/exiftool.exeC:/Programs/Advanced Renamer/exiftool.exe".
Quote from: hvdwolf on May 30, 2021, 03:43:42 AM
By now this becomes a serious issue as more and more users use the alternative installer
Please explain how my installer causes "problems" to enable me fixing it if necessary.
Quote from: hvdwolf on May 30, 2021, 03:43:42 AM
or copy exiftool in c:\programs or c:\windows, as Phil suggests
Phil, may I ask you to reconsider the installation instructions in this regard? c:\windows is really not the right place.
Oliver
Quote from: obetz on June 03, 2021, 04:21:37 AM
Quote from: hvdwolf on May 30, 2021, 03:43:42 AM
This is an issue with windows security. An app that has not been downloaded from the app store, can't execute a program from c:\Programs (c:\Program Files or c:\windows)
I can't believe this. Would you mind to provide more information?
This has been tested by a user who filed a ticket (https://github.com/hvdwolf/jExifToolGUI/issues/). He mentioned that it did work if he used JTG with admin rights. But that was indeed on c:\windows, not "C:\Program Files\..." (see below). I did not dive into the details. I just follow the user who tested it, but I guess that a user using exiftool directly from c:\windows is different from a "non-appstore, possibly malicious third-party program" trying to execute exiftool. On my (windows) work laptop we use group-policies doing the exact same things to some functionalities. Another user mentioned in a ticket that he himself had set restrictions (suggested by windows 10) which prevented him from executing programs (both exiftool and JTG) outside the normal locations (Program Files(x86)). He reversed that the moment he found out (and again: please don't ask me as I did not ask him).
Quote from: obetz on June 03, 2021, 04:21:37 AMAnd you don't answer PersistentPacifier's observation about concatenation of two path entries. BTW: "El sistema no puede encontrar el archivo especificado" means "The system cannot find the specified file" which is obvious for "C:/Programs/Exiftool/exiftool.exeC:/Programs/Advanced Renamer/exiftool.exe".
I did answer that:
QuoteThe fact that you see 2 entries (or 10) is not that it tries both (or 10) at the same time, but that it can't execute either of them.
However, my observation was wrong. The app searches the PATH and lists all found exiftools. I do a string split on line endings, but windows and unixes have different line endings and the split doesn't work on windows. I need to fix and improve that. So indeed: On windows this delivers a concatenated path with "all" the exiftools found. On unix/linux alikes it works correct (although this "multiple occurrences in the PATH" does not happen on unixes/linuxes unless done on purpose, and MacOS separates this by using the app bundles).
Quote from: obetz on June 03, 2021, 04:21:37 AM
Quote from: hvdwolf on May 30, 2021, 03:43:42 AM
By now this becomes a serious issue as more and more users use the alternative installer
Please explain how my installer causes "problems" to enable me fixing it if necessary.
Not your installer needs to be fixed, but my my program. On every call of exiftool (actually only a few standardized calls), I "escape" spaces in the PATH, apart from the very first "where is exiftool and check it" call where I forgot to that. Already fixed in the development tree.
(Windows is my weak spot. I don't have windows at home, only linuxes, chromebooks (using linux beta) and an old Macbook.)Quote from: obetz on June 03, 2021, 04:21:37 AMQuote from: hvdwolf on May 30, 2021, 03:43:42 AM
or copy exiftool in c:\programs or c:\windows, as Phil suggests
Phil, may I ask you to reconsider the installation instructions in this regard? c:\windows is really not the right place.
Agree :)
===
I am currently working on a Version 2.0 which contains many bug fixes (and probably new bugs) and new functionalities. (And version jump to 2.0 as I drop support for java 8 (Support from Oracle was already dropped March 2013!) and include exiftool in relevant releases (to overcome other issues, whether or not my (programming) fault(s)). Of course it will still be possible to select your own version of exiftool via the preferences.
Quote from: hvdwolf on June 03, 2021, 05:20:53 AM
(Windows is my weak spot. I don't have windows at home, only linuxes, chromebooks (using linux beta) and an old Macbook.)
then please double check before posting about Windows.
Quote from: obetz on June 03, 2021, 06:22:41 AM
then please double check before posting about Windows.
I do double-check, but then still you can make errors (I do). And sometimes you have to fully trust on observations of users. There are so many more situations and configurations than you can ever check.
And actually I do sextuple checks (double-checks on three platforms and actually even more for different linux distros). By now on more than 30.000 lines of code (and no: I do not test every option again and again on every platform).
Testing and checking on 3 platforms takes a lot of time and more time than only windows and is therefore more error-prone, especially if you are not a fulltime programmer but just an amateur having to do this in spare time.
Quote from: obetz on June 03, 2021, 04:21:37 AM
Phil, may I ask you to reconsider the installation instructions in this regard? c:\windows is really not the right place.
Sure. Tell me what you want me to say and I'll update the Windows install instructions.
- Phil
Quote from: Phil Harvey on June 03, 2021, 08:01:57 AM
Sure. Tell me what you want me to say and I'll update the Windows install instructions.
The recommended directories are:
1. For all users, with admin rights: %ProgramFiles(x86)%\ExifTool. The advantage is that the ExifTool installation is then protected against unintentional or malicious modification.
2. Without admin rights: %LocalAppData%\Programs\ExifTool. Also good if you want to fiddle with the sources.
Of course, the user might want to change the "ExifTool" part, e.g. to deal with different versions one might use \ExifTool_12.25 and so on. But those will figure it out...
Oliver
I will manually add the "%LocalAppData%\Programs\ExifTool" to the "search exiftool" on windows, and have a look at wildcards in the path.
Hi Oliver,
Quote from: obetz on June 03, 2021, 10:22:38 AM
The recommended directories are:
1. For all users, with admin rights: %ProgramFiles(x86)%\ExifTool. The advantage is that the ExifTool installation is then protected against unintentional or malicious modification.
2. Without admin rights: %LocalAppData%\Programs\ExifTool. Also good if you want to fiddle with the sources.
Thanks. Are both of these locations in the default Windows PATH? Does this work for XP, Windows 7 and Windows 10?
- Phil
Quote from: Phil Harvey on June 03, 2021, 12:31:54 PM
Thanks. Are both of these locations in the default Windows PATH?
No, they would have to be added to PATH. Which would discourage inexperienced users.
Quote from: StarGeek on June 03, 2021, 12:35:08 PM
No, they would have to be added to PATH. Which would discourage inexperienced users.
This is the reason the instructions recommend C:\WINDOWS
- Phil
Installing to c:\windows saves the user from creating the path entry, but that doesn't make it a good place.
I don't know of any program that installs there.
Adding a path entry manually is no that difficult these days: Hit the Windows key once, then enter "envi" and Windows will offer "Edit system environment variables" and "Edit environment variables for your account". The individual "path" elements are displayed in rows.
Using the installer is even simpler and safer.
Just my two cents, I don't insist on changing the instructions.
I was trying this out and have a few questions/comments.
I tried to load some images with the Load Directory option. The progress bar started and it showed the number of images in the status bar but would never load any. The folder was the Windows default Pictures directory. I assume this is because of some permissions issue. I could load individual images from that directory fine though. Other directories also seemed to work.
Double column mode doesn't seem to work for me no matter what I set in Preferences. It's always single column. Nevermind. I misunderstood what "double column" meant.
I selected some images and created an Arg file just to see what the output would be. Where are these files created? I couldn't find them. Maybe this feature isn't implemented yet?
Just a suggestion: it might be a nice feature to be able to load images from a text file. Either CSV or filenames on a newline.
Quote from: Mizkreant on August 13, 2021, 06:49:44 AM
I tried to load some images with the Load Directory option. The progress bar started and it showed the number of images in the status bar but would never load any. The folder was the Windows default Pictures directory
I selected some images and created an Arg file just to see what the output would be. Where are these files created? I couldn't find them. Maybe this feature isn't implemented yet?
Just a suggestion: it might be a nice feature to be able to load images from a text file. Either CSV or filenames on a newline.
I really don't know. I don't have a windows machine at home and must admit that on my tests I never tried the Pictures folder. I will have a look.
All files that are "extra" created, like arg, csv, pdf, sidecar, xmp, etc. are written to the same folder as where the image resides.
About your suggestion: I will think about that. It might indeed be handy, but did you know that you can specify folders, files, folders with wildcards, files with wildcards, and mixes of that on the command line?
And also that you can drag&drop files or a folder onto the (opened) program window, and on Windows also onto the program icon.
(I have been on a very long stand-still due to an overload of project work which simply took too much time, and in the occasions when I had the time, I didn't have the motiviation to program. Now picking up again)
Finally! A new version.
Version 1.9.0 released
Releases page (https://github.com/hvdwolf/jExifToolGUI/releases) Changelog (https://github.com/hvdwolf/jExifToolGUI/blob/master/Changelog.md)
Only important thing to mention here out of the long and extensive Changelog (https://github.com/hvdwolf/jExifToolGUI/blob/master/Changelog.md) is:
- Dropped support for java-8. See for details the Changelog (https://github.com/hvdwolf/jExifToolGUI/blob/master/Changelog.md) itself.
Looks like some really nice QoL changes. Definitely would use it if I already wasn't better with the command line :D
Quote from: StarGeek on October 23, 2021, 11:47:44 AM
Looks like some really nice QoL changes. Definitely would use it if I already wasn't better with the command line :D
:) Yeah. Something like "real men use the command line". :)
Quote from: Phil Harvey on June 03, 2021, 02:46:19 PM
This is the reason the instructions recommend C:\WINDOWS
Windblows is not really designed (IMHO) for running command line programs. On my XP and Win7-64 systems, I have cygwin installed and start up two Xterms running Zshell. That gets me a Linux-link environment to run command line stuff. Not for the faint of heart.
If I did install exiftool on Windblows (I run it under Linux), I would place it in "Program Files(x86)\exiftool". IMHO, it is not a good idea to drag programs to the desktop, only shortcuts. Easier to find them when they are in the standard installation location. The C:\WINDOWS location is NOT a place to install programs. Unfortunately "Program Files(x86)" is not meant as a place to install programs, but to contain directories that have the actual program. But, for programs like exiftool that a single executables, with no support files, a user could create a "bin" directory there and add that to the PATH. Then all simple executables could be placed in there and be found. Doesn't help with exiftool though.
Unfortunately, because exiftool can't be run like a shell, i.e., starts and listens for commands, I know of no simple way to start exiftool and pass it options all at one go under Windblows.
Just my 10 cents (inflation).
Quote from: MrVideo on November 03, 2021, 10:09:40 AM
Unfortunately, because exiftool can't be run like a shell, i.e., starts and listens for commands, I know of no simple way to start exiftool and pass it options all at one go under Windblows.
I'm not sure if this is exactly what you meant, but ExifTool can start and listen for commands. This is done via
-@ and the
-stay_open option.
- Phil
Interesting. Like I said, I keep learning new things about your program. Not exactly the same as starting a CMD terminal.
But, what you have allows users to create a shortcut to the program and then modify the properties to add those command line options
But, thinking about it, nothing stops a user from creating a shortcut to the CMD program in order to start exiftool from there. No different than my starting a cygwin terminal with a more powerful unix shell.
That is right. You can also make so called "droplets" on windows. Create shortcuts to .bat/.cmd scripts on your desktop for exiftool that do specific things. Like a droplet that (re)sets all images dropped onto it to their "DateTimeOriginal", or a droplet that adds your name, copyright notice, whatever to all the images your drop on it.
You can even create a droplet that does renaming when you drop images on top of it. It can ask prefix, suffix, a nice name, or tag selected from the images (if that is a script option).
That is already a very old technique. When I was still using Windows (until 2006 and from 2010-2012 again?), I've used that for many command-line tools.
Version 1.10 released
Releases page (https://github.com/hvdwolf/jExifToolGUI/releases) | Changelog (https://github.com/hvdwolf/jExifToolGUI/blob/master/Changelog.md)
I am working on a version 2.0.
Versions so far contained a table (top to bottom) displaying images.
Version 2.0 (not released yet) contains an image grid (wrap left to right).
The table is still used when you don't want to see images (I have users loading 1000 images at a time).
See a preview on Youtube (https://www.youtube.com/watch?v=wS9jmhdmjTc).
I added subtitling as comment as that was the simplest and fastest.
Quick question, as I wasn't sure trying to help someone using the GUI. Under the "Your Commands" tab, is quoting system dependent?
Quote from: StarGeek on December 12, 2021, 11:12:56 AM
Quick question, as I wasn't sure trying to help someone using the GUI. Under the "Your Commands" tab, is quoting system dependent?
Yes, it is. The commands are directly given to exiftool, together with the selected images. The (only) advantage to direct exiftool is that you can see the previews and select the images you want to run the command on.
And the exiftool command itself should not be specified.
Linux/macOS: '-FileModifyDate<DateTimeOriginal'
Windows: "-FileModifyDate<DateTimeOriginal"
Thanks for the info.
Sorry if this is mentioned elsewhere, I was heading out while after I answered the question and didn't have time to check.
I found this app today and it looks like the compare option could be useful.
But I can't get that bit to work.
Starting with a fresh reboot, I open JexiftoolsGUI and load just two images.
If I highlight either one I get the Exif data as expected.
Then I select (highlight) both and it says "Multiple images/files selected - Select appropriate action"
I click on the button to compare selected images and it says
"Preparing image metadata for comparison"
But it never goes any further, even after an hour :-(
Have I missed something?
I'm running jExifToolGUI V1.10.0 and ExifTools is version 12.3.9.0
Thanks Bob
Please let me know on which platform you are using JTG.
Secondly: Depending on the platform you are using you will find a logs folder.
- Windows: in the same folder where you run the exe
- Linux: installed debian deb version: in the user home folder; the imageApp: in the same folder as the AppImage
- MacOS: Inside the user home folder
- universal jar: in the same folder as the jar.
Please zip the log(s) and please attach to a post or a PM. Preferably first set the log to a high level (minimal debug), run it again, and share that log. Then you can set back the log level as a high level is slightly slower but also creates large log files.
Many thanks for looking into this, there's no hurry.
I'm on Windows 10 (not sure what JTG is)
Attached is the latest log, hope it helps
Regards, Bob.
Hi all,
I now released version 2.0.0.
I made the version jump from the 10th version in the 1.0 series (1.10.0) due to the reworked thumbnail images grid.
It took quite some time for this release as I have been working overtime for the past 7-8 months for a global project for my "real world job" and couldn't find the motivation to work hard on JTG in my spare free time.
Full changelog (https://github.com/hvdwolf/jExifToolGUI/blob/2.0.0/Changelog.md)
Releases page with current changelog (https://github.com/hvdwolf/jExifToolGUI/releases)
Hi,
I released a bugfix 2.0.1 which also comes with a new Simplified Translation (partially).
Full changelog (https://github.com/hvdwolf/jExifToolGUI/blob/master/Changelog.md)
Releases page with current changelog (https://github.com/hvdwolf/jExifToolGUI/releases)
Title: -title<${filename;s/\..*?$//} works on ExifToolGUI but NOT in jExifToolGUI
I am an irregular user of ExifToolGUI and am hoping to move to the newer supported jExifToolGUI.
I have installed (added to a folder) on Windows 10 and placed the latest exiftool.exe in the same folder as jExifToolGUI.exe and preferences show that folder for ExifTool location.
Mostly it works fine from there.
However in "exiftool direct"/"exiftool commands" Tab
[] These work fine on both ExifToolGUI and jExifToolGUI
-title=titlexxx
-Objectname=object name
[] But these work fine on ExifToolGUI but NOT in jExifToolGUI and gives message "The system cannot find the file specified".
-title<${filename;s/\..*?$//}
-Objectname<${filename;s/\..*?$//}
Same results on both *.jpg and *.png
Is there a different way of inputting more complex commands in jExifToolGUI?
Quote from: jimlad68 on October 15, 2022, 05:26:03 PM[] But these work fine on ExifToolGUI but NOT in jExifToolGUI and gives message "The system cannot find the file specified".
-title<${filename;s/\..*?$//}
-Objectname<${filename;s/\..*?$//}
Try putting quotes around the commands
"-title<${filename;s/\..*?$//}"
"-Objectname<${filename;s/\..*?$//}"
Quote from: StarGeek on October 16, 2022, 03:30:02 PMTry putting quotes around the commands
"-title<${filename;s/\..*?$//}"
"-Objectname<${filename;s/\..*?$//}"
That worked fine thanks. I had tried quotes, but in the wrong place!
As previously stated I am an irregular user of ExifToolGUI and am hoping to move to the newer supported jExifToolGUI. So far I am hopeful but it does not seem as "rounded" as ExifToolGUI. e.g.
[] The file/thumbnail list
- without previews some of the filenames are truncated e.g.
20221005_173012=dpfr Hunter Wreck race=Bradfield, Hobson Moss-remains stone building=(JGO=@53.441684,-1.671593.jpg
truncates to
20221005_173012=dpfr Hunter Wreck race=Bradfield, Hobson Moss-remains stone
- I cannot find a way to remove items
- the exiftoolGui offers file list with column details. The ideal would be to able to select items for columns, file and metadata, similar but better than xnview.
[] I prefer the general layout of ExifToolGUI.
For the present I think I will stay with ExifToolGUI, but will keep a hopeful eye out for jExifToolGUI
It is always complains to me that there is no internet. :(
Version 2.0.2 released
After almost a year now as first thing a bugfix release. I had a difficult 2022 demotivating me for all my hobbies including this "hobby programming".
No further explanation for my long absence :).
As there were quite some bugs to fix, that is now the first release for 2023.
Releases page (https://github.com/hvdwolf/jExifToolGUI/releases) | Changelog (https://github.com/hvdwolf/jExifToolGUI/blob/master/Changelog.md)
Thanks, will check it out.
Quote from: hvdwolf on March 18, 2023, 11:37:28 AMI had a difficult 2022 demotivating me for all my hobbies including this "hobby programming".
Hope things are going better. Totally understand this.
Quote from: Bimbam on March 02, 2023, 06:59:07 AMIt is always complains to me that there is no internet. :(
Do you use a a proxy or private VPN?
Quote from: StarGeek on March 19, 2023, 12:06:30 PMHope things are going better. Totally understand this.
Everything is fine now. Thanks for asking.
I have a lot of images on my phone with the date format in the filename (for example: 20190228_201849.jpg), so I am looking for a way to use that date to copy it to different tags. Most often (for me) the date in the filename is the only date that is accurate, while the existing dates in the metatag data are a big mess. I installed this tool, but I can't find that specific function... any help appreciated!
Since some years I use jExiftoolGUI to insert lens-info in my Photographs with great pleasure.
I use version 1.8.1 because it shows info next to the thumbnails, like focal length.
Unfortunately this info lacks in newer versions, making it hardly usable to quickly add lens-info (i.e. that then I have to look up each file one for one to see which lens has been used).
Now I have been moved, I have to get jExiftoolGUI onto another pc. So I copied the whole folder with version 1.8.1 and created the same path to exiftool.exe.... BUT upon starting jExiftoolGUI the exiftool-lacking-error appears without any possibility to specify the correct path: after pressing OK the result is nothing. No jExiftoolGUI running.
So there seems to be no way being able using jExiftoolGUI on the new pc.
What to do?
Help would be highly appreciated!
Jan.
OS: Windows 10
Newest Java version installed.
Was there ever any resolution to the problem of multiple exiftool entries in the PATH variable on Windows? I tried putting a copy of exiftool.exe in the jExifToolGUI folder, but I still get the error "The ExifTool specified in your preferences does not exist." Naturally, I can't get to my preferences unless the program starts, which it doesn't. Here's the log entry:
#logback.classic pattern: %d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n
22:12:23.175 [main] INFO org.hvdw.jexiftoolgui.Application - Start application jExifToolGUI
22:12:23.175 [main] INFO org.hvdw.jexiftoolgui.Application - Continuing in system language or, if not translated, in English
22:12:24.530 [AWT-EventQueue-0] INFO org.hvdw.jexiftoolgui.mainScreen - string for DB: C:\Users\Tom\jexiftoolgui_data\jexiftoolgui.db
That's all I get.
Development has stopped.
Apologies to all users.
Unfortunately I can't edit the first post anymore.
Since about a year I stopped active development of jExifToolGUI and also lost all interest in "special" photography like animal, bird and panorama photography. I sold all my equipment and got myself an expensive smartphone with good main lens, ultrawide and 3x tele which fits my needs on hikes/walks, travels and holidays, but doesn't require any progam other than Google Photos (for example).
Last months not so serious but annoying and "not going away" health issues, also made me focus on things I now consider more important.
I know there are bugs in the program and I know there are still things that can be improved. And there are users asking for more functionality.
So again: apologies for leaving it in this state where some users stumble on serious bugs or not completed functionality, but at the same time in a state where most users can easily and comfortably use it.
If someone wants to take over, please let me know and I give full access to the repository (https://github.com/hvdwolf/jExifToolGUI). It is 100% open source anyway. Or you simply fork it and continue it in your own way.
Thanks for your support and I hope you understand.
(I was never interested in donations and in all those years, I received an amount to go 2~3 times out on diner with my wife (combined with my other open source projects), so please do not expect or require me to finish something)