Skip to main content
N
NotASpeckOfCereal
Known Participant
February 24, 2020
Question

New v9.2 Performance Issues: screen blacks out in Develop

  • February 24, 2020
  • 9 replies
  • 2021 views

[ There is an older thread that is similar, but it's not the same and it's really stale ]

Symptons while working in Develop panel:

  • Frequent hangs
  • Main screen blacks out
  • Windows titlebar says "Lightroom (Not Responding).
  • When it returns from hang, sometimes an edit streaks across screen (as if it detected a mouse movement from X to Y with button down, which did not occur). 
  • Second monitor goes away
  • Even when not hung, all LR actions are very slow to react. Screen draws on 2nd monitor from something done in development panel take a long time to show up.

 

This is all a production killing, total work-stoppage environment. (Please see system specs at the bottom.)

 

Resolutions attempted (that did not fix the issue):

  • Restart LR between attempts /pref-changes, rebooted computer several times
  • Turn off GPU processing (this might have slightly reduced the issues, but not a resolution), turned it back on -- no joy.
  • Purged ACR cache (though it was only using ~25% of 200GB)
  • Purged Video cache

 

This is all on a system that has not changed in hardware and has been working for a long time just fine.

 

The only thing I can think of that I have been doing, which might contribute to the issue, is:

  • I've been doing large exports, like 300-1000 file exports to 16-bit 8k TIFFs (over 200MB each)
  • I recently re-started using my WACOM tablet, but have since unplugged it to see if it was a contributing factor (it doesn't seem to have been).
  • I am writing to a large hard drive enclosure and have been for awhile (usb 3.1), but since both files and catalog are on that drive, I'm going to test it. Windows reports it's fine, but I'll still test it for throughput speed. Film at 11.

 

System Specs:

  • Win10 Pro Workstation 64bit, 64GB memory, I7-8700 CPU (3.20GHz), NVMe SSD boot, NVMe SSD scratch, tons of free drive space all around, dual 4K monitors, all Adobe components updated (including ACR and DNG convertor).

 

Chris

 

This topic has been closed for replies.

9 replies

N
NotASpeckOfCerealAuthor
Known Participant
March 11, 2020

Update: performance is still dismal.

 

What I've done:

  • Moved the catalog to an SSD (which I also replaced with a current model Samsung 970 Evo Plus, hoping for much faster write speeds). The move to SSD is thanks to David's suggestion above.
  • Completely re-built the hard-drive array that the main photographs live on (a 4 disk JBOD box). This is a Windows Storage Space formated with the ReFS file system, which is almost as fast as my SSDs. I have two file locations in my catalog, one on drive F (see system info posted above), which is just a disk; but the larger collections of files (for large time-lapse projects for which I do large operations on such as exports of hundreds of files) are on drive T, which is this fast drive array (this is where the performance problems occur).
  • Did low-level speed tests of all discs in the system (using FIO). They are all up to snuff.
  • Upgraded the video card driver (also thanks to David's suggestion above) via the manufacturers site (not Windows update) and did a Clean Install
  • Tried Lightroom with/without smart previews, and with/without GPU on (or set to Auto). 
  • Moved the export target location from drive T (the location of the source files) to drive S (a separate SSD).

 

After doing all of that, performance seemed to go well for awhile until the past day or two. At first, I noticed it while doing simple brush erase work on a graduated filter (on a single keyframe image). I got all of the old symptoms, system hangs, Lightroom non-responsive, Lightroom window blacking out, Second monitor image disappearing (and turning off in the LR UI). Then, after I finally finished that frustratingly slow work on keyframes, I tried Export. At first, the export dialog did not even come up. I learned that I had to wait. Even after a reboot, this occured, then I came back from the kitchen to find multiple export dialogs up (erroring out).

 

Also: while doing brush erase work on the grad filter (using a WACOM tablet and pen), I occassionally experienced unintended streaks across the image. Scenario: brush horizontally from point A to point B, then up vertically from point B to point C: RESULT: get a line from point A to point C. Doing an UNDO fixes that, but with this performance, you have to sit back in your chair and WAIT for the undo to actually occur to resume work (the same kind of wait that you have to endure with just basic brush strokes).

 

It's really quite an intolerable way to work.

 

BUT MOSTLY: the state I am in AND the amount of work-around I have had to follow are WELL BEYOND what you really want any of your users to experience. Ever.

 

Finding a alternative platform that doesn't have this problem would be very attractive to a lot of users.

 

Chris

 

PS: this is a community forum. Is there an actual Adobe bug system I can report this on that will get in-house technical review?

 

GoldingD
GoldingD
Legend
March 4, 2020

 

 

 

 

Win10 Pro Workstation 64bit, 64GB memory, I7-8700 CPU (3.20GHz), NVMe SSD boot, NVMe SSD scratch, tons of free drive space all around, dual 4K monitors, all Adobe components updated (including ACR and DNG convertor).

 

 

 

 

 

 

 

Application folder: C:\Program Files\Adobe\Adobe Lightroom Classic
Library Path: F:\LightroomCatalog\LightroomCatalog-2-2-2.lrcat
Settings Folder: C:\Users\chris\AppData\Roaming\Adobe\Lightroom

 

 

 

 

So your Scratch is on a seperate SSD than your boot drive? Excelant

 

And as well as PS Scratch, this is where you keep LRC Camera RAW CACHE?

 

I assume you're Page File is on the boot drive? (point being to not have scratch and page on same drive)

 

Now that F drive, SSD? As one would hope for for LRC performance.

 

Ahh, opps, Yes I see external hard drive, USB 3.1, still slower than internal SSD.

 

Side note. Location of Photos does not matter in terms of performance.

 

 

 

N
NotASpeckOfCerealAuthor
Known Participant
March 4, 2020

Thanks David,

 

No, drive F is not SSD, but a 7200rpm internal. You also say "Location of Photos does not matter in terms of performance".

 

So does that mean that I can move my catalog / previews to SSD, but leave the photos on the non-SSD drive, and see an increase in performance?

 

I really can't move the photos because of drive space requirements, but perhaps the catalog can move.

 

Thanks, Chris

 

PS: I did a full clean install of the most recent NVIDIA drivers, and also made the recommended post-update changes in the NVIDIA Control Panel. I will attempt to make heavy edits in the next day or two to see if perf has improcved in Develop mode.

 

GoldingD
GoldingD
Legend
March 4, 2020

The location for the photos in terms of performance does  not matter. While you are editing, the changes are stored in the database, the catalog, the photos are not touched. Lightroom only wrights to the photos if you rename them. Lightroom only occasionally reads them (one instance being at import, another at export)

 

Some people seperate the photos from the catalog in order to place them on a larger but slower regular hard drive, as opposed to clobbering the hard drive the catalog is on.

 

The Libary previews must be on the same drive, within a common folder with the catalog. But not the photos.

 

You can move the catalog, then after you notice that the folder panel is complaining, you can fix the folder locations (typically fixing the parent folder location)

 

http://www.computer-darkroom.com/lr2_find_folder/find-folder.htm

 

 

 

GoldingD
GoldingD
Legend
March 4, 2020

Hoping, I am not answering something I answered before, fairly sure it was on someone else's similar posting. Moving on

 

So, you will not like this, you spent big bucks for the best, the biggest, but the 4K, LRC still has issues, especially as you accomplish more and more edits, especially adjustment brushes . But cut down on the display resolution. Each time you touch any develop mod, all, and I mean all of those pixals get recreated, and not just the last mod, all the mods. So cut down to 2K to get the work done.

 

Side note 1. No Photoshop does not enter in the argument. PS is a raster editor, it only recreates the specific pixals touched, and builds on what came before. Lightroom Classic is a Parametric editor, walks thru each and every edit to get to the result at each and every new edit.

 

Side note 2. Not applicable to MACOS. You can not reduce the actual resolution on MACOS, you can only Scale, that makes the display look like a lower resolution, but all those pixals are being created.

 

GoldingD
GoldingD
Legend
March 4, 2020

NVIDIA  used to have an issue in which settings were reset to defaults upon GPU driver updates. The settings for the GPU.

 

see:

https://www.winhelp.info/boost-lightroom-performance-on-systems-with-nvidia-graphics-chip.html

 

If you previously accomplished vs, perhaps it got undone.

 

note, not a Quadra owner, might have some bad assumptions based on GeForce usage.

 

 

 

 

GoldingD
GoldingD
Legend
March 4, 2020

So, Windows 10. I did not see in your attempts, mention of making sure some Windows update did not revert some OS settings to defaults. Specfically Power Settings to High Performance, as opposed to Balanced.

 

See tip 8 in:

https://au.pcmag.com/windows-10-1/5180/11-tips-to-speed-up-windows-10

 

 

GoldingD
GoldingD
Legend
March 4, 2020

 

Graphics Processor Info:
DirectX: NVIDIA Quadro P1000 (26.21.14.4166)

 

 

So, NVIDIA Quadra P1000 v441.66

 

From NVIDIA web page, current would be v442.15 dated 2/27/2020, so not so old based on v numbering.

 

One thing I may have overlooked in your previous attempted fixes, is replacing the existing a GPU driver, selecting custom, to run a clean install. As you may want to update anyhow, accomplish a clean install.

 

N
NotASpeckOfCerealAuthor
Known Participant
March 4, 2020

Thanks David, I'll try a clean install using the most recent NVIDIA driver.

KR Seals
Community Expert
KR SealsCommunity Expert
Community Expert
March 4, 2020

Hi Chris,

My system is extremely similar to yours except for my video card which is a GTX 960. My catalog is on a separate SSD internal drive.

I suspect that the USB connection to the external drive may be too slow or intermittent. Try putting the Catalog Folder on one of the SSD drives and see how that works. Also, see what happens once you have the catalog and previews on an SSD drive if you also put a folder of images on that same drive.

Separately, how does the import function in LR CL work with large numbers of files?

Ken Seals - Nikon Z 9, Z 8, 14mm-800mm. Computer Win 11 Pro, I7-14700K, 64GB, RTX3070TI. Travel machine: 2021 MacBook Pro M1 MAX 64GB. All Adobe apps.
N
NotASpeckOfCerealAuthor
Known Participant
March 4, 2020

Thanks Kenneth,

 

I can try creating a catalog on a SSD drive and will test that.

 

However, the USB drive I'm using is box with 7200rpm drives and it's USB 3.1 (10Gbps), so it should be relatively fast.

 

However, the exports (as reported) have been taking longer than previously. The imports are not slow, which is not surprising since it's a database operation and not an file copy / creation operation.

 

I'll test on SSD and will get back on that.

 

Chris

 

GoldingD
GoldingD
Legend
February 24, 2020

Please post your system information AS LIGHTROOM REPORTS IT.

 

In LRC, click on Help, then System Info, then Copy. Paste into a reply.

 

N
NotASpeckOfCerealAuthor
Known Participant
February 24, 2020

Sure, here is the LR system info from the dialog:

 

Lightroom Classic version: 9.2 [ 202001311240-2d026470 ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10
Version: 10.0.18363
Application architecture: x64
System architecture: x64
Logical processor count: 12
Processor speed: 3.1 GHz
SqLite Version: 3.30.1
Built-in memory: 65471.3 MB
Real memory available to Lightroom: 65471.3 MB
Real memory used by Lightroom: 9172.3 MB (14.0%)
Virtual memory used by Lightroom: 10153.1 MB
GDI objects count: 811
USER objects count: 2625
Process handles count: 2009
Memory cache size: 1628.6MB
Internal Camera Raw version: 12.2 [ 384 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 5371MB / 32735MB (16%)
Camera Raw real memory: 5470MB / 65471MB (8%)
System DPI setting: 168 DPI (high DPI mode)
Desktop composition enabled: Yes
Displays: 1) 3840x2160, 2) 3840x2160
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info:
DirectX: NVIDIA Quadro P1000 (26.21.14.4166)

 

Application folder: C:\Program Files\Adobe\Adobe Lightroom Classic
Library Path: F:\LightroomCatalog\LightroomCatalog-2-2-2.lrcat
Settings Folder: C:\Users\chris\AppData\Roaming\Adobe\Lightroom

Installed Plugins:
1) AdobeStock
2) ColorChecker Passport
3) Export to Photomatix Pro
4) Facebook
5) Flickr
6) HDR Efex Pro 2
7) Helicon Focus Export
😎 LRT Export 5
9) Nikon Tether Plugin

