Lightroom Classic 7.4: Smart Previews White Balance turns turns image very greenish

  • 3
  • Problem
  • Updated 1 week ago
  • Acknowledged
  • (Edited)
When setting the WB of a smart preview (original placed in an external HDD and disconnected), the photo turns turns very greenish.

I have been able to reproduce for Sony A7III raw files with 2 specific lenses (with a different lens it works fine):
- Sigma 50mm F1.4 DG HSM Art 018.
- Sony FE 25-105mm F4 G OSS.

Steps:
1. Import Standard + Smart Previews.
2. Place original in external HDD.
3. Disconnect HDD.
4. Select photo and develop.
5. Set the WB (from menu or modify any slider).
6. It turns very greenish.
7. If the HDD is connected back, the photo turns OK.

Versión de Lightroom Classic: 7.4 [ 1176617 ]Licencia: Creative Cloud
Configuración de idioma: es-ES
Sistema operativo: Mac OS 10
Versión: 10.13.6 [17G65]
Arquitectura de la aplicación: x64
Cantidad de procesadores lógicos: 8
Velocidad del procesador: 2,9 GHz
Memoria incorporada: 16.384,0 MB
Memoria real disponible para Lightroom: 16.384,0 MB
Memoria real usada por Lightroom: 3.073,5 MB (18,7%)
Memoria virtual usada por Lightroom: 6.872,2 MB
Tamaño de memoria de caché: 1.483,9MB
Revisión interna de Camera Raw: 976
Número máximo de subprocesos que usa Camera Raw: 5
Optimización de SIMD de Raw de cámara: SSE2,AVX,AVX2
Memoria virtual de Camera Raw: 458MB / 8191MB (5%)
Memoria real de Camera Raw: 482MB / 16384MB (2%)
Pantallas: 1) 3840x2400

Información de procesador gráfico: 
Metal: AMD Radeon Pro 560



Carpeta de la aplicación: /Applications/Adobe Lightroom Classic CC
Ruta de la biblioteca: /Users/mpovedano/Pictures/Lightroom/Lightroom Catalog.lrcat
Carpeta de ajustes: /Users/mpovedano/Library/Application Support/Adobe/Lightroom

Plugins instalados: 
1)  Plug-in de conexión al equipo de Nikon
2) Adobe Stock
3) Facebook
4) Flickr
5) Plugin de conexión al equipo de Canon
6) Plugin importador de Aperture/iPhoto

Indicadores config.lua: None

AudioDeviceIOBlockSize: 512
AudioDeviceName: Salida integrada
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 44100
Build: 10.0x7
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 Pro 560 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_depth_bounds_test 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 
 
Photo of Miguel Povedano

Miguel Povedano

  • 17 Posts
  • 1 Reply Like

Posted 4 months ago

  • 3
Photo of Just Shot Me

Just Shot Me

  • 227 Posts
  • 59 Reply Likes
How why are you setting, changing, the WB?
Photo of Miguel Povedano

Miguel Povedano

  • 17 Posts
  • 1 Reply Like
It is my workflow. I keep it auto in camera, shot in raw and change it if necessary through the WB settings in the develop panel
Photo of Todd Shaner

Todd Shaner, Champion

  • 1113 Posts
  • 360 Reply Likes
I was able to reproduce a similar issue after removing the raw files and switching back to the Library module. Clearly something is wrong with the Smart Previews. I suggest posting one of your raw file that exhibits the issue in the Develop module to Dropbox or other file sharing site for confirmation.

Photo of Miguel Povedano

Miguel Povedano

  • 17 Posts
  • 1 Reply Like

Hi, Todd.

Thanks for your help. That is exactly what I get. I will upload a raw file (14 bit - uncompressed) later on today.

Whenever the WB is changed, the image turns that color. If you undo (Cmd-Z) or reconnect the HDD, it looks back OK.

Moreover, I have realized that in some files the bug arises just when you change to the develop module. In this case, some greenish squares/rectangles overlap the image, not the complete image (it depends on the image: in some it is a big strip, in other a big square,...). In the same way, whenever the original raw file is reconnected, the issue disappears.

BR, 
Miguel

Photo of Todd Shaner

Todd Shaner, Champion

  • 1113 Posts
  • 360 Reply Likes
The 2nd issue sounds like a graphics driver issue (greenishsquares/rectangles overlap the image). In LR go to menu Edit> Preferences> Performance and uncheck 'Use Graphics Processor.' In fact both issues may be due to an incompatible graphics driver. After rebooting my system this morning I can no longer duplicate the issue with the same file I used yesterday. It will be interesting to see if I can duplicate the issue with one of your files.
Photo of Miguel Povedano

Miguel Povedano

  • 17 Posts
  • 1 Reply Like

Hi, Todd.

I will upload an original once I am back in my studio later today (this is why I use to work with smart previews and love this feature...).

Thought it was the GPU too. I tried disabling it, but same result.

Moreover, if you close the program and launch it again, sometimes solves it, but temporarily. Sonner or later you will experience it again.

And it never happens when working with the original. If you have a greenish square, rectangle,... or even the complete photo and you reconnect the external HDD with the original, the issue automatically disappears.

BR,
Miguel
Photo of Sunil Bhaskaran

Sunil Bhaskaran, Official Rep

  • 349 Posts
  • 121 Reply Likes
Miguel,
I have contacted you through an email for one of the raw files where you find the issue.

Thanks,
Sunil
Photo of Miguel Povedano

Miguel Povedano

  • 17 Posts
  • 1 Reply Like
Todd, Sunil,

Please, you may download a couple of samples form de following link: https://www.dropbox.com/sh/44kuc6pfe7mxahv/AAD7rx08e5EDHme_-wMSlD51a?dl=0

I have aso included screen captures (.pnf files) of the issue.

Once dowloaded, please let me know to delete them.

As said, whenever I reconnect the external HDD with the originals, the photo turns OK automatically.

Again, many thanks for your help.

BR,
Miguel
Photo of Todd Shaner

Todd Shaner, Champion

  • 1103 Posts
  • 357 Reply Likes
I was able to duplicate the issue with one of the files (DSC3440.ARW). The green tint appears in the Library module, but not the Develop module. It appears you are using a Mac system. What OS X version? I'm on Windows 7 SP1, which may explain the difference in the symptoms.  I had to change the Camera Profile to 'Adobe Standard' and WB setting to 'Daylight' to trigger the green color shift. When I clicked on the Develop Reset and reentered the same settings the green shift would no longer appear. Whatever is causing this issue it's difficult to duplicate at least on Windows 7.

Regardless of these differences the issue appears on both platforms and needs to be investigated by Adobe Engineering.
Photo of Miguel Povedano

Miguel Povedano

  • 17 Posts
  • 1 Reply Like
Many thanks for your feedback, Todd.

MacOS 10.13.6.

BR,
M
Photo of Sunil Bhaskaran

Sunil Bhaskaran, Official Rep

  • 346 Posts
  • 117 Reply Likes
Hi, Miguel.

We have downloaded the images. Thanks for it.

Thanks,
Sunil
Photo of Miguel Povedano

Miguel Povedano

  • 17 Posts
  • 1 Reply Like
Thanks to you, Sunil.

I have just deleted them.

Anything else, let me know.

BR,
M
Photo of Todd Shaner

Todd Shaner, Champion

  • 1103 Posts
  • 357 Reply Likes
Thank you Sunil.
Photo of Miguel Povedano

Miguel Povedano

  • 17 Posts
  • 1 Reply Like
Hi, Sunil.

I believe a Lr Classic update has been released today. Does it address this issue?

Many thanks,
Miguel
Photo of Miguel Povedano

Miguel Povedano

  • 17 Posts
  • 1 Reply Like
Made some tests today. It has not been solved yet.

With the experience I would say it affects to high ISO and high contrast photos mainly.

BR,
M



Photo of Todd Shaner

Todd Shaner, Champion

  • 1113 Posts
  • 360 Reply Likes
Miguel, there is no mention of this issue being fixed in the LR 7.5 Release Notes. I've changed the status of this report to 'Acknowledged' so hopefully it will get some attention.

https://helpx.adobe.com/lightroom/help/whats-new.html
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 4286 Posts
  • 816 Reply Likes
The bug is still open in our system. 
Photo of Todd Shaner

