PSP XI & exif...to Lightroom

I won't talk about Lightroom much right now (still testing)...
After importing several hundred images (mixed raw and jpeg), I've discovered:
1. PaintshopPro doesn't preserve complete exif data when saving image. To be more precise: complete Makernote section is missing. You want to know e.g. which lens was used when picture was taken? Bad luck: it's a part of Makernote data -so Lightroom will give you "Unknown Lens".
2. Also it seems, that PSP doesn't write DateTime values as it should. Result? Lightroom refuses to recognise DateTime values saved with PSP... so you'll get "Unknown Date" in Metadata Browser. At first I though it's Lightroom's fault, but Opanda PowerExif showed values (DateTime) written by PSP are out of specification (which is somehow tolerated by many other browsers and exifers).
What to say... I'll be more carefull in the future. Hope this info has value for you -so we don't blame LR for everything :-)
Bogdan

Further findings:
PSP actually doesn't delete Makernote data when saving jpeg image. Makernote data is written into exif, but (again) wrong way -so wrong, that even PSP itself isn't capable to read that data again :-)
Using Exiftool (great tool, but hard to use) I've discovered, that Makernote is somehow "displaced", hence can't be viewed. Exiftool is capable to "recover" Makernote -if everything else inside exif is in place.
Now: Do you get "Unknown Lens" in Lightroom's Metadata Browser? Look into Metadata-EXIF on right panel: if "Focal Length" is shown (but no "Lens" info), then that probably describe above issue. If so, then Makernote can probably be recovered. I've tried many tools, but AFAIK only Exiftool can do that.
And finally... suggestions:
1.Would be nice, if forum moderators (Adobe crew members) would have some sign besides their names.
2.Is there a list of "official recognized" Lightroom's bugs? If not, then would be good to have one -so members here wouldn't repeat the same compains again and again.
Greetings to all

Similar Messages

Date/Time, EXIF and Lightroom

I am quite aware of the past thread on the date/time issue started by Judy
Nicholls. But id did not help me to solve a mystery I am experiencing with a
bunch of jpegs made shot some years back.
Lightroom states that these files have no date - none is shown in the metadata
panel to the right, and they are selected in the metadata browser when selecting
"unknown date".
But several EXIF reader programs, including EXIFUtil, EXIFEditor and EXIF Pilot
clearly show me that the three relevant EXIF dates are there, are correct and
are identical. The EXIF header, the whole metadata section, seems to be complete
and readable outside LR. Oddly, EXIFER shows a date of "3--DEC-99" for Date
Taken in its file listing, but then shows the three relevant date entries
correctly and identically when doing an EXIF edit.
Why can't LR read these dates?
As a test, I tried to add the capture date through the menu (Metadata - Edit
Capture time ...), and it LR reacted to the added date by putting the file among
those with a known date (2003). But it did not change the EXIF data in the file,
apparently only a date in the LR database. I exported XMP to the file, read the
resulting data with EXIFUtil - but could not find any difference with the
original file!
Can anybody explain what is going on here?
Chris

Ok, here's what I've found:
If the "xmp" sidecar exists and you do "Read metadata from file", it will read the metadata from the "xmp" sidecar. If the "xmp" sidecar doesn't exist, then if you "Read metadata from file" it reads it from the image itself.
Thus, if you have an "xmp" sidecar file that exists and use an EXIF editor on the original image, the EXIF time change will *never* be imported again from the image file no matter how hard you try (ie: it will be ignored). If you remove the "xmp" sidecar, then you can get it to read the EXIF time data from the image. I don't think you have to "reimport" as some have done, but rather just delete the "xmp" sidecar.
However, and this is important, if you've already made Develop edits, those edits will be lost on the "Read metadata from file", import of EXIF data from the image.
If you think you'll be tricky and move out the "xmp" sidecar, edit the EXIF time data in the original image, import the metadata from the image, move back the "xmp" sidecar, and re-import the metadata and you'll get the best of both worlds, well no, you're SOL. The "xmp" sidecar date/time overrides the EXIF date/time previously imported.
So, I'll probably be stuck exporting my RAWs, then fixing the EXIF time data after the fact in the JPEGs since I've already made tons of edits across my 1,000+ photos for this batch.
Incidentally, iMatch by Photools can do a batched EXIF time correction by partial or full hour offset (or day) and Lightroom seems to be happy with the EXIF date format. iMatch is a pretty nice tool in of itself and probably better for general photo organization at least in the iteration of Lightroom (it is not a RAW converter though).
It can also do edits of XMP data, including with Visual Basic like scripted edits, so perhaps I can eak it out to do the fix that way (or re-export the fixed EXIF data into the XMP data without touching the rest of the Develop edit data also there).
Yuck!
Lightroom is a very nice app, but it's certainly still pretty "beta" in many respects.

