P: High CPU usage makes it unusable during export

26 Votes
LEGEND ,
Oct 31, 2017 Oct 31, 2017

Copy link to clipboard

Copied

After latest Lightroom Classic CC I almost can't work in Lightroom during export as it's using around 90% off mu CPU. Maybe exporting itself is a bit faster but when exporting 2000 pics I'm unable to work for about half an hour as there are huge lags. In the end I would rather prefer slower export working in a background and still have ability to work with pics without such noticable slow down. It was much better balanced before updating to Classic CC.
My CPU: Intel Core i7-6700K (4 cores, od 4.00 GHz do 4.20 GHz, 8 MB cache)

Bug Unresolved
TOPICS
macOS , Windows

Views

718

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
82 Comments
Participant ,
Apr 10, 2020 Apr 10, 2020

Copy link to clipboard

Copied

1. recommend that you turn RAPID mode for this drive
2. do other operations just slow down a bit or does the machine become unusable? Slowdown to be expected as resources are being shared but should not become unusable. 

Votes

Translate

Translate

Report

Report
Community Beginner ,
Apr 10, 2020 Apr 10, 2020

Copy link to clipboard

Copied

Thanks for the rapid mode tip. I have read an article showing that ssd's only give a very minimal performance boost when exporting in Lightroom, even when compared to slow platter drives. Would rapid mode really make much of a difference? Exporting seems to be primarily a cpu intensive task.

https://www.pugetsystems.com/labs/art...

In response to your second question, everything slows down and the cpu is at 100%

Votes

Translate

Translate

Report

Report
LEGEND ,
Apr 10, 2020 Apr 10, 2020

Copy link to clipboard

Copied

"Exporting seems to be primarily a cpu intensive task."

Indeed. I just did a quickie timing and my Macbook Pro exports a large batch of raws to the internal SSD at a rate of about 1 per second, with each exported JPEG averaging 8 MB.   So that's 8 MB per second written to the disk, an order of magnitude less than spinning disks (even cheap ones) are capable of.

Votes

Translate

Translate

Report

Report
New Here ,
Apr 15, 2020 Apr 15, 2020

Copy link to clipboard

Copied

When you are working live tethered in an event and need to export almost live while still capturing and with the client breathing on your neck, wanting both his exports and selecting the live shots, this is unusable and the client laughs at Lightroom or how you have a slow laptop even though you have a 4000$ machine to try and minimize that issue. It is a bug for that use case.

Votes

Translate

Translate

Report

Report
LEGEND ,
Jul 05, 2020 Jul 05, 2020

Copy link to clipboard

Copied

 I've been measuring and it seems that the problem is solved in the latest LR updates.

PC, con CPU: Intel Core i5 6600K a 350 Ghz, RAM: 32 GB, GPU Intel HD Grafic 530 y Windows 10 Pro

C: Samsung ssd 970 evo plus 500gb (operating system and programs)

😧 Kingston HyperX Fury SSD 240gb  (develop Ligthroom).

E: Western digital blue wd5000aakx 500gb (My documents)

F: Western digital blue wd5000aakx 500gb (Retouching Photoshop)

G: Western digital Green wd10earx 1000gb (Finished photo)


It is true that the CPU is at or near 100% when exporting from the Lightroom.


But it automatically drops the % if I'm using other applications:


 Yesterday I measured the export of 1305 ORF (Olympus raw OM-D E-M1 ) to Tif (91 MB) and the time was 41 minutes, while I was stacking with the Zerene Stacker and cleaning with the touch-up brush in Photoshop, no problem.




Votes

Translate

Translate

Report

Report
Participant ,
Jul 05, 2020 Jul 05, 2020

Copy link to clipboard

Copied

Ran a test on my system just for grins. 
 
1304 EM1 raw files 
    tried 1305 but one file was corrupt and 
    didn't see the need to rerun for just 
    one file 
No concurrent tasks 
Xeon 6-core 36/40 GHZ 
 
==== TIFF test ==== 

Image Format: TIFF
Compression: None
Color Space: Adobe RGB 
Bit Depth: 16 bits/component 
Resize: unchecked 
Sharpen: unchecked 
Include: All Metadata 
Watermark: unchecked 
 
12 threads driven with about the same load per thread 
CPU 77-85% 
Memory 6.01-6.08 GB
Disk 108-127 MB/s 
GPU 0% 
 
Duration: 22:05 
Exported Size: 108 GB  
 
==== JPEG test ==== 

Image Format: JPEG 
Quality: 100%
Color Space: sRGB 
Resize to Fit: Dimensions 
Don't Enlarge: checked 
3840x2160 
240 pixels per inch 
Sharpen: Screen 
Amount: Standard 
Include: All Metadata 
Watermark: unchecked 
 
12 threads driven with about the same load per thread 
CPU 74-86% 
Memory 7.4 GB
Disk 16-26 MB/s 
GPU 0% 
 
Duration: 24:58 
Exported Size: 7.63 GB

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jul 06, 2020 Jul 06, 2020

Copy link to clipboard

Copied

Appreciate the testing guys, but I'm still experiencing the same slow downs. 

For example I just exported a few PSDs from RAW files and not only was Lightroom unusable, my music playing in a Chrome tab was cutting out.

Please look at this Adobe, I use Lightroom A LOT and it is not only painful but also makes me less productive.

Votes

Translate

Translate

Report

Report
LEGEND ,
Jul 06, 2020 Jul 06, 2020

Copy link to clipboard

Copied

Absolutely agree that Adobe should fix this.  While waiting for a fix, if you're on Windows you might consider this workaround:
https://feedback.photoshop.com/photoshop_family/topics/classic-cc-uses-90-cpu-during-export?topic-re...

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jul 06, 2020 Jul 06, 2020

Copy link to clipboard

Copied

Hi John, I've tried your batch file with updated paths but nothing runs. I'm on a i7 machine, what would be the hexidecimal mask to use?

Votes

Translate

Translate

Report

Report
LEGEND ,
Jul 06, 2020 Jul 06, 2020

Copy link to clipboard

Copied

Hmm, that .bat no longer works with LR for some obscure reason. I've updated the post to include an alternative that works on my Windows 10 / LR 9.3:
https://feedback.photoshop.com/photoshop_family/topics/classic-cc-uses-90-cpu-during-export?topic-re...

Votes

Translate

Translate

Report

Report
LEGEND ,
Jul 06, 2020 Jul 06, 2020

Copy link to clipboard

Copied

Also, you'll need to find out how many virtual processors your i7 has. Go to Task Manager, click on the Performance tab, and look at the bottom for "Virtual processors".  I suggest changing the .bat file to use 3/4 of the number of total virtual processors. So if you have 8 total processors, change the file to use 6 processors by replacing "7" with "63"; if you have 12 total processors, replace "7" with "511"; etc.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jul 06, 2020 Jul 06, 2020

Copy link to clipboard

Copied

Thanks John, can confirm this is working for me. Computer is definitely more usable but as I expected it doesn't help with my main issue - Lightroom itself is still unusable during exports.

Votes

Translate

Translate

Report

Report
New Here ,
Jul 14, 2020 Jul 14, 2020

Copy link to clipboard

Copied