Config.lua flags: None

Adapter #1: Vendor : 10de
Device : 1cb1
Subsystem : 11bc10de
Revision : a1
Video Memory : 4019
Adapter #2: Vendor : 1414
Device : 8c
Subsystem : 0
Revision : 0
Video Memory : 0
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Speakers (Sound Blaster Z)
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: 0
GL_BLUE_BITS: 8
GL_DEPTH_BITS: 24
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_SIZE: 32768
GL_MAX_TEXTURE_UNITS: 4
GL_MAX_VIEWPORT_DIMS: 32768,32768
GL_RED_BITS: 8
GL_RENDERER: Quadro P1000/PCIe/SSE2
GL_SHADING_LANGUAGE_VERSION: 4.60 NVIDIA
GL_STENCIL_BITS: 8
GL_VENDOR: NVIDIA Corporation
GL_VERSION: 4.6.0 NVIDIA 441.66
GPUDeviceEnabled: false
OGLEnabled: true
GL_EXTENSIONS: GL_AMD_multi_draw_indirect GL_AMD_seamless_cubemap_per_texture GL_AMD_vertex_shader_viewport_index GL_AMD_vertex_shader_layer GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_bindless_texture GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_cl_event GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_compute_shader GL_ARB_compute_variable_group_size GL_ARB_conditional_render_inverted GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_2_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_fragment_shader_interlock GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gl_spirv GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader_int64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_parallel_shader_compile GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_polygon_offset_clamp GL_ARB_post_depth_coverage GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sample_locations GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counter_ops GL_ARB_shader_atomic_counters GL_ARB_shader_ballot GL_ARB_shader_bit_encoding GL_ARB_shader_clock GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shader_viewport_layer_array GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_sparse_buffer GL_ARB_sparse_texture GL_ARB_sparse_texture2 GL_ARB_sparse_texture_clamp GL_ARB_spirv_extensions GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_filter_anisotropic GL_ARB_texture_filter_minmax GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transform_feedback_overflow_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add 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_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled 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_multiview_tessellation_geometry_shader GL_EXT_multiview_texture_multisample GL_EXT_multiview_timer_query GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset_clamp GL_EXT_post_depth_coverage GL_EXT_provoking_vertex GL_EXT_raster_multisample GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shader_image_load_formatted GL_EXT_shader_image_load_store GL_EXT_shader_integer_mix GL_EXT_shadow_funcs GL_EXT_sparse_texture2 GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_filter_minmax GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shadow_lod GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_R8 GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback2 GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_EXT_window_rectangles GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_context_flush_control GL_KHR_debug GL_EXT_memory_object GL_EXT_memory_object_win32 GL_EXT_win32_keyed_mutex GL_KHR_parallel_shader_compile GL_KHR_no_error GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_EXT_semaphore GL_EXT_semaphore_win32 GL_KHR_shader_subgroup GL_KTX_buffer_region GL_NV_alpha_to_coverage_dither_control GL_NV_bindless_multi_draw_indirect GL_NV_bindless_multi_draw_indirect_count GL_NV_bindless_texture GL_NV_blend_equation_advanced GL_NV_blend_equation_advanced_coherent GL_NVX_blend_equation_advanced_multi_draw_buffers GL_NV_blend_minmax_factor GL_NV_blend_square GL_NV_clip_space_w_scaling GL_NV_command_list GL_NV_compute_program5 GL_NV_conditional_render GL_NV_conservative_raster GL_NV_conservative_raster_dilate GL_NV_conservative_raster_pre_snap_triangles GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_deep_texture3D GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_draw_texture GL_NV_draw_vulkan_image GL_NV_ES1_1_compatibility GL_NV_ES3_1_compatibility GL_NV_explicit_multisample GL_NV_feature_query GL_NV_fence GL_NV_fill_rectangle GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_coverage_to_color GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_fragment_shader_interlock GL_NV_framebuffer_mixed_samples GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_geometry_shader_passthrough GL_NV_gpu_program4 GL_NV_internalformat_sample_query GL_NV_gpu_program4_1 GL_NV_gpu_program5 GL_NV_gpu_program5_mem_extended GL_NV_gpu_program_fp64 GL_NV_gpu_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_memory_attachment GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_path_rendering_shared_edge GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_query_resource GL_NV_query_resource_tag GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_sample_locations GL_NV_sample_mask_override_coverage GL_NV_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_atomic_float64 GL_NV_shader_atomic_fp16_vector GL_NV_shader_atomic_int64 GL_NV_shader_buffer_load GL_NV_shader_storage_buffer_object GL_NV_shader_subgroup_partitioned GL_NV_stereo_view_rendering GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_rectangle_compressed GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_transform_feedback2 GL_NV_uniform_buffer_unified_memory GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_attrib_integer_64bit GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NV_viewport_array2 GL_NV_viewport_swizzle GL_NVX_conditional_render GL_NVX_linked_gpu_multicast GL_NV_gpu_multicast GL_NVX_gpu_multicast2 GL_NVX_progress_fence GL_NVX_gpu_memory_info GL_NVX_multigpu_info GL_NVX_nvenc_interop GL_NV_shader_thread_group GL_NV_shader_thread_shuffle GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent GL_OVR_multiview GL_OVR_multiview2 GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control

N
NotASpeckOfCerealAuthor
Known Participant
March 3, 2020

<bump>

 

I'm now getting an automated request to mark one answer as "Correct", but there have been zero recommendations. Why was this dropped like a hot-potato?

 

If anyone has any ideas, please respond. This has made my work-flow very slow.

 

Chris

 

    dj_paige
    dj_paige
    Legend
    February 24, 2020

    Are you doing a lot of local adjustments (spot healing, brushing) on an image when this happens?

    N
    NotASpeckOfCerealAuthor
    Known Participant
    February 24, 2020

    Yes. In fact, when this came to a head yesterday evening, I was doing a gradient masking (applied a gradient to darken the sky, used the erase brush to mask out buildings, etc.).  I also have a filter going (4 files of 340 images basied on star rating, doing keyframe work). 

    But even when I get out of the gradient editing, any work in the Develop panel is just slow. Right now, while typing this (Lightroom not being in Windows focus), the develop mode went black for a couple of moments and the 2nd monitor disappeared. 

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices