Lightroom Classic: Many metadata fields in CR3 files not imported

  • 3
  • Problem
  • Updated 8 hours ago
  • In Progress
  • (Edited)
[Update: LR 7.3.1 doesn't import a number a metadata fields from .CR3 files that are read from other raw formats, including the GPS fields, XMP:Rating, XMP:Title, EXIF:ImageDescription, EXIF:UserComment.  See below for more details.

-- John Ellis] 



-----------------------------------------------------------------------------------------------------------

Dear community,

 

I own a new Canon EOS M50 and took a lot of GPS tagged pictures in my last holiday. Lightroom is importing the CR3 files without any problems, but I miss the GPS position. If I look to the files with the tool of Canon I see, that the position where the picture was taken, is inside of the file. Even if I export the pic to a jpg and import it then to Lightroom I have the position - but I like to have the raw file.

So far I found no way to display the position in combination with the CR3 file. I could put it in manually for each file, but therefor these are to many.

I already double-checked the import parameters and no preset was applied, so I guess this is obviously still an issue of the cr3 implementation in the camera raw module.



Here a link to an example file: https://1drv.ms/u/s!AtdqMJFRUFadgrYafe8Xh8oe1NJ5fg 




Maybe somebody has an idea or workaround... At least it should be known and be fixed in a future release.



Thanks and regards

Andreas
Photo of Andreas Morgenstern

Andreas Morgenstern

  • 2 Posts
  • 2 Reply Likes

Posted 4 weeks ago

  • 3
Photo of Smit Keniya

Smit Keniya, Employee

  • 164 Posts
  • 85 Reply Likes
Official Response
Hi,

I was able to reproduce Rating, Title, Description and UserComment not getting imported for CR3 files. Thanks again for the file. I have logged the bug for this.

Thanks,
Smit
(Edited)
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3298 Posts
  • 565 Reply Likes
Official Response
Lightroom Classic CC Version 7.4 was released earlier today and should have a fix for the GPS portion of this issue. Give it a try and let us know if you continue to see this problem. Thank you for your patience!
(Edited)