Exporting and publishing from Lightroom Classic 9.3 on my iMac (27" 5k 2017, 64gb RAM, OSX 10.15.5) renders the machine unusable..   CPU%  has gone over 800% !!!  ter is t
he computer inisorkeytokesn.

Right, I'll try again.  When I'm exporting rom LR Classic 9.3, the CPU usage is going through the roof - so much that I can't even type - the keyboard doesn't recognise half of the keystrokes because the system is running so slowly..  it's awful.  It's been getting slow the last couple of versions..  I've just had to install CPU Setter to limit the process in order to be able to edit this post.  

It's averaging 500-600% CPU resources, but has peaked at over 800%... 

Votes

Translate

Translate

Report

Report
LEGEND ,
Feb 21, 2021 Feb 21, 2021

Copy link to clipboard

Copied

I have the same cursor lag problem while exporting, but it does lag only if i'm into the lightroom app itself; if i go into chrome, while still exporting ofc, no mouse lag at all. This is kind of interesting.. what you guys think?

Votes

Translate

Translate

Report

Report
Community Beginner ,
Feb 21, 2021 Feb 21, 2021

Copy link to clipboard

Copied

Hi Frank, yes Lightroom seems to lower resource usage when another app is focused. Which is great if you want to do other things, but good luck using Lightroom when exporting.

Adobe, any update on the ability to manage CPU usage for exporting? Or at least an export queue like capture one?

One thing I have done recently that is helping: When doing final exports for a project, change your export preset so it does not automatically import the files back into Lightroom. The import process seems to take a lot of resources and is even slower than the export process. I manage the exported files with explorer (or finder for mac users). Both are quite adept at working with the types of files we export from Lightroom.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Feb 06, 2022 Feb 06, 2022

Copy link to clipboard

Copied

During operations such as Photo Merge and Export, I see Lightroom eat 100% CPU and stomp on other running processes. I saw there was an old thread about this issue, but that looks like it's closed due to the forum migration, and I'm still seeing this problem.

 

https://feedback-readonly.photoshop.com/conversations/lightroom-classic/lightroom-classic-high-cpu-u...

 

I'm on Build [202112022200-7fd1f998] running Windows 10 on a i7-9700K with 64GB of RAM.

Easiest way to notice is to have music or something playing through Youtube in the background, and it will cut and stutter during these activities as CPU runs out of headroom to decode the audio/video.

Ideal result would be Lightroom consuming maximum CPU possible without stomping on other processes to the extent of disrupting their functionality.

Votes

Translate

Translate

Report

Report
Adobe Community Professional ,
Feb 06, 2022 Feb 06, 2022

Copy link to clipboard

Copied

So does Photo Merge work despite the CPU report?


Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"

Votes

Translate

Translate

Report

Report
LEGEND ,
Feb 06, 2022 Feb 06, 2022

Copy link to clipboard

Copied

Please post your System Information as Lightroom Classic (LrC) reports it. In LrC click on Help, then System Info, then Copy. Paste that information into a reply. Please present all information from first line down to and including Plug-in Info. Info after Plug-in info can be cut as that is just so much dead space to us non-Techs.

Votes

Translate

Translate

Report

Report
Adobe Community Professional ,
Feb 06, 2022 Feb 06, 2022

Copy link to clipboard

Copied

quote

Ideal result would be Lightroom consuming maximum CPU possible without stomping on other processes to the extent of disrupting their functionality.

 

The easy workaround to do exactly that is to use the Windows Task Manager to lower the priority on LrC to "below normal". During the normal user interactions, you will see no difference since there is normally the CPU usage of the system is well under 100%. During the high CPU times, LrC will consume all the CPU time not used by other apps while allowing them to run normally.

 

Votes

Translate

Translate

Report

Report
LEGEND ,
Feb 07, 2022 Feb 07, 2022

Copy link to clipboard

Copied

Usually, LR uses about 85 - 90% of total CPU for intensive operations like exporting, leaving enough CPU for interactive use. But as you've seen and experienced, there have been a fair number of reports over the years of LR using 100% CPU.

 

Given that this problem hasn't been addressed in the five years since it was first reported, I recommend that you consider workarounds.  You could create a .bat script containing this line to start LR at low process priority, as suggested by @ManiacJoe:

start "Lightroom" /low "c:\Program Files\Adobe\Adobe Lightroom Classic\Lightroom.exe"

 

I recall some reports that this didn't help that much.  If it doesn't work well for you, then instead of changing priority, restrict LR to use at most 6 of your 8 processor cores:

start "Lightroom" /affinity 3f "c:\Program Files\Adobe\Adobe Lightroom Classic\Lightroom.exe"

 

This ensures there will always be 2 cores available for non-LR tasks.

Votes

Translate

Translate

Report

Report
LEGEND ,
Feb 07, 2022 Feb 07, 2022

Copy link to clipboard

Copied

Votes

Translate

Translate

Report

Report
Community Beginner ,
Feb 07, 2022 Feb 07, 2022

Copy link to clipboard

Copied

Yes, Photo Merge, Import, Export, etc all work. They just noticeably stomp on other processes. I appreciate the community help in finding workarounds as well, but figured it was worth adding my experience to the list in case we can ever get Adobe's attention on this issue.

 

Lightroom Classic version: 11.1 [ 202112022200-7fd1f998 ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10 - Business Edition
Version: 10.0.19044
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 3.6GHz
SqLite Version: 3.36.0
Built-in memory: 65454.8 MB
Real memory available to Lightroom: 65454.8 MB
Real memory used by Lightroom: 6389.4 MB (9.7%)
Virtual memory used by Lightroom: 27665.1 MB
GDI objects count: 1109
USER objects count: 2878
Process handles count: 3477
Memory cache size: 15673.3MB
Internal Camera Raw version: 14.1 [ 993 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 10297MB / 32727MB (31%)
Camera Raw real memory: 10373MB / 65454MB (15%)
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 2560x1440, 2) 2560x1440
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info:
DirectX: NVIDIA GeForce RTX 2080 (30.0.14.7212)

 

Application folder: C:\Program Files\Adobe\Adobe Lightroom Classic
Library Path: C:\Users\jltd9\Pictures\Lightroom\Lightroom Catalog-v10-v11.lrcat
Settings Folder: C:\Users\jltd9\AppData\Roaming\Adobe\Lightroom

Installed Plugins:
1) AdobeStock
2) Facebook
3) Flickr
4) Nikon Tether Plugin