Lightroom does not Recognize Capture Date

I have a lot of slides that I am scanning into Digital images.
The Nikon CoolScan does not include a capture date in the .jpg file so I add one using the ExifPilot program.
All other programs that I have tried correctly recognize this EXIF data, including Adobe Photoshop Elements. But the Lightroom does NOT recognize it and the file gets put into the library under "Unknown Date" Attempts to change the date with the Metadata/Edit Capture Time command do not work.
Any Ideas on what could fix the problem?

Yes, this is a problem, not only with files from scanner. I started a threat
called "Date/Time, Exif and Lightroom" on March 6 about that - have a look
there. Alas, no solution.

How can I display and use the full RAW file?

Hi,
my camera (Canon S95) has a sensor with 4:3 aspect ratio and thus saves all RAW files in this format. Additionally, the camera can automatically create JPGs with a cropped ratio (e.g. 3:2 or 16:9). This is very helpful because you can see the target format already on the camera screen (with black bars on top and bottom), which helps the composition. However, when processing the photos on the big screen afterwards, it often also helps the photo to adjust the ratio a little bit and therefore use the additional information saved in the bigger 4:3 RAW file. This works very well with many of the freely available software tools.
The problem found in Lightroom is now that it only shows the RAW photo in the cropped format and up to know I have found no way to display or use the full RAW format. So my question is: Which settings do I have to change to use the full format? What do I need to change?
Searching a little bit on the web I found many other photographes having the exactly same problem with many different cameras. However none of them reported to have a solution for this. Still I am pretty sure that there must be a solution, since otherwise this would be a really heavy bug within Lightroom and I cannot imagine that Adobe would leave this matter unsolved.
So I would really appreciate if someone could help me with this.
Many Thanks
Martin

Hi Jao, Victoria, Lee Jay,
Thanks for clearification. Do you have additional information about when this fix will be available and whether at least some popular old cameras will be supported?
What I do not get is why Adobe would need to redo all existing cameras. I think this is a more general issue, where Lightroom misinterpretes the exif data which includes both the exif image height/width as well as the cropped image height/width. Intepreting this information correctly, any software should be able to display both - the full image and the cropped area (as shown by many cheap or free software tools). In the internet I found another workaround for the issue in Lightroom, which is undermining this point: When setting the cropped image height/width to the numbers of exif image height/width manually (e.g. with exif tools), Lightroom actually is able to display the full 4:3 picture.
So this bug should be easily fixed for all cameras and I have no clue why Adobe still has no fixed it with Lightroom already available in version 4.2.
Cheers
Martin

Unknown Capture Date/Time

I have several dozen photos with either no capture date or something irregular that I concocted up (like "2012 Spring"). I notice that Lightroom assigns today's date and time to those photos when importing them. That means that I can't find them using the metadata "unknown date" filter. Is there any way I can get it to leave them alone, or just leave the date field blank? Thanks in advance!!

In the absence of specific camera exif data Lightroom will always work with the date created or modified e.g. the date scanned or the date of the last edit. You can edit or add metadata, but unfortunately it’s a manual process. See this help link.
http://help.adobe.com/en_US/lightroom/using/WS57264460-DC72-4a1f-A665-1E90907A9FFD.html
If you need the images in a fixed order for a project such as a slideshow or web gallery, its best to use a collection. The thumbnails can then be dragged around and will remain fixed in you chosen order.
http://blogs.adobe.com/jkost/2012/02/lr3-how-do-you-change-the-order-of-images-before-rena ming.html

Dates 1 hour off.

I just imported some photos from the last couple months, and I found that all of the timestamps are 1 hour off. I've seen the "Date/Time, EXIF and Lightroom" thread, but that seems to be addressing photos with missing timestamps, or photos there were modified by programs that rewrote the EXIF data incorrectly. The photos I'm having a problem with are CRW files straight from my Digital Rebel (300D) and have not been touched by any software. Other programs (ex: RawShooter) display the date correctly.
In that other thread, I saw a thread by "Judy Nicholls" being referenced, and maybe that thread has the solution, but for the life of me I can't find it (these forums have some of the poorest search functionality I've EVER seen).
Can anyone point me to a solution for this (other than manually adjusting all the dates by hand)?

Well, it appears to be a DST-related issue in general, but doesn't appear to be related to the recent DST change.
I'm looking back at the last couple years worth of photos (all of which were imported in Beta 3) and all the photos shot during standard time are showing off by an hour in Lightroom, whereas RawShooter and Photoshop CS2 are showing the correct time. On the other hand, any photos shot during DST are showing up correctly in all three programs.
So to reiterate, any photo shot during standard time (November-March)is showing off by 1 hour in lightroom, no matter whether that photo was imported in Beta 3 or the final 1.0 release. Photos shot during DST (April to October) are showing up correctly.

Meta Data Will Not Write! I've tried everything...

So, I love LR very much, except for the fact it WILL NOT write metadata. I've done numerous tests with Picasa, IrfanView, and other applications and while other applications successfully write to the IPTC header of the jpg or sidecar, I cannot get LR to write any of the metadata for the life of me. I've turned on and off the "Write XMP" checkbox in the options.
I've waited a substantial amount of time, then checked the file in a reader app and never see any kind of change to the file.
Why won't Lightroom write the metadata through to the file? It reads it in fine, but I cannot get it to update the file.
Thanks for your thoughts.

There's another issue here. Depending on what you're looking at it with, the programs cache. I was going crazy thinking they were not being written by looking with exifer and several other programs. Someone said try Bridge, which I'd never used, and voila, they were there. Bridge ALSO caches, but there is an option to empty the cache for this folder and you have to do that every time you want to check if Lightroom has written something. If you're on Windows, Microsoft Photo Info does display some metadata fields and does not have the caching problem.
In my case, I'm checking dates I'm writing in exifer for Lightroom, since Lightroom can't write capture and digitize dates.

EXIF: and TIFF: metadata is missing from XMP block in Lightroom 4

I've recently purchased Lightroom 4 and on the whole I'm very happy with it, but I have run into a problem. I have a few scripts which grab information from the XML-based XMP metadata block that's embedded in the DNG and JPG files that I use. I've found that images processed with Lightroom 4 no longer export the exif: and tiff: data.
To illustrate, a photo I exported with a previous version of Lightroom has the following data in the XMP block
   tiff:Make="Canon"
   tiff:Model="Canon EOS 40D"
   tiff:ImageWidth="850"
   tiff:ImageLength="567"
   tiff:XResolution="240/1"
   tiff:YResolution="240/1"
   tiff:ResolutionUnit="2"
   exif:ExifVersion="0221"
   exif:ExposureTime="1/800"
   exif:ShutterSpeedValue="9643856/1000000"
   exif:FNumber="71/10"
   exif:ApertureValue="5655638/1000000"
   exif:ExposureProgram="3"
   exif:DateTimeOriginal="2010-08-22T10:52:07.58+01:00"
   exif:DateTimeDigitized="2010-08-22T10:52:07.58+01:00"
   exif:ExposureBiasValue="0/1"
   exif:MaxApertureValue="4625/1000"
   exif:SubjectDistance="428/100"
   exif:MeteringMode="5"
   exif:FocalLength="80/1"
   exif:CustomRendered="0"
   exif:ExposureMode="0"
   exif:WhiteBalance="0"
   exif:SceneCaptureType="0"
   exif:FocalPlaneXResolution="3888000/876"
   exif:FocalPlaneYResolution="2592000/583"
   exif:FocalPlaneResolutionUnit="2"
   exif:PixelXDimension="850"
   exif:PixelYDimension="567"
There is, of course, a lot more information in the XMP block, but in a file exported using Lightroom 4 there is nothing in the XMP block with the exif: or tiff: namespaces so none of this information is available to any script which queries the XMP metadata. I'm pretty sure that the metadata is still there, embedded in the original EXIF data, as I can view it using the metadata panel in the Library module, but that's not accessible to my scripts as it's not in the XMP block. I've made doubly sure that the metadata has been saved and also double-checked all my settings and even tried to export the files multiple times with every different setting that I can think of (even though my current settings worked fine in previous versions) but the files never get the exif: or tiff: data.
I have called Adobe, but the best help they could give me so far was to post here and hope someone can help!

I just compared two JPEGs exported with LR 3.6 and LR 4.1RC. The tags you mentioned are exported neither by 4.1 nor by 3.6. These tags are only present in the normal Exif metadata, but not in XMP. Which version of LR 3.x did you use before? Perhaps Adobe changed something already in the later versions of LR 3.x. If this is the case, you have to use a script or tool that is able to read the Exif metadata directly.
In the XMP metadata in the file exported by LR 3.6, I see only crs (camera raw), aux (e.g. serial no.) and some other XMP namespaces, but no exif or tiff.
P.S. I viewed the metadata of the exported files with exiftool. File format was JPEG (with "quality" setting, not with "limit file size", because apparently there are still some XMP differences between these two modes).

Lightroom 4 Export - EXIF data missing

I noticed that the EXIF data did not seem to be included in the jpeg file resulting from EXPORT.
I have double checked to make sure that under the METADATA section to select "ALL" and have both boxes (Remove Location Info & Write Keyword as Lightroom Hierarchy) unchecked.
Doing the same export in Lightroom 3 has no problem to include EXIF data in the JPEG file.
I am running the MAC version of the released Lightroom 4. Thank you in advance.

Hi Dorin, thank you for your reply. After reading your reply, I went back and checked my jpeg files carefully. You are correct that all the EXIF metadata are there.
My statement of 'missing' EXIF data was based on my EXIF data did not show up after I uploaded my JPG files to pBase, while all still worked well with Lightroom 3. Uploading the same set of jpeg files to other photo site like Picasa, the EXIF information is all there. Also, when I import those jpeg files in Lightroom 4, t=all the EXIF metadat are there too. It implies that it is a problem with pBase having probelm reading the EXIF of jpeg file from Lightrrom 4. Not sure what is the difference in Lightroom preparing the jpeg files, but I believe this 'missing EXIF' problem is site specific (i.e. pBase).
I will modfify the Topis to show pBase problem only if I can. Thank you.

Lightroom strips very valuable EXIF data - details

Hey everyone - I've just been playing around with some EXIF stuff, and I noticed something very concerning.
I do a lot of macro photography, specifically with Canon's MP-E 65mm 1x-5x Macro. This lens records its macro magnification factor in the EXIF data, and does so far more accurately and conveniently than I can.
I know that Lightroom and Photoshop strip out A LOT of obscure EXIF data when processed, but this magnification data is extremely valuable when reviewing my photos at a later date.
I can provide sample files if needed, and here is my observations so far:
- data stays intact when converting from .CR2 to .DNG
- data is stripped when converting to JPG, TIFF, and other formats
- data is stripped by both Lightroom and Photoshop
Here is the EXIF data (from exiftool) right from the Canon CR2 or DNG file (both are identical):
http://don.komarechka.com/exif/exif-original.txt
Here is the EXIF data (from exiftool) from a jpg that has gone through Lightroom:
http://don.komarechka.com/exif/exif-lightroom.txt
You'll notice a HUGE amount of extra data in the original raw file. It is certainly worth noting that the EXIF data in a JPG, unaltered from the camera, contains all of the same data as the RAW file.
So, is this something that has been overlooked, is there any way to change this behaviour? Even though Lightroom might not be able to decode this data, I don't see a reason why it cannot be left intact.
Thank you.
- Don Komarechka
http://don.komarechka.com

donkom wrote:
clvrmnky, thanks for your response.
Here's an example for you, the one I've been giving:
I shoot with a special macro lensm the Canon MP-E 65mm f/2.8 1-5x Macro. This lens does not zoom, but the magnification can change from 1x to 5x.This lens communicates its magnification to one decimal point accuracy to the camera, which adds it to the maker notes.
This is important in reviewing images for a number of reasons, including calculating the effective aperture and depth fo field. This is a valuable piece of information that is stored within the makernotes that is removed from the image when sending it through LR, Photoshop, or ACR.
That isn't the only valuable information, however.
The makernotes will tell me if the image was captured using LiveView, if Mirror Lockup was used, if the shot is part of a bracketed set, what the internal camera temperature was, etc. etc.
I'm not sure you've justified your reasoning behind why this block of data shouldn't be blindly copied. If it is removed simply because it is not understood, I would like the option to understand this data on my own, using third-party tools, after the image has left LR.
I understand that this can be proprietary, but likely far less so than the RAW file formats that LR and ACR already understand. It would be trivial to understand where this block of data begins and ends and to leave it in the file on export.
I think this would allow for more in-depth searching based on metadata, for whoever wants to take up that torch. For example, what if I want to see all macro photos I took at a 4x magnification or higher. What if I want to see all photo I took using LiveView. Even if LR doesn't want to do this, stripping the data out prevents anyone else from doing it in the future.
Well, there is an SDK for metadata that has been around for awhile, which allows for custom metadata definitions. But, according to the SDK:
"Values stored in custom metadata fields are stored only in Lightroom's database. In the current release, a plug-in cannot link custom metadata fields to XMP values or save them with the image file."
So, this is more for searching and interfacing with tagset plugins.
Even so, using the SDK to get at maker notes is a losing proposition.
Note that some metadata is proprietary and will not be read into the database. This is to be expected. Lr is not an arbitrary metadata reading app, and there is no guarantee that any app could read all metadata. For example, Lr tries its best to get the serial number info, but this is because there is a lot of value in that for other Lr operations. So the contortions necessary to reliably get that is worth it. Another example is lens info (which is a twisty maze of passages; no app is ever guaranteed to actually retrieve lens info reliably in all cases) where there is a lot of value trying to extract the information that makers often store in very interesting ways. In some of those cases I think Lr will look in the maker notes, but only after exhausting other avenues, and with the caveat that it may never be able to get some information. The app does its best to get at the most valuable info it can get that fits with the standardized metadata models in place.
However, the key here is that maker note data is not in exported files that Lr makes, because it is not normalized data that belongs to the vendor. (This obviates the recommendation of using Metadata Wrangler, which can filter out only that metdata that exists in Lr; I had vaguely remembered a setting that referred to this section but was wrong.)
The field and data formats are not standardized, so you are asking Lr to understand most or all data from all or most lenses and bodies (all of it in varying degrees of similarity and difference) not just data from this lens and this body.
This is also not a trivial matter of "copying" the maker notes over, because copying implies parsing and duplicating what is essentially unknown formatted data containing proprietary data, possibly by custom serialization routines. Remember that maker notes were never intended to be editable, and could be composed of any number of data formats. Some cameras make maker notes that are megabytes of nulls and nothing else!
I think you are out of luck for this specific case. Perhaps with EXIF 3 we will have a more standardized interface cameras and software can more easily interoperate on shared data. Makers need to stop using the maker notes! It was always an egregious hack.
One workaround I can think of is to have a post-export action that uses EXIFTool to update exported images. For those cases where it matters, you could create your own "sidecar" file that has only the maker notes, and then shove those into the JPEG after they are created, or just read it from the on-disk copy and then put it in the new file (possibly in the same directory and added back into the catalogue for convenience.)

Lightroom strips out certain EXIF data (maker notes)

Hi there!
Simple issue: Lightroom and Camera Raw strip certain EXIF data that is extremely useful to macro photographers.
Use case: Canon macro photographer using the MP-E 65mm lens. The lens communicates its Macro Magnification value and this is passed to the camera which stores it in the maker notes. This data is extremely valuable to determine scale and measurements of photographed subjects.
This data is removed when the image is processed through any Adobe product.
Here's some supporting documents:
- RAW file from Canon 5D mark II: http://donkom.ca/lr4-makernotes/_MG_1848.CR2
- EXIF data (extracted via exiftool), please note the inclusion of "Macro Magnification" and the value "4.8x": http://donkom.ca/lr4-makernotes/_MG_1848.txt
- Processed JPG file from Canon 5D mark II through Lightroom 4 (all exif data selected to be included): http://donkom.ca/lr4-makernotes/_MG_1848-processed.jpg
- EXIF data (extracted via exiftool), please note the absense of "Macro Magnification": http://donkom.ca/lr4-makernotes/_MG_1848-processed.txt
Thanks very much,
- Don Komarechka
www.donkom.ca

Just checked this in the final release of LR4 and this issue has not been addressed. I'm hoping that someone has noticed this and can give it some attention!

Lightroom modifies EXIF after import?

When I import photos with Lightroom, they seem to loose part of the lens data that DxO uses to process images with. For example, a photo with the lens Nikon 12-24mm f/4 AF-S will just be 12-24mm afterwards, and DxO won't know which lens algorithm to do the processing with.
Is there something I'm missing, or does Lightroom always modify the EXIF like this?
TIA.

I'm importing as they are, either RAW (NEFs) or JPEG. I know Lightroom isn't supposed to touch the EXIF, but somehow the lens data gets missing or corrupted, and I'm wondering if theres a setting on Lightroom that does this? I notice the Lens info gets turned into the same as whats in the Lens tree in the Metadata Browser.

Lightroom 5 Exif "File Number"

I would like to rename my images to below format:
Foldername_DSCFileNumber_Year-Day-Month
so example name would be:
Test_DCS2342352_2012-12-12
Unfortunatelly lightroom cannot read the file number from EXIF.
Is there any way to do it without using any external software as renaming outside lightroom would screw my collections.
thx

blwegrzyn wrote:
so i modified:
I assume you modified the 'Exif Rename' preset (or a duplicate of it), that would be the closest to what you want.
Normally image number is available as:
exif['FileNumber']
If you want to see other choices, you can run Jeffrey Friedl's online metadata viewer here:
http://regex.info/exif.cgi
Anyway, the folder name is available like this:
local folderName = LrPathUtils.leafName( LrPathUtils.parent( photoPath ) )
If you need more help with FileRenamer, let's take it out of the forum via personal messaging, OK?
Rob

[Lightroom Mobile] Date in Exif info are not correct.

i'm use Lightroom Mobile in Bangkok, Thailand on iPad with Ratina Display.
Device Date&Time setting..
But, in Lightroom Mobile App. wrong to show year in exif data..
how i to fix this issue?
Thank You.

Thank for help me, Geoff the kiwi
i use LRM in Thailand. time zone UTC+7
i try to see exif info in another app. and all show correct.
i shoot this photo on 13 Oct 2013 (year in my time zone is 2556)
Light Room 5.2 (on PC)
iPhoto (on iPad)
Filterstorm Neue (on iPad)
Lab (on iPad)
all app show the year correct. but, LRM not!!
and i send original file to your PM. but i don't send tiger picture to you. because i lose it original file
thank again.

Corrupted EXIF data in photos exported from Lightroom CC

After upgrading to Lightroom CC EXIF can't be read by some apps. "Re-saving" a file in Photoshop fixes the problem. I'm using Mac OSX 10.9.5. Are there any plans to update and fix the EXIF data generated when exported from Lightroom CC?
Also, this command fixes the issue with Create Date part of EXIF.
#!/bin/sh
exiftool -AllDates="$(exiftool ${1} | grep 'Create Date' | awk '{print $(NF-1), $NF }')" -overwrite_original ${1}
The reason I'm asking is because we run a site where "Create Date" read from JPG's EXIF is crucial and it's a matter of letting users upload the pic or deny uploading.
So again, any plans on the fix?
Regards,
Pawel Kadysz

I confirmed that the Exiftool command line:
exiftool -m -all= -tagsfromfile @ -all:all -unsafe file.jpg
removes the ICC Profile, which could account for significant color differences, considering that the profile is Adobe RGB. I think this may be a bug in Exiftool, so I filed a bug report. (But it might be that Exiftool just can't handle the non-standard layout of LR's JPEGs.) The author is typically very responsive.
I tried some alternate Exiftool command lines that touch as little metadata as possible, and this one seems to address both of LR 6's JPEG problems:
exiftool -m '-exif:datetimeoriginal<exif:datetimeoriginal' -xmp-crs:all= file.jpg
The -m option ignores minor errors and issues, in particular, when there are more than 1000 entries in the XMP metadata.
The '-exif:datetimeoriginal<exif:datetimeoriginal' option sets the EXIF Date Time Original Field with its current value; this tricks Exiftool into rewriting just the EXIF metadata without touching the other metadata segments (e.g. the ICC profile), addressing the first JPEG problem. (You could use any EXIF field that's present -- I picked DateTimeOriginal since every camera adds that.)
The -xmp-crs:all= option option deletes all of LR's develop settings from the XMP metadata, addressing the second JPEG problem.That metadata is not ready by any programs other than LR, as far as I know.
I've tested this new command line on a couple of pics, including the example you provided above, and it appears to work correctly. But given that we're dealing with buggy output from LR that doesn't conform to the de facto and de jure standards, it's hard to have high confidence without testing on dozens if not hundreds of pics.

PSP XI & exif...to Lightroom

Similar Messages

Maybe you are looking for