Skip to main content
Participating Frequently
February 28, 2019
Answered

Radical Color Cast Shift in Developer Module

  • February 28, 2019
  • 7 replies
  • 2128 views

Using Lightroom CC Classic Latest Release, 8.2

Random DNG images show a radical color cast when in Developer Module.  Same images when opened in Photoshop directly from Developer Module show no shift and are rendered normally.  When I shut LR down, the same images show normally in DEV mode when LR opened again, but invariably the shift appears again.  What is going on?

    This topic has been closed for replies.
    Correct answer johnrellis

    Hi.  Thanks!  I am sure as you say: it is a preview rendering issue.  GPU is turned off.

    Sorry to say, I don´t know how to rebuild display profile, or how to make sure it is not a V4 spec profile, as you suggest.  For now, I am managing by fooling around with the Navigator zoom options.  Cheers!   .j.


    it is a preview rendering issue.

    To use more precise terminology, it could be corruption in the Camera Raw Cache, which is used in Develop.  In LR's terminology, "previews" refer to the previews built for use in Library, which are entirely separate and are not used in Develop.

    The most reliable way to rule out a corrupt Camera Raw Cache is to clear it, by going to Preferences > Performance and clicking Purge Cache. You won't lose any edits and you'll only take a mild performance hit as LR slowly rebuilds the contents of the cache incrementally as you edit.

    7 replies

    GoldingD
    Legend
    March 1, 2019

    After you verify it is or is not corrupt previews (Library and more to the point Develop, hat tip to johnrellis) and that fails to solve your issue, perhaps a proper reset of your preferences file. Following are links on the why, they how, and notes about what that will do, read them all:

    https://lightroomers.com/replacing-the-lightroom-preference-file/745/

    https://www.youtube.com/watch?v=bARt-hoCc2Q

    https://helpx.adobe.com/lightroom/kb/preference-file-and-other-file-locations---lightroom-6.html

    https://helpx.adobe.com/lightroom/kb/recover-catalog-images-resetting-lightroom.html

    Jerimiah27402358zhax
    Participating Frequently
    December 2, 2022

    Unchecking "Use Graphics Processor" works to make the colors match export, library, and develop screen images on two different computers with different brands of graphics cards.

     

    I'd like someone to tell us all how we can have the benefits of hardware acceleration and have accurate colors when developing photos! Is there anyone guru who knows this answer? 

     

     

     

    Ian Lyons
    Community Expert
    Community Expert
    December 2, 2022
    GoldingD
    Legend
    March 1, 2019

    Ok, perhaps I missed a previous inquiry on this, just scrolled thru all above, did not see this, and I may have in fact stated the following. But lets go at this again.

    For the current exemplar.The image in your last set of screenshots. Accomplish the following as a diagnostic test. note that their will be collateral damage in the form of loosing all develop edits, etc.

    Fore the one image, remove it from your catalog. DO not delete it. This will also remove all previews,

    Now add it back in to the catalog.

    Point is to delete all previews for the one  image that is all previews not just the 1:1 or Smart Previews.

    Does the image behave? If so, your previews are fubar.

    GoldingD
    Legend
    February 28, 2019

    You might want want to look at this

    In your system information, something does not look correct in the GPU section

    Graphics Processor Info:

    Check OpenGL support: Failed

    Vendor:

    Version:

    Renderer:

    LanguageVersion:

    Actual GPU not listed. Perhaps this basic laptop uses an integrated graphics card, but should that not be presented in the info?

    Please from your OS devices identify your graphics card or chip. And driver version.

    Also, as OpenGL support failed I am wondering about the capability of that chip. Mind you, before LR Classic CC v8.2 Adobe support pretty much calls for DirectX not OpenGL on Windows OS, but that needs to be  DirectX 12. Niw they apparently want OpenGL v3.3

    also view

    Adobe Lightroom GPU Troubleshooting and FAQ

    GoldingD
    Legend
    February 28, 2019

    And what camera?

    Participating Frequently
    February 28, 2019

    Thanks for the help.  I have a fairly basic Laptop setup.  Use no accelarator. Have used LR for years and have not had this problem until this last release. It seems to be something going on within the DEV MODULE itself.  Here are some pics as you requested:

    Camera: Panasonic DMC FZ1000

    Lightroom Classic version: 8.2 [ 1204643 ]

    License: Creative Cloud

    Language setting: en

    Operating system: Windows 7  - Home Premium Edition

    Version: 6.1.7601

    Application architecture: x64

    System architecture: x64

    Logical processor count: 4

    Processor speed: 2.2 GHz

    Built-in memory: 7331.7 MB

    Real memory available to Lightroom: 7331.7 MB

    Real memory used by Lightroom: 1698.1 MB (23.1%)

    Virtual memory used by Lightroom: 1745.8 MB

    GDI objects count: 941

    USER objects count: 3167

    Process handles count: 1504

    Memory cache size: 222.6MB

    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: 1063MB / 3665MB (29%)

    Camera Raw real memory: 1083MB / 7331MB (14%)

    System DPI setting: 96 DPI

    Desktop composition enabled: No

    Displays: 1) 1366x768, 2) 1024x768

    Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

    Graphics Processor Info:

    Check OpenGL support: Failed

    Vendor:

    Version:

    Renderer:

    LanguageVersion:

    Application folder: C:\Program Files\Adobe\Adobe Lightroom Classic CC

    Library Path: C:\Users\PERSONAL\Pictures\Lightroom\Lightroom Catalog-2.lrcat

    Settings Folder: C:\Users\PERSONAL\AppData\Roaming\Adobe\Lightroom

    Installed Plugins:

    1) AdobeStock

    2) Facebook

    3) Flickr

    4) Nikon Tether Plugin

    5) SmugMug

    Config.lua flags: None

    Adapter #1: Vendor : 8086

    Device : 116

    Subsystem : fc301179

    Revision : 9

    Video Memory : 64

    AudioDeviceIOBlockSize: 1024

    AudioDeviceName: Altavoces (Realtek High Definition Audio)

    AudioDeviceNumberOfChannels: 2

    AudioDeviceSampleRate: 48000

    Build: 12.1x4

    Direct2DEnabled: false

    GL_ACCUM_ALPHA_BITS: 16

    GL_ACCUM_BLUE_BITS: 16

    GL_ACCUM_GREEN_BITS: 16

    GL_ACCUM_RED_BITS: 16

    GL_ALPHA_BITS: 8

    GL_BLUE_BITS: 8

    GL_DEPTH_BITS: 24

    GL_GREEN_BITS: 8

    GL_MAX_3D_TEXTURE_SIZE: 2048

    GL_MAX_TEXTURE_SIZE: 8192

    GL_MAX_TEXTURE_UNITS: 8

    GL_MAX_VIEWPORT_DIMS: 8192,8192

    GL_RED_BITS: 8

    GL_RENDERER: Intel(R) HD Graphics Family

    GL_SHADING_LANGUAGE_VERSION: 1.40  - Intel Build 8.15.10.2827

    GL_STENCIL_BITS: 8

    GL_VENDOR: Intel

    GL_VERSION: 3.1.0 - Build 8.15.10.2827

    GPUDeviceEnabled: false

    OGLEnabled: true

    GL_EXTENSIONS: GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_blend_color GL_EXT_abgr GL_EXT_texture3D GL_EXT_clip_volume_hint GL_EXT_compiled_vertex_array GL_SGIS_texture_edge_clamp GL_SGIS_generate_mipmap GL_EXT_draw_range_elements GL_SGIS_texture_lod GL_EXT_rescale_normal GL_EXT_packed_pixels GL_EXT_texture_edge_clamp GL_EXT_separate_specular_color GL_ARB_multitexture GL_EXT_texture_env_combine GL_EXT_bgra GL_EXT_blend_func_separate GL_EXT_secondary_color GL_EXT_fog_coord GL_EXT_texture_env_add GL_ARB_texture_cube_map GL_ARB_transpose_matrix GL_ARB_texture_env_add GL_IBM_texture_mirrored_repeat GL_EXT_multi_draw_arrays GL_NV_blend_square GL_ARB_texture_compression GL_3DFX_texture_compression_FXT1 GL_EXT_texture_filter_anisotropic GL_ARB_texture_border_clamp GL_ARB_point_parameters GL_ARB_texture_env_combine GL_ARB_texture_env_dot3 GL_ARB_texture_env_crossbar GL_EXT_texture_compression_s3tc GL_ARB_shadow GL_ARB_window_pos GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_ARB_vertex_program GL_EXT_texture_rectangle GL_ARB_fragment_program GL_EXT_stencil_two_side GL_ATI_separate_stencil GL_ARB_vertex_buffer_object GL_EXT_texture_lod_bias GL_ARB_occlusion_query GL_ARB_fragment_shader GL_ARB_shader_objects GL_ARB_shading_language_100 GL_ARB_texture_non_power_of_two GL_ARB_vertex_shader GL_NV_texgen_reflection GL_ARB_point_sprite GL_ARB_fragment_program_shadow GL_EXT_blend_equation_separate GL_ARB_depth_texture GL_ARB_texture_rectangle GL_ARB_draw_buffers GL_ARB_color_buffer_float GL_ARB_half_float_pixel GL_ARB_texture_float GL_ARB_pixel_buffer_object GL_EXT_framebuffer_object GL_ARB_draw_instanced GL_ARB_half_float_vertex GL_EXT_draw_buffers2 GL_WIN_swap_hint GL_EXT_texture_sRGB GL_ARB_multisample GL_EXT_packed_float GL_EXT_texture_shared_exponent GL_ARB_texture_rg GL_ARB_texture_compression_rgtc GL_NV_conditional_render GL_EXT_texture_swizzle GL_ARB_sync GL_ARB_framebuffer_sRGB GL_EXT_packed_depth_stencil GL_ARB_depth_buffer_float GL_EXT_transform_feedback GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_ARB_framebuffer_object GL_EXT_texture_array GL_EXT_texture_integer GL_ARB_map_buffer_range GL_EXT_texture_snorm GL_INTEL_performance_queries GL_ARB_copy_buffer GL_ARB_sampler_objects GL_NV_primitive_restart GL_ARB_seamless_cube_map GL_ARB_uniform_buffer_object GL_ARB_depth_clamp GL_ARB_vertex_array_bgra GL_ARB_draw_elements_base_vertex GL_ARB_fragment_coord_conventions GL_EXT_gpu_program_parameters GL_ARB_compatibility GL_ARB_vertex_array_object

    johnrellis
    johnrellisCorrect answer
    Legend
    March 1, 2019

    Hi.  Thanks!  I am sure as you say: it is a preview rendering issue.  GPU is turned off.

    Sorry to say, I don´t know how to rebuild display profile, or how to make sure it is not a V4 spec profile, as you suggest.  For now, I am managing by fooling around with the Navigator zoom options.  Cheers!   .j.


    it is a preview rendering issue.

    To use more precise terminology, it could be corruption in the Camera Raw Cache, which is used in Develop.  In LR's terminology, "previews" refer to the previews built for use in Library, which are entirely separate and are not used in Develop.

    The most reliable way to rule out a corrupt Camera Raw Cache is to clear it, by going to Preferences > Performance and clicking Purge Cache. You won't lose any edits and you'll only take a mild performance hit as LR slowly rebuilds the contents of the cache incrementally as you edit.

    GoldingD
    Legend
    February 28, 2019

    How about a new screenshot. This one of that pink one. Screenshot if your entire Lightroom Develop module screen, need to see Navigator preview, history panel,  histogram, filmstrip with selected image in view, and of course loupe if image, and at least the basic panel, tone curve panel, and HSL panel in view.

    hmm, base on older similar discussions, probably should include a similar screenshot, but from the library module, with loupe instead of grid selected.

    GoldingD
    Legend
    February 28, 2019

    Ok, first up be advised that in Lightroom, the Library and Develop modules use different color space, they also use different previews.

    That being said, your exemplars show a lot more difference than that would present. So something is wrong.

    A few questions

    1. What make/model is your GPU

    2. What is your GPU driver version ?

    (you can get both from Lightroom’s System Information, in LR click on Help, then System Information)

    hmmm, since you have assumedly obtained that system information, probably best to also click on copy, and paste that in a reply.

    3. What make/model is your monitor calibration device?

    Per Berntsen
    Community Expert
    Community Expert
    February 28, 2019

    First of all, try disabling the GPU. Go to Preferences > Performance, uncheck Use graphics processor.

    If that doesn't help, you probably have a defective monitor profile. Try setting the monitor profile to sRGB, see instructions here: http://www.lightroomqueen.com/articles-page/how-do-i-change-my-monitor-profile-to-check-whether-its-corrupted/

    If that fixes the issue, you should ideally calibrate your monitor with a hardware calibrator. This will create a new monitor profile that describes your monitor's color response accurately.