martin_hirsch's profile

128 Messages

 • 

668 Points

Thu, Oct 22, 2020 6:18 PM

Horrible noise in Library Module

Pictures in Library Module has horrible noise if the picture has a little bit added noise.

This conversation has been merged. Please refer the main conversation:

Lightroom Classic image previews with grain are very very very bad

Responses

2.2K Messages

 • 

25.2K Points

7 m ago

Viewing at 1:1? 

Further, the only accurate way to view images is in Develop, again at 1:1 or greater. All other modules use a differing preview architecture.

Did you try rebuilding the previews and if not a fix, try cleaning out the ACR cache in Preferences. 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

128 Messages

 • 

668 Points

@andrew_rodney Not at 1:1. In full mode. Cleaning the cache or rebuild the previews doesn't work. Other collegues here have the same problem. It's only a problem if noise is addes in develop before.

 

2.2K Messages

 • 

25.2K Points

So you don't see it at 1:1 right? 

When images are zoomed out, in LR or Photoshop (anywhere), all the pixels are subsampled down for the zooming out of the image. You can often see moiré and, in this case, the increase in grain. Which is why the only accurate way to view the image is at 1:1 (100%) which means one image pixel for one display pixel. Or greater. Depending on image content, in this case grain, or in other cases a pattern, a zoomed out appearance can look ugly but it isn't in your actual data. This is just an artifact of the preview process. 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

128 Messages

 • 

668 Points

Sure. I know this. But normaly not so extrem. This is only since the last Version 10.0

128 Messages

 • 

668 Points

 The same picture in library mode in the old version

2.2K Messages

 • 

25.2K Points

What if you disable GPU in preferences?

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

128 Messages

 • 

668 Points

The same. Can you not comprehend this? Here is this the same on all PCs and MACs i have tested. 

(edited)

128 Messages

 • 

668 Points

The same. Can you not comprehend this? Here is always the same on all pc's an mac's i've tested

2.2K Messages

 • 

25.2K Points

7 m ago

Here is what I can comprehend: 

It's well know that Library and Develop previews don't always match and that the only accurate way to view your data is in Develop at 1:1. 

What I can comprehend and see is that in Library and Develop, at Fit and Fill, I do NOT see the same disconnect you show with images that have high ISO and thus grain. 

What I can comprehend is that perhaps, there is an issue on your end with previews (how they are built, your display etc). Because again, I comprehend by viewing the same images in the latest version of LR and earlier, they preview pretty much the same. 

Now you want to hunt down a fix for your issue or you're sure this issue affects everyone and thus, it's absolutely Adobe's fault? Maybe give us a better idea of your OS, version, display, video card etc, camera used, ISO, uploading a raw for others to examine etc. 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

128 Messages

 • 

668 Points

Ok, you don't try it. This picture is no High Iso. It's taken by ISO 200. I only added a little bit of grain in develop  mode. Try it and you will see it.

128 Messages

 • 

668 Points

A lot of people in a german Facebook Group for Lightroom has the same problem. And this is the same also: https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-classic-image-previews-with-grain-are-very-very-very-bad/5f90576d35f40c2520b9ea58

2.2K Messages

 • 

25.2K Points

I did try and NO I don't see it. 

You want help, find a fix or just complain? 

My core belief is that if you're complaining about something for more than three minutes, two minutes ago you should have done something about it.“ -Caitlin Moran

Want to do something about it? 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

Champion

 • 

2.4K Messages

 • 

38.7K Points

I reported this at the below link and it was discussed at length. The Library module interpolation for 1:3 and smaller Zoom previews was changed from bicubic to nearest neighbor. This is the cause of the artifacts the OP is seeing in LrC 10.0, but not in older versions. The Develop module uses bilinear interpolation, which produces a more accurate preview. 

https://feedback.photoshop.com/conversations/lightroom-classic/library-preview-zoom-interpolation-changed/5f5f462c4b561a3d4277ef23

2.2K Messages

 • 

25.2K Points

I reported this at the below link and it was discussed at length. The Library module interpolation for 1:3 and smaller Zoom previews was changed from bicubic to nearest neighbor. 

None the less, no, I can't produce this egregious difference in the two modules, after adding noise. I'm not alone. Yes, some are having issues. Is the goal here to rant or find what's going on and get it fixed IF it's solely an Adobe issue?

