I use Chronosync to keep four hard drives (one working at home, one working at work, & 2 backups) of photographs synced. My drives are organized by year/event and to make Chronosync faster, I usually create a new Chronosync document for each year. I hadn't done drive-wide syncs in a long time so a few days ago I decided to do full drive syncs. Surprisingly I discovered that a group of photos (NEFs) from May/June 2016 were conflicting with the problem being different file sizes. The get info command (Mac) showed image sizes of 0 x 0 and the color space and color profile were missing in the smaller version of the files so it appears some metadata is missing. The size difference was usually about 12,800 bytes.
So here's where this may or may not be Photo Mechanic related. The files were vacation photos from different time zones than I live. On those vacations, I had borrowed a computer from a friend that had Photo Mechanic and had brought two of my drives with me. The photos were copied daily to the hard drives from the memory cards. I used PM on the trips to cull, crop and keyword the photos. This, of course, would not affect/write to the NEFs directly. However, when I got home, I copied the images from the memory cards to the other two drives and when I ran Chronosync, it came up with a time difference (two drives showed a time difference from the other two drives). I presumed it had to do with the time zone differences between where they were taken and/or written so I used PM to fix the creation and modification times on two of the drives which would write to the NEFs.
So here's the question, is it possible that PM corrupted the metadata when writing to the files or is there another possibility/explanation? Using PM on two drives but not the other two is the only difference in handling that I can think of.
Unfortunately I can't tell you the OS or exact PM version although I know it was v5. The NEF files were from Nikon D7200 and D810.
Thanks and sorry for the long story (but needed to understand what happened).
