Dave, Thanks for responding! I know you don't work for Adobe—I didn't mean to imply that. You just seemed to have some pertinent knowledge so I figured I'd ask (in case you or anyone else viewing this thread could shed some light). As I mentioned, I thought I was running the latest PS version (I generally install updates as soon as I see them), but when I encountered the issue—and after rebooting my Macbook—I then checked for updates and saw there was one. I applied the update, but the issue persisted. Wasn't until I turned off Open CL that the tool started working again. Just to re-iterate, it had literally just worked fine with Open CL ON on the first photo I edited, then the second photo is when I encountered the issue. I hadn't even closed the previous photo before I started on the second one (something I usually do to try and keep color adjustments consistent in photo sets), so absolutely nothing had changed on my system—the tool just stopped working suddenly. That said, I'm definitely running the latest PS version, now. I'm also running OS X El Capitan 10.11.6—haven't migrated to Sierra yet because I wanted to give Adobe time to patch any issues first. If anyone is running Adobe PS CC on Sierra, I'd be interested to know how it's working. I used to work on Windows, where I never had any real problems with Photoshop (not to say there weren't any, I just never encountered them in my workflow). Wasn't until I moved over to a Mac that I started noticing little things here and there not working—most of which I've just gotten used to working around, but nothing like this where a tool/function just completely stops working at all, right in the middle of an edit, no less. Anyways, if anyone knows anything about this topic/issue, it would be great to know what might be the cause of such an issue, so I can try to avoid it. Frankly, if I was in Terry's (the most recent comment on this thread) position, I'd be pretty ticked off right about now. At least turning Open CL off worked for me—Terry seems to be having the same issue, but caused by something else perhaps. That's even more disturbing, because there could be something else at play that we don't know about. Of course, each system (computer) is different, so it could be something local to the machine, but without knowing what to look out for, there doesn't seem to be a good way to be proactive about avoiding such a problem. Thanks again and good luck to anyone else having this issue! Hopefully, some light will be shed on this at some point or Adobe will find/fix the bug (if indeed it is one). Jeremy
... View more