Here's Library vs. Develop on an image with grain; they are darn close and this is a 33% zoom:

This is the cause of the artifacts the OP is seeing in LrC 10.0

Then why isn't it seen above? 

IF the OP wants help, he now knows what kind of data to provide. If. 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

128 Messages

 • 

668 Points

Ok, thanks. Had hoped this was a bug but if this was a new feature, then this ist horrible for me and my work.

2.2K Messages

 • 

25.2K Points

The Library module interpolation for 1:3 and smaller Zoom previews was changed from bicubic to nearest neighbor. 

It appears Lightroom Classic 9.3 was changed and now creates its Zoom view previews using the inaccurate nearest neighbor interpolation

This is straight from Adobe engineering? 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

2.2K Messages

 • 

25.2K Points

7 m ago

Had hoped this was a bug but if this was a new feature, then this ist horrible for me and my work.

It isn't a feature and again, I cannot replicate this behavior. But yeah, if you want to believe it's a feature and everyone sees the same behavior you report, fine. Fact is, I can't and don't see it. It was never reported or discussed during pre-release so I'm not alone either. 

We might get to the bottom of why you and some others see this, but not without proper feedback and data. Your call. 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

Champion

 • 

2.4K Messages

 • 

38.7K Points

We might get to the bottom of why you and some others see this, but not without proper feedback and data. 

Andrew at the post where I reported this issue John Ellis mentioned he could not see the issue on his MacBook. So it appears this is a Windows 10 issue when 'Use GPU for display' is checked in LrC Preferences> Performance settings.

Had hoped this was a bug but if this was a new feature, then this ist horrible for me and my work.

I agree and suggest you add your Like, Follow, and Comments at the report.

128 Messages

 • 

668 Points

It's no matter if 'Use GPU for display' is activated or not. Both had the same result. And the problem occurs in 'filled' mode also.

OS: Windows 10 (latest)

GPU: NVidia Geforce GTX 1060

(edited)

2.2K Messages

 • 

25.2K Points

So it appears this is a Windows 10 issue when 'Use GPU for display' is checked 

But I asked the OP here to adjust the GPU and he reported no difference. And we don't yet know his OS.

And where did this change in interpolation algorithm you report come from?

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

Champion

 • 

2.4K Messages

 • 

38.7K Points

7 m ago

It's no matter if 'Use GPU for display' is activated or not. Both had the same result. And the problem occurs in 'filled' mode also.

After unchecking 'Use GPU for display' you need to close and reopen LrC for the change to take affect.

128 Messages

 • 

668 Points

I have done this for the test

2.2K Messages

 • 

25.2K Points

I have done this for the test

Then it is clearly not the GPU. 

Now can you tell us exactly what OSs (and versions of them) you've tested and better, can you upload a DNG with the edits baked in as well as the preview? Then others can load and test this under differing configurations and operating systems as well as versions of LR.

There's no need for anyone to speculate the cause, interpolation or otherwise but there is need to get to the bottom of the issue. What's quite clear is, it doesn't affect everyone. 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

Champion

 • 

2.4K Messages

 • 

38.7K Points

7 m ago

And where did this change in interpolation algorithm you report come from?

By intuitive reasoning after comparing images resized to 33% (i.e. 1:3) using nearest neighbor interpolation to the original raw file displayed at 1:3 Zoom. They exhibit identical artifacts.

Also as mentioned at the report, "I checked LR Classic 8.4 and Camera Raw 12.3 (most current) and they both appear to use bicubic or bilinear interpolation, which does not exhibit the artifacts seen with nearest neighbor interpolation.

2.2K Messages

 • 

25.2K Points

By intuitive reasoning after comparing images resized to 33% (i.e. 1:3) using nearest neighbor interpolation to the original raw file displayed at 1:3 Zoom. They exhibit identical artifacts.

That doesn't wash. Should we ask the Adobe engineers as you know we both can, so we both know the facts? 

Also as mentioned at the report, "I checked LR Classic 8.4 and Camera Raw 12.3 (most current) and they both appear to use bicubic or bilinear interpolation, which does not exhibit the artifacts seen with nearest neighbor interpolation.

This also sounds like speculation and it's easy for both of us to find out what's going on under the hood. I suggest one or both of us do so. 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

Champion

 • 

2.4K Messages

 • 

