Welcome Dialog

Welcome to the Community!

We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.


P: Spot Removal Brush Render Glitch When Converted to Compressed DNG

0 Votes
New Here ,
Mar 02, 2021 Mar 02, 2021

Copy link to clipboard

Copied

I am consistently finding all spot removal adjustments rendered as pink block artifacts after converting to compressed DNG. I am using LR Classic 10.1.1 on a 2017 15 inch MacBook Pro running macOS Catalina 10.15.7. I've seen the problem with a Canon R5 (raw and c-raw), Canon 5DmkIII, and Fuji X-T3 (RAF). The artifacts don't immediately appear - only when rendering 1:1 - so they are easy to overlook. I can remove the artifacts by modifying each spot removal adjustment in some way (often I'll just select an adjustment and nudge the feather slider up and down by one so the adjustment isn't affected). Also, there doesn't seem to be a problem when adding spot removal adjustments to images after they are converted to compressed DNG. Not sure how long this problem has been around - I've just discovered it when testing compressed DNG as a possible way to manage file sizes from the R5. Here are screenshots showing the original raw, compressed DNG, and exported PSD...

 

ScreenShot20210302at10.41.04AM-af527e27-1407-4254-a635-7b5456463afc-550570952.pngScreenShot20210302at10.41.04AM-af527e27-1407-4254-a635-7b5456463afc-550570952.png
 
ScreenShot20210302at10.41.57AM-d15e384b-e048-459d-9f9c-cc9cb20efd06-957768218.pngScreenShot20210302at10.41.57AM-d15e384b-e048-459d-9f9c-cc9cb20efd06-957768218.png
ScreenShot20210302at10.59.47AM-b9b434ca-a31c-4d37-92d9-b225af63868f-1774670656.pngScreenShot20210302at10.59.47AM-b9b434ca-a31c-4d37-92d9-b225af63868f-1774670656.png
 
Bug Investigating
TOPICS
macOS, Windows

Views

32

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Mar 03, 2021 Mar 03, 2021
I've logged this bug with the Classic team. Thanks for the reports.

Votes

Translate

Translate
16 Comments
Adobe Employee ,
Mar 02, 2021 Mar 02, 2021

Copy link to clipboard

Copied

Do you see the same rendering artifacts in Adobe Camera Raw?

Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Mar 02, 2021 Mar 02, 2021

Copy link to clipboard

Copied

Interestingly, no. I just opened the same DNG in Photoshop via Camera Raw and do not see the artifact... it only renders in LR.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Mar 02, 2021 Mar 02, 2021

Copy link to clipboard

Copied

That is curious. Do you see the artifact in Lightroom Classic with the GPU disabled?

Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Mar 02, 2021 Mar 02, 2021

Copy link to clipboard

Copied

I turned off GPU acceleration and at first the artifact remained even when I navigated to other photos and back (also switching between library and develop modules). After quitting and relaunching LR I initially saw the artifact but it went away when I switched from Library to Develop - and the artifact no longer renders in an exported PSD.

However... (there's always a 'however', right?) with the GPU sill off I went back to a copy of my original CR3, added a spot removal, and converted to compressed DNG. The artifact is in this new file.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Mar 02, 2021 Mar 02, 2021

Copy link to clipboard

Copied

Sorry for the rapid-fire responses. I may have been too quick to reply the last time. With further poking around, turning the GPU acceleration off does not seem to reliably correct the artifact. Not sure what I did before, but I have another file where the artifact persists regardless of GPU setting. 

Thanks for your attention on this.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Mar 02, 2021 Mar 02, 2021

Copy link to clipboard

Copied

Can you walk me through, step by step, how to create the issue on an image which currently doesn't exhibit the problem?

  1.  
  2.  
  3.  
  4.  
  5.  
  6.  
  7.  
Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Mar 02, 2021 Mar 02, 2021

Copy link to clipboard

Copied

Sure, no problem.

1. Select any raw image.

2. Add at least one spot removal adjustment.

3. Convert the file to  DNG (using the Library -> Convert Photo to DNG... menu item in the Library module) with the "Use Lossy Compression" option selected.

4. If the artifact doesn't immediately appear, view image at 100%, making sure to wait for the preview to fully render.

Hope this helps. I've been able to reproduce this on three computers using images from multiple cameras.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Mar 02, 2021 Mar 02, 2021

Copy link to clipboard

Copied

I can duplicate the pink square issue with your recipe .  I see it in Library Loupe and the thumbnail in Grid and on the filmstrip in ALL the modules.  

Canon 5dMk3.  MacOS 10.15.7

Photo of blue sky for sensor test.

ScreenShot20210302at11.53.15AM-048efddb-f521-431b-8848-f5ad3fa0f6e6-697497888.jpg

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Mar 02, 2021 Mar 02, 2021

Copy link to clipboard

Copied

Thanks - I appreciate the confirmation

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Mar 02, 2021 Mar 02, 2021

Copy link to clipboard

Copied

I can confirm the same on my Windows machine. Like Bob, both in library Loupe and Grid

Screenshot20210302192355-c1408c9b-e2f5-4380-b784-c9af479bfeee-762514812.jpg

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Mar 02, 2021 Mar 02, 2021

Copy link to clipboard

Copied

I never use compressed DNG as there have been several threads of issues with it from past forum threads including this issue. 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Mar 02, 2021 Mar 02, 2021

Copy link to clipboard

Copied

That's good to know. I've been extensively using DNG in our workflow for years with no issues. As I mentioned, I've been trying out the compressed option to lessen the impact of our new R5. Fortunately we do have a huge storage upgrade for our servers being provisioned to roll out in the next few weeks - so if, as you say, compressed DNG is generally problematic I may just stick with the old reliable non-compressed option.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Mar 02, 2021 Mar 02, 2021

Copy link to clipboard

Copied

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Mar 02, 2021 Mar 02, 2021

Copy link to clipboard

Copied

Wow, definitely the same issue and some in-depth info. I did search before posting to see if my problem had been discussed already but failed to find these conversations. I'll be doing some reading this evening.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Mar 02, 2021 Mar 02, 2021

Copy link to clipboard

Copied

I can also replicate this issue on my Windows 10 machine after converting to lossy DNG from a NEF raw file.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Mar 03, 2021 Mar 03, 2021

Copy link to clipboard

Copied

LATEST

I've logged this bug with the Classic team. Thanks for the reports.

Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines