Skip to main content
alanterra
Inspiring
December 8, 2016

P: Tone curve still broken in

  • December 8, 2016
  • 95 replies
  • 3002 views

The bug that I reported here has not been squashed in the latest Lightroom.

The problem is hysteresis in the response of points on the tone curve control when following mouse movements.

If you drag a point (say, the white point) in the Tone Curve and move it back and forth, after a few drags you will not be able to put the point back in the upper right corner of the response panel.

The underlying cause is that (a) the point does not move directly with the cursor (LR hides the cursor so you can't see this, but when you let go of the mouse button you will see that the cursor does not align with the point, (b) as you drag, the relationship between the cursor position and the point changes, when the point hits the right edge of the box and the cursor continues to the right, then when you move the cursor back to the left it does not "pick up" the point at the same location that it "left" the point, and (c) the (invisible) cursor is limited by Mac OS to stay on the screen.

The work-around (which is not perfect), is to make your Lightroom window smaller so that there is more space beyond the right edge of the window, so the hysteresis effect doesn't show up as quickly. If you have 2 screens, you can move the Lightroom window to the left screen, which effectively solves this problem.

I assume that this problem occurs for all four edges of the Tone Panel, but because the Tone Panel is on the right hand side of the Lightroom window, the effect is seen mostly when trying to move a point on the tone curve to the right hand side of the panel.

If this is not clear, let me know, and I'll see if I can post a video.

[Edit -- I just confirmed this bug for the top edge of the Tone Curve as well.]

This topic has been closed for replies.

95 replies

Participating Frequently
February 8, 2017
Yes Carlos, the LR implementation of curves isn't a tool I like to use. It' just makes it harder to get what you want compared to curves in any other software.
Carlos_Oliveras
Known Participant
February 8, 2017
As somebody already said previously, I think there is a mix up between people who is complaining about a specific bug, and people like me who just doesn't get what's the point in implementing a curves UI in such a weird an "unique" way. Specially when there's the tried and true Curves panel from Photoshop, Camera Raw and even other software that just allows us to place and move points along the curve without stepping into an alternate space-time warping reality as soon as we perform a mouse click.
For other people, maybe this method has some kind of added value, but for me... I'm almost unable to do anything with LR's curves and keep my blood pressure levels below a healthy threshold. Maybe I'm too "spoiled" because I spent to much time in ACR/PS... 😞
alanterra
alanterraAuthor
Inspiring
February 8, 2017
In response to Oscar's comments, let me reiterate my request that Adobe just copy the tone curve interface from Photoshop. In the Photoshop interface you can select a point. This allows you to use the keyboard arrows to tweak the curve by 1/256, and to use the delete key to get rid of a point. In Lightroom you can't use the arrows, and to delete a point you have to do an annoying right (control) click and select from a pop-up menu to delete a control point.

Why Adobe would abandon a well-designed interface to implement something much less effective is beyond me.

But this is something I see in Apple's software all the time. Some programmer says to him/her self "Hey, some really smart people spent a lot of time figuring out a user interface for a problem. I bet I can come up with something much better." Answer: you usually can't, but it gets implemented anyway because the new programmer is in charge.
Inspiring
February 8, 2017
You're not picky. I've got the same problem. Moving point to the left and down is fluent and very predictable,  but moving them right or up is soo hard and annoying. It's simply impossible to adjust point just like you want.  As you said,  the problem appeared few updates ago. On the very beginning, I was thinking that maybe my mac is full of junk but after clean install of OS the problem persists.
Participant
February 8, 2017


Hello!

This is not a bug I am guessing. I just want to show my dissatisfaction with the accuracy/control of the curve points.
The points haven't always had bad accuracy for me, it started a few updates ago (not sure which one).

My problem is that I am working with very small margins (I am picky about colours) and sometimes i just need to move the points one step up, down, left or right, but this is now very hard to do immediately every time, like I used to be able to do (even though it was't perfect back then either). Making small movements with both my mouse and trackpad the points wont move at all up and to the right, while to the left and down it moves right away (and often to much).

Anyone else have thought about this? I am afraid I am just very picky and others don't see this as a big problem, but for me this really is a huge deal since I am working a lot with curves.

If it helps I am using a macbook retina from 2015 with a force click touchpad and my very beloved Logitech MX518. I have more problem with my mouse than with my trackpad, but both makes a terrible job at controlling the points.

By the way, sorry for making an account just to come and address this problem. I really love lightroom aside from this! ❤️
Inspiring
February 3, 2017
I'm glad to learn that it's not just me. I have the same problem when trying to move points on a curve with my mouse or trackpad. 2012 retina MacBook Pro with macOS Sierra 10.12.3 and up-to-date Lightroom CC.
sageb62028076
Participant
January 27, 2017


In the latest versions of Lightroom CC, when trying to tweak individual points in the curves section, it's almost impossible to move your point a small adjustment without it freaking out.  I'm running OSX and it happens when using both my mouse and trackpad.  It never used to be like this in older versions of LR.
Inspiring
January 18, 2017
I have a bit different problem with tone curve. No matter of position of LR on the screen, when I move point to the left or down, everything seems to be alright.  But when I try to move it up or right, mouse seems to be 100 times less sensitive - I have to scroll it like few centimeters on the desk to make a small move on the screen.  And when I move mouse with same speed as I do to the left or down, it simply does nothing. I can slide trough whole desk with no affect on the curve.  As I said, it does not depend on the position of the point on the curve or position of LR on the screen, it's always like that and it was to me from the very beginning of the sierra on my mac.   Even after clean install.

Lightroom version: CC 2015.8 [ 1099473 ]
License: Creative Cloud
Operating system: Mac OS 10
Version: 10.12 [2]
Application architecture: x64
Logical processor count: 8
Processor speed: 2,3 GHz
Built-in memory: 16 384,0 MB
Real memory available to Lightroom: 16 384,0 MB
Real memory used by Lightroom: 1 614,7 MB (9,8%)
Virtual memory used by Lightroom: 2 509,0 MB
Memory cache size: 518,3 MB
Maximum thread count used by Camera Raw: 8
Camera Raw SIMD optimization: SSE2,AVX
Displays: 1) 1920x1080

Graphics Processor Info: 
Check OpenGL support: Failed
Vendor: Intel Inc.
Version: 4.1 INTEL-10.22.25
Renderer: Intel HD Graphics 4000 OpenGL Engine
LanguageVersion: 4.10


Application folder: /Applications/Adobe Lightroom
Library Path: /Users/arturjarosz/Pictures/Lightroom- kluby i zlecenia/Kluby i zlecenia.lrcat
Settings Folder: /Users/arturjarosz/Library/Application Support/Adobe/Lightroom

Installed Plugins: 
1) Aperture/iPhoto Importer Plug-in
2) Canon Tether Plugin
3) Nikon Tether Plugin

Config.lua flags: None

AudioDeviceIOBlockSize: 512
AudioDeviceName: HDMI
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 48000
Build: LR5x4
CoreImage: true
GL_ACCUM_ALPHA_BITS: 0
GL_ACCUM_BLUE_BITS: 0
GL_ACCUM_GREEN_BITS: 0
GL_ACCUM_RED_BITS: 0
GL_ALPHA_BITS: 8
GL_BLUE_BITS: 8
GL_DEPTH_BITS: 24
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 2048
GL_MAX_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_UNITS: 8
GL_MAX_VIEWPORT_DIMS: 16384,16384
GL_RED_BITS: 8
GL_RENDERER: Intel HD Graphics 4000 OpenGL Engine
GL_SHADING_LANGUAGE_VERSION: 1.20
GL_STENCIL_BITS: 8
GL_VENDOR: Intel Inc.
GL_VERSION: 2.1 INTEL-10.22.25
OGLEnabled: true
GL_EXTENSIONS: GL_ARB_color_buffer_float GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_instanced_arrays GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_provoking_vertex GL_ARB_seamless_cube_map GL_ARB_shader_objects GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shadow GL_ARB_sync GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_non_power_of_two GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_transpose_matrix GL_ARB_vertex_array_bgra GL_ARB_vertex_blend GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_window_pos GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_clip_volume_hint GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_draw_buffers2 GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample 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_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture_array GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc GL_EXT_texture_env_add GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod_bias GL_EXT_texture_rectangle GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_timer_query GL_EXT_transform_feedback GL_EXT_vertex_array_bgra GL_APPLE_aux_depth_stencil GL_APPLE_client_storage GL_APPLE_element_array GL_APPLE_fence GL_APPLE_float_pixels GL_APPLE_flush_buffer_range GL_APPLE_flush_render GL_APPLE_object_purgeable GL_APPLE_packed_pixels GL_APPLE_pixel_buffer GL_APPLE_rgb_422 GL_APPLE_row_bytes GL_APPLE_specular_vector GL_APPLE_texture_range GL_APPLE_transform_hint GL_APPLE_vertex_array_object GL_APPLE_vertex_array_range GL_APPLE_vertex_point_size GL_APPLE_vertex_program_evaluators GL_APPLE_ycbcr_422 GL_ATI_separate_stencil GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_ATI_texture_mirror_once GL_IBM_rasterpos_clip GL_NV_blend_square GL_NV_conditional_render GL_NV_depth_clamp GL_NV_fog_distance GL_NV_light_max_exponent GL_NV_texgen_reflection GL_NV_texture_barrier GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod
alanterra
alanterraAuthor
Inspiring
January 6, 2017
Now that these two threads have been merged, I encourage everyone to read my original post, which suggests some (partially successful) work-arounds, while we wait for Adobe to squash this bug.
Participant
January 6, 2017
Here is my quick video demonstrating the problem:
https://www.youtube.com/watch?v=j3Kus4pEm5U