Lightroom Classic: Custom Order lost when slight accidental movement of thumbnail in filmstrip

  • 8
  • Problem
  • Updated 2 months ago
  • Acknowledged
  • (Edited)
When sort order is set to date order, it then changes to custom order each and every time an image is edited in Photoshop
Photo of Nick Harrison

Nick Harrison

  • 60 Posts
  • 10 Reply Likes

Posted 3 years ago

  • 8
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
yeah it happens to me nearly all the time, mine goes to the end sometimes, other times it gets mixed in with a new order and you have to try and find it....when you have a shoot containing about 1000 images it's very frustrating. I'm trying Lightroom alternatives at the moment.

Photo of Jack Line

Jack Line

  • 2 Posts
  • 2 Reply Likes
I also shoot weddings and this is going to really mess things up. Does anyone know why this is happening and how to get back to how things worked before?
Photo of John R. Ellis

John R. Ellis, Champion

  • 5112 Posts
  • 1446 Reply Likes
I think it's unlikely this bug will be addressed until Adobe product developers can reproduce it. Reviewing past posts, two employees and at least two very experienced users have tried but failed. 

If several of you experiencing this bug could post full-resolution screen recordings on Dropbox, Google Drive, Youtube, or similar, showing the full screen with your entire workflow, from selecting a photo to edit in Library grid view, editing it in Photoshop, returning to Library, this could provide more clues about how to reproduce the problem.  (Using Library grid view rather than Loupe view in Library or Develop might provide more clues; but if it only happens in Loupe view, then a screen recording of that would be better than nothing.)
Photo of John R. Ellis

John R. Ellis, Champion

  • 5112 Posts
  • 1446 Reply Likes
The original poster provided two screen recordings, but unfortunately, they're no longer available on Youtube.
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
I will upload one shortly to vimeo.....its a nude image so youtube wont accept it
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 5646 Posts
  • 2256 Reply Likes
> its a nude image so youtube wont accept it

Please bear in mind that this is also a family-friendly site...
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
i will post a link only
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
I manage a goldfinch video.....safe and family friendly

https://vimeo.com/342464270


The other vids on my channel are Art Nude....be careful
Photo of Nick Harrison

Nick Harrison

  • 60 Posts
  • 10 Reply Likes
This is identical to the problem I continually have on the Apple Mac with Lightroom, where I usually have the order set to Capture, but on returning from Photoshop the order changes to Custom, and I have to set it back to Capture Time.  Very frustrating 
Photo of John R. Ellis

John R. Ellis, Champion

  • 5112 Posts
  • 1446 Reply Likes
John, your video has all the clues need to explain what you're observing. (If a picture is worth a 1000 words, a video can be worth ten times that.) Your issue is different than Nick's (the original poster).

You're working in a folder set to Sort: Custom Order. You edit the first file, a raw, in Photoshop and then save that file as a TIFF. LR stacks that TIFF on top of the original raw (you have the option Preferences > External Editing > Stack With Original set). And then that stack moves to the end of the filmstrip.

This occurs because LR always sorts grid view and the film strip by the attributes of the top photo in a stack. When any file gets added to a folder or collection with Custom Order, that file's custom-order position gets set to the end of the folder or collection (e.g. if there are 3 photos in the folder and you add one to the folder, it gets position 4).

Thus, in this situation, the newly added TIFF gets a Custom Order position at the end of the folder, and since it's on top of the stack, the stack gets sorted at the end of the filmstrip. You can verify this by right-clicking the original raw and doing Stacking > Move To Top Of Stack -- the stack moves to the beginning of the filmstrip.

A partial workaround is to set the sort order of the filmstrip to Capture Time or File Name.  Then the stack won't get moved around when you edit, since the newly added TIFF will sort in the same location as the original raw. Of course, if you really want that custom order in your editing workflow, this workaround isn't satisfactory.

I think it would be less confusing for a TIFF created by Photo > Edit In to inherit the Custom Order position from the original.  Then the resulting stack wouldn't jump around in the filmstrip.  You could file a separate feature request for that -- Adobe won't see it buried here. 

