I was trying out the new Enhance Details function on Lightroom 8.2, and it is working well on some images, but on other images, it creates the new file, but totally messes it up by cutting out a square in one part of the image, and then other green, blue and magenta squares of the same size are placed randomly in other parts of the image.
This doesn't happen on all files (and it isn't consistent as to which files...two shots taken minutes apart with the same camera and lens, and one it won't process correctly, but the other it will. If it messes up on a file, it always messes up in the same way if you try again. It doesn't matter whether GPU processing is enabled or not.
Example showing the effect: http://www.jordansteele.com/2019/enhanced.jpg
System Info:
Lightroom Classic version: 8.2 [ 1204643 ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10 - Business Edition
Version: 10.0.17763
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 4.0 GHz
Built-in memory: 32726.0 MB
Real memory available to Lightroom: 32726.0 MB
Real memory used by Lightroom: 824.8 MB (2.5%)
Virtual memory used by Lightroom: 1044.2 MB
GDI objects count: 765
USER objects count: 2833
Process handles count: 1906
Memory cache size: 117.5MB
Internal Camera Raw version: 11.2 [ 134 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 158MB / 16363MB (0%)
Camera Raw real memory: 158MB / 32726MB (0%)
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 2560x1440, 2) 1920x1200
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No
Graphics Processor Info:
DirectX: NVIDIA GeForce RTX 2070 (25.21.14.1881)
This doesn't happen on all files (and it isn't consistent as to which files...two shots taken minutes apart with the same camera and lens, and one it won't process correctly, but the other it will. If it messes up on a file, it always messes up in the same way if you try again. It doesn't matter whether GPU processing is enabled or not.
Example showing the effect: http://www.jordansteele.com/2019/enhanced.jpg
System Info:
Lightroom Classic version: 8.2 [ 1204643 ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10 - Business Edition
Version: 10.0.17763
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 4.0 GHz
Built-in memory: 32726.0 MB
Real memory available to Lightroom: 32726.0 MB
Real memory used by Lightroom: 824.8 MB (2.5%)
Virtual memory used by Lightroom: 1044.2 MB
GDI objects count: 765
USER objects count: 2833
Process handles count: 1906
Memory cache size: 117.5MB
Internal Camera Raw version: 11.2 [ 134 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 158MB / 16363MB (0%)
Camera Raw real memory: 158MB / 32726MB (0%)
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 2560x1440, 2) 1920x1200
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No
Graphics Processor Info:
DirectX: NVIDIA GeForce RTX 2070 (25.21.14.1881)
Posted 10 months ago
This reply was created from a merged topic originally titled Lightroom Classic CC: Line artifacts in Enhance Details (merging).
That’s subtle by comparison of what I’m getting. Enhanced details takes about 10 minutes to process one photo and this is what I get as a result. I’m running the most current version of Mac (10.13.6) This update is a far cry from what Fuji shooters were expecting when we read it improves Fuji x-trans files and absolutely not what we should have to deal with. Really considering leaving for pretty much anything else. I’m getting tired of Adobe sitting in the corner eating glue while everyone else has figured out how to read and display Fuji RAF files flawlessly for years now
Note: This conversation was created from a reply on: Lightroom Classic CC: Line artifacts in Enhance Details.
That’s subtle by comparison of what I’m getting. Enhanced details takes about 10 minutes to process one photo and this is what I get as a result. I’m running the most current version of Mac (10.13.6) This update is a far cry from what Fuji shooters were expecting when we read it improves Fuji x-trans files and absolutely not what we should have to deal with. Really considering leaving for pretty much anything else. I’m getting tired of Adobe sitting in the corner eating glue while everyone else has figured out how to read and display Fuji RAF files flawlessly for years now
Note: This conversation was created from a reply on: Lightroom Classic CC: Line artifacts in Enhance Details.
John R. Ellis, Champion
Please copy and paste all the lines from the menu command Help > System Info -- that will help troubleshoot the issue.
I have almost exactly the same issue - about half of the picture is fine (and enhanced), half of the squares are black. Enabling/disabling GPU acceleration does not do anything (HD6970M acceleration is not supported by Lightroom anyways).
John R. Ellis, Champion
"It takes about 4 minutes to generate an enhanced DNG"
Most likely that's because Mac OS is using the CPU rather than your relatively older GPU (graphics processor) to do the machine-learning computations. You can verify in Activity Monitor by doing Window > GPU History.
Most likely that's because Mac OS is using the CPU rather than your relatively older GPU (graphics processor) to do the machine-learning computations. You can verify in Activity Monitor by doing Window > GPU History.
Unluckily Mojave is not available for iMac 2011 so that is not an option. I understand my iMac is dated and no longer fulfills the system requirements (no Metal support, which could well be the reason for the issue).
John R. Ellis, Champion
"no Metal support, which could well be the reason for the issue"
It seems that MacOS 10.13 has bugs in its machine-learning library (Core ML) that LR trips over, and these bugs are fixed in 10.14. I.e. the issue is unrelated to whether your hardware supports Metal.
It seems that MacOS 10.13 has bugs in its machine-learning library (Core ML) that LR trips over, and these bugs are fixed in 10.14. I.e. the issue is unrelated to whether your hardware supports Metal.
Yeah, I’ve had enough of Adobe’s s*** and decided to ditch Adobe all together. It shouldn’t be this complicated or frustrating to read and display a Fuji (in my case) RAF file correctly when multiple other softwares have had it figured out for years now. I shouldn’t have to use a special feature on every picture and wait 5 minutes for it to process just to get a useable image. This is absurd. Im moving over to Exposure X4. Adobe needs to stop eating glue and get their act together before they lose all their Fuji customers
It seems that MacOS 10.13 has bugs in its machine-learning library (Core ML) that LR trips over
Enhance Details works fine on my 2013 Mac Pro (AMD D500 GPUs) running MacOS 10.13.6. Processing times for Nikon NEFs and Fuji RAFs are between 10-20 seconds. The rendering quality of the X-Trans files is typically similar to that of Iridient Developer and Iridient X-Transformer.
Enhance Details works fine on my 2013 Mac Pro (AMD D500 GPUs) running MacOS 10.13.6. Processing times for Nikon NEFs and Fuji RAFs are between 10-20 seconds. The rendering quality of the X-Trans files is typically similar to that of Iridient Developer and Iridient X-Transformer.
Rikk Flohr, Official Rep
For those experiencing the color tiling issue in Enhanced Details who are using Nvidia RTX series cards, a new driver has been released.The driver version that has the fix is called 419.67 (this is the term that Nvidia uses on their web site). It was just released yesterday, 3/25. Please update your driver from the Nvidia site and let us know if you continue to have the issue afterwards.
Somewhat fixed and somewhat still problematic. Still have the issue with 419.67 Creator Ready Driver when viewing the file in Lightroom CC...but now when opening that same file in Photoshop CC, it renders properly.
RTX2070, Windows 10.
RTX2070, Windows 10.
(Edited)
Simon Chen, Principal Computer Scientist
Please follow https://helpx.adobe.com/lightroom/kb/lightroom-gpu-faq.html Solution #4 to do a CLEAN driver install. If you have put in place any workarounds previously, undo it (no forcing to OpenGL).
(Edited)
I updated my Mac Pro with a Sapphire Pulse Radeon RX 580 GPU. System Info reports: Metal: Supported, feature set macOS GPUFamily1 v3. The Geekbench performance is significantly better (*10) than the original card. I'm running 10.13.6.
Enhance Details still fails with colored squares all over the image. And it takes a long time - on the order of 3 or 4 minutes.
I have access to a 2017 iMac with a "Radeon Pro 580" graphics card. It's running 10.13.6 also. It's Geekbench score is slightly less than my Mac Pro now. Here's the deal, however. The iMac runs enhance detail in 30 seconds or so with no squares. (We can talk later about if I can a significant difference.)
One idea is CPU speed matters a lot. My Mac Pro is a 2.8 GHz Quad-Core Intel Xeon while the iMac is a 3.8Ghz Intel Core i5. Whatever the problem, I can't see that Lightroom or ACR are using the GPU at all. I have 'Use GPU' checked and Adobe "System Info" reports:
Graphics Processor Info:
Metal: AMD Radeon RX 580
(Edited)
Yes - that confirms the GPU is NOT being used.Here's what I'm seeing about the GPU under Help>System Info:
glgpu[0].GLVersion="2.1"glgpu[0].IsIntegratedGLGPU=0
glgpu[0].GLMemoryMB=8192
glgpu[0].GLName="AMD Radeon RX 580 OpenGL Engine"
glgpu[0].GLVendor="ATI Technologies Inc."
glgpu[0].GLVendorID=4098
glgpu[0].GLRectTextureSize=16384
glgpu[0].GLRenderer="AMD Radeon RX 580 OpenGL Engine"
glgpu[0].GLRendererID=16915464
Which seems to say they 'see' it, just refuse to use it.
glgpu[0].GLVersion="2.1"glgpu[0].IsIntegratedGLGPU=0
glgpu[0].GLMemoryMB=8192
glgpu[0].GLName="AMD Radeon RX 580 OpenGL Engine"
glgpu[0].GLVendor="ATI Technologies Inc."
glgpu[0].GLVendorID=4098
glgpu[0].GLRectTextureSize=16384
glgpu[0].GLRenderer="AMD Radeon RX 580 OpenGL Engine"
glgpu[0].GLRendererID=16915464
Which seems to say they 'see' it, just refuse to use it.
John R. Ellis, Champion
"Which seems to say they 'see' it, just refuse to use it."
This could be a Mac OS bug, not a LR bug. See this discussion:
https://forums.adobe.com/message/11012837#11012837
This could be a Mac OS bug, not a LR bug. See this discussion:
https://forums.adobe.com/message/11012837#11012837
Interesting. The bug is in Mojave but I'm running High Sierra. Two out of three machines I have access to - all running High Sierra - apparently have the bug but the third, an iMac doesn't. Entering the Twilight Zone here.
Simon Chen, Principal Computer Scientist
You would need to update to the latest macOS 10.14.4 to give a try.
I did update to 10.14.4. The convert time dropped to 24 seconds. Now I just need to be convinced it is actually better. So far, way to subtle for me. Curious about when to apply it - before sharpening, after?
(Edited)
James Gilbert
George