Todd Shaner, Champion

  • 1113 Posts
  • 360 Reply Likes
Thanks for the update Rikk!
Photo of Miguel Povedano

Miguel Povedano

  • 17 Posts
  • 1 Reply Like
Many thanks you all.

BR,
Miguel
Photo of Katie Phillips

Katie Phillips

  • 5 Posts
  • 2 Reply Likes
This issue started happening to me in June and has been very frustrating. I am a professional editor and clients send me their pictures to edit through smart previews. It is embarrassing and makes my job almost impossible. Any help with this would be greatly appreciated!
Photo of Katie Phillips

Katie Phillips

  • 5 Posts
  • 2 Reply Likes
Hi again. Like I mentioned before this has been an everyday issue for me so I have done lots of trial and error testing. I think I finally figured out where the bug is! 

I figured out that the smart previews didn't corrupt when I used my old (2011) computer. So I tried to figure out why. I cleared my normal computer (twice) and it still happened. I used a computer similar to mine, still happened. I used a newer computer than mine, still happened. I used parallels to use an older version of the computer software on my current computer, still happened. I tried to think of the other differences between my old computer and the other computers I have tried besides the software. Someone mentioned the screen resolution to me. I have retina on my current computers and all of the others ones I tried. So I turned down the resolution of my computer screen on my current computer and no previews have corrupted! 

So it is kind of crazy, but I am pretty sure it has to do with computer screen resolution communicating with smart previews. I would love if that bug could be fixed so I could edit using higher resolution. Hopefully this can help the bug getting fixed!

Photo of Miguel Povedano

Miguel Povedano

  • 17 Posts
  • 1 Reply Like
Hi, Katie.

I believe Adobe has just launched an update today. Have not been able to check if it address the bug (and Adobe has not listed the fixed ones yet)

BR,
Mguel
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 4286 Posts
  • 816 Reply Likes
This issue is still active in our system.
Photo of Miguel Povedano

Miguel Povedano

  • 17 Posts
  • 1 Reply Like
Hi, Rikk.

With the update it is getting even worse.

I understand there are priorities and that it might be not that easy to solve it. However, is there a timeline to fix it?

This bug is not just irritating. It affects our complete workflow.

Thanks,
Miguel


Photo of Andy Baker

Andy Baker

  • 3 Posts
  • 0 Reply Likes
I am also facing this problem. It should be at the top of the priority list for fixes as it seems more and more widespread and as others have mentioned, it's entirely debilitating. It's nearly impossible to work on my files without having to plug a cumbersome hard drive in in order for Lightroom to recognize the file and correct the horrific green cast. We're paying for this service so that we can use smart previews to edit remotely. This, for my needs, cuts the usability of Lightroom by at least 50%. Adobe needs to step up and fix this as it's entirely unacceptable. 
(Edited)
Photo of Rachel Guy-Whittle

Rachel Guy-Whittle

  • 1 Post
  • 0 Reply Likes
I have the same issue. I'm an image editor and it's really messing up my workflow. I had it on my older mid 2011 iMac and now my 2017 iMac. I never have it on my own personal files (Fuji full size RAW files) it only appears on certain clients SP lrcats. GPU on/off toggling makes no difference. I'm running the newest OSX  and the latest LR Classic update which was downloaded fresh as a daisy today and it's just happened again so looks like it's still an issue. I thought I was toggling something on and off without realising during busy season. I bet a few other users have assumed it'd something they are doing rather than a system bug.  
(Edited)
Photo of Andy Baker

Andy Baker

  • 3 Posts
  • 0 Reply Likes
Still waiting on a fix from this. I spent an hour with customer service who assured me that it would be fixed in the NEXT update. Today Lightroom Classic was updated...with no fix for the issue at hand. This is not acceptable. For all of us doing remote editing for other photographers who can't access the drive the original files are located on, this bug is preventing us from doing our job! It's so embarrassing to send back a catalog that looks broken to clients, all while explaining that it's absolutely out of our control. Adobe needs to be acting more swiftly to correct this error as it's got a monopoly on the editing game and this issue has been plaguing folks for over 4 months. PLEASE Adobe, PLEASE fix this debilitating issue. I demanded to be refunded for services that don't perform as intended and was credited for two months free, and I highly recommend everyone experiencing this issue does the same. Maybe once Adobe gets the message that it's customers are seriously unhappy they will move to solve the problem a bit quicker. 
Photo of Katie Phillips

Katie Phillips

  • 5 Posts
  • 2 Reply Likes
Have any of you tried lowering the resolution of your computer screen? I know it’s weird but doing that has solved my problem and has saved my sanity these last few weeks. I’m curious if it will help others as well because I know how awful this bug is. Hopefully they can fix it soon!
Photo of Miguel Povedano

Miguel Povedano

  • 17 Posts
  • 1 Reply Like
I tried, Katie. It didn't solve it in my case.

Thanks and BR,
Miguel
Photo of Katie Phillips

Katie Phillips

  • 5 Posts
  • 2 Reply Likes
I'm sorry it didn't work for you! Do you have a mac? Are you still in Retina even with the lower resolution? I downloaded "Display Menu" from the app store and made sure it is not on retina and 1440x900. I had the green issue daily for months and since I put it on that lower resolution it hasn't done it in 3 weeks. Once I accidentally got back on retina display and my files started corrupting immediately. So I am completely convinced it has worked for me. Sorry it didn't for you though!
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 4286 Posts
  • 816 Reply Likes
While the bug is still open in our system, we have as yet been unable to reproduce this behavior in-house with either, our own files or the files provided by Miguel to Sunil. If someone is willing to create a catalog containing one or two files that exhibit this issue and share the catalogs and accompanying Smart Previews with us, it would help us nail down the issue. 
Photo of Todd Shaner

Todd Shaner, Champion

  • 1113 Posts
  • 360 Reply Likes
Rikk, let me repeat what I did to reproduce the issue on my Windows 7 system.

The green tint appears in the Library module, but not the Develop module. It appears you are using a Mac system. What OS X version? I'm on Windows 7 SP1, which may explain the difference in the symptoms.  I had to change the Camera Profile to 'Adobe Standard' and WB setting to 'Daylight' to trigger the green color shift. When I clicked on the Develop Reset and reentered the same settings the green shift would no longer appear. Whatever is causing this issue it's difficult to duplicate at least on Windows 7.

With the original file removed and the Smart Preview present switch to the Develop module. Change the camera profile to Adobe Standard or Adobe Color and switch back to the Library module. If that doesn't cause the green tint switch back to the Develop module and change the WB setting to Daylight or As Shot. Switch back to the Library module and the green tint should appear. Once I click on the Develop Reset the green tint can not be replicated when changing camera profile or WB settings.
(Edited)
Photo of Miguel Povedano

Miguel Povedano

  • 17 Posts
  • 1 Reply Like
Library with a couple of samples, including smart previews, in the following link: https://www.dropbox.com/sh/5mbeer4otfdil1q/AAD5DO9MpGQGlJ6IwrJlLPdYa?dl=0

When downloaded, please, let me know.

Also attaching a screen shot of what I see.

BR,
Miguel

Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 4243 Posts
  • 808 Reply Likes
Thanks for the test files. I have pulled them down and attached them to the bug report so the team can attempt to replicate what you are seeing. 

You can take your files offline if you wish.
(Edited)
Photo of Andy Baker

Andy Baker

  • 3 Posts
  • 0 Reply Likes
I'm not sure what help it would be, but my wife and I have had the majority of our problems when a catalog is built on a Windows 10 system and then worked on on a Mac OSX system. 75% of the time a catalog is built on a Mac system and edited on another Mac system, there are no issues...but recently we've had a problem in this scenario as well. Unlike others, the issue is present in both the Library and Develop modules. 
Photo of Katie Phillips

Katie Phillips

  • 5 Posts
  • 2 Reply Likes
I have Mac OS and it started off slowly, and it was only in the library module. Over the course of about a month it went from only a few catalogs to every single catalog, and in both the library and develop module. So it progressively got worse and worse and files corrupt faster and faster. I sent a catalog to the technical team months ago and it was happening to them. Since I lowered the resolution on my screen I haven't had the issue, but if you need another catalog I can change the resolution back to what it should be and send another one. Thanks!