Lightroom/Camera Raw: Enhance Details causes cut out colored squares

  • 28
  • Problem
  • Updated 7 months ago
  • (Edited)
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)

Photo of Jordan Steele

Jordan Steele

  • 8 Posts
  • 0 Reply Likes

Posted 9 months ago

  • 28
Photo of Nathan Johnson

Nathan Johnson

  • 26 Posts
  • 22 Reply Likes
This problem was SOLVED for me by upgrading to Mojave (from High Sierra). Definitely worth it for me as I'm seeing  a massive improvement in the details from my Fuji X-T2! 
Photo of James Gilbert

James Gilbert

  • 2 Posts
  • 0 Reply Likes
I can't upgrade my iMac. It is too old for Mojave.
Photo of George

George

  • 16 Posts
  • 0 Reply Likes
Likewise, moving up to Mojave solved the problem.  However the DNG conversion takes about 4 minutes on my MAC Mini (late 2014).
Photo of Matt Angley

Matt Angley

  • 13 Posts
  • 7 Reply Likes
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.
Photo of John R. Ellis

John R. Ellis, Champion

  • 4562 Posts
  • 1221 Reply Likes
Please copy and paste all the lines from the menu command Help > System Info -- that will help troubleshoot the issue.
Photo of Janne Turunen

Janne Turunen

  • 3 Posts
  • 0 Reply Likes
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).
Photo of Janne Turunen

Janne Turunen

  • 3 Posts
  • 0 Reply Likes
Lightroom Classic version: 8.2 [ 1204643 ]License: Creative Cloud
Language setting: en
Operating system: Mac OS 10
Version: 10.13.6 [17G65]
Application architecture: x64
Logical processor count: 4
Processor speed: 3,1 GHz
Built-in memory: 12 288,0 MB
Real memory available to Lightroom: 12 288,0 MB
Real memory used by Lightroom: 1 493,6 MB (12,1%)
Virtual memory used by Lightroom: 3 115,8 MB
Memory cache size: 41,1MB
Internal Camera Raw version: 11.2 [ 134 ]
Maximum thread count used by Camera Raw: 3
Camera Raw SIMD optimization: SSE2,AVX
Camera Raw virtual memory: 234MB / 6143MB (3%)
Camera Raw real memory: 234MB / 12288MB (1%)
Displays: 1) 2560x1440

Graphics Processor Info: 
OpenGL: AMD Radeon HD 6970M OpenGL Engine

Check OpenGL support: Passed
Vendor: ATI Technologies Inc.
Version: 4.1 ATI-1.68.20
Renderer: AMD Radeon HD 6970M OpenGL Engine
LanguageVersion: 4.10
Total Video Memory: 1024 MB


Application folder: /Applications/Adobe Lightroom Classic CC
Library Path: /Users/dasurpha/Pictures/Lightroom Classic CC Catalog/Lightroom Classic CC Catalog.lrcat
Settings Folder: /Users/dasurpha/Library/Application Support/Adobe/Lightroom

Installed Plugins: 
1) AdobeStock
2) Aperture/iPhoto Importer Plug-in
3) Facebook
4) Flickr
5) Nikon Tether Plugin

Config.lua flags: None

AudioDeviceIOBlockSize: 512
AudioDeviceName: Built-in Output
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 44100
Build: 12.1x4
CoreImage: true
GL_ACCUM_ALPHA_BITS: 0
GL_ACCUM_BLUE_BITS: 0
GL_ACCUM_GREEN_BITS: 0
GL_ACCUM_RED_BITS: 0
GL_ALPHA_BITS: 8
GL_BLUE_BITS: 8
GL_DEPTH_BITS: 24
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_UNITS: 8
GL_MAX_VIEWPORT_DIMS: 16384,16384
GL_RED_BITS: 8
GL_RENDERER: AMD Radeon HD 6970M OpenGL Engine
GL_SHADING_LANGUAGE_VERSION: 1.20
GL_STENCIL_BITS: 8
GL_VENDOR: ATI Technologies Inc.
GL_VERSION: 2.1 ATI-1.68.20
OGLEnabled: true
GL_EXTENSIONS: GL_ARB_color_buffer_float GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_instanced_arrays GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_provoking_vertex GL_ARB_seamless_cube_map GL_ARB_shader_objects GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shadow GL_ARB_shadow_ambient GL_ARB_sync GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_non_power_of_two GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_transpose_matrix GL_ARB_vertex_array_bgra GL_ARB_vertex_blend GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_window_pos GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_clip_volume_hint GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_draw_buffers2 GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture_array GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc GL_EXT_texture_env_add GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_rectangle GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_timer_query GL_EXT_transform_feedback GL_EXT_vertex_array_bgra GL_APPLE_aux_depth_stencil GL_APPLE_client_storage GL_APPLE_element_array GL_APPLE_fence GL_APPLE_float_pixels GL_APPLE_flush_buffer_range GL_APPLE_flush_render GL_APPLE_object_purgeable GL_APPLE_packed_pixels GL_APPLE_pixel_buffer GL_APPLE_rgb_422 GL_APPLE_row_bytes GL_APPLE_specular_vector GL_APPLE_texture_range GL_APPLE_transform_hint GL_APPLE_vertex_array_object GL_APPLE_vertex_array_range GL_APPLE_vertex_point_size GL_APPLE_vertex_program_evaluators GL_APPLE_ycbcr_422 GL_ATI_blend_equation_separate GL_ATI_blend_weighted_minmax GL_ATI_separate_stencil GL_ATI_texture_compression_3dc GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_ATI_texture_mirror_once GL_IBM_rasterpos_clip GL_NV_blend_square GL_NV_conditional_render GL_NV_depth_clamp GL_NV_fog_distance GL_NV_light_max_exponent GL_NV_texgen_reflection GL_NV_texture_barrier GL_SGI_color_matrix GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod 
Photo of John R. Ellis

