Difficulty setting black and white levels in Tone Curve

  • 1
  • Problem
  • Updated 2 years ago
  • Acknowledged
Merged

This conversation has been merged. Please reference the main conversation: Lightroom 2015 curves bug

This is the same bug as I reported in the forums, but with the hope that an Adobe employee might notice and confirm. It seems different than this bug, but they may both be a result of the same code change.

If I grab the white level (top right gray point) in the curve and drag, my mouse disappears, and as I drag around, I quickly "run out of room" to drag, and I can no longer drag the point to the right. When I let go of the mouse button, my mouse reappears on the screen, and it turns out to be on the edge of my screen. If you play with this control, you will quickly see that Adobe has disconnected the mouse position with the dot position (presumably to allow finer control), but when you run into the edge of the screen, you can't move the dot any farther in that direction.
Screen Shot 2016-12-05 at 121214jpg

If you move the right edge of your window away from the edge of the screen, then you regain more control (although you can still "run out of space") but at the cost of a smaller image to judge the effects of your edits. There is some hysteresis so that as you drag to the right, and then drag back to the left, the mapping of cursor location to point on the curve keeps moving farther and farther to the right, ensuring that sooner or later you will run past the edge of the screen.

I so much prefer Photoshop's curve control, where you can use the arrow keys and can type in numbers to set the x & y position.

Lightroom CC 2015.7. Macintosh iMac 5K. 

Photo of Alan Harper

Alan Harper

  • 426 Posts
  • 84 Reply Likes

Posted 2 years ago

  • 1
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1452 Posts
  • 454 Reply Likes
Photo of Alan Harper

Alan Harper

  • 426 Posts
  • 84 Reply Likes
Thanks, Simon. That is the problem. Of course, I searched throughout the Adobe forums for previous reports and responses, but neglected to search the "Community Powered Support" or else I probably would have seen this. I'll see if the shift key is a work-around.

This conversation is no longer open for comments or replies.