Date Feature now selecting wrong dates
Looks like 2021.1 (15.1.0.10100) has introduced a problem in selecting photos by capture date. The attached screenshot shot shows a selected date of 6th March, but the photo capture date is 7th March. (Looks like a time zone issue, but I see no way to fix the time zone of Australia/Canberra (+10)).
Thanks for any help. Craig.
-
You'll have to report this to tech support Craig. There were some changes made for this version to allow different date formats according to language settings in the OS. It's possible there is a bug in the program or a setting change you might be able to make that I don't know about. Use the Submit a request link below after reading this article on How to submit a problem to ON1 Tech Support - A Step-by-step Guide
0 -
Thanks Brian. Will do...
0 -
I am using the latest version 2022 and the date of capture of the photos are still incorrect in my catalogue.
has this been fixed or has the defect crept back into the latest version?
Do I need to report it to support?TIA
Glyn0 -
The program only displays the capture date as recorded in the image's metadata by the camera. If you're seeing something different then yes, you should report it to tech support.
How to submit a problem to ON1 Tech Support - A Step-by-step Guide
0 -
I may be having problems with the same bug in ON1 Photo Raw version 2023.5 (17.5.1.14051).
I'm using a Panasonic S5 and ON1 is reading the date wrong in either the JPG or raw file so that the two don't pair up properly. I can use the feature Photo > Edit Capture Date... > Set to create date and then the two image have the same date. Then I have to go into preferences, turn off pairing, go back into preferences, turn on pairing, and then the files are paired together.
Then when I do something like copy an edit from one photo to another, and the date changes to the wrong date again! Then I have to go through all the steps to correct the date all over again.
I'm sure it's a time zone offset problem since the date is always off by either 8 or 7 hours and I'm in California with -8 for Pacific Standard Time, or -7 for Pacific Daylight Time.
I've sent in detailed screenshot examples, RAW and jpg examples, and I recently send in a screen recording of what happens. My support tickets are 347543 and 356659 but they haven't been able to help me or haven't been able to reproduce the problem.0 -
I haven't had this problem either as Canon, FujiFilm and Sony record the correct date & time from the time zone in the camera settings ... where I set the date and time and then the Area/Time Zone, when I move to another Time Zone I just change the Area/Time Zone and it records the correct date and time as per that Time Zone.
0 -
What the camera records is not the problem. They all record the date/time according to what the user has set for that camera. The problem is that sometimes Photo RAW is not using the date that was recorded. Rather, it is applying some kind of offset. Most likely back to UTZ as Nicholas mentioned. I see this problem with some of my Canon files. Mostly on older stuff I've had for a while.
0 -
Now that I'm looking into this bug it's getting completely ridiculous! I'm spending hours just fixing the dates on my photos constantly. ON1 Photo is nearly unusable with this bug-- I like the software otherwise.
When I import some photos the RAW and jpg dates don't match so I have to fix the dates, unpair the images in preferences, exit preferences, and then pair the images again. Then while I'm editing, the dates will mess up again and I'll have to fix them again. And now I see that it exports the images +14 hours into the future, so I have to go through every exported image and fix the dates again! The exported images have the incorrect date in the EXIF data so I have to use a separate EXIF editing program to fix those.
I can't even image how the programmers messed up the dates so badly.0 -
I am frustrated with this problem as well. I have an Olympus camera and live in Sydney Australia. My date time meta data is being offset by 10 hours.
I don't understand why ON1 can't communicate what the fix is or when it will be fixed.
0
Please sign in to leave a comment.
Comments
9 comments