Nick, the original poster, observes a different problem: He's editing a photo in a folder or collection (not clear which) with Sort: Capture Time, and after returning to Photoshop the order gets set to Sort: Custom Order.
(Edited)
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
Hi John

No, sorry....all my folders are set to Capture time. They are only set to Custom sort when Lightroom fails as shown in the video. The folder the goldfinch was in was set to Capture before sending it to PS. I'll see if I can get another video showing the 'sort' before edit.
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
The point is.....something is causing the sort to change, I always set it to Capture
Photo of John R. Ellis

John R. Ellis, Champion

  • 5112 Posts
  • 1446 Reply Likes
The video shows Sort: Custom Order before you invoke Edit In. So at least in this case, it's the stacking issue causing the reordering.  A video showing Sort: Capture Time before you invoke Edit In could be helpful, as would starting in Library grid view rather than Loupe view -- that will show more LR settings that are hidden by Loupe view.
Photo of John R. Ellis

John R. Ellis, Champion

  • 5112 Posts
  • 1446 Reply Likes
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
Actually I found something odd.....you dont actually have to send an image to PS for editing, LR seems to change from capture to custom without it. I set all my folders in 2009 to Capture....went back to double check and one has set itself to custom without editing anything.
I will see if I can video it.
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
Well spotted John...so it is, something is changing it, re my last post.
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
Ok definitely the sort is changing without editing, all 2009 folders were at Capture. I reset LR and the folder I last used is now at Custom without doing anything. It's a bit random to try and capture on video but will try tomorrow.
Photo of Nick Harrison

Nick Harrison

  • 60 Posts
  • 10 Reply Likes
To confirm - I work in folders, not collections (importing from folders as set up in Finder, working on the photos contained within, and then archiving afterwards from Lightroom to avoid overloading)
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
I found that it changes from Capture to Custom on clicking an image, got it on video. I just need to edit the useless section of the video. Will post shortly.
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
So 20 seconds into the video you can see the order change on its own, I didn't even click on the image, just hovered the mouse over an image. 

https://vimeo.com/342546452

I didn't even notice it had changed til later, as you can see in the video.
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
Here's another example at 5:00 mins

https://youtu.be/YT63p4ISdis


Photo of John R. Ellis

John R. Ellis, Champion

  • 5112 Posts
  • 1446 Reply Likes
John, can you please post the entire output from the menu command Help > System Info?  I've got some hypotheses based on your recent two videos, and seeing the detailed configuration could help refine them.
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
Sure, here it is :-

Lightroom Classic version: 8.3.1 [ 201905241238-dcd7e2de ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10 - Business Edition
Version: 10.0.17763
Application architecture: x64
System architecture: x64
Logical processor count: 4
Processor speed: 3.4 GHz
Built-in memory: 16336.4 MB
Real memory available to Lightroom: 16336.4 MB
Real memory used by Lightroom: 2455.8 MB (15.0%)
Virtual memory used by Lightroom: 2787.5 MB
GDI objects count: 636
USER objects count: 1867
Process handles count: 2144
Memory cache size: 766.5MB
Internal Camera Raw version: 11.3 [ 197 ]
Maximum thread count used by Camera Raw: 3
Camera Raw SIMD optimization: SSE2,AVX
Camera Raw virtual memory: 1126MB / 8168MB (13%)
Camera Raw real memory: 1129MB / 16336MB (6%)
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 1920x1080
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info: 
DirectX: NVIDIA GeForce GTX 750 Ti (26.21.14.3086)



Application folder: C:\Program Files\Adobe\Adobe Lightroom Classic
Library Path: D:\Users\Fox\Pictures\Lightroom\Lightroom 4 Catalog-2-2-2-2.lrcat
Settings Folder: C:\Users\Fox\AppData\Roaming\Adobe\Lightroom

Installed Plugins: 
1) AdobeStock
2) Facebook
3) Flickr
4) HDR Efex Pro 2
5) Lightroom to Exposure
6) LR/Instagram
7) Nikon Tether Plugin
8) ON1 Effects Standalone 2019
9) SlickPic v5
10) ViewBug

