Downgraded to El Capitan from macOS Sierra today, because of this notorious Tone Curve bug and everything is fine. The problem with hitting the edge of the screen when "Adjust ... by dragging in the photo" exists but is not that bad. For me it seems like for now LR6 is NOT compatible with macOS Sierra and is still having big issue with shadows reproduction in El Capitan as well (https://feedback.photoshop.com/photoshop_family/topics/tone-curve-still-broken-in-lr-cc2015-8) ... View more

Downgraded to El Capitan from macOS Sierra, because of notorious Tone Curve bug Lightroom CC 2015.8: Tone curve still broken in | Photoshop Family Customer Community and this problem exists. So this is El Capitan and Sierra issue for me and again, the only good working is for DEVELOP module with "Use Graphics Processor" switched ON - but it's hard to use because of flickering issues. Really don't like the this bug and I wonder if Adobe will give me my money back when I will have to downgrade to Yosemite to work with LR5.7 which was last good working version for me and the only reason of buying LR6 was a promise of this problem solved. ... View more

I have posted this info of the problem in a still existing from LR5 days topic "Lightroom 5: ICC Table Profiles clipped shadows under OSX" Lightroom 5: ICC Table Profiles clipped shadows under OSX | Photoshop Family Customer Community ... View more

Writing from forums.adobe.com because Jao vdL suggested me to do so. Updated to 6.8 version of Lightroom and problem exists on very dark images: STILL: "When "Use Graphics Processor" switched ON: Develop is OK (same as Soft Proofing), Library is NOT"Use Graphics Processor" switched OFF: Develop and Library are NOT and have clipped shadows  I would get over it (even with bug in Library, which still should not be present), but can't have to have "Use Graphics Processor" switched ON because of occasional flickering." I use default "Display" profile, but it also is not working on any other profile and software calibration which Apple provides. Suggesting that this is a bad monitor profile is bit tricky, because it seams that LR6 is not working on out of the box configuration of my MacBook (MBP mid 2015, AMD Radeon R9 M370X 2048 MB without external monitor).  The problem is that for me Adobe solved this problem only for DEVELOP module with "Use Graphics Processor" switched ON. In every other option problem still exists, mainly in LIBRARY module - which means that the problem is linked not only to the graphic card processing chain, but to the way macOS Sierra/LR6 interprets ICC profiles. The funny thing is that the same RAW files in Finder's QuickLook are displayed as they should, and also in Capture One, but not in LR6. spec: macOS Sierra, MBP 15 (mid 2015), 16 GB RAM, AMD Radeon R9 M370X 2048  MB ... View more

Jao cdL: D Fosse is right, I use default "Display" profile, but it also is not working on any other profile and software calibration which Apple provides. Suggesting that this is a bad monitor profile is bit tricky, because it seams that LR6 is not working on out of the box configuration of my MacBook (MBP mid 2015, AMD Radeon R9 M370X 2048  MB without external monitor). The problem is that for me Adobe solved this problem only for DEVELOP module with "Use Graphics Processor" switched ON. In every other option problem still exists, mainly in LIBRARY module - which means that the problem is linked not only to the graphic card processing chain, but to the way macOS Sierra/LR6 interprets ICC proofiles. The funny thing is that the same RAW files in Finder's QuickLook are displayed as they should, and also in Capture One, but not in LR6. ... View more

Actually the  hysteresis  problem exist not only for Tonal Curve. Just try using  "Adjust ... by dragging in the photo" from HSL/Color/B&W close to TOP or BOTTOM edge of the screen and adjust accordingly. It will adjust as long as you will not hit the edge! I think it is a general engine problem of calculating change of cursor position by it's relation to the screen area instead of using raw mouse/trackpad data. ... View more

Updated to 6.8 version of Lightroom and problem exists on very dark images: STILL: "When "Use Graphics Processor" switched ON: Develop is OK (same as Soft Proofing), Library is NOT "Use Graphics Processor" switched OFF: Develop and Library are NOT and have clipped shadows I would get over it (even with bug in Library, which still should not be present), but can't have to have "Use Graphics Processor" switched ON because of occasional flickering." ... View more

I wish I could confirm that but it wouldn't be true... First of all... it's MUCH better - thank you for that. But (unfortunately) the fix is not fully working, at the start it works smooth and as it should, but after the moment of adjusting the curve my mouse hits invisible wall on the right side of curve area. It seams like Lightroom is still sending some data to macOS (not all, just from time to time) about cursor position changes and when they accumulate enough to hit the right border of the screen the invisible wall on curve area appears - because mouse can't go any further. In LR5 (even on macOS Sierra) problem does not exist, because when you hit the curve area it looks like macOS somehow ignores mouse moves and not letting it to reach the screen border after a while of constant adjusting. In general, it looks like there were a conflict between mouse position on curve area and general mouse position (from OS point of view) and now LR is just reading general mouse position which is limited by screen borders. WORKAROUND (can't believe I still have to look for workarounds ;P): - making smaller adjustments and not "going crazy" on curve area OR resize LR window so the curve area is further from the border of the screen Guys, let me know if you can confirm that. ... View more

I can confirm the problem. macOS Sierra and using Tone Curve is almost impossible, very frustrating... Same with brush sizes. Waiting for Adobe to see this problem and solve 😕 ... View more

Yes, updated 6.7 version. Standard monitor profile (MBP Retina) - was always good before capitan/sierra. Now: When "Use Graphics Processor" ON: Develop OK (same as Soft Proofing), Library NOT OFF: Develop and Library NOT I would get over it (even with bug in Library, which still should not be present), but can't have to have GP ON because of occasional flickering. ... View more

macOS Sierra, Lightroom 6.7 and bug exist in Library module and Develop (if Graphics Processor turned OFF) ... View more

macOS Sierra, Lightroom 6.7 and bug exist in Library module and Develop (if Graphics Processor turned OFF) ... View more

macOS Sierra, Lightroom 6.7 and bug still exist in Library module and Develop (if Graphics Processor turned OFF) ... View more

Lightroom 6.7 with same bug still present (macOS Sierra).Turning off "Use Graphics Processor" helps only in Develop module, but Library module still wrong. ... View more

D Foss - after your post  I've bought Lr6 and was happy that this problem is no more... but after two days of working the problem came back with no reason :/. Now I have macOS Sierra, brand new Lightroom 6 which is useless to work with my dark photos and I have lost 80 euro to be in the sam place. EDIT: just found out one thing. The problem exist when user turns OFF "Use Graphics Processor" in Preferences>Performance. I have to turn OFF this option because my pictures flickers when editing. So now I have to choose between flickering or bad shadows. Does anyone knows where to report that? ... View more

macOS Sierra and still the same issue with clipping shadows in Lightroom... only way to work is to use Soft Proofing Can anyone in Adobe do something with that? It's ridiculous and from client point of view it does not matter if it's Apple's or Adobe's fault. Would be really great if this two big companies work together to solve such problems which makes pros unable to work 😕 ... View more