Really love Photo AI. It’s helped me recover/improve a lot of old low resolution photos. However, I wish it wouldn’t change the Capture Date in the photo metadata to the current date, but rather retain the capture date of the original image. I’m using the Lightroom Plugin.
I’m having the same issue, and it’s really screwing up my calendar view in Mylio Photos. Does anyone know if we can shut off Topaz’s date changing?
They fixed it in Lightroom some time ago. Don’t use Mylio so I can’t speak to that application.
1 Like
This seems like a popular cause of headache. I’ve documented it for my team and we’ll take a look at it.
I’d like to have an option to keep either all or some of the dates from the original file. Normally in a file to have a creation, added, and modification dates. It would great if I could select some or all of those dates to keep.
I understand that file has been changed, so the change date “should” be altered, but that should still be an option.
@brian.spiker Thanks for the feedback.
I think this goes against what most people would want (having the date the image was processed be the date of record) but if there is enough demand to keep the original or have a setting for it, it’s definitely a possibility.
I’m in the process of capturing many hours of personal DV tapes. The resulting .DV files all have a DateTimeOriginal tag with the correct dates and times the video was created. I further split the master file into smaller lossless DV files based on scene changes with dvpackager. Each DV file also has the correct date/time the “scene” was taken.
Now post processing these DV files via VEAI produces great output but minus the Date/Time information. Not good.
So I am looking at work-around scripting with EXIFTool to capture the original Date/Time to re-write it back into the VEAI output file. Perhaps Topaz could add a checkbox to keep this information if existing in the input file. I cannot see why anyone processing personal vintage media would not appreciate it.
Regards
1 Like
I just got a new computer and am finding the date change, but I don’t recall it happening before. It sounded like enough people want to keep the original capture date. I hope this will be an option soon, it is throwing everything off for sorting my pictures.
I just bought Topaz Photo AI yesterday after doing a trial . Since the save function was disabled in the trial, there was no way for me to be aware of this deficiency .
Topaz Labs, why has this option not been added yet ? Will it ever be ?
I often sort my photos by capture time. I also store my photos in a year\month directory structure.
My import filters rely on the capture date, so, if I ever need to recreate my Lightroom Classic catalog, the Topaz processed files will all end up in the wrong folder.
This is a showstopper for me. I am considering getting a refund due to this problem.
I no longer use LRC, but I use Photoshop and Camera Raw with Mylio to organize my photos. I have edited photos with Topaz from within PS and Topaz keeps the original file capture date, so I have no issues using Topaz. I also edit roundtrip from Mylio to Topaz back to Mylio and again the capture date remains intact.
Best Regards,
Rick
I filed a support case. Topaz confirmed this is a bug in Photo AI. It only occurs when using RAW files with the the plug-in function in File / Plug-in extras / Process with Topaz Photo AI, and then exporting back from Photo AI 3 to LRc in DNG format.
This is the workflow described at The Recommended RAW Workflow in Lightroom Classic for Topaz Photo AI - Topaz Labs .
The metadata loss issue does not happen when exporting to TIFF from Photo AI, which forcibly happens if you edit the lighting or color balance.
Unfortunately, so far, Topaz labs has not provided an ETA on when they will fix this problem.
The problem might not apply to Photoshop since it generally does not produce DNGs.
I totally agree with Madbrain… a real problem when you want to keep the DNG format. I spend a lot of time (too much) editing dates!
MadBrain - does Topaz have an external facing system that tracks this issue so we can follow the progress of the issue.
Because of this issue, I have remained on Topaz Photo AI 2.x