Config.lua flags: None

Adapter #1: Vendor : 10de
Device : 1380
Subsystem : 84bb1043
Revision : a2
Video Memory : 2007
Adapter #2: Vendor : 1414
Device : 8c
Subsystem : 0
Revision : 0
Video Memory : 0
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Speakers (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: 0
GL_BLUE_BITS: 8
GL_DEPTH_BITS: 24
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 2048
GL_MAX_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_UNITS: 4
GL_MAX_VIEWPORT_DIMS: 16384,16384
GL_RED_BITS: 8
GL_RENDERER: GeForce GTX 750 Ti/PCIe/SSE2
GL_SHADING_LANGUAGE_VERSION: 4.60 NVIDIA
GL_STENCIL_BITS: 8
GL_VENDOR: NVIDIA Corporation
GL_VERSION: 4.6.0 NVIDIA 430.86
GPUDeviceEnabled: false
OGLEnabled: true
GL_EXTENSIONS: GL_AMD_multi_draw_indirect GL_AMD_seamless_cubemap_per_texture 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_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_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_robustness 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_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_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_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_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_provoking_vertex 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_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_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object 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_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_NV_blend_minmax_factor GL_NV_blend_square GL_NV_command_list GL_NV_compute_program5 GL_NV_conditional_render 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_float_buffer GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 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_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_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_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_atomic_int64 GL_NV_shader_buffer_load GL_NV_shader_storage_buffer_object 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_NVX_conditional_render 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
Photo of John R. Ellis

John R. Ellis, Champion

  • 5112 Posts
  • 1446 Reply Likes
Thanks. One more question: Are you using a mouse, and if so, do you have a mouse helper utility (e.g. Logitech) installed?
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
it's a mouse...with a mouse button configurator called X-Mouse Button Control 
Photo of John R. Ellis

John R. Ellis, Champion

  • 5112 Posts
  • 1446 Reply Likes
I'm wondering if the combination of mouse, X-Mouse Button Control, and LR is generating spurious mouse click or drag events of very short duration. LR's sort order changes to Custom with very short drags even if they're not large enough to change the actual order. If these drags are short enough, then LR may not have time to generate a noticeable visual indication that the drag has started.

Further, I noticed in the two videos that this happens when you start mousing over filmstrip thumbnails that have three dots in the upper-right corner. The three dots indicate that LR hasn't yet generated a standard-sized preview for the photo. Normally, when you click on such a thumbnail, LR moves that photo to the head of the queue for background preview generation, which can cause a spike in CPU utilization and change both Windows and LR's scheduling of concurrent tasks.  This process might cause timing "races" somehow between X-Mouse Button Control and LR that generate the spurious clicks.

LR's internal architecture has some basic design "gotchas" with respect to concurrent programming (multiple simultaneous tasks), and these sorts of rare races can sneak in even with the most careful programming.  Or it could be a problem solely with X-Mouse Button Control or the mouse driver.  Hard to know from the outside.

Regardless, to determine if this is the cause, I'd suggest using a generic mass-brand mouse (e.g. Microsoft or Logitech) with no extra mouse software installed (i.e. uninstalled, not just disabled).  If the problem doesn't recur, then you know it's somewhere between the mouse hardware and LR. You could go back to your current mouse but no X-Mouse, and then try the generic mouse with X-Mouse installed, and see which combination (if either) generates the problem.

Painful, but that's where the evidence is pointing.
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
I think you could be right there John, I'll try disabling the X-mouse and see what happens. Many thanks for your help and insights :)
Photo of Nick Harrison

Nick Harrison

  • 60 Posts
  • 10 Reply Likes
And would this apply to using a Wacom tablet and pen ? I have never used a mouse with LR (I don’t have one), so it would be difficult/impossible to work without the Wacom. I would hope that such common hardware/software as Wacom does not effect LR in the way we are experiencing
Photo of John R. Ellis

John R. Ellis, Champion

  • 5112 Posts
  • 1446 Reply Likes
The hypothesis is that there's an incompatibility between LR and pointing-device drivers/utilities that causes infrequent, spurious small click-and-drags when you hover the mouse over thumbnails in the filmstrip.   So it's entirely possible that this is the cause of your problems. But so far, it's just a hypothesis that needs to be verified.
Photo of John R. Ellis

John R. Ellis, Champion

  • 5112 Posts
  • 1446 Reply Likes
A possible way to reduce or eliminate the spontaneous switches to Custom Order: Select all the images in grid view or in the filmstrip, do Library > Build Standard-Size Previews, and wait for that to finish before starting to work. 

My hypothesis is that, at least for John McNairn, clicking on a thumbnail that doesn't yet have a preview triggers LR to build one, which causes a spike in CPU usage, which makes the spurious click-and-drag more likely.  Again, just a hypothesis.
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
Is there any way of 'locking' the sort function into Capture Time mode?
Photo of John R. Ellis

John R. Ellis, Champion

  • 5102 Posts
  • 1443 Reply Likes
Unfortunately not. And the sort order isn't exposed to plugins, so it isn't possible to write a plugin that would change the order back automatically.
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
ah well many thanks for your help :)
Photo of Kai Dong