38.7K Points

7 m ago

This also sounds like speculation and it's easy for both of us to find out what's going on under the hood. I suggest one or both of us do so. 

Go for it and let us know what you find out. Whether it's an interpolation change that was implemented or a bug that was introduced LrC 8.4 does not exhibit the issue on the same Windows 10 platform using the same graphics driver. Either way it needs to be fixed. 

Whether the OP here is experiencing this issue or something else remains to be determined, but at least one other Windows 10 user at my report confirmed they can see the issue.

(edited)

2.2K Messages

 • 

25.2K Points

Go for it and let us know what you find out.

I suppose since you never did, but made such reports of a code-base preview, algorithm change, I will do so. 

In the meantime, maybe you can explain what you see below, a preview in LR5 and a preview in LR10, both in Library, both from updated previews in each application using different preview/lrdata, that indicates why you believe, without any data from the team, that the interpolation algorithm changed. Both are zoomed to 33%. 

And if you would rather examine the higher resolution TIFF, it's here:

http://digitaldog.net/files/LR5vsLR10Lib.tif

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

Champion

 • 

2.4K Messages

 • 

38.7K Points

Andrew, I already stated Mac systems do not have the issue. You're using a Mac system correct? Give it a try on a Windows 10 system!

2.2K Messages

 • 

25.2K Points

Andrew, I already stated Mac systems do not have the issue. You're using a Mac system correct? Give it a try on a Windows 10 system!

You are not making sense to me.

Yes I am on a Mac.

The OP has tried BOTH Mac and Windows and sees the issue.

The OP tried both with and without GPU.

Mac or Windows, what you reported about previews and interpolation algorithms is Unsubstantiated. 

So please explain to me what you are talking about.

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

Champion

 • 

2.4K Messages

 • 

38.7K Points

I suggest the OP export an image file with the issue to DNG file format and upload to Dropbox or other file sharing site. Then we can look at it on our systems for further troubleshooting.

The OP has tried BOTH Mac and Windows and sees the issue.

Here's what he said......I don't see Mac listed.

It's no matter if 'Use GPU for display' is activated or not. Both had the same result. And the problem occurs in 'filled' mode also.

 

OS: Windows 10 (latest)

GPU: NVidia Geforce GTX 1060

2.2K Messages

 • 

25.2K Points

Here's what he said......I don't see Mac listed.

He wrote this above:

Can you not comprehend this? Here is this the same on all PCs and MACs i have tested. 

Not that this has anything to do with preview interpolation algorithms. 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

128 Messages

 • 

668 Points

I don't use DNG. I'm just only working with RAW Files from my Canon Bodys (EOS R & EOS 5DIII) and with tiff after editing with photoshop

128 Messages

 • 

668 Points

I have only tested it on three Windows 10 PC's but the same issue was seen by two others photographers in our facebook group on her mac. 

2.2K Messages

 • 

25.2K Points

Martin, you can upload a proprietary raw and sidecar but just EXPORTING a DNG bakes all this and a JPEG preview into the DNG and makes testing easier. 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

Champion

 • 

2.4K Messages

 • 

38.7K Points

Use the Export module with the below settings to create the DNG file. As Andrew mentions it will contain all of your LrC edits.

128 Messages

 • 

668 Points

You mean a raw file with my LR settings?

128 Messages

 • 

668 Points

https://www.dropbox.com/sh/y6hzwf4ytexja41/AAAV5k4beT5dehZjNd7oC404a?dl=0

2.2K Messages

 • 

25.2K Points

If you upload a proprietary raw, the editing data is in an associated sidecar file. And if use a fixed/certain camera profile we need that too in order to exactly see on our end, what you see from your data and edits. This is why exporting a DNG as shown ensures all this is contained in one document to upload.

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

2.2K Messages

 • 

25.2K Points

OK good, got the DNG and I see ALL your edits which is necessary. 

First, when I import into LR10, I DO see a big difference as you describe, between Library and Develop at 33%. The preview in Develop looks very odd. But if I use the Update DNG Preview and Metadata command, and zoom in to 1:1 and back out to 33%, the odd preview goes away, and greatly matches Library. You can see the three screen captures below, it should be obvious which module since I kept some of the UI in the captures. The last is the screen shot AFTER this update of metadata and preview. 

