Missing Exposure EXIF Metadata After RAW Conversion

I am running Photoshop CS6 on a 64-bit Windows 7 PC. Since upgrading from CS5 I have noticed that the Exposure EXIF metadata as viewed in Bridge vanishes after RAW conversion/adjustment of my images. I've read at least one other posting to the forums describing a similar situation, however, I've not seen an acknowledgement of an issue or bug in Bridge. Clearing the RAW conversion settings restores the missing EXIF metadata.
Regards,
TonyQ

Have you seen this post? http://forums.adobe.com/thread/1014540?tstart=30

Similar Messages

Why is there missing EXIF metadata after merging aperture libraries?

I had an old library and a new library. All metadata and files were fine in the respective libraries.
After importing one into the other, I am missing all EXIF metadata like Camera, Lens, ISO, Aperture, Focal Length.
Anyone experience this problem or have any ideas?

FIXED!
I waited this long for a simple fix:
Select all the photos, control-click on a photo and select Update from Original.

Exposure to the Right, RAW Conversion

Hi,
I am quite new to ETTR only having started seriously looking into it this week. I have got the "in camera" part OK. What is giving me a headache at the moment is the subsequent RAW conversion as far as exposure is concerned. I note that if I reduce exposure with the "exposure" slider or "recovery" slider, I can get rid of any clipping. But I notice that the histogram and appearance of each procedure is different. Could someone lead me gently and advise which if either is the preferred route?
Peter

Jao vdL wrote:
Yeah, your time is far more valuable than a potential 0.3 dB better signal
to noise.
Horseshyte....
Unless you are shooting a fleeting moment never to happen again (such as news, sports or something like a wedding), you would be a fool not to double check the scene contrast range and compare it to your sensor dynamic range and decide for yourself where to place your exposure on the scale between "normal" VS ETTR.
Most cameras these days handle a good 10-11 stops of scene contrast range no problem. If you are shooting on even a hazy day (let alone a cloudy day) todays sensors can prolly handle the scene with a plus 1/3 to 1 stop increase in base exposure. A +1 stop increase win base exposure in a scene with 10 stops or less will prolly not blow highlights but will result in a capture that when ETTR will produce a less noisy image than "normally" exosed (based on the through the lens metering of todays DSLRs).
If the scene contrast range is less than the dynamic range of the sensor, you are wasting bits to do a "normal" exposure...
All bets are off if the scene contrast range is beyond the dynamic range of the sensor...but of course, making that determination requires knowing both the dynamic range of the sensor (not supper easy to determine) and the contrast range of the scene (again, not easy to determine).
But don't disregard ETTR out of hand without knowing EXACTLY what we are talking about in terms of scene contrast range and dynamic rang os the sensor. In any even, you should try real hard to know what the f$%ck you are doing BEOFRE you actually exposure the frame...

DNG and MESZ timestamp / sony A100 RAW conversion

Hello,
i have a question regarding the timestamp within the EXIF metadata after the RAW to DNG conversion for my A100 pictures. Today I have seen that the timestamp betwen the RAW original file and the converted DNG file differs about 3 hours. I can't explain me this difference by myself. Has someone here an idea for this difference? I use the Mac Version of the actual free DNG converter. My timezone is MESZ/CEST what also means UTC+2 at the moment if I'm right. So 2 hours difference I could imagine because of such a time zone missmatch, but not 3 hours. But if i look at the RAW files the timestamp addition also shows MESZ like in the DNG after conversion. The main reason why I want to use DNG format is the linkage with my GPS logger data. But if the timestamps will convert wrong, this would be a no go for me.
Thanks for your help.
Greetings,
Tschubi