Kai Dong

  • 3 Posts
  • 1 Reply Like
It's funny that two Adobe employees can't reproduce the problem, while so many others have been suffering it for so long time. I don't remember when this problem started to appear, it's been a long time. But it has nothing to do with the pointer device. Recently switched to Wacom tablet from Logitech mouse, it still exists.

However, I found if you let the LR to load all the thumbnails first, then the problem will not occur.
Photo of John R. Ellis

John R. Ellis, Champion

  • 5104 Posts
  • 1444 Reply Likes
Did you have the Logitech utility installed? The bug may not be specific to any one device, but it may be provoked by third-party pointing-device drivers and utilities.
Photo of Nick Harrison

Nick Harrison

  • 60 Posts
  • 10 Reply Likes
Have you tried testing in conjunction with a Wacom tablet to see if this is a factor to eliminate John ??  I have never used a mouse (pointing device), and always used a Wacom (and trackpad) when working in LR.  I have no other way of pointing on my iMac.
For information, the issue has now become a lot worse - the thumbnail order now changes order, away from Capture Time, constantly.  Every time I check, and it can be every few minutes, the order has changed.  There is certainly something bizarre with this situation (and very inconvenient / frustrating)
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
I think the problem is two fold....the sort is changed if long clicked with the slightest of drag, and there is something else going on that isn't easily seen. First thing Adobe should do is remove the long click problem, the sort should only change when the thumbnail in the film strip is completely moved to a new position. This would at least allow a clearer view of the other problem without spurious mouse/pen clicks etc etc.
(Edited)
Photo of Nick Harrison

Nick Harrison

  • 60 Posts
  • 10 Reply Likes
Seems a very sensible way forward and should be simple for Adobe to implement
Photo of John R. Ellis

John R. Ellis, Champion

  • 5104 Posts
  • 1444 Reply Likes
"the sort should only change when the thumbnail in the film strip is completely moved to a new position"

That's a good idea.
Photo of Jerry Syder

Jerry Syder

  • 491 Posts
  • 223 Reply Likes
Yup - it's bizarre the way it currently works. I've gotten used to it and know, almost every time when LR is going to change to custom order when I don't want it to. Yesterday, I highlighted 6 photos and I saw, in the split second that my hand shifted to the right(too much coffee). I then thought to check the sort order and lo and behold, it was changed to custom, so I changed it back to capture time.
Photo of Robert Somrak

Robert Somrak, Champion

  • 706 Posts
  • 221 Reply Likes
I was wondering for a long time why my sort order changed at random.  Thanks John McNairn.  This should be an easy fix for Adobe if they can be convinced it is an issue.
Photo of Kai Dong

