![]() ![]() When I look at its Properties in Windows Explorer, I see that its "Date taken" as displayed under the file's Details has been changed as I wanted. In the Metadata Panel I can modify the Date Digitized but not the Date Created. I don't know how to use "ExifTool Command Processor." I'm working on JPG files, not NEF. I'm trying to use the "Modify EXIF Date and Time". Have installed and am running iMatch 2019.5.2. Still having trouble modifying date and time stamps. If needed, I can also supply the two jpegs. However, I have provided the attached files in case the problem is one that might impair the new TimeWiz tool. So, for my purposes, I would now rate the issue as not very important. The few that don't are easily identified later and can be adjusted with the tool in absolute mode. Many of the ones I still need to modify appear to behave well with the Modify tool. How critical is a resolution of this issue to me? I think I found a cluster of poorly behaving files yesterday. The output from the EXIFtool is attached as well as a zipped version of the debug log file for the operation. As well, after a restart of iMatch, I selected them as a group of two files and attempted to modify their time in relative mode. For each, I attach a copy of their metadata. I have selected one file that is modified correctly in relative mode (Iron Islands) and one which does not (Talbot Creek). I look forward to any advice you can offer.įurther experimentation suggests it is confined to a smallish subset of the jpegs. I've also checked that the permissions to modify EXIF data (Preferences>Metadata2) in the main installation are on the default values indicated in the Help page. txt files of the EXIF output from attempting to use the modify tool in relative mode on a single file for the main database (ModifyRelMain.txt) and from the virtual database (ModRelTest.txt). I returned to my main database, performed a cold boot and a repair of the iMatch ver 2019.5.2 installation and found again that the modify tool worked properly in absolute mode but not in relative mode. I then updated to the latest version of iMatch and repeated the test with the same result, ie, flawless operation. I found I could modify the time and date in both absolute and relative modes using the tool. I made a database using copies of a subset of the troublesome jpegs. I mainly use it in absolute mode, correctly setting dates on old scanned images.Īs a test, I set up Win10 Home in a virtual machine and loaded iMatch ver 2019.2.2. Overall, I find the Modify tool extremely valuable. I'm almost certain this problem is recent, as I fixed another batch of his photos last week and also earlier fixed one of my own problems, when I photographed furiously in Amsterdam for two days before I remembered that my camera still thought it was on the other side of the planet.Īs I have updated iMatch in the last couple of days, I will try to see if that is the problem by installing the previous version on another computer and setting up a small test database. Taking the images one at a time and changing them using the Modify tool in absolute mode works well, but tediously, as does changing the data manually in the Metadata panel. As they are shot over the duration of an expedition, each has a different, but incorrect, time stamp in all time-related metadata fields (examined using the metadata panel).Īttempting to fix the problem by using the Modify tool in relative mode, for either single images or a batch, gives EXIF output (viewed in Output panel) that indicates changes have been made, but no metadata fields were actually changed. His are jpegs and all are out by 25 minutes. Like tomdriver, I am trying to align, in time line view, a stream of my photos with those of a friend. I, too, have found problems recently with the "Modify EXIF date and time tool".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |