Views
1113
Replies
16
Status
Closed
Adobe time error bug – CS2, ACR, Bridge, and DNG converter
Photoshop CS2 erroneously reads the "Date Time" timestamp in File/File Info/ Camera Data 1 in the raw files of Canon 300D and Canon S45 and I suspect some other cameras too.
Adobe Camera Raw (ACR), Adobe Bridge, and Adobe DNG converter all have the same bug. Bridge and ACR then propagate these wrong times into XMP files and any files made from the raw files (PSDs, JPGs, etc.).
And to make matters worse, these erroneous times are embedded into "read only" fields in the "child" files.
This is all quite a shame to totally disable such a major work of software. Our business was in the process of building a complete new workflow around CS2, Bridge, & DNG converter, but we can’t use any of it because accurate date/time stamps are an essential and integral part of our complete filing system. We can’t even use the new ACR for any conversions because it ruins the conversion with a false timestamp.
We never saw any sign of this problem with previous versions of Photshop (CS) and ACR (pre 3.0). Now, using the same raw image files, we are seeing different time values with the new CS2 and its attendant plugins and supporting software.
I have posted a table with some sample files that show how in some cases the timestamp data is handled erroneously by the Adobe products and in other cases the timestamp data is handled properly. I am hoping that:
1) Adobe uses this information to fix this problem quickly so that we can get on with using this otherwise great software.
2) Adobe creates a utility to repair the damage it has done in embedding this erroneous timestamp data into DNG files, XMP files, and processed image files created from raw files.
The table and the files can be accessed by clicking here.
Photoshop CS2 erroneously reads the "Date Time" timestamp in File/File Info/ Camera Data 1 in the raw files of Canon 300D and Canon S45 and I suspect some other cameras too.
Adobe Camera Raw (ACR), Adobe Bridge, and Adobe DNG converter all have the same bug. Bridge and ACR then propagate these wrong times into XMP files and any files made from the raw files (PSDs, JPGs, etc.).
And to make matters worse, these erroneous times are embedded into "read only" fields in the "child" files.
This is all quite a shame to totally disable such a major work of software. Our business was in the process of building a complete new workflow around CS2, Bridge, & DNG converter, but we can’t use any of it because accurate date/time stamps are an essential and integral part of our complete filing system. We can’t even use the new ACR for any conversions because it ruins the conversion with a false timestamp.
We never saw any sign of this problem with previous versions of Photshop (CS) and ACR (pre 3.0). Now, using the same raw image files, we are seeing different time values with the new CS2 and its attendant plugins and supporting software.
I have posted a table with some sample files that show how in some cases the timestamp data is handled erroneously by the Adobe products and in other cases the timestamp data is handled properly. I am hoping that:
1) Adobe uses this information to fix this problem quickly so that we can get on with using this otherwise great software.
2) Adobe creates a utility to repair the damage it has done in embedding this erroneous timestamp data into DNG files, XMP files, and processed image files created from raw files.
The table and the files can be accessed by clicking here.
Related Tags
Master Retouching Hair
Learn how to rescue details, remove flyaways, add volume, and enhance the definition of hair in any photo. We break down every tool and technique in Photoshop to get picture-perfect hair, every time.