Creation Time Problem on my Mac

[Junebug]

O.K. I just developed a problem on my MacBookPro (OSX 10.5.2)

All of my images (PM 4.5.3.1) appear to have a creation time of 12:00AM so I can't adjust the time.

Same images in Bridge show the correct creation time.

What steps should I take to get PM back on track?

Thanks,

Jb.

[Kirk Baker]

Junebug,

O.K. I just developed a problem on my MacBookPro (OSX 10.5.2)

All of my images (PM 4.5.3.1) appear to have a creation time of 12:00AM so I can't adjust the time.

Same images in Bridge show the correct creation time.

What steps should I take to get PM back on track?

What are you using to see the creation time?  What variable?

-Kirk

[Junebug]

Hi Kirk.... No Variables involved

In a Contact Sheet. Click on Magnifier.
The "Info" pallet reads:
Date: 4/9/08 (correct)
Time: 12:00:00 AM (same for every image)

Selecting a bunch of images and going to "Tools->Adjust Capture Dates and Times" the information in that window for every image reads:
Original date: 4/9/08 12:00:00 AM
Date: 4/9/2008 (correct)
Time: 12:00:00 AM (same for every image)

I noticed this behavior about a week ago but thought, "Haven't check my camera clocks in a while, that must be the glitch" of course it wasn't. And now I on some shoots that scream for syncronized time coding.  Hmmm just realized I haven't checked if PM on another machine reads the time correctly, but as I mentioned earlier Bridge reads the time correctly on the same files. FYI: these are D2x nef and dng files.

[Kirk Baker]

Hi Kirk.... No Variables involved

In a Contact Sheet. Click on Magnifier.
The "Info" pallet reads:
Date: 4/9/08 (correct)
Time: 12:00:00 AM (same for every image)

That is showing you the IPTC date and time, which is not necessarily the capture time.

Selecting a bunch of images and going to "Tools->Adjust Capture Dates and Times" the information in that window for every image reads:
Original date: 4/9/08 12:00:00 AM
Date: 4/9/2008 (correct)
Time: 12:00:00 AM (same for every image)

I noticed this behavior about a week ago but thought, "Haven't check my camera clocks in a while, that must be the glitch" of course it wasn't. And now I on some shoots that scream for syncronized time coding.  Hmmm just realized I haven't checked if PM on another machine reads the time correctly, but as I mentioned earlier Bridge reads the time correctly on the same files. FYI: these are D2x nef and dng files.

Bridge is probably always showing you the capture time and not the IPTC date/time.

How are your images getting onto your system?  If you're using Ingest, are you applying the IPTC Stationery Pad with the date set to apply?

-Kirk

[Junebug]

OK. I've done some testing on three Macs. TWO Intel MacBookPro's and a G5 PowerPC. OSX 10.5.2, PM 4.5.3.1

My findings....

PM reads the Nefs time correctly, but as soon as I convert to DNG with Adobe DNG Converter v4.4.
PM reads the time as 12:00:00 AM and I can't adjust the times or figure out what else to do???

[Junebug]

PS.. I'm not using the IPTC Stationary Pad.

Straight nef to DNG conversion with Adobe DNG Converter then editing in PhotoMechanic.

I just finished looking back a couple of weeks and some shoots PM shows the time correctly.. Others all are set to 12:00:00 AM.

Now I'm really confused. This is happening on different Macs.

Jb.

[Junebug]

Ooops and I apologize for using the words "Creation Time"

This all started when I tried to use the "Adjust Capture Date and Time" Tool and couldn't.

Jb.

[Kirk Baker]

Junebug,

Ooops and I apologize for using the words "Creation Time"

This all started when I tried to use the "Adjust Capture Date and Time" Tool and couldn't.

It's probably our parsing of DNG files then.  Do you have older DNG files that work properly?  Or are all DNG files, even older ones incorrect?

-Kirk

[Junebug]

I've gone back and looked at older dng files.

My current suspicion is that this time thing...

1. started about a month ago
2. doesn't happen every time
3. It's happening on 4 different macs to two different photographers

I'm still investigating. Would files help?

[Kirk Baker]

I've gone back and looked at older dng files.

My current suspicion is that this time thing...

1. started about a month ago
2. doesn't happen every time
3. It's happening on 4 different macs to two different photographers

I'm still investigating. Would files help?

Probably, and a set of steps to reproduce the problem would be nice.

-Kirk

[Junebug]

Sorry I haven't reported back sooner, but a new release of DNG converter came out (v4.4.1) and we haven't been able to to recreate the problem again.

Everything seems to be working now.

We don't know what the problem was but it's gone now.

Jb.