I think what you are seeing is a longstanding mis-match between how Exif and XMP record date-time values, and--possibly--a failure on the part of some of your software to understand how to use date-times read from XMP for the Exif date-time properties. When reading an Exif date-time from XMP, the UTC offset should always be ignored when interpeting the date-time--it has no meaning.
Three date-time metadata properties are involved in this issue, in XMP they are stored as the following properties:
exif:DateTimeDigitized
exif:DateTimeOrigional
xmp:ModifyDate
When Adobe software reads Exif metadata from files, it maps the values in the Exif tag(s) to XMP properties. The XMP is stored inside the file when the software saves or updates a file (or sidecar .xmp file for RAW files).
For exmaple, the exif:DateTimeDigitized the value is taken from two Exif tags, 0x9003 ("DateTimeDigized") and 0x9291 ("SubSecTimeDigizied"). See Part 2 of the XMP Specification for more details about how Exif is mapped to XMP.
The Exif specification defines no way to record a time zone or UTC offset for its date-time values. If you are trying to figure out what time the picture was taken reading Exif, it's impossible to know what time zone is correct. If cameras are recording the time zone, they are storing it in propritary metadata in the file, and not in a standard Exif tag.
Unfortunetly until recently the XMP Specification defined a date-time string format that requires a UTC offset. That's the mismatch. So, what's the software do when it's supposed to write a UTC offset, but doesn't have one to go with the time? Traditionally Adobe software uses whatever time zone your computer's clock has at the time the XMP property is created (that is, when the Exif is read).
So, if your camera's clock was set to record 2009:08:28 11:26:07 in the Exif, and you convert your raw file to a DNG with a computer in Europe, you're probably going to get something like 2009-08-28T11:26:07+02:00 in the XMP. But if I convert the same RAW file to a DNG here in Seattle, I'm going to get 2009-08-28T11:26:07-07:00.
Of course the right thing to do would be to just write 2009-08-28T11:26:07 in the XMP, leaving out the time zone designator (TZD). Expect that in the future. The XMP Specification now says that the TZD is optional and that "software should not assume anything about the missing time zone," but even the most recent release of the DNG Converter (5.5 as I write this) has not yet caught up with this update to the XMP Specification, and it still writes the bogus TZD. Also, any XMP written by older Adobe software will have the TZDs.
What Adobe software like Bridge and Lightroom have done tradtionally is to ignore the TZD in the XMP when using these dates. You'll notice that browsing DNGs with the dates 2009-08-28T11:26:07+02:00 and 2009-08-28T11:26:07-07:00, and running Bridge anywhere in the world (that is regardless of the the clock's Time Zone setting on your computer), the metadata panel will still show you that you took the picture at 11:26 am on August 28, 2009. If other software is trying to shift dates to local times based on the UTC offsets recorded in XMP for these dates, that's a bug.
Note that unlike other date-time values in Exif, the Exif specification says that the GPSTimeStamp is UTC, so this problem does not affect GPS metadata.
I mentioned the XMP specification a few times, you can download it here:
http://www.adobe.com/devnet/xmp/
-David

Missing metadata after saving in LR 1.3 (Windows)

I have touched this subject before in other threads, but I have never got around to do a proper test in 1.3 and someone asked for proof before, so here is the proof.
What I did was shot a JPG with my Canon 1D Mk II and then add some IPTC tags using a IPTC tagger program. I then opened the image in LR, added a keyword and saved it using ctrl-S.
What I found is that some EXIF information is missing from the saved file, but from what I found it seems to be just EXIF information that is moved to XMP. I find it strange that not all EXIF fields are moved to XMP, but it's not a big deal.
But worse is IPTC information that was in the file is also missing and not converted to XMP. In the ExifTool that I used to create the linked files, the ID of the missing IPTC fields are 76 (Contact), 1b (Content location name), 0c (Subject reference), 0a (Urgency) and 07 (Edit status).
Metadata as directly from camera: http://www.svartsinn.net/test/LR/NY7Y1043-fromcamera.txt"
Metadata after tagging IPTC: http://www.svartsinn.net/test/LR/NY7Y1043-Memoria.txt
Metadata after tagging IPTC then saving from LR: http://www.svartsinn.net/test/LR/NY7Y1043-Memoria-LR13.txt
I can accept that LR can not show and edit all types of metadata, but I find it difficult to accept that data is removed from image files.