John R. Ellis, Champion

  • 4562 Posts
  • 1221 Reply Likes
A few people here have reported that upgrading to Mac OS 10.14 (Mojave) fixed this problem.
Photo of George

George

  • 16 Posts
  • 0 Reply Likes
Yes, updating to Mojave solved that problem. However on my Mac Mini (late 2014 with 16gb ram) it takes about 4 minutes to generate an enhanced DNG!
Photo of John R. Ellis

John R. Ellis, Champion

  • 4562 Posts
  • 1221 Reply Likes
"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.
Photo of Janne Turunen

Janne Turunen

  • 3 Posts
  • 0 Reply Likes
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).
Photo of John R. Ellis

John R. Ellis, Champion

  • 4562 Posts
  • 1221 Reply Likes
"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.
Photo of Matt Angley

Matt Angley

  • 13 Posts
  • 7 Reply Likes
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
Photo of Chris Kern

Chris Kern

  • 16 Posts
  • 3 Reply Likes
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.
Photo of Philipp

Philipp

  • 3 Posts
  • 1 Reply Like
I can confirm that it worked for me after upgrading to Mac OS 10.14 (Mojave), appareantly bringing some updates and improvements to the Apple machine learning framework necessary for this (as I understood it, correct me if I'm wrong).

BUT! Be aware that Apple cut it's support for a wide range of NVidia graphics card with the Mojave update. Although officially being 'unsupported' it has been possible before to use NVidia GPUs (e.g. in an upgraded Mac Pro 4,1 or 5,1), but after the Mojave update Apple seems to refuse to cooperate with NVidia to develop / update new drivers required, rendering NVidia cards useless. There is all sorts of complaints about this on the internet and it seems that this will be a permanent issue.

I was running a Mac flashed NVidia GTX 980 in my Mac Pro 5,1 and switched to a Sapphire RX 580 PULSE for around 200 €, which is fully supported by Apple. Everything works nicely again and performance is even a bit better but I still would have appreciated to spend the money on something else... ;)

https://support.apple.com/en-us/HT208898

(Edited)
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 6184 Posts
  • 1369 Reply Likes
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. 
Photo of Jordan Steele

Jordan Steele

  • 8 Posts
  • 0 Reply Likes
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.
(Edited)
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1673 Posts
  • 575 Reply Likes
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)
Photo of Nikita Zhukov

Nikita Zhukov

  • 1 Post
  • 0 Reply Likes
Thank you, Mr.Rikk Flohr, for this important news. Have immediately installed NVIDIA Creator Ready Driver version 419.67, - and, indeed, for me this solved the matter of color tiling in "Enhance Details". Just few extra words if you please: (a)  I will never understand why the company of Adobe calibre decided to release this half-baked feature to users in the first place. Believe that a couple of months ago this issue was as evident to Adobe as it became to the Lightroom users upon installation. (b) Just to tell you the truth, - while I have most highly appreciated that I no longer see these ugly color squares in my "_Enhanced.dng" photos, I have to honestly admit that I can hardly see much differences between my initial (big enough) RAW file and the resulting  ( h u g e ) _Enhanced.dng photo...  Looks like at the end of the day "the mountain gave birth to a mouse"... and the whole story probably wasn't worth all the mountain's labours...
Photo of RIchard Zimmerman

RIchard Zimmerman

  • 7 Posts
  • 0 Reply Likes

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


Any ideas how to fix this?  As to Mojave - I saw something that said it requires "Metal 2"  True? 
(Edited)
Photo of RIchard Zimmerman

RIchard Zimmerman

  • 7 Posts
  • 0 Reply Likes
An update - I disabled Use GPU in ACR, did enhance detail - took 5:36.  Then enabled the GPU, did enhance detail on the same image - took 5:36.  So, I conclude Adobe doesn't use my GPU at all.  No matter what the preferences are.   Major Bummer. 
Photo of John R. Ellis

John R. Ellis, Champion

  • 4562 Posts
  • 1221 Reply Likes
"So, I conclude Adobe doesn't use my GPU at all. "

Sounds like it.  You can easily verify that by starting Activity Monitor and doing the menu command Window > GPU History.
Photo of RIchard Zimmerman

RIchard Zimmerman

  • 7 Posts
  • 0 Reply Likes
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. 
Photo of John R. Ellis

John R. Ellis, Champion

  • 4562 Posts
  • 1221 Reply Likes
"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
Photo of RIchard Zimmerman

RIchard Zimmerman

  • 7 Posts
  • 0 Reply Likes
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. 
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1624 Posts
  • 540 Reply Likes
You would need to update to the latest macOS 10.14.4 to give a try. 
Photo of RIchard Zimmerman

RIchard Zimmerman

  • 7 Posts
  • 0 Reply Likes
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)
Photo of George

George

  • 16 Posts
  • 0 Reply Likes
when I used a Mac Mini (2014) I5proceesor with 16Mb ram it took 4 minutes to process and enhanced detail DNG file.
That same file processed on a MacBook Pro (2018) with a Radeon 560 GPU and 16Mb ram did the same in only 8 seconds!!
I am convinced that a fast GPU makes all the difference.  The folks at Lightroom recommend a dedicated GPU for this process.
george