This is a really interesting train of thought, and as
somebody that has spent days (literally), trying to correctly adjust
times on my camera, it's very compelling to me. I worry though that
the learning curve is too steep. |
I'm not sure people will understand why taking a picture of their
computer would somehow affect the timestamps on their photos,
especially if they were taking a picture of a barcode. Maybe a thing
that would make it more obvious would be to have a screen where half
of the picture was the current time (something that makes sense to
humans), and the other half was the barcode (for the computers).
I'm also concerned that I wouldn't use the feature because I
wouldn't expect to have my computer near me when I remembered to set
the time on my camera, so maybe a matching iPhone/Android app should
Another question I know I'd have if I used this feature
would be how the time zone setting on my computer/phone would affect
the time stamp on the camera/photos. I'm not an expert on EXIF, so I
don't know whether JPEGs, cameras, f-spot, nautilus, etc. support
it, so I'd be worried that would be messed up somehow. Again, maybe
showing the time zone on the barcode screen (if it's encoded) would
A mock up or sketch of how this would look would make things gel
much more, I think, though I'm terrible at making these things. I'll
bounce this off some people, and see if anybody has any ideas...
Jan Girlich wrote on 09/06/2010 03:50 AM:
Am 06.09.2010 12:29, schrieb Matija Cizmek:
> On Tue, Aug 31, 2010 at 11:16 AM, Jan Girlich
> <vollkorn cryptobitch de> wrote:
>> Am Dienstag, den 31.08.2010, 07:52 +0200 schrieb Mike
>>> Am Dienstag, den 31.08.2010, 01:17 +0200 schrieb Jan
>>>> This is just a preparatory step for syncing GPS
>>>> pictures, for which accurate EXIF times are
>>> Just let the user adjust the time. If he or she
>>> photo properly, you exactly know the difference of
UTC and Exif
>>> time. So, I don't see a problem there. From my
>>> time is normally far away from be set properly. I
>>> to do the clock change and also my camera clock is
>>> minutes out of sync.
>> I am sorry, but from this statement I must assume you did
>> understand my idea at all.
>> You just repeated the problem I'm trying to solve with my
>> the camera clocks are way off. I proposed a
semi-automatic way to
>> correct the EXIF timestamps properly.
>> Positioning one photo correctly on a map is not a very
>> solution because people usually spend more time than one
>> at one spot to take a picture. So by placing one picture
>> correctly you only determine a time frame of several
>> which is not accurate enough and causes the user to
>> several pictures until he pinpointed the time properly
>> whole import roll.
>> My way for time synchronization has two advantages:
>> 1) More accurate (and easier to use, I think).
>> 2) Can be implemented right now, all the necessary libs
>> available (No need for a map widget).
>> Cheers Jan
> Hi, sorry for late contribution to this discussion, but your
> solution seems really complicated. What I do on my trips is
> when my GPS acquires signal lock I take a picture of it's
> with visible time displayed. Later, I can easily calculate
> time difference by comparing file time with photograph
That's exactly the idea. But instead of taking a picture of your
you take a picture of a 2D barcode encoding the time (this barcode
changes every second) and the time difference is calculated
automatically. So it's much easier than your usual way since it
automates half the process, I'd say. Also it works for people who
a GPS tracker without any display like mine.
What the user would do:
1. Start f-spot and hit a button added by the extension. A 2D
changing every second will show up.
2. The user takes a photo of his screen with the barcode.
3. The user imports the photos of his camera. The user is done
4. The f-spot extension automatically reads the barcode,
the time difference and sets the pictures properly.
It's as simple as that.
f-spot-list mailing list
f-spot-list gnome org