Sorry to bump this, but are there anyone here who have experienced the same?

After unicode conversion Variant missing

Dear All,
After unicode conversion in transaction S_ALR_87013611 and
S_ALR_87013613 variant is missing.
We checked in table VARIT - "Variant Texts" data is missing.
Kindly suggest.
Thanks and regards,
Joseph

Hello
Did you discover the reason for this? We are now facing the same issue and we cannot find the reason.
I don't think that note 987914 can be the answer.
Can it be something connected to the procedure for conversion or caused by a wrong-executed step?
Every suggestion can help,
Thanks
Luca

Add Exposure Mode Field to EXIF Metadata

Bridge has a field in the EXIF metadata called Exposure Mode. Lightroom does not. Can this field be added in Lightromm? And, if so, how?
Thanks

The ExifMeta plugin lets you view, filter, and search via smart collections any metadata field.

RAW conversion look terrible

With the upgrade to iPhoto 6, RAW conversions from my D70 now look horribly noisy after increasing exposure. For that matter they look terrible when nothing has been done to them. What is going on!?
Left is Preview and Right is iPhoto with out any adjustments.
Powermac G5 Mac OS X (10.4.4)

If you're on the Mac, there was a problem with the update. Read this http://helpx.adobe.com/bridge/kb/acr-84-bridge-cs6-metadata.html

Photoshop Bug? GPS exif metadata stripped out

We recently discovered that ANY changes made in Photoshop CS4 stripped out our GPS exif metadata. We also tried it in CS3 - same thing! And by changes, this includes anything - changing IPTC, adjusting levels, etc. It even happened when just opening, re- saving and closing the file in Photoshop.
FYI: We tested it with images exported from both Adobe Camera RAW (Canon files) and Phocus(Hasselblad), and the problem occurred with both. We've also tried it with files from different cameras, which used different GPS brands altogether, therefore we can rule out: the GPS units, camera (Canon 1Ds Mark II, Hasselblad H3D-39), and software used to convert RAWS (Phocus, Adobe Camera RAW, Lightroom). We also tried different computers to make sure no preferences were corrupt on an individual machine, to rule that out.
To make things even more complicated, we just discovered that even though we can no longer see the GPS info in Photoshop CS4, Adobe Bridge DOES see the GPS info! But - none of our other softwares which normally recognize GPS can see the info (iView, Cumulus).
Very, very frustrating.......HELP!
Mac OS 10.5.6, PowerMac 2 x 2.66 GHz Dual-Core Intel Xenon, Photoshop CS4, Files exported to Prophoto RGB 16-bit TIFF) using both Lightroom and Phocus

Addendum: Does anyone know how to add EXIF back into a file?
I assume this would be difficult, as EXIF is hard to remove, much less put back.
Many of these files have already been worked on extensively, and re-importing and re-working is not a good option.
We have already tried the following (did NOT work):
1) Exporting the XMP from the file BEFORE any changes are made (with GPS info still intact), and importing XMP to finished file (tried all 3 option settings)
2) Copy and pasting the finished file on top of the original (GPS intact file) and flattening, so that the finished file would take on the properties of the old, un-retouched file. What's odd about this is that after flattening the file, saving, and looking at File Info - it appeared it had WORKED. But when you close the file, and re-open, the GPS is gone again.

Export exif / metadata

Hi,
how can i export all exif / metadata from an image to a txt/csv file?
I'm missing the copy & paste function for the metadata. If i edit an image with an external app, some of the exif data gets lost...
Cheers

*missing the edit button*
I want to extract all the exif data (ISO, Aperture, Exposure, ...) I see inside Aperture.
And is there a way to write the exif (ISO, Aperture, Exposure, ..., NOT ONLY the subject, description, ...) from one image to a new image?

Brushes not working with new RAW conversion for Nikon D7000