Kai Dong

  • 3 Posts
  • 1 Reply Like
Hello John, I do have logitech software running at the background. I cannot disable it because my keyboard is also from Logitech. LOL.
Photo of Kai Dong

Kai Dong

  • 3 Posts
  • 1 Reply Like
Hello John, I do have logitech software running at the background. I cannot disable it because my keyboard is also from Logitech. LOL.
Photo of Lizzy Biggs

Lizzy Biggs

  • 1 Post
  • 1 Reply Like
Even when I have custom order set and take a round trip - edit in photoshop and save and go back to lightroom the picture and its new linked edit jump to the back. Highly frustrating and slows workflow.

Side note after an above comment about why Adobe doesn't seem to care about this issue  - I have friends pushing me to move to work in capture one, I have others telling me Affinity is soon going to be companioned with its version of a lightroom type programme currently under development.

I am highly tempted especially because while powerful I always seem to be waiting for lightroom no matter how far I upgrade my hardware. Task manager isn't showing any core, ram or disk on close to full capacity yet I'm still waiting for lightroom!

Argggg Rant over.

I use Wacom, I use Genius. I don't use any photoshop plugins - i do rely on sorting and editing many photos and need to do this quickly... The jumping is frustrating if there are 1000 photos in a folder/collection from a wedding etc.
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
I agree entirely, very very frustrating. I too am waiting for the Affinity companion, I already have Affinity. Capture one came close but I rejected it because it lacked sufficient export functions. OnOne was strong contender but performance and again export functions were not good enough.
Photo of Nick Harrison

Nick Harrison

  • 60 Posts
  • 10 Reply Likes
This is not a side issue - it is a main issue.  And will lose Adobe customers.  Why have they not resolved this issue now - it has been a problem for many many years, and hinders a myriad of users 
Photo of Paul McLoughlin

Paul McLoughlin

  • 1 Post
  • 1 Reply Like
Me too.... had it for last couple of years at least . The intermittency of it drives me nuts. Come on Adobe ... sort it.  I have a old Wacom attached but never us it. Have tried disconnecting it and problem persists.
We pay a subscription fee and this sort of thing should have been fixed years ago !!. Any body tell me where I can change the sort back to file order rather than capture?

Photo of David Golding

David Golding

  • 138 Posts
  • 18 Reply Likes
Curious, why has no one with the issue simply altered their file naming workflow to rename the photos using the syntax:

YYYYMMDD_hhmmss

And sort by filename, never capture time. Photos edited in PS will still have, perhaps, metadata capture time issues, but that would not effect your sort.

Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
@David is still moves to custom order, doesn't solve anything.
Photo of Nick Harrison

Nick Harrison

  • 60 Posts
  • 10 Reply Likes
Pardon ......  Photos are exported from LR with a specific and relevant filename.  Why would I want to rename in LR prior to exporting, just to keep the image order ??  

And I do think Adobe have not taken Wacom users seriously when looking into this issue
Photo of Robert Somrak

Robert Somrak, Champion

  • 714 Posts
  • 223 Reply Likes
Lightroom might revert to Custom Order even if you have sort by Filename so it wouldn't solve the issue.  Also, renaming all your files seems like an extreme workaround when the easier workaround is to just check the sort on return from Photoshop.  It doesn't happen to everyone and appears random to the ones that is does so I am sure it is a difficult bug to solve.
Photo of bchiles

bchiles

  • 1 Post
  • 0 Reply Likes
Add me to the list too. I've also had this issue for a few years now. Across new computers and fresh installs of Lightroom and PS. My workflow is to star the images I want to keep and work on. I've never tracked the percentage that this happens but I would say at least 50%. 
Photo of George Westlund

George Westlund

  • 2 Posts
  • 0 Reply Likes
The problem also appears, although not consistently, when sorting using ratings in develop module on my last pass to straighten the one's I'm going to export.  I had been sorting, straightening and then turning the sort off after switching to the library module (selecting "None" at the top of the collection window) and that's when I would notice the change to Custom.  I've found that if I turn the filter off with the "switch" before leaving the develop module, it doesn't appear to happen any more.  No external editing tool was used.
Photo of Dace Voit