Something is odd on your end, creating the previews used in Develop I believe because that preview, shown above looks pretty awful.

We can try to drill down farther but you might try converting to DNG, and trying the update command, maybe even on another machine, maybe a Mac. And I can upload your DNG after I did this update so you can see if you still see the odd preview in Develop. 

Develop after import:

Library Preview
 

Develop module after update of metadata and preview:

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

2.2K Messages

 • 

25.2K Points

Updated and resaved/exported DNG in my dropbox:

https://www.dropbox.com/s/weddz4uhkktto9p/Updated8G2A7866.dng?dl=0

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

2.2K Messages

 • 

25.2K Points

One more possibly interesting data point. I imported your DNG into LR5. It does NOT show up in B&W and one reason there could be a severe disconnect is in LR5, I see PV (Process Version) set for PV2012 in that old version. Makes sense, the newer PV didn't exist back then. But I also do NOT see the odd previews in Develop and the preview there and Library, although both in color, match very closely. Now both preview database files (LR5 vs. LR10) differ. But it is somewhat of an interesting find and maybe this will help Adobe if we can get them your DNG after you do more testing (perhaps in LR10, start from scratch but with an older PV?). 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

2.2K Messages

 • 

25.2K Points

When I open your DNG in ACR 13, I see the odd preview for a split second and then ACR updates and there is no weird preview. So try opening your DNG there too. 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

2.2K Messages

 • 

25.2K Points

7 m ago

I have only tested it on three Windows 10 PC's but the same issue was seen by two others photographers in our facebook group on her mac. 

Getting a DNG from one of the Mac users would help also.

(edited)

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

128 Messages

 • 

668 Points

7 m ago

The updatet dng in my LR (Library). There is no change

2.2K Messages

 • 

25.2K Points

The updatet dng in my LR (Library). There is no change

It's in color, so there's a change. Is this my DNG from my Dropbox? If so, something is really off on your system and I don't know what. We may need to get actual system info (you can do this under LR's "Help" menu, send your DNG and mine to Adobe. And do try opening both my DNG and your original in ACR; any difference? 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

2.2K Messages

 • 

25.2K Points

Do you agree based on what you see on your end, the preview in Develop is wrong? It looks awful on this end, massive noise clumps, but in Library, it looks as I'd expect and do see when I update the previews on a Mac. 

If you agree, that in Develop, that preview is what's off, I still have to wonder if this is an ACR cache issue. Lr will then go to the Camera Raw cache and find the corresponding cache file. If none exists it will render it out. The speed up comes from having the Camera Raw Cache version available. Once again, I'd try quitting LR, then find where your ACR cache is, delete it forcing LR to create a cache file again. If you still see an issue, that kind of points to the creating of this cache. 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

128 Messages

 • 

668 Points

Re-Import my own dng - this is also in color. The prewiew in develop ist ok. The Problem ist only the library in full mode.

Maybe the is the same problem like my other: https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-classic-bug-on-synchronizing-a-blackwhite-picture-from-a-raw-to-a-tiff/5f91cc3649d3ca75248bfac7

128 Messages

 • 

668 Points

Do you have any idea where to find the acr cache?

Edit: Found. But there is nothing. The folder ist complete empty

(edited)

128 Messages

 • 

668 Points

Wrong Folder. Sorry ;) LR stopped, cleared and restart. Preview in Library is the same. This ist changing if i zoom in and out. Seems ok. 

(edited)

2.2K Messages

 • 

25.2K Points

It's odd it's empty, it shouldn't be if you've processed raws in Develop. Which may be part of the issue but I don't know. Again, does the large clumps of 'noise' and that really blocking image I've captured in Develop appear correct to you? IT doesn't to me and further, when I update that preview, it looks like I'd expect from those noise settings and more importantly, matches very closely the preview in Library. 

Initially you said "Horrible noise in Library Module" is it possible that the horrible noise as I see it, is actually in Develop? The previews in the two modules are totally different, different data, stored differently etc. So first thing to uncover is, which is 'wrong' and where. Then we need system info from you. Then we could really use a DNG from Mac users reporting the same issue, ideally from your raw if possible. 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

128 Messages

 • 

668 Points

But it is no solution for me. Zoom in lasts a lot of seconds. I have tons of pictures.

2.2K Messages

 • 

25.2K Points

