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

  • 8
  • Problem
  • Updated 5 days 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

  • 26 Posts
  • 4 Reply Likes

Posted 1 year ago

  • 8
Photo of Charles Sternaimolo

Charles Sternaimolo

  • 15 Posts
  • 3 Reply Likes
Just completed editing a wedding that was sent to me in a catalogue with smart previews.  Asked the sender to not label any files green.  I didn't have any issues.  So I have narrowed the issue down to the use of filters and smart previews when the images are not on the same hard drive.  The green filter is obviously the main culprit and switching back from Develop to Library although as I've mentioned previously, the red filter and blue filter have given me some not as dramatic issues.  Would love to hear back from a LR rep regarding this as I am unable to color filter images to show a client. 
Photo of James Nonov Urbusniz

James Nonov Urbusniz

  • 3 Posts
  • 0 Reply Likes
Are you saying that if you, for example, have photos in LR on one computer, apply a filter on it, and THEN Create Smart Preview, it screws it up?

So a better way would be to:

1. Import Photos
2. Generate Smart Previews
3. Apply Filter separately on the other computer on the Smart Previews.

Is this right?
Photo of Charles Sternaimolo

Charles Sternaimolo

  • 15 Posts
  • 3 Reply Likes
I work remotely from where the original files are located.  The catalog is sent to me via Dropbox with smart previews from a photographer for me to edit.  He has some files labeled green as they are favorites that he may have done some tweaking to already.  As soon as I start working on one of the files highlighted green, and especially if I toggle from Library to Develop or via versa, a funky dark olive green hue starts affecting that file, as well as a handful of other files - making them hard to view.  Once this happens I am unable to use LR to show images to a client as they can't see some of the images through the dark green.  I have a similar issue to a much lesser extent with the red and blue highlight filter.  I have not found a workaround other than to ask the photographer sending the files to not highlight any smart preview files with a color, esp. green.  Totally messes with our workflow.
(Edited)
Photo of Pavan Kumar

Pavan Kumar, Employee

  • 17 Posts
  • 1 Reply Like
Hi Charles, I tried to reproduce this issue several times, especially with the green filter, but could not. Could you please share a catalog which has the green smart previews? Thanks.
(Edited)
Photo of James Nonov Urbusniz

James Nonov Urbusniz

  • 3 Posts
  • 0 Reply Likes
Has this still not been fixed?
Photo of Katie Phillips

Katie Phillips

  • 6 Posts
  • 7 Reply Likes
Any news on when this issue is going to be resolved?
Photo of Pavan Kumar

Pavan Kumar, Employee

  • 19 Posts
  • 1 Reply Like
Hello Katie, I could not repro this issue with the images and catalog that we received. Could you please make a new catalog and make a few smart previews which have the green tint and share it with us? Thanks!
Photo of Andy Baker

Andy Baker

  • 6 Posts
  • 5 Reply Likes
Just want to say it’s entirely inappropriate that this bug is still present in Lightroom, especially considering the price increase in the photography software package. Is Adobe keen to just ignore this problem?
Photo of Cindy Lewis

Cindy Lewis

  • 1 Post
  • 1 Reply Like
I agree. I have had this problem for over a year and it's random, so you never know when it's going to destroy a photo. 

Photo of Pavan Kumar

Pavan Kumar, Employee

  • 19 Posts
  • 1 Reply Like
Hi Andy, Cindy, we're unable to reproduce the issue with a catalog and images that Miguel provided to us. I've also written what all steps I tried in a comment below. Could you please check if you have a few images where the issue can be replicated repeatedly? If yes, please share them with us so that we can work on the issue. Thanks!
Photo of Todd Shaner

Todd Shaner, Champion

  • 1442 Posts
  • 474 Reply Likes
I can't reproduce the issue either using LR Classic 8.3.1, but could previously using the OP's ARW files with LR Classic 7.4. If using LR 8.3.1 please post some sample files that exhibit the issue to a file sharing site and post the share link in a reply here. Thank you.

UPDATE: I just went back to LR where I was testing one of the OP's files (DSC00574.ARW) and it has the green tint when I switched back to the Library module. Going back to the Develop module also now has the green tint.

It appears it can take a few minutes with the Smart Preview open in the Develop module with the original file disconnected before the issue occurs. Here's what I did to reproduce it:

1) Import the file with 'Build Smart Previews' selected in the Import module's right panel.
2) Apply the Green Label.
3) Using Windows Explorer rename the file with .HOLD extension (DSC00574.ARW.HOLD).
4) Switched back to the Develop module and left LR idle doing nothing.
5) After about five minutes I switched back to the Library module and the green tint appeared.
6) Switched back to the Develop module and the green tint appears there as well and won't go away!
7) Using Windows Explorer I removed .HOLD extension restoring the original file name DSC00574.ARW and the green tint goes away.




UPDATE PART II: I can repeatedly reproduce  the issue with an even worse rendering using the Smart Preview with the following steps:

1) Select the ARW file and go to Library> Previews> Discard Smart Previews> 'Discard One.' Then remove the file from the Library module using Delete> 'Remove.'
2) Import the file with 'Build Smart Previews' selected in the Import module's right panel.
3) Select the file in the Library module and assign the Green Label.
4) Using Windows Explorer rename the file with .HOLD extension (DSC00574.ARW.HOLD).
5) Switch to Develop module and the preview immediately look like the below screenshot with no changes to the settings and the Library module flashes green and then looks correct.
6) Next apply +Exposure slider in the Develop module. Now the Library module preview remains green as in thumbnail in the below screenshot.

This is repeatable every time using the above outlined six steps.

(Edited)
Photo of Andy Baker

Andy Baker

  • 6 Posts
  • 5 Reply Likes
I’m on mobile so can’t do more than attach a couple of screen caps, but here’s an example of a photo looking normal in grid/library mode and then turning into an uneditable, unfixable contrasty mess when switching into develop module. As has been mentioned, this is a random occurrence and does not seem to have any trackable pattern in my experience. I know this isn’t super helpful to fixing the problem, but it truly happens so sporadically I can’t understand what’s causing it. Hope these images illustrate the problem I’m having.
Photo of Pavan Kumar

Pavan Kumar, Employee

  • 19 Posts
  • 1 Reply Like

What I've tried so far on a Mac book 2017 High sierra and a Win 10 machine:

Created a new catalog on both win and mac machines, imported a few ARW images and then created smart previews. I also coloured them green (based on the comments on this thread) and filtered for green ones and removed the raw images. In develop module, changed WB to daylight,auto,as shot(all three different combinations) and then moved the tint slider and switched back to loupe view in library and the image looks just fine!

I have tried it with versions 7.4, 8.1, 8.2 and 8.3. Could someone point out if there's something more specific to reproduce it? I also tried it with different screen resolution on Mac, with images that were provided earlier on this thread but even those looked fine.

Will be great if someone can share a sample catalog and test images on which the green tint bug can be reproduced frequently. Thanks!
Photo of Miguel Povedano

Miguel Povedano

  • 26 Posts
  • 4 Reply Likes
I provided one to Sunil Bhaskaran almost a year ago...
Photo of Pavan Kumar

Pavan Kumar, Employee

  • 19 Posts
  • 1 Reply Like
He passed it over to me and I didn't find any issues with those images.. I also tried on other files shot on A73 and still nothing. So, please let me know if you have other images on which the green tint can always be reproduced. Also, if you could make a new catalog and share that as well, would be great. Thanks!
Photo of Miguel Povedano

Miguel Povedano

  • 26 Posts
  • 4 Reply Likes
Lib. w/ a couple of test photos: https://www.dropbox.com/sh/v6tzd7ce4jw7iry/AABPsfdgOkVd0Lxo_sox2r3za?dl=0

When downloaded, let me know to delete it.

Keep in mind I am using at this moment macOS 10.14.5 and Lr Classic 8.3.1 
Photo of Pavan Kumar

Pavan Kumar, Employee

  • 19 Posts
  • 1 Reply Like
Hey Miguel, thanks for sharing your catalog! I tried to reproduce the issue on 8.3.1 on a Mac and was successful only once, and the image got back to its original state very shortly(about one second) after turning green. Is that the case in your machine as well?
Photo of Miguel Povedano

Miguel Povedano

  • 26 Posts
  • 4 Reply Likes
I exported this two photos to its own catalog (including the standard and smart previous from the original one).

In the original catalog, they remain green no matter the module I am working on until I reconnect the HD with the original files.

However, I have realized that, in the exported catalog (the one I shared with you) they are green when opened until I change from library to develop. At that moment, they go back to normal.
Photo of Miguel Povedano

Miguel Povedano

  • 26 Posts
  • 4 Reply Likes
Try with this catalog with a couple of smart previews: https://www.dropbox.com/sh/n7mmtu9s9gexit7/AACW0b3s6hdieC4zRXpP-lcLa?dl=0

Both look normal in Library module. Change to Develop and both turn and remain in green.

Let me know    

Photo of Pavan Kumar

Pavan Kumar, Employee

  • 19 Posts
  • 1 Reply Like
Tried with the catalog and it looks normal in both modules!
Photo of Todd Shaner

Todd Shaner, Champion

  • 1439 Posts
  • 471 Reply Likes
I can't see any issues either because you have not included the original ARW files with the catalog files. Try adding them and then we will have to remove them them on our end following the outlined procedure. This is necessary so the Camera Raw Cache can be updated with the ARW file and then when it is removed the Smart Preview rendering becomes corrupt. Without that step it's not going to happen.

Pavan, did you try the procedure I outlined in my reply above? It is easily reproduced on my Windows 10 system using LR 8.3.1. It is also similar to what Andy Baker is seeing in his reply above. Here's the procedure:

UPDATE PART II: I can repeatedly reproduce  the issue with an even worse rendering using the Smart Preview with the following steps:

1) Select the ARW file and go to Library> Previews> Discard Smart Previews> 'Discard One.' Then remove the file from the Library module using Delete> 'Remove.'

2) In the Library module Import the file with 'Build Smart Previews' selected in the Import module's right panel. Do not view the file in the Develop module.

3) Select the file in the Library module and assign the Green Label.

4) Using Windows Explorer rename the file with .HOLD extension (DSC00574.ARW.HOLD).

5) Switch to Develop module and the preview immediately look like the below screenshot with no changes to the settings and the Library module flashes green and then looks correct.

6) Next apply +Exposure slider in the Develop module. Now the Library module preview remains green as in thumbnail in the below screenshot.

This is repeatable every time using the above outlined six steps.
(Edited)
Photo of Pavan Kumar

Pavan Kumar, Employee

  • 19 Posts
  • 1 Reply Like
Hello Todd, does that happen with any ARW file? I tried with some on Win 10 and 8.3.1 and still unable to reproduce! I did exactly what you've described in the steps.. 
Photo of Miguel Povedano

Miguel Povedano

  • 26 Posts
  • 4 Reply Likes
Take a look also at this two screen shots of photo DSC03740:
 - The first one: Lib. module --> it looks green.
 - The second one: Dev. module --> lees green, but a contrasty mess. At this one, the preview at the upper left corner looks normal.

Link to the original photo: https://www.dropbox.com/s/jbntwnkjem25n3p/DSC03740.ARW?dl=0

Photo of Todd Shaner

Todd Shaner, Champion

  • 1439 Posts
  • 471 Reply Likes
With the DSC03740.ARW file I can see a similar rendering using this simpler three-step procedure:

1) Switch to the Library module and import the file with 'Build Smart Previews' selected in the Import module's right panel. DO NOT VIEW THE FILE THE DEVELOP MODULE.

2) Using Windows Explorer rename the file with .HOLD extension (DSC00574.ARW.HOLD) or simply move it to a subfolder.

3) Now switch to Develop module and the preview will immediately look like the below screenshot with no changes to the settings and the Library module flashes magenta and then looks correct.

If you you can't duplicate the issue using the above three-steps please follow the six step procedure I posted in my reply above. This is necessary if you inadvertently switched to to the Develop module BEFORE the original file was removed.

If the original file is removed BEFORE it has been viewed in the Develop module the Camera Cache is not properly updated. From my testing assigning the Green Label is NOT necessary to duplicate the issue.

In a laptop workflow some users may import new image files into the LR catalog, assign Labels and ratings, etc., but not edit them in Develop module. They then remove the external drive to continue working and apply Develop edits. This will cause the issue to appear, but should be a perfectly acceptable editing workflow.


Photo of Alec Bartsch

Alec Bartsch

  • 1 Post
  • 0 Reply Likes
I'm also having this problem, with smart previews of RAW files shot on Sony a7iii, when the source images are offline. Let me know if there's anything I can provide to help nail down a repro case. Only certain images show the problem, but the problem persists with those particular images (rather than showing up intermittently).
(Edited)