Dace Voit

  • 5 Posts
  • 3 Reply Likes
I have experienced this off and on for a while.  I can say with confidence that it has to do with the Wacom tablet I have.  The tablet is a new tool for me.  Before, when only using a mouse, the sort order when returning to Photoshop would switch to custom from capture time only if I would change the order of the images before sending the image to Photoshop.  If you move an image around in Lightroom, it automatically changes the sort order to custom.  At least this is my experience.

Now, with the tablet, it has happened most of the time and driving me nuts.  The pen/tablet interface is quite sensitive.  I am having a hard time getting used to the tablet because of this in the first place.  What I believe is happening is when touching the image in lightroom, it moves slightly, perhaps imperceptably, but doesn't actually change the order of the images.  Lightroom, however, see the slight move as an order change and switches the order to custom.  When I go back to using the mouse, the sort order doesn't change.  When I use the pen, it does.

Turning off Lightroom automatically changing to custom order would fix this problem.
Photo of Nick Harrison

Nick Harrison

  • 7 Posts
  • 2 Reply Likes
I think you are right, in that the Wacom tablet may have a contributing part to this infuriating issue.  I have come to this conclusion having read many years worth of comments on the matter.  And I have never used a mouse on my iMac, and always had the problem with Lightroom viewing order

I would have thought it is a simple matter for Adobe to strengthen the choices of viewing order, or simply offering a lock for a particular choice of viewing order, which could be toggled on or off if a change in order is required

Rectifying this issue would save hours and hours for many people during photo editing (post shoot production)

Otherwise, time to look for other photo editing software
(Edited)
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
I have to say I rarely use a tablet and it happens when using the mouse, sadly I have to keep using Lightroom for another year due to a long term project. After that I'm done with it, as much as I like it the problem is nearly constant. I've tried alternative software and some of them are more than viable
Photo of Nick Harrison

Nick Harrison

  • 7 Posts
  • 2 Reply Likes
It is hard to believe that such a simple and widespread issue has not been resolved after so many years of users having to struggle with this handicap
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 7515 Posts
  • 1721 Reply Likes
I find the last couple of comments intriguing. 

We've never reliably reproduced this behavior in testing. Have any of you disconnected your Wacom tablet and then been able to reproduce this - or is it only reproducible with the tablet attached?
Photo of Nick Harrison

Nick Harrison

  • 7 Posts
  • 2 Reply Likes
I do not have a mouse, so have not disconnected my tablet.  But I understand this issue occurs for others who do not use a tablet.  Is there any way that a viewing choice can be locked i.e. on 'capture time' ?  I literally never use any other sort order !

I could try a test without the Wacom, but not very easily, and probably only confirm what others have found and struggled with as well
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
Rikk...seriously? 100% of my actions in Lightroom is mouse related, the capture time order changes at an extremely annoying rate. 
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 7515 Posts
  • 1721 Reply Likes
John, I will rephrase my question to you. Do you have a tablet attached or a Wacom driver installed - regardless of whether you use it or not? 
Photo of George Westlund

George Westlund

  • 2 Posts
  • 0 Reply Likes
I also use mouse only.  However I think I've managed to limit where its happening to filtering while in the develop module.  If I filter in Library, then go into develop to work on the higher rated photos and then back out, the order doesn't change.
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
no...no wacom software.
Photo of Dace Voit

Dace Voit

  • 5 Posts
  • 3 Reply Likes
It happened to me sometimes before I got the tablet.  After I started using the tablet, it happens almost every time.  By saying almost, I mean 99% of the time.  I don't need to unplug the tablet.  I have a mouse also.  When I use the mouse, tablet still plugged in, the problem rarely happens, if at all. 

I agree with Nick, a simple lock to toggle on/off for the sort order would solve this issue.
Photo of Nick Harrison

Nick Harrison

  • 7 Posts
  • 2 Reply Likes
