Skip to main content
Known Participant
July 15, 2018

P: Smart Previews White Balance turns turns image very greenish

  • July 15, 2018
  • 89 replies
  • 1837 views

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 
 

This topic has been closed for replies.

89 replies

Adobe Employee
August 22, 2019
Hey Todd, tried again and again, no luck! Didn't happen on the windows and Mac 10.14 machines at all.. I tried with 8.3.1 and previous versions as well, with GPU on. I shall try to get a set of images where it can be replicated constantly and try again.
eaaronross
Participant
August 19, 2019
I was having this problem only when my source files were connected for some reason. If I built a smart preview and disconnected it would be fine. That said, here are two solutions I found.

1. Go into Preferences > Performance > Check Use Graphics Processor.
Mine was unchecked and when I turned it back on, presto! For reference, my graphics processor is apparently a "Metal: NVIDIA GeForce GT 750M". I know Premiere Pro has been giving me some stupid pop up messages lately about incompatibility. Maybe it's related to that ̄\_(ツ)_/ ̄  
2.My files were already DNG files, but I reconverted the DNG from itself and chose the LOSSY option. I know this isn't ideal cause you lose quality supposedly, but problem fixed. If option 1 works, stick with that.

3. As I mentioned, I could also build smart previews, disconnect, then edit based just on the previews. Then, reconnect just to export.
eaaronross
Participant
August 19, 2019
I was having this problem only when my source files were connected for some reason. If I built a smart preview and disconnected it would be fine. That said, here are two solutions I found.

1. Go into Preferences > Performance > Check Use Graphics Processor.
Mine was unchecked and when I turned it back on, presto! For reference, my graphics processor is apparently a "Metal: NVIDIA GeForce GT 750M". I know Premiere Pro has been giving me some stupid pop up messages lately about incompatibility. Maybe it's related to that ̄\_(ツ)_/ ̄  
2.My files were already DNG files, but I reconverted the DNG from itself and chose the LOSSY option. I know this isn't ideal cause you lose quality supposedly, but problem fixed. If option 1 works, stick with that.

3. As I mentioned, I could also build smart previews, disconnect, then edit based just on the previews. Then, reconnect just to export.
Inspiring
July 24, 2019
Wow, I'm so glad I found this thread. I thought I was the only one having this problem!

Many images turn half green in develop module when changes are made. For some reason, the thumbnail in the upper left navigator panel updates correctly, but not the grid or the preview module.

Source HDD is disconnected. Smart previews and 1:1 previews were built on import. a7riii raw files on 8.3.1 Mac OS. 

Is there a fix on the way? Any eta?
Participating Frequently
July 19, 2019
I'm at my wits end with this problem! It's one thing to have access to the drive where the files are being stored, but as has been mentioned by loads of other folks in this thread we're having to edit photographer's files remotely as professional editors and don't have access to the drive where the files are stored. This results in an ultimate abortion of the job because the problem starts randomly and seems to snowball, to an extent, as editing progresses. There are few things more embarrassing than trying to explain this to a client. I'm not seeing a lot of progress in this thread with solutions for the problem and it seems that the most helpful things have come from other users and not Adobe. I appreciate that there are Adobe employees here trying to reproduce the problem and start the long path of fixing the issue, but it has been over a year since this problem was acknowledged and at this point we feel a little bit like we're being held hostage as Lightroom is the only program with which our editing workflow works! Abandoning it for an alternative would result in a huge $ investment loss and we're desperate at this point. 

Sincerely, 
a distressed customer
Adobe Employee
July 19, 2019
Thanks a lot for sharing the steps, I'll try this again and confirm if the issue happens with my windows machine as well. 
Participating Frequently
July 19, 2019
Just wanted to comment hoping to get more attention on this. Very frustrating. My Smart Preview workflow is useless and it's been a year.

Sony a7iii raw files here as well.
Inspiring
July 12, 2019
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).
Todd Shaner
Legend
July 2, 2019
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.


mpovedanoAuthor
Known Participant
July 2, 2019
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