But it is no solution for me. Zoom in lasts a lot of seconds. I have tons of pictures.

What solution? I'm asking you to help trouble shoot the issue. I don't understand "Zoom in lasts a lot of seconds", can you explain? 

Again, is the preview in Develop, as I've shown in the screen capture PRIOR to an update what you consider correct? It looks really wrong and awful to me. 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

128 Messages

 • 

668 Points

I'm just talking about awful pictures in library mode. Sorry, but my english ist not so god

128 Messages

 • 

668 Points

Zoom in, needs 5 to 10 seconds the the picture will be better

2.2K Messages

 • 

25.2K Points

On this end, the image looks OK and as expected in Library and incorrect, ugly, blotching (like the top photo you provided in your first post) IN Develop. 

Are you saying you see the opposite? 

Again, because we need to be clear IF we move on. When I open your DNG, it looks pretty good in Library. It doesn't match Develop. In Develop module on this end, it looks like the VERY FIRST picture above of the boxer girl. But if I update the preview, it looks more like the 2nd picture above you posted of the boxer girl (far less noise). 

We need to know which is which. Which preview is 'wrong'. I suspect the wrong preview is in DEVELOP because on this end, when I update the preview, it changes and then looks like Library. Which is what I'd expect. If we try to fix this, or find the issue, we need to know which module is producing the incorrect preview. 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

128 Messages

 • 

668 Points

Changing the grain in your dng again leads to this awful view in library again

2.2K Messages

 • 

25.2K Points

Zoom in, needs 5 to 10 seconds the the picture will be better

OK, now we're getting somewhere. Zoom in looks better where, Library or Develop? 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

128 Messages

 • 

668 Points

Zoom in in library. I NEVER work in develop, except doing a setting. I always talking about library mode

128 Messages

 • 

668 Points

Library: Fit mode looks horrible, zoomin in takes 5-10 seconds, then it's ok

But only if i never change the grain. if i change the grain then it's the same agin.

Switching to develop from library without zoom in before, leads to an awful picture for one sedond, then it's ok. but switching then back to library (without changes) leads to the same awful pic

2.2K Messages

 • 

25.2K Points

Library: Fit mode looks horrible, zoomin in takes 5-10 seconds, then it's ok

Let's do this slowly, one step at a time. This behavior where zooming is slow, is this a NEW behavior or you always had to wait 5-10 seconds for it to look OK in Library. 

Switching to develop from library without zoom in before, leads to an awful picture for one sedond, then it's ok. 

Awful looking in Library; yes or no? Because above you say something about 5-10 seconds. You must zoom in to see the preview in either module correctly. 

I understand we may have a language barrier here. So I can't help unless we break down exactly what is happening and where. Maybe you and draft a step by step of where and what's happening, like:

1. Go into Develop at 33%, preview looks >>>>> (good, bad?)

2. Zoom in at 1:1, it takes XX seconds and looks >>>

3. Go to Library at XXX Zoom, preview looks>>>> 

Has ANYTHING above changed behavior from your first post here since you deleted the ACR cache? 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

128 Messages

 • 

668 Points

No changes after deleting the cache.

Can we restart please.

1. The picture in library looks horrible (Fit Mode)

2. Switching to Develop the pic is also horrible, but only for one second then it will be better (Fit Mode)

3. Switching back to library the pic ist horrible (Fit Mode)

4. Zoom in (Library) and the pic will be better after 5 to 10 seconds

5. Back to fit mode 

 

After this the pic will be alright in library or develop.

Changing the grain and the game starts again

Champion

 • 

2.4K Messages

 • 

38.7K Points

7 m ago

OK good, got the DNG and I see ALL your edits which is necessary. 

First, when I import into LR10, I DO see a big difference as you describe, between Library and Develop at 33%.

When I first import the DNG file and view it at Fit view the Library module is slightly noisier than the Develop module. If I set Zoom to 33% the Library and Develop modules look identical with the expected Grain setting. Even increasing Sharpening Amount to 100 does not reveal the interpolation issue I thought might be causing the issue. I tested a few other Canon EOS R CR3 files and they all exhibit the Library module interpolation artifacts at 33% Zoom view. So in short I can't duplicate what the OP is seeing (noise in Library module) on my Windows 10 system.

2.2K Messages

 • 

25.2K Points

 Even increasing Sharpening Amount to 100 does not reveal the interpolation issue I thought might be causing the issue. 

There is NO interpolation issue, please get past that concept. You've made this concept up in two differing posts, and there's zero proof that anything was changed, nor can I replicate this in LR10 down to LR5. 

There IS an issue with the OP's image/preview as seen on this end, but updating the preview, on this end, fixes that. Now why is he getting this wonky preview in the first place? Got nothing to do with interpolation; it's just totally incorrect in how it was initially created IN Develop. 

So in short I can't duplicate what the OP is seeing (noise in Library module) on my Windows 10 system.

And I CAN on Mac OS. So it's an issue but it's got zero to do with interpolation. The preview in Develop looks awful, incorrect and updating it on Mac IN Develop 'fixes' it and it then does very closely match Library; as expected. What's going on in Develop on the OP's side creating a preview? Let's concentrate on that, not some unproven, non issue with interpolation algorithms that no one from Adobe has ever stated exist. Please. 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

128 Messages

 • 

668 Points

I need a reasonable library picture for selection. It is not practicable if i have to switch to develop mode.

128 Messages

 • 

668 Points

I edit on picture an synchronize a lot of other to this. Then i go back to library for selection. That's may way for select my pictures.

128 Messages

 • 

668 Points

7 m ago

Interesting: Switching your DNG to monochrome, export it as a new dng and import this again, leads to a color picture :( I think there ist something wrong on my LR

2.2K Messages

 • 

25.2K Points

( I think there ist something wrong on my LR

Which is why I asked if you'd also examine Adobe Camera Raw....

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

128 Messages

 • 

668 Points

I don't know what ACR is. I only know the camera raw module in LR ans PS. I cannot find an application with this name in my cloud abo

(edited)

2.2K Messages

 • 

25.2K Points

Sorry: ACR is Adobe Camera Raw. Please also test in that Photoshop plugin and let us know what you see.

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

128 Messages

 • 

668 Points

Opening your DNG:

ACR shows me a awfully monochrome picture for one second, then it will be ok.

2.2K Messages

 • 

25.2K Points

ACR shows me a awfully monochrome picture for one second, then it will be ok.

And that's what I see too. But on Mac. 

I wonder if you might try creating a new catalog. Import one or a few of these raws, having that catalog rebuild new previews for both Develop and the other modules. Any improvement or the same issue? 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

128 Messages

 • 

668 Points

I've tested a new catalog. The picture (dng) in library is monochrome (not in color like the other) but also bad. 

2.2K Messages

 • 

25.2K Points

The picture (dng) in library is monochrome (not in color like the other) but also bad. 

Try one more thing; import the original raw, not the DNG into this new catalog. 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

128 Messages

 • 

668 Points

Done. If i use grain on this raw, it's the same like in the other catalog. 

(edited)

2.2K Messages

 • 

25.2K Points

but it seems the problem with the color/bnw is solved here

Solved how? Sorry I'm not sure what's now going on although I am happy to hear something is solved. 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

128 Messages

 • 

668 Points

Sorry, nothing is solved. My failure. It's all the same, except that LR opens the DNG monochrome and not colored like the other catalog

2.2K Messages

 • 

25.2K Points

So it is OK in Camera Raw after a second. If you apply a tiny edit in ACR, click ”Done” then examine the same raw in LR AFTER using the update metadata from disk (to update that new edit from ACR), how does it look; match ACR?

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

128 Messages

 • 

668 Points

Sorry, i don't know what you mean. If i save a raw in PS i have a tiff.

2.2K Messages

 • 

25.2K Points

Sorry, i don't know what you mean. If i save a raw in PS i have a tiff.

You could have a TIFF if you click Open, I don't want that, I want you to SAVE the edits from ACR using "Done" then examine the raw in LR after you ask it to update the metadata. 

See:

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

22 Messages

 • 

250 Points

7 m ago

I have the same problem.
In the library and in the develop module, the photo is terrible (as if too much grain).
I have a disconnected HDD disk (there are original photos on the disk).

I describe the problem here:

https://feedback.photoshop.com/conversations/lightroom-classic/poor-photo-in-the-library-and-develop-module-smart-previews/5f95f02a35f40c3a18c91af6?commentId=5f95f1aa72a09d5d5ced3a2a&replyId=5f96067c4833934b896f12d0