Frank Caggiano

Q: Import Window Time Zone brick

Has anyone noticed any weird behavior when trying to change the time zone of images on import?

 

I keep my camera on UTC and set the actual time zone on import. This has been working since I first started using Aperture but I just noticed that going back a week or so it doesn't appear to be working.  No matter what settings I set in the camera/actual time pulldowns the time of the image remains the time the camera put on the image.

 

I can change the time zone using Metadata batch change, that works as expected.

 

I've tried all the standards, new library, new user, booted up in Snow Leopard and tried it. None of that made a difference.

 

So either I'm going crazy (medium-high probability) or something broke on me.

 

Thanks in advance,

 

regards

iMac 3.06ghz 8gb 1 TB, Mac OS X (10.7.2), Aperture 3.2.2

Posted on Jan 4, 2012 7:47 PM

Close

Q: Import Window Time Zone brick

  • All replies
  • Helpful answers

Previous Page 2
  • by léonie,

    léonie léonie Jan 6, 2012 2:01 PM in response to Frank Caggiano
    Level 10 (107,942 points)
    iCloud
    Jan 6, 2012 2:01 PM in response to Frank Caggiano

    Hiklmn, Germany,

    A salute to your wicked sense of humor, Frank. I enjoyed that little joke very much.

     

    OT: It seems we use different translators - the translator I used translated back and forth the string I wanted, and it gave me a nice translation for "फ्लोरिडा", too - only with an additional, surprising "i" inserted.

     

    Makes me wonder, what I really wrote - I sincerely hope, it is not something offensive, what I posted, not really being able to read that script

     

    Cheers, Léonie

  • by léonie,

    léonie léonie Jan 7, 2012 12:54 AM in response to Frank Caggiano
    Level 10 (107,942 points)
    iCloud
    Jan 7, 2012 12:54 AM in response to Frank Caggiano

    OT: I'll change the location string back to german. Since I changed it yesterday, I am flooded with Spam mail  written in Dutch - I found spam is even more annoying if you can't even read it.

  • by Frank Caggiano,

    Frank Caggiano Frank Caggiano Jan 9, 2012 6:03 AM in response to Frank Caggiano
    Level 7 (25,796 points)
    Jan 9, 2012 6:03 AM in response to Frank Caggiano

    Just a final wrap-up on this I'll save you the gory details.

     

    Basically I rolled back Aperture to 3.0.2 and started forward one upgrade at a time. The Time Zone brick worked as it should on import up until 3.1.3. I was surprised by this as 3.1.3 came out in the summer and I was sure my normal import routine was working after that.

     

    BTW this occured on both Lion and Snow Leopard machines.

     

    I never rolled back the Camera Raw updates so there might be some weird interaction going on but I wasn't able to spend the time trying all the different combinations of Aperture and Camera Raw now so I'll have to let it go at that.

     

    Here is a screen shot of the images after import into Aperture. The camera was set to UTC the actual time is EST. The image was shot at 10:38 EST (15:38 UTC EST is UTC – 5). You can see that the first four images (in projects named for the versions they were imported in, 3.0.1 to 3.1.2) all have their time set to 10:38 the final image's time is 15:38, the camera time.

     

    Screen Shot 2012-01-09 at 01-09 08.53.41.png

     

    Anyway at this time I have multiple workarounds so its not a show stopper. I sent a bug report off, hopefully in some future version this will work again as it should.

Previous Page 2