Is there any chance of this Rikk ?
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 7515 Posts
  • 1721 Reply Likes
The chance depends upon getting a reproducible scenario documented that we can pass onto engineering. They can't fix it unless we can show them it is broken. To that end we need specific system information and a step-by-step process for reproducing the behavior reliably. 

As a Lightroom Classic user with 380K images cataloged, I've sent at minimum 6500 images (and probably many more) from Lightroom to Photoshop over the past 13 years.  I recall it happening 1 time about 7 years ago. It hasn't happened to me since.  What does that mean? 
  • I have a workflow that is slightly different and don't encounter it?
  • I have a system configuration that doesn't reproduce the scenario?
  • I have a higher tolerance for this so it ceases to impinge upon my awareness? 
  • All of the above in some combination?
If anyone can give me step-by-step clean steps for reproduction, and I can reproduce the behavior, a bug will be written immediately and then I can escalate it through the channels and the Product manager.  Till that time, I continue to gather data and investigate possibilities. 

In three years, this post has only garnered 6 Me Too votes. It wouldn't hurt to hit the button at the top if you haven't already. 
Photo of Nick Harrison

Nick Harrison

  • 7 Posts
  • 2 Reply Likes
I have given step by step details of the actions I take (in LR & Ps) and the results, which I can repeat for you.  But I am not sure, from what you have said, that this will reproduce the issue on your computer.  Are there any system files or logs that you would find useful ?

I can confirm software and hardware, but this is not always specific, as for example the problem has occurred over many updates of macOS, and also several updates of Wacom drivers (and several updates of LR and Ps software). And to confirm I am currently using the latest versions of all.  I have also tested several levels of sensitivity settings for the Wacom stylus  

To me it all points to a conflict between LR and Wacom software/settings in some way, which is why I wondered if any logs would be of use to you ?
Photo of John R. Ellis

John R. Ellis, Champion

  • 5112 Posts
  • 1446 Reply Likes
I think a trivial change to LR would fix the issue, without needing a reproducible recipe.

Currently, when you select a thumbnail and drag it towards the next photo and release the mouse button before the cursor reaches the border, LR will change the sort order to Custom, even though the order hasn't actually changed. See this screen recording. (Some pointing devices conspire with LR to cause these spurious drags.)

LR should only change to Custom if the order actually changes.
Photo of Nick Harrison

Nick Harrison

  • 7 Posts
  • 2 Reply Likes
Yes, I agree this is probably the main issue

But I do not use a pointer (Wacom stylus) most of the time to pick images, as I use arrow keys to move from one image to another and keyboard shortcuts to open from LR to Ps

The issue also occurs without taking an image into Ps, just during use of LR
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
Here is a video of it happening.....run to 13:00 and you will see the sort change
https://drive.google.com/file/d/1q7yjgLvzM9MhtKnWA9eitVzOUhiiq6zE/view?usp=sharing

Photo of Robert Somrak

Robert Somrak, Champion

  • 714 Posts
  • 223 Reply Likes
Unfortunately the video doesn't show anything about change of sort order after an edit in Photoshop.  I looks like it could be the issue of "bumping" the thumbnail a little and the sort order changes to custom when you don't actually move the photo. I have ran into this issue a few times.  If you click and hold a little too long and move or maybe something to do with the mouse click sensitivity settings then the photo will "bump" just a little and the sort changes.  Adobe should correct this and make it operate where you have to move the photo more than a few pixels to change the sort order.  It is too sensitive now.  
Photo of Robert Somrak

Robert Somrak, Champion

  • 714 Posts
  • 223 Reply Likes
To add to my comment, I didn't see if "bumping" was happening but it happened when you were clicking the filmstrip.
Photo of Dace Voit

Dace Voit

  • 5 Posts
  • 3 Reply Likes
This.  Exactly.
Photo of John R. Ellis

John R. Ellis, Champion

  • 5112 Posts
  • 1446 Reply Likes
"Adobe should correct this and make it operate where you have to move the photo more than a few pixels to change the sort order.  It is too sensitive now."