Config.lua flags: None

Adapter #1: Vendor : 10de
Device : 1e87
Subsystem : 37af1458
Revision : a1
Video Memory : 8010
Adapter #2: Vendor : 1414
Device : 8c
Subsystem : 0
Revision : 0
Video Memory : 0
AudioDeviceIOBlockSize: 1024
AudioDeviceName: $$$/dvaaudiodevice/SystemDefaultAndEffectiveDeviceName=System Default - Headphones (2- FiiO K5 Pro)#{comment}DVAAU-4201250: Open the audio hardware preferences page.
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 44100
Build: LR5x38
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: NVIDIA GeForce RTX 2080/PCIe/SSE2
GL_SHADING_LANGUAGE_VERSION: 4.60 NVIDIA
GL_STENCIL_BITS: 8
GL_VENDOR: NVIDIA Corporation
GL_VERSION: 4.6.0 NVIDIA 472.12
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_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_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_NV_memory_object_sparse 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_NV_timeline_semaphore 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_compute_shader_derivatives GL_NV_conditional_render GL_NV_conservative_raster GL_NV_conservative_raster_dilate GL_NV_conservative_raster_pre_snap GL_NV_conservative_raster_pre_snap_triangles GL_NV_conservative_raster_underestimation GL_NV_copy_depth_to_color GL_NV_copy_image 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_barycentric 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_mesh_shader 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_representative_fragment_test GL_NV_sample_locations GL_NV_sample_mask_override_coverage GL_NV_scissor_exclusive 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_shader_texture_footprint GL_NV_shading_rate_image 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

Votes

Translate

Translate

Report

Report
Community Beginner ,
Feb 07, 2022 Feb 07, 2022

Copy link to clipboard

Copied

Thanks for the help on workarounds. I've tested the 6 core workaround and that seems to be working fairly well for me right now, though it makes launching a bit more annoying since I can't pin a shortcut to the .bat to my taskbar for some reason, at best adding it to my lightroom taskbar icon for right click access.

Votes

Translate

Translate

Report

Report
LEGEND ,
Feb 07, 2022 Feb 07, 2022

Copy link to clipboard

Copied

"I can't pin a shortcut to the .bat to my taskbar for some reason"

 

This method worked for me:

https://www.easytechguides.com/pin-a-batch-file-to-the-taskbar-or-start-menu-in-windows-10/#windows-...

Votes

Translate

Translate

Report

Report
LEGEND ,
Feb 07, 2022 Feb 07, 2022

Copy link to clipboard

Copied

I recently wrote, "Given that this problem hasn't been addressed in the five years since it was first reported..."

 

LR 11.2 was just released, and its splash screen suggests the problem may have been at least partially fixed in 11.2:

johnrellis_0-1644300270864.png

 

There's no mention of this in the release notes (yet).

 

@David23026570qggd, let us know how much 11.2 addresses the issue for you.

 

Votes

Translate

Translate

Report

Report