I have always worked with RAW files w/A2 & A3.1.1 with my Nikon (D80) And now, just got Nikon's D7000 and of course, waited for the RAW conversion that just came out.
Apple addressed the Nikon D7000 RAW situation (which was fixed this month), but now when I use "brushes" on RAW pics, very little if any changes occur.
Very little affect occurs (if any) with A3.1.1 and the "new" RAW conversion for Nikon. I shot (at the same time) both RAW and JPEG (as cameras can) and put them side by side in A3. Pulled down Dodge / Burn / Skin Smoothing & Blur from brushes and they all did a great job. But on the RAW pic that was taken at the same time..... nada, nothing (maybe a minute change, but nothing to call home about).
Bottom line, the newest RAW capability that came out a couple of weeks ago, somehow messed up brushes? I don't think I am that smart or lucky to see this issue. Am I missing something here? If so, please set me straight.
I have tried the places one pulls down brushes but no affect on RAW. Using curves from bricks and luminance, etc, works just fine. Guess I am stuck with JPEG's until this is resolved by our A3 guys, or someone realigns me.

I am able to import them, but I cannot edit them as RAW files. They behave like .jpegs. So correcting exposure for example is a horrible experience. My 5D Mark II files behave as they did in Aperture, so it is the FZ1000 RAWs in particular that are problematic.

OS X 10.4.6 - RAW Conversion

The last I heard in the "where are RAW support fixes contained" was that because AP uses CoreImage to convert RAW, they would be contained in OS X updates, i.e. 10.4.6. Has anyone verified if the RAW conversion problems have been fixed or not (I'm particularly interested in Canon CR2)? Unless I'm missing something, we all should now be holding a fixed converter for RAW formats that were supported prior -- my guess is that new formats will require an Aperture update -- but I would think for existing formats that already were supported, we should be fixed, if the fix was to CoreImage.
At the moment, I have not tested yet, but will later tonight or tomorrow. I would love to hear (or better yet see image comparisons) from someone who has run a test already.
Cheers,
Brad

Yes, William is correct. 10.4.6 delivers support for
several new cameras, but you won't see changes in the
existing RAW decode until 1.1.
This approach was taken so that your existing images,
which you may have spent a great deal of time
adjusting, stay just as you adjusted them until you
explicitly choose to migrate them up to the newer RAW
decode (this can be done in a batch process on select
images or whole projects).
This approach is excellent and I think the only sane thing to do with RAW decoders, but one thing I wanted to confirm - if a person imports a new image into Aperture after loading 10.4.6, that image will be using the new decode, correct?

Bad D3 RAW Conversion - Clipped color in shadows...

...and other issues.
Well. My thread was deleted last time and I didn't get any reasons as to why. What is up with this place? Good thing I always copy my message before posting. Never know when the internet is going to go kaboom... (or somebody is going to delete your thread.)
I just shelled out $200 for this product and the moderators are deleting my threads?!
I think I smell fish.
- Issue 1.
Aperture's raw conversion for the Nikon D3 is clipping the color from shadows.... generally. (About 99% of the time.) It is possible that the couple of images I haven't seen the problem occur in have color detail just above the clipping threshold.
This really makes for some ugly images.
Aperture team: How about we get an update to fix this?
I just spent 5 hours importing and organizing ~3k images into my existing library now that Aperture finally supports the D3 but now I can't use it. Unfortunately I have been forced to use Bridge for the last couple of months due to no D3 support. Through this, I have become accustomed to its (Bridge's) speed and ACR's RAW conversion. Now Aperture flies and it is MUCH appreciated but the raw conversions are a little noisy and the colorless shadows is a BIG problem.
In the samples below, watch the shadow on the brown wall behind her as well as the shadow areas on the neck in the close up. Note that the red strap in the file with the color clipped has almost no red left.
I have another image I took that I was playing with to see how far I could pull the file and still retain shadow detail. The image is in color and looks alright when opened with ACR but when I open it in Aperture, there is almost no color at all in the image. This leads me to believe that Aperture's D3 raw conversion is throwing away color information at a specific level.
I have a couple of sample images side by side here:
http://www.uberfoto.com/images/misc/temp/colorclipfull.png
http://www.uberfoto.com/images/misc/temp/colorclipcrop.png
- FYI, I don't have any of these issues with D200 NEF's.
- Issue 2.
The RAW sharpening has absolutely no affect on any of my D3 images. I bring up the camera model because it could be a specific camera issue. I haven't heard of anybody else having this problem.
- Issue 3.
Where are the CA removal tools?
I don't mean this in any sort of rude way. My intention was to bring up some issues that I have come across and see if I could get some feedback.
-Josh

The email I received was strictly regarding my post being deleted. I have not heard anything in reference to the RAW 2.0 problem.
Here is a comparison of the same image. One exported from Aperture and the other opened in ACR and saved as a JPG.
http://www.uberfoto.com/images/misc/temp/colorclipAP-ACR.jpg
http://www.uberfoto.com/images/misc/temp/colorclip_AP-ACRzoom.jpg
Another thing I noticed is that Aperture preview generator does not clip the color data like the raw converter does. Previews created after image adjustments retain their color in the shadows while the full composite view displays in monochrome. This is an image I took in the studio where the PW died and the flash didn't pop so it was very dark. The original image was nearly all black with no discernible details until I pulled the exposure back up. The ACR conversion looks nearly identical (discarding small differences in brand interpretation) to the "Preview" in AP2.0.
http://www.uberfoto.com/images/misc/temp/colorclipraw.jpg
http://www.uberfoto.com/images/misc/temp/colorclippreview.jpg

How to make Canon specific EXIF metadata visible in LR?

Hi
I love LR but it excludes some fields of EXIF metadata that are provided by Canon's propietary raw converter. I am sure that there must be a way to make these visible inside LR so one can filter and create smart collections based on these metadata.
What is the best way to achieve this? A plug-in? Any additional info?
Thanks,
Juan Dent

