Photo Mechanic > Support
Incremental ingest and time zones
devenh:
Just returned from a trip and I was using PM every day to incrementally ingest photos. Worked fine. I didn't ingest the last day's photos until I returned home. When I ingested, PM read the entire card. I suspect this is be because my laptop's time zone changed. When I reset the laptop's time zone to where I was before, incremental ingest worked.
Using 4.6.9 under Window 7 64 bit.
Deven
Kirk Baker:
Deven,
--- Quote from: devenh on June 22, 2012, 10:27:52 AM ---Just returned from a trip and I was using PM every day to incrementally ingest photos. Worked fine. I didn't ingest the last day's photos until I returned home. When I ingested, PM read the entire card. I suspect this is be because my laptop's time zone changed. When I reset the laptop's time zone to where I was before, incremental ingest worked.
--- End quote ---
Interesting. We'll have to look into that for PM5.
-Kirk
devenh:
Another thing you may want to look at is the insufficient disk space warning. This appears to be calculated using the entire space used on the card rather than just on the images that need to be incrementally ingested.
Deven
fotopan:
--- Quote from: Kirk Baker on June 22, 2012, 10:30:07 AM ---Deven,
--- Quote from: devenh on June 22, 2012, 10:27:52 AM ---Just returned from a trip and I was using PM every day to incrementally ingest photos. Worked fine. I didn't ingest the last day's photos until I returned home. When I ingested, PM read the entire card. I suspect this is be because my laptop's time zone changed. When I reset the laptop's time zone to where I was before, incremental ingest worked.
--- End quote ---
Interesting. We'll have to look into that for PM5.
-Kirk
--- End quote ---
Was this problem solved? Because today - first day after my time zone changed (from UTC+1 to UTC+2 - daylight time saving) PM tried do ingest all photos from a card that has photos dating from November the 1st, 2016 instead of last shot only.
When I compare c:\Users\...\AppData\Roaming\Camera Bits, Inc\Photo Mechanic\ingest\incremental\{ACCF9DAD-194A-437d-82F5-8EB2EB7ABC83} file written today and the same file from a backup, I can see that today the timestamps of files created before time zone change are calculated incorrectly thus making PM downloading all the files again.
In a file written before time zone change, I can see:
DCIM\123_1101\R0001885.JPG 6619136 1477970832 -> PM thinks the file was created Tue Nov 1 3:27:06 UTC 2016
In a file written today I see:
DCIM\123_1101\R0001885.JPG 6619136 1477967232 -> PM thinks the file was created Tue Nov 1 2:27:22 UTC 2016
Kirk Baker:
--- Quote from: fotopan on March 26, 2017, 03:40:53 PM ---
--- Quote from: Kirk Baker on June 22, 2012, 10:30:07 AM ---Deven,
--- Quote from: devenh on June 22, 2012, 10:27:52 AM ---Just returned from a trip and I was using PM every day to incrementally ingest photos. Worked fine. I didn't ingest the last day's photos until I returned home. When I ingested, PM read the entire card. I suspect this is be because my laptop's time zone changed. When I reset the laptop's time zone to where I was before, incremental ingest worked.
--- End quote ---
Interesting. We'll have to look into that for PM5.
-Kirk
--- End quote ---
Was this problem solved? Because today - first day after my time zone changed (from UTC+1 to UTC+2 - daylight time saving) PM tried do ingest all photos from a card that has photos dating from November the 1st, 2016 instead of last shot only.
When I compare c:\Users\...\AppData\Roaming\Camera Bits, Inc\Photo Mechanic\ingest\incremental\{ACCF9DAD-194A-437d-82F5-8EB2EB7ABC83} file written today and the same file from a backup, I can see that today the timestamps of files created before time zone change are calculated incorrectly thus making PM downloading all the files again.
In a file written before time zone change, I can see:
DCIM\123_1101\R0001885.JPG 6619136 1477970832 -> PM thinks the file was created Tue Nov 1 3:27:06 UTC 2016
In a file written today I see:
DCIM\123_1101\R0001885.JPG 6619136 1477967232 -> PM thinks the file was created Tue Nov 1 2:27:22 UTC 2016
--- End quote ---
Part of the problem is that getting the modification time (seconds since the OS epoch) on a file changes when your GMT offset changes. What we'd need to do is write out the modification time adjusted to absolute GMT time and moreover determine which ingest tracking files have the old style modification times and convert them to the "new way" or everyone would have this problem.
Windows in particular does return a different modification time for a file when the GMT offset changes. This would have to be solved first.
-Kirk
Navigation
[0] Message Index
[#] Next page
Go to full version