My proposal is much simpler: The sort order will change to Custom only if the actual order of the photos changes.

Currently, changing the actual order isn't very sensitive and requires a very large mouse movement. In the filmstrip, the mouse has to move 1.5 thumbnails to the left or right. In grid view, it has to move 1.5 thumbnails left or right, or completely outside the current thumbnail moving up or down.

Photo of Robert Somrak

Robert Somrak, Champion

  • 714 Posts
  • 223 Reply Likes
Photo of Robert Somrak

Robert Somrak, Champion

  • 714 Posts
  • 223 Reply Likes
As soon as the black bar between the photo shows up Lightroom assumes a move was made.  I agree with you proposal John, the sort order shouldn't change until an actual change is made.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 7535 Posts
  • 1726 Reply Likes
Robert & John:
It sounds like you two are in agreement that this is not an Edit in Photoshop/return to Lightroom issue. Can we chalk this up to subtle unintended movements in the filmstrip? While Wacom may or may not be involved, its involvement is more likely to be the less precise nature of Wacom hover/drag when working with the filmstrip. 

John McNair & Nick Harrison - are you in agreement with this analysis?
Photo of Robert Somrak

Robert Somrak, Champion

  • 714 Posts
  • 223 Reply Likes
Rikk,

I don't ever recall the sort order changing when returning from Photoshop but I have had the sort order change several time because of moving the photos slightly in the filmstrip.  This happens accidentally and more often when I select photos and start to move them to a collection and change my mind and want to select different photos.  I start the drag, drag back to their original location, let go of the mouse and the sort changes.  As John said, the sort shouldn't change unless you actually move the photos in the filmstrip.  
Photo of John McNairn

John McNairn

  • 29 Posts
  • 10 Reply Likes
Rikk,

The sort change happens a lot and I notice it more when an image returns to lightroom, but it could be that the sort change is done before the image goes to PS for editing. I am thinking that locking down the filmstrip is probably a good start then take it from there.
Photo of John R. Ellis

John R. Ellis, Champion

  • 5112 Posts
  • 1446 Reply Likes
"Can we chalk this up to subtle unintended movements in the filmstrip?"

It does seem that this is a cause of what people are observing here.
Photo of Dace Voit

Dace Voit

  • 5 Posts
  • 3 Reply Likes
Rikk,

"It sounds like you two are in agreement that this is not an Edit in Photoshop/return to Lightroom issue. Can we chalk this up to subtle unintended movements in the filmstrip? While Wacom may or may not be involved, its involvement is more likely to be the less precise nature of Wacom hover/drag when working with the filmstrip. 

John McNair & Nick Harrison - are you in agreement with this analysis?"

This^^^.  I agree with John and Nick.  It's not a Ps issue.  That's just where I noticed the change had occured.  But now I can look in Library after being in Develop and see the change of Sort order has happened before I've sent to Ps.  I have noticed when I tap an image with my pen, sometimes it moves slightly, enough to show the black line when an image is moved.  I don't actually move the image, it's just a slight movement because the pen-tablet interface is very sensitive.

You should be able to recreate this easily by slightly nudging and image but not actually moving it.  I can recreate with a mouse intentionally.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 7535 Posts
  • 1726 Reply Likes
I will log an issue with the team. I have retitled the thread as Edit in Photoshop does not appear to be a contributing factor. 
Photo of Nick Harrison

Nick Harrison

  • 7 Posts
  • 2 Reply Likes
Rikk
I agree that the issue does not necessarily occur due to sending to / returning from Ps, and that it does appear to be down to the sensitivity of the slightest of movements in the filmstrip.  And that this is also irrespective of pointer tool being used (mouse or Wacom stylus pen).
On this basis a reduction in sensitivity, to actually fully moving an image beyond another image, or the application of a lock on the filmstrip sort order choice, would be a logical and much appreciated 
Thank you 
Photo of Dace Voit

Dace Voit

  • 5 Posts
  • 3 Reply Likes
Thanks Rikk!