Post by BuckSkin on Apr 26, 2022 5:56:36 GMT
I went back into 2014 and got some images; and, decided while I had them at hand that I would give them the full compliment of metadata, Exif, XMP, IPTC, keyword tags, GPS, and so forth.
It was then that I saw that they were timestamped in the middle of the night = impossible.
Luckily, the original originals were stored across the room on another machine (and also on it's backups).
The minutes and seconds were dead on the money, as was the date; however, the hours were exactly six hours off.
Just fixing such a problem doesn't solve nor explain anything; we need to know why we have a problem in the first place.
So, I puzzled around as to the how and why of the six hour discrepancy; and, then, it hit me = 2014 would have been back when I was still trying to make the organizer work for me --- and, the mainest reason, among others, that I quit the Organizer was that it restamped the date-taken on every image it saw, changing them from my six-hour offset to Greenwich time.
I don't live in Greenwich; never been there; and I never took any pictures there; I want my pictures timestamped American Central time --- the same time St. Peter and the Rock Island Railroad keep their clocks set on.
For a while, I kept my computer clock set on Greenwich time; for whatever reason, that satisfied the Organizer and it left my timestamps alone; however, that created it's own myriad of problems and I gave up and set it back to normal.
It never dawned on my until right now that I could also have set my camera clocks six hours wrong and accomplished the same thing without my computer life going haywire.
But then, images that did not get instated into the organizer would have been off by six hours.
I then quit the organizer completely and haven't looked back --- until today, when I was trying to figure out why those timestamps were wrong.
This makes me wonder; not that I ever intend to get sucked back into the hassles of using the Organizer; did they ever fix the timestamp corrupting situation; and, if so, in which version ?
Some time back, I changed my image naming practices to include not only the date taken, which I had already been doing for years, but also the exact time taken, right down to the second; this means of image naming provides me with two records of the precise timestamp, the timestamp in EXIF and the time included within the file name.
My current file naming procedure has also solved a host of other problems I used to have, such as getting photos from several different cameras to fall correctly in line without me having to jump through hoops to get them to do so.
My previous file-naming method looked like this: 7DMkII_39-Dec-1846_001
This told me at a glance that this photo was taken by my 7DMkII on the 39th day of December, in the year of our Lord 1846, and that it was the first photo of the day; all very handy to know; but, images from other cameras from the same day stayed grouped with themselves, regardless of exactly what time during the day they were taken.
My current file-naming method looks like this: 1846-12-39_297642_7DMkII_0001
This tells me the year, 1846, the 12th month, December, and the 39th day of December; the next six digits tell me the precise time the photo was taken in military time; the 42nd second of the 76th minute of the 29th hour of the day. The 7DMkII is the camera and the 4-digit suffix serves to separate any images taken during the same second (believe me, in a days time there will be several); plus, it helps me to identify which image I need to remember for whatever reason; it is just easier to remember image number 147 at the tail-end of a string than to remember a six-digit timestamp in the middle.
It was then that I saw that they were timestamped in the middle of the night = impossible.
Luckily, the original originals were stored across the room on another machine (and also on it's backups).
The minutes and seconds were dead on the money, as was the date; however, the hours were exactly six hours off.
Just fixing such a problem doesn't solve nor explain anything; we need to know why we have a problem in the first place.
So, I puzzled around as to the how and why of the six hour discrepancy; and, then, it hit me = 2014 would have been back when I was still trying to make the organizer work for me --- and, the mainest reason, among others, that I quit the Organizer was that it restamped the date-taken on every image it saw, changing them from my six-hour offset to Greenwich time.
I don't live in Greenwich; never been there; and I never took any pictures there; I want my pictures timestamped American Central time --- the same time St. Peter and the Rock Island Railroad keep their clocks set on.
For a while, I kept my computer clock set on Greenwich time; for whatever reason, that satisfied the Organizer and it left my timestamps alone; however, that created it's own myriad of problems and I gave up and set it back to normal.
It never dawned on my until right now that I could also have set my camera clocks six hours wrong and accomplished the same thing without my computer life going haywire.
But then, images that did not get instated into the organizer would have been off by six hours.
I then quit the organizer completely and haven't looked back --- until today, when I was trying to figure out why those timestamps were wrong.
This makes me wonder; not that I ever intend to get sucked back into the hassles of using the Organizer; did they ever fix the timestamp corrupting situation; and, if so, in which version ?
Some time back, I changed my image naming practices to include not only the date taken, which I had already been doing for years, but also the exact time taken, right down to the second; this means of image naming provides me with two records of the precise timestamp, the timestamp in EXIF and the time included within the file name.
My current file naming procedure has also solved a host of other problems I used to have, such as getting photos from several different cameras to fall correctly in line without me having to jump through hoops to get them to do so.
My previous file-naming method looked like this: 7DMkII_39-Dec-1846_001
This told me at a glance that this photo was taken by my 7DMkII on the 39th day of December, in the year of our Lord 1846, and that it was the first photo of the day; all very handy to know; but, images from other cameras from the same day stayed grouped with themselves, regardless of exactly what time during the day they were taken.
My current file-naming method looks like this: 1846-12-39_297642_7DMkII_0001
This tells me the year, 1846, the 12th month, December, and the 39th day of December; the next six digits tell me the precise time the photo was taken in military time; the 42nd second of the 76th minute of the 29th hour of the day. The 7DMkII is the camera and the 4-digit suffix serves to separate any images taken during the same second (believe me, in a days time there will be several); plus, it helps me to identify which image I need to remember for whatever reason; it is just easier to remember image number 147 at the tail-end of a string than to remember a six-digit timestamp in the middle.