One possibility is to use Exiftool that can read Canon tags and transform it to keywords or captions that LR can understand. Check out this list from http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/Canon.html:
Canon CameraSettings Tags
Index
Tag Name
Writable
Values / Notes
1
MacroMode
int16s
1 = Macro
2 = Normal
2
SelfTimer
int16s
3
Quality
int16s
1 = Economy
2 = Normal
3 = Fine
4 = RAW
5 = Superfine
130 = Normal Movie
4
CanonFlashMode
int16s
0 = Off
1 = Auto
2 = On
3 = Red-eye reduction
4 = Slow-sync
5 = Red-eye reduction (Auto)
6 = Red-eye reduction (On)
16 = External flash
5
ContinuousDrive
int16s
0 = Single
1 = Continuous
2 = Movie
3 = Continuous, Speed Priority
4 = Continuous, Low
5 = Continuous, High
7
FocusMode
int16s
0 = One-shot AF
1 = AI Servo AF
2 = AI Focus AF
3 = Manual Focus (3)
4 = Single
5 = Continuous
6 = Manual Focus (6)
16 = Pan Focus
9
RecordMode
int16s
1 = JPEG
2 = CRW+THM
3 = AVI+THM
4 = TIF
5 = TIF+JPEG
6 = CR2
7 = CR2+JPEG
10
CanonImageSize
int16s
0 = Large
1 = Medium
2 = Small
5 = Medium 1
6 = Medium 2
7 = Medium 3
8 = Postcard
9 = Widescreen
129 = Medium Movie
130 = Small Movie
11
EasyMode
int16s
0 = Full auto
1 = Manual
2 = Landscape
3 = Fast shutter
4 = Slow shutter
5 = Night
6 = Gray Scale
7 = Sepia
8 = Portrait
9 = Sports
10 = Macro
11 = Black & White
12 = Pan focus
13 = Vivid
14 = Neutral
15 = Flash Off
16 = Long Shutter
17 = Super Macro
18 = Foliage
19 = Indoor
20 = Fireworks
21 = Beach
22 = Underwater
23 = Snow
24 = Kids & Pets
25 = Night Snapshot
26 = Digital Macro
27 = My Colors
28 = Still Image
30 = Color Accent
31 = Color Swap
32 = Aquarium
33 = ISO 3200
38 = Creative Auto
261 = Sunset
12
DigitalZoom
int16s
0 = None
1 = 2x
2 = 4x
3 = Other
13
Contrast
int16s
0 = Normal
14
Saturation
int16s
0 = Normal
15
Sharpness
int16s
(some models use a range of -2 to +2 where 0 is normal sharpening, and others use a range of 0 to 7 where 0 is no sharpening)
16
CameraISO
int16s
17
MeteringMode
int16s
0 = Default
1 = Spot
2 = Average
3 = Evaluative
4 = Partial
5 = Center-weighted average
18
FocusRange
int16s
0 = Manual
1 = Auto
2 = Not Known
3 = Macro
4 = Very Close
5 = Close
6 = Middle Range
7 = Far Range
8 = Pan Focus
9 = Super Macro
10 = Infinity
19
AFPoint
int16s
0x2005 = Manual AF point selection
0x3000 = None (MF)
0x3001 = Auto AF point selection
0x3002 = Right
0x3003 = Center
0x3004 = Left
0x4001 = Auto AF point selection
0x4006 = Face Detect
20
CanonExposureMode
int16s
0 = Easy
1 = Program AE
2 = Shutter speed priority AE
3 = Aperture-priority AE
4 = Manual
5 = Depth-of-field AE
6 = M-Dep
7 = Bulb
22
LensType
int16s
--> Canon LensType Values
(this value is incorrect for EOS 7D images with lenses of type 256 or greater)
23
LongFocal
int16u
24
ShortFocal
int16u
25
FocalUnits
int16s
26
MaxAperture
int16s
27
MinAperture
int16s
28
FlashActivity
int16s
29
FlashBits
int16s
Bit 0 = Manual
Bit 1 = TTL
Bit 2 = A-TTL
Bit 3 = E-TTL
Bit 4 = FP sync enabled
Bit 7 = 2nd-curtain sync used
Bit 11 = FP sync used
Bit 13 = Built-in
Bit 14 = External
32
FocusContinuous
int16s
0 = Single
1 = Continuous
8 = Manual
33
AESetting
int16s
0 = Normal AE
1 = Exposure Compensation
2 = AE Lock
3 = AE Lock + Exposure Comp.
4 = No AE
34
ImageStabilization
int16s
0 = Off
1 = On
2 = On, Shot Only
3 = On, Panning
35
DisplayAperture
int16s
36
ZoomSourceWidth
int16s
37
ZoomTargetWidth
int16s
39
SpotMeteringMode
int16s
0 = Center
1 = AF Point
40
PhotoEffect
int16s
0 = Off
1 = Vivid
2 = Neutral
3 = Smooth
4 = Sepia
5 = B&W
6 = Custom
100 = My Color Data
41
ManualFlashOutput
int16s
0x0 = n/a
0x500 = Full
0x502 = Medium
0x504 = Low
0x7fff = n/a
42
ColorTone
int16s
0 = Normal
46
SRAWQuality
int16s
0 = n/a
1 = sRAW1 (mRAW)
2 = sRAW2 (sRAW)

Updating EXIF metadata

My new imports into Aperture 2 show some metadata which was not present in in 1.5. Specifically, the new version identifies lenses specifically and records camera serial numbers.
I would like to get my imported library to show these metadata items too. The info must be in the raw file, but doesn't show in the Aperture 2 metadata. I assume this means that the metadata is parsed at import and then not touched again.
Does anyone know a way of forcing Aperture to update the metadata from raw files to take advantage of software improvements?

I am disappointed to see that a bunch of EXIF metadata is still not imported correctly from my EOS 1D Mk 3 - ie metering mode, exposure mode and white balance are still only represented by numbers and not their actual selection title.
Is this my error are there any other EOS1D Mk3 users out there experiencing the same issue?
Dingah

Missing Exposure EXIF Metadata After RAW Conversion

Similar Messages

Maybe you are looking for