Lightroom: 3.6 Metadata conflicts with TIF

  • 1
  • Problem
  • Updated 5 years ago
  • (Edited)
lightroom 3.6 on WinXP. After roundtripping to a plugin (eq, Silver Efex Pro 2 or Color Efex Pro 4), Lr flags the image as having meta data conflicts. I have tried to retry the export numerous times to no avail. Looking at the file properties I see no reason why this should be a problem (not Read-only, permissions good).
Two issues:
1) How to resolve the conflict
2) How to find all files which have conflicts

Thanks.
Photo of terry.doner

terry.doner

  • 1 Post
  • 0 Reply Likes

Posted 7 years ago

  • 1
Photo of john beardsworth

john beardsworth

  • 998 Posts
  • 219 Reply Likes
I have seen something similar. Have you got the very latest SFX? I think 2.002 resolved it. Also what Color Space is defined in LR's external editors for Nik? I seem to recall this was related to the problem.

As for 2, do you include any info in the filename to indicate it went through a Nik app? I always add SFX, for example.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 379 Reply Likes
1) Caused by incompatibility between apps writing file/metadata. If the latest versions of the apps still won't play nice together, and JB's other suggestions don't get it, then the only recourse I know of is to re-save the file using a more forgiving (can read metadata) and nicer (can re-write it how Lightroom likes) app, or use exiftool (requires considerable know-how).

2) If you are not adverse to plugin assistance, SQLiteroom will create a collection of photos having metadata conflicts upon startup, regardless of how those conflicts came to be...

Reminder to Adobe: please provide more information (e.g. better error messages...) to help people with these kinds of problems. And, some way to correct these kinds of problems in Lightroom might not be a bad idea.
Photo of thusband

thusband

  • 2 Posts
  • 0 Reply Likes
I'm having the same issue and use ProPhoto RGB. I changed to AdobeRGB (1998) and still had the problem. SFX version 2.003 didn't resolve it either. There's a version 2.003 out now but I have tried it. The release notes didn't mention the metadata conflict.

Using a work around doesn't seem workable. Isn't this a problem with either Adobe or NIK? There must be thousands of folks using this combination.
Photo of john beardsworth

john beardsworth

  • 998 Posts
  • 219 Reply Likes
Do you have Photshop? if so, Edit as Smart Object and then launch SFX. Apart from the advantages of a smart onject workflow, this avoids the problem.
Photo of thusband

thusband

  • 2 Posts
  • 0 Reply Likes
Right. I'll do that.

The other solution was to revert to 3.5 but I don't think I want to do that.

Thanks!
Photo of john beardsworth

john beardsworth

  • 998 Posts
  • 219 Reply Likes
The beauty of Lr to smart object to Sfx is that your Sfx adjustments are applied as smart filters. So they remain editable and you can also copy them to other smart object based files. The only downside is file size, but you have a much more flexible workflow.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4104 Posts
  • 1469 Reply Likes
Is anyone still seeing this between Color Efex and LR5? I've just had a report which sounds very similar, however the user said it was working in LR4.