Modification time +1:00 after shooting time
Locked
 
|
I just notice that Digikam displays a modification time that is equal to the shooting time + 1 hour.
How comes? I have not modified anything yet, I've only rated a couple of pictures, in the process of sorting them? Marie-Noëlle -- Une galerie photos, un blog ... pourquoi pas ? Webmaster en herbe Parcourez les Cévennes à ma façon : Cévennes Plurielles Et toutes mes autres publications à partir de ma page d'accueil générale _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Modification time +1:00 after shooting time
|
|
From metadata or file timestamp. Look file properties...
Gilles Caulier 2011/12/27 Marie-Noëlle Augendre <[hidden email]>: > I just notice that Digikam displays a modification time that is equal to the > shooting time + 1 hour. > How comes? I have not modified anything yet, I've only rated a couple of > pictures, in the process of sorting them? > > Marie-Noëlle > > -- > Une galerie photos, un blog ... pourquoi pas ? Webmaster en herbe > > Parcourez les Cévennes à ma façon : Cévennes Plurielles > > Et toutes mes autres publications à partir de ma page d'accueil générale > > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
File properties.
Metadata seem to be OK (= shooting time), but file properties is 1 hour later (and same in the file manager outside Digikam) . This is quite recent, as only the past 2 weeks photos seem to have this problem. Marie-Noëlle 2011/12/27 Gilles Caulier <[hidden email]> From metadata or file timestamp. Look file properties... -- Une galerie photos, un blog ... pourquoi pas ? Webmaster en herbe Parcourez les Cévennes à ma façon : Cévennes Plurielles Et toutes mes autres publications à partir de ma page d'accueil générale _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Modification time +1:00 after shooting time
|
|
Is it exactly 1 hour to the second or just 'around' 1 hour? What OS?
If it is exactly 1 hour, it might be related to the timezone/daylight savings setting for your OS. I had some 1 hour offsets going between windows and linux because of this once (not digikam related, just made rsync go crazy). On Tue, Dec 27, 2011 at 3:19 PM, Marie-Noëlle Augendre <[hidden email]> wrote: > File properties. > Metadata seem to be OK (= shooting time), but file properties is 1 hour > later (and same in the file manager outside Digikam) . This is quite recent, > as only the past 2 weeks photos seem to have this problem. > > Marie-Noëlle > > > 2011/12/27 Gilles Caulier <[hidden email]> >> >> From metadata or file timestamp. Look file properties... >> >> Gilles Caulier >> >> 2011/12/27 Marie-Noëlle Augendre <[hidden email]>: >> > I just notice that Digikam displays a modification time that is equal to >> > the >> > shooting time + 1 hour. >> > How comes? I have not modified anything yet, I've only rated a couple of >> > pictures, in the process of sorting them? >> > >> > Marie-Noëlle >> > >> > -- >> > Une galerie photos, un blog ... pourquoi pas ? Webmaster en herbe >> > >> > Parcourez les Cévennes à ma façon : Cévennes Plurielles >> > >> > Et toutes mes autres publications à partir de ma page d'accueil générale >> > >> > >> > _______________________________________________ >> > Digikam-users mailing list >> > [hidden email] >> > https://mail.kde.org/mailman/listinfo/digikam-users >> > >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users > > > > > -- > Une galerie photos, un blog ... pourquoi pas ? Webmaster en herbe > > Parcourez les Cévennes à ma façon : Cévennes Plurielles > > Et toutes mes autres publications à partir de ma page d'accueil générale > > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Just 1 hour.
I'm running Linux / Fedora 16. I didn't change anything recently, and the problem seems to have arisen a couple of weeks ago; on photos taken before, the time is OK. Marie-Noëlle
2011/12/28 JD Rogers <[hidden email]> Is it exactly 1 hour to the second or just 'around' 1 hour? What OS? -- Une galerie photos, un blog ... pourquoi pas ? Webmaster en herbe Parcourez les Cévennes à ma façon : Cévennes Plurielles Et toutes mes autres publications à partir de ma page d'accueil générale _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Modification time +1:00 after shooting time
|
|
Marie-Noëlle Augendre wrote:
> Just 1 hour. > I'm running Linux / Fedora 16. I didn't change anything recently, and the > problem seems to have arisen a couple of weeks ago; on photos taken before, > the time is OK. If the problem has already started a couple of weeks ago (not just 2 weeks ago, as you said in an earlier post) then I'd say it could be due end of daylight saving time (DST). I also had a similar problem because I forgot to change the camera's time back from DST to standard time. When I tried to geotag some photos with a .gpx file from a GPS logger I saw that they were assigned to a wrong location. This was because my Linux system time (CET; I live in Germany) had changed from UTC+2h to UTC+1h at the end of DST, but my camera was still on UTC+2h, so the geotags which are UTC time only were assigned with a position where I had been 1 hour before or later. You should check if all time related settings are OK. In a console window you can enter the following command to check your Linux system's UTC time and local time: export LANG=; date -u; date On my machine the result is: Wed Dec 28 14:03:02 UTC 2011 Wed Dec 28 15:03:02 CET 2011 i.e. the difference is exactly 1 hour. If my assumption that you live in France is correct then your local time should also be CET, and thus the command above should yield the same difference of 1h. If your local time is also the correct currnt time then your Linux time should be OK, and see if the camera shows the same time as your PC. Martin _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Modification time +1:00 after shooting time
|
|
In reply to this post by tosca
As you mentioned it I took a look on my own photos and I can see the same.
During Summer season (summer time) the difference is two hours and during winter time it is one hour off. Metadata matches real shooting time, file date is one hour ahead. So other than Marie I have this problem since at least half a year. I use Fedora 16 as well and my system is set to CET (hardware clock is set to UTC). Regards Martin Am Dienstag, 27. Dezember 2011, 22:19:24 schrieb Marie-Noëlle Augendre: > File properties. > Metadata seem to be OK (= shooting time), but file properties is 1 hour > later (and same in the file manager outside Digikam) . This is quite > recent, as only the past 2 weeks photos seem to have this problem. > > Marie-Noëlle > > 2011/12/27 Gilles Caulier <[hidden email]> > > > From metadata or file timestamp. Look file properties... > > > > Gilles Caulier > > > > 2011/12/27 Marie-Noëlle Augendre <[hidden email]>: > > > I just notice that Digikam displays a modification time that is > > > equal to> > > the > > > > > shooting time + 1 hour. > > > How comes? I have not modified anything yet, I've only rated a > > > couple of pictures, in the process of sorting them? > > > > > > Marie-Noëlle > > > > > > -- > > > Une galerie photos, un blog ... pourquoi pas ? Webmaster en herbe > > > > > > Parcourez les Cévennes à ma façon : Cévennes Plurielles > > > > > > Et toutes mes autres publications à partir de ma page d'accueil > > > générale > > > > > > > > > _______________________________________________ > > > Digikam-users mailing list > > > [hidden email] > > > https://mail.kde.org/mailman/listinfo/digikam-users > > > > _______________________________________________ > > Digikam-users mailing list > > [hidden email] > > https://mail.kde.org/mailman/listinfo/digikam-users Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Just in case ... do you remember if you change Digikam version at that time?
Marie-Noëlle 2011/12/28 Martin (KDE) <[hidden email]> As you mentioned it I took a look on my own photos and I can see the same. -- Une galerie photos, un blog ... pourquoi pas ? Webmaster en herbe Parcourez les Cévennes à ma façon : Cévennes Plurielles Et toutes mes autres publications à partir de ma page d'accueil générale _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Modification time +1:00 after shooting time
|
|
Am Mittwoch, 28. Dezember 2011, 16:10:48 schrieb Marie-Noëlle Augendre:
> Just in case ... do you remember if you change Digikam version at that time? Not very likely. I used Fedora 15 until about one month ago and only used the digikam version shipped with fedora (1.9 at that time). Most likely this is a problem of vfat file system (wich almost all cameras are using internally). Unlike unix file system vfat is not able to handle local time versus UTC. The strange thing however is: photos taken in May this year have a matching timestamp and photos taken in June differs (two hours). May be there was a change in digikam (fedora package) at this time. So may be I switched from F14 to F15 in between. Martin > > Marie-Noëlle > > 2011/12/28 Martin (KDE) <[hidden email]> > > > As you mentioned it I took a look on my own photos and I can see the > > same. During Summer season (summer time) the difference is two hours > > and during winter time it is one hour off. Metadata matches real > > shooting time, file date > > is one hour ahead. So other than Marie I have this problem since at > > least > > half > > a year. > > > > I use Fedora 16 as well and my system is set to CET (hardware clock > > is set > > to UTC). > > > > Regards > > Martin Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Modification time +1:00 after shooting time
|
|
Am Mittwoch, 28. Dezember 2011, 16:32:07 schrieb Martin:
> Am Mittwoch, 28. Dezember 2011, 16:10:48 schrieb Marie-Noëlle Augendre: > > Just in case ... do you remember if you change Digikam version at that > > time? > Not very likely. I used Fedora 15 until about one month ago and only used > the digikam version shipped with fedora (1.9 at that time). Most likely > this is a problem of vfat file system (wich almost all cameras are using > internally). Unlike unix file system vfat is not able to handle local time > versus UTC. OK, this has nothing to do with digikam at all. I have just taken a photo and opened it a few seconds afterwards with dolphin. It reports a timestamp of one hour in the future for the file. Most likely something changed in between in the kernel or another system lib/tool. Martin > > The strange thing however is: photos taken in May this year have a matching > timestamp and photos taken in June differs (two hours). May be there was a > change in digikam (fedora package) at this time. So may be I switched from > F14 to F15 in between. > > Martin > _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Modification time +1:00 after shooting time
|
|
In reply to this post by Martin (KDE)
Interesting.. Martin, good call on checking your own photos. I just
did and see that I have this as well, but it's intermittent. Photos from last week are fine, photos from some time back have an hour difference. I'll see if I can nail down when the change happened tonight which might help determine what caused it. One thing to try is grabbing some pics from the camera as a mounted usb device vs through digikam and see if there is a difference. I guess in the end, I don't mind too much as long as the metadata is correct. If the filesystem dates are off, one could always right a script to grab the date using exiv2 and correct the file system time using touch, but sounds like more work than it's worth. On Wed, Dec 28, 2011 at 9:32 AM, Martin (KDE) <[hidden email]> wrote: > Am Mittwoch, 28. Dezember 2011, 16:10:48 schrieb Marie-Noëlle Augendre: >> Just in case ... do you remember if you change Digikam version at that time? > > Not very likely. I used Fedora 15 until about one month ago and only used the > digikam version shipped with fedora (1.9 at that time). Most likely this is a > problem of vfat file system (wich almost all cameras are using internally). > Unlike unix file system vfat is not able to handle local time versus UTC. > > The strange thing however is: photos taken in May this year have a matching > timestamp and photos taken in June differs (two hours). May be there was a > change in digikam (fedora package) at this time. So may be I switched from F14 > to F15 in between. > > Martin > >> >> Marie-Noëlle >> >> 2011/12/28 Martin (KDE) <[hidden email]> >> >> > As you mentioned it I took a look on my own photos and I can see the >> > same. During Summer season (summer time) the difference is two hours >> > and during winter time it is one hour off. Metadata matches real >> > shooting time, file date >> > is one hour ahead. So other than Marie I have this problem since at >> > least >> > half >> > a year. >> > >> > I use Fedora 16 as well and my system is set to CET (hardware clock >> > is set >> > to UTC). >> > >> > Regards >> > Martin > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Modification time +1:00 after shooting time
|
|
Am Mittwoch, 28. Dezember 2011, 09:47:08 schrieb JD Rogers:
> Interesting.. Martin, good call on checking your own photos. I just > did and see that I have this as well, but it's intermittent. Photos > from last week are fine, photos from some time back have an hour > difference. I'll see if I can nail down when the change happened > tonight which might help determine what caused it. > > One thing to try is grabbing some pics from the camera as a mounted > usb device vs through digikam and see if there is a difference. > > I guess in the end, I don't mind too much as long as the metadata is > correct. If the filesystem dates are off, one could always right a > script to grab the date using exiv2 and correct the file system time > using touch, but sounds like more work than it's worth. As I used the digikam option to change the file's timestamp on every metadata update this is nothing I worry about. But I want to know why the offset is there. Martin _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Modification time +1:00 after shooting time
|
|
In reply to this post by Martin (KDE)
> > OK, this has nothing to do with digikam at all. I have just taken a photo > and opened it a few seconds afterwards with dolphin. It reports a > timestamp of one hour in the future for the file. Most likely something > changed in between in the kernel or another system lib/tool. This would be interesting to know. There is a bug report opened recently about a similar problem, and as DST happens twice a year I would have expected such problem to have been reported before. Memory cards are usually vfat which stores time in local time and have no time zone info, so it's clear that things can break but I would be interested if, and if, why, things worked so far. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Modification time +1:00 after shooting time
|
|
In reply to this post by tosca
Just a shot in the dark, but it may not be a problem with digikam per
se. I've had a similar problem with the << at >> command, so it may be an internal problem with C libraries. If I recall correctly, at the time, I did a search on Google and there were plenty of references to that problem. Bug reports are on file, either with Debian or Fedora or both. I use both and I don't remember which one I checked. I wish now I had made notes. That might have been helpful. Sorry. Regards Philippe On Wed, 28 Dec 2011 14:07:08 +0100 Marie-Noëlle Augendre <[hidden email]> wrote: > Just 1 hour. > I'm running Linux / Fedora 16. I didn't change anything recently, and > the problem seems to have arisen a couple of weeks ago; on photos > taken before, the time is OK. > > Marie-Noëlle > > 2011/12/28 JD Rogers <[hidden email]> > > > Is it exactly 1 hour to the second or just 'around' 1 hour? What OS? > > If it is exactly 1 hour, it might be related to the > > timezone/daylight savings setting for your OS. I had some 1 hour > > offsets going between windows and linux because of this once (not > > digikam related, just made rsync go crazy). > > > > > > On Tue, Dec 27, 2011 at 3:19 PM, Marie-Noëlle Augendre > > <[hidden email]> wrote: > > > File properties. > > > Metadata seem to be OK (= shooting time), but file properties is > > > 1 hour later (and same in the file manager outside Digikam) . > > > This is quite > > recent, > > > as only the past 2 weeks photos seem to have this problem. > > > > > > Marie-Noëlle > > > > > > > > > 2011/12/27 Gilles Caulier <[hidden email]> > > >> > > >> From metadata or file timestamp. Look file properties... > > >> > > >> Gilles Caulier > > >> > > >> 2011/12/27 Marie-Noëlle Augendre <[hidden email]>: > > >> > I just notice that Digikam displays a modification time that > > >> > is equal > > to > > >> > the > > >> > shooting time + 1 hour. > > >> > How comes? I have not modified anything yet, I've only rated a > > >> > couple > > of > > >> > pictures, in the process of sorting them? > > >> > > > >> > Marie-Noëlle > > >> > > > >> > -- > > >> > Une galerie photos, un blog ... pourquoi pas ? Webmaster en > > >> > herbe > > >> > > > >> > Parcourez les Cévennes à ma façon : Cévennes Plurielles > > >> > > > >> > Et toutes mes autres publications à partir de ma page d'accueil > > générale > > >> > > > >> > > > >> > _______________________________________________ > > >> > Digikam-users mailing list > > >> > [hidden email] > > >> > https://mail.kde.org/mailman/listinfo/digikam-users > > >> > > > >> _______________________________________________ > > >> Digikam-users mailing list > > >> [hidden email] > > >> https://mail.kde.org/mailman/listinfo/digikam-users > > > > > > > > > > > > > > > -- > > > Une galerie photos, un blog ... pourquoi pas ? Webmaster en herbe > > > > > > Parcourez les Cévennes à ma façon : Cévennes Plurielles > > > > > > Et toutes mes autres publications à partir de ma page d'accueil > > > générale > > > > > > > > > _______________________________________________ > > > Digikam-users mailing list > > > [hidden email] > > > https://mail.kde.org/mailman/listinfo/digikam-users > > > > > _______________________________________________ > > Digikam-users mailing list > > [hidden email] > > https://mail.kde.org/mailman/listinfo/digikam-users > > > > > _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |