Skip to main content
S
simontruby
Participant
December 11, 2024
Question

Issues with blank Tags and Title column in windows for CR2 files processed by LRC

  • December 11, 2024
  • 2 replies
  • 395 views

Hi, I fairly new to LRC and still finding my way around.

I take photos on a phone and a Canon 80D.  The files are mixed together in a folder, and tagged and titled using Adobe Bridge.

I export the files to JPEG in LRC - the All Metadata setting is set, and the files are created successfully. 

When output JPEG files are viewed in Bridge or other products, the Tags and Title are present.  When viewed through Windows File Manager, these fields are only populated for the output files that originated from a phone based JPG.  All those that had a CR2 file as the input to the LRC export are missing this info both in the standard windows details view or if viewed individually using Properties>Details.

If I load one of the errant files into Photoshop and save it with the same filename, all fields are displayed for that file in Windows File Manager.

I can't work out if I'm doing something wrong, it's a Windows bug or an LRC bug.

Has anyone else come across this issue?

This topic has been closed for replies.

2 replies

johnrellis
johnrellis
Legend
December 11, 2024

The most efficient way to troubleshoot this is to provide sample JPEGs showing the issue. In particular, attach here a JPEG that has keywords and title showing in Bridge but not in Windows File Explorer. I'll put it under the microscope to see what might be going wrong and where.

S
simontrubyAuthor
Participant
December 18, 2024

Thanks for the response.
I’ve dug a bit deeper into this issue and it seems to be playing out as follows.
I follow a process to collect all photos I take either from phone or SLR together for post processing. After adding titles, tags and geotagging information, I add them into LrC using an import filter to make some changes to exposure etc.
Once that’s done, I then export everything to JPG or TIFF – it doesn’t matter in this instance as the issue occurs with both formats – I’ve stuck to JPG for this example.
The resulting files when viewed in Bridge have the correct information displaying in the correct fields, and when viewed through Windows File Manager (WFM) the same is true.
Following this, I take these files and use a product called BreezeBrowser Pro (BBP) to process all the output JPGs from the LrC export to add a bordered watermark that contains text from some of the aforementioned fields. It’s the JPGs coming out of this last process that are displaying the issues. These files with an original JPG file imported into LrC process fine and display correctly in both Bridge and WFM, and the watermark text is correct. The JPG files coming out of BBP that originated from a CR2 file input to LrC, display correctly in Bridge, contain the correct watermarks but have completely blank fields when displayed in WFM.
I’ve tested a couple of additional scenarios, as this used to work okay. If I take the JPG produced by LrC from an input CR2 and open and save it with Photoshop (or other products) BBP produces files that are okay and display everything correctly. I have also reverted through the existing versions of LrC. Following this process flow on any version of V14 produces the missing field displays. When I revert to V13.5 everything works fine.
The only thing that has changed is the version of LrC.

 

johnrellis
johnrellis
Legend
December 22, 2024

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]

 

The bug is in Windows File Manager. The two relevant files are:

 

LrC_v13_CR2-2-JPG_Export_(BBP-output).jpg

LrC_v14_CR2-2-JPG_Export_(BBP-output).jpg

 

File Manager doesn't show the keywords or rating for the v14 file, while LR 14.1.1, Mac Preview, and Exiftool (the most authoritative tool for examining metadata) all show those fields.

 

Further, Exiftool shows the metadata fields for the v13 and v14 files contain identical metadata, except for the expected differences in dates and software versions.  See the difference listing below.

 

Most likely, there is a subtle but standards-conforming difference in how LR 14 lays outs the metadata internally in the exported file compared to LR 13, causing BBP to output a slightly different but conforming layout of metadata, and that's tripping up File Manager. 

 

This isn't surprising. Windows File Manager, Mac Finder, and the two platforms' other apps for examining metadata aren't to be trusted. They have numerous glitches that have surfaced here over the years. LR, PS, and Bridge are much better, though not perfect. Exiftool is by far the most authoritative. The industry standards for photo metadata are a complicated legacy mess, and most developers and product managers don't have the patience to get it right.

 

* * *

 

Here are screenshots showing LR 14.1.1's Metadata panel, Mac Preview's Inspector panel, and File Manager's Properties window for the v13 and v14 files, followed by the listing of differences of the two files' metadata fields as displayed by Exiftool:

 

LrC_v13_CR2-2-JPG_Export_(BBP-output).jpg:

 

LrC_v14_CR2-2-JPG_Export_(BBP-output).jpg:

 

 

$ diff *.g1.txt
2c2
< [System] File Name : LrC_v13_CR2-2-JPG_Export_(BBP-output).jpg
---
> [System File Name : LrC_v14_CR2-2-JPG_Export_(BBP-output).jpg
5,7c5,7
< [System]  File Modification Date/Time : 2024:12:22 08:58:14-08:00
< [System]  File Access Date/Time       : 2024:12:22 09:11:06-08:00
< [System]  File Inode Change Date/Time : 2024:12:22 09:10:26-08:00
---
> [System]  File Modification Date/Time : 2024:12:22 08:59:13-08:00
> [System]  File Access Date/Time       : 2024:12:22 09:29:09-08:00
> [System]  File Inode Change Date/Time : 2024:12:22 09:29:08-08:00
29,30c29,30
< [IFD0] Software    : Adobe Photoshop Lightroom Classic 13.5.1 (Windows)
< [IFD0] Modify Date : 2024:12:18 09:11:52
---
> [IFD0] Software    : Adobe Photoshop Lightroom Classic 14.1.1 (Windows)
> [IFD0] Modify Date : 2024:12:18 08:33:33
76,77c76,77
< [IFD1] Thumbnail Length : 14890
< [IFD1] Thumbnail Image  : (Binary data 14890 bytes, use -b option to extract)
---
> [IFD1] Thumbnail Length : 14894
> [IFD1] Thumbnail Image  : (Binary data 14894 bytes, use -b option to extract)
102,103c102,103
< [XMP-xmp] Metadata Date : 2024:12:18 09:11:52Z
< [XMP-xmp] Modify Date   : 2024:12:18 09:11:52Z
---
> [XMP-xmp] Metadata Date : 2024:12:18 08:33:33Z
> [XMP-xmp] Modify Date   : 2024:12:18 08:33:33Z
105c105
< [XMP-xmp] Creator Tool : Adobe Photoshop Lightroom Classic 13.5.1 (Windows)
---
> [XMP-xmp] Creator Tool : Adobe Photoshop Lightroom Classic 14.1.1 (Windows)
111c111
< [XMP-crs] Version : 16.5
---
> [XMP-crs] Version : 17.1
233a234
> [XMP-crs] Look Copyright : ? 2018 Adobe Systems, Inc.
235c236
< [XMP-crs] Look Parameters Version : 16.5
---
> [XMP-crs] Look Parameters Version : 17.1
290c291
< [Composite] Modify Date : 2024:12:18 09:11:52+00:00
---
> [Composite] Modify Date : 2024:12:18 08:33:33+00:00

 

 

 

 

 

 

 

    S
    simontrubyAuthor
    Participant
    December 11, 2024

    Update to the above - checked back on a load of files I ran through this process a few months back and all okay - would suggest this is an issue introduced with the latest update in Oct ?

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices