X-Git-Url: https://git.gag.com/?p=web%2Fgag.com;a=blobdiff_plain;f=bdale%2Fblog%2Fposts%2FDigital_Photo_Creation_Dates.mdwn;h=170ab0864ddad8f1cf8315af2a7ddd4cf78b9a2b;hp=dba0151a2faaeb51326e5c055a0faba91fe4fc61;hb=1610a84b87eb89aa66d987d5cddc399251777428;hpb=adc437a64a169b9cbaf3b2a985edee359db7c9e1 diff --git a/bdale/blog/posts/Digital_Photo_Creation_Dates.mdwn b/bdale/blog/posts/Digital_Photo_Creation_Dates.mdwn index dba0151..170ab08 100644 --- a/bdale/blog/posts/Digital_Photo_Creation_Dates.mdwn +++ b/bdale/blog/posts/Digital_Photo_Creation_Dates.mdwn @@ -69,7 +69,7 @@ important, she needs to make sure her camera's time is correctly set, taking advantage of the function that allows here to set the local time from the GPS time. But of course, that only helps future photos... -# The problem +# How I fixed the problem So the problem in front of me was several thousand images taken with the camera's clock "off" by 15 hours and 5 minutes. We figured that out by a @@ -127,7 +127,7 @@ paths quickly followed: done -At this point, all the files on disk wer updated, as a little quick checking +At this point, all the files on disk were updated, as a little quick checking with exif and exiv2 at the command line confirmed. But my second problem was figuring out how to get Piwigo to notice and incorporate the changes. That turned out to be easier than I thought! Using the admin interface to go into @@ -137,6 +137,5 @@ date range (which I expressed as taken:2019-12-14..2021), then selected all photos in the resulting set, and performed action "synchronize metadata". All the selected image files were rescanned, the database got updated... -Voila! - +Voila! Happy wife!