Luminous Landscape Forum
Raw & Post Processing, Printing => Adobe Lightroom Q&A => Topic started by: Eric Brody on May 24, 2017, 05:26:24 pm
-
I just upgraded Lightroom and Camera Raw per the Creative Cloud app. It seemed to be working just fine on my MacBook Pro, but then I tried using the targeted adjustment tool as I have done for years. Instead of showing me the tool to raise or lower the adjustment, e.g. saturation or luminance, for example, it went to the + button to zoom the image. Also I was able to select all THREE of the targeted adjustment tools! I rebooted the machine and tried again, it worked properly with the first image I selected but then would not work properly at all as I just noted.
It may be just me, but my sense is that this may be a bug?
I'd like to hear of others' experience with this.
Thanks.
Eric
-
FWIW, I trashed LR from my MacBook Pro SSD, went to my trusty backup disk with Carbon Copy Cloner, and copied LR (previous version) from the backup I made two days ago to the MacBook Pro SSD. It appears to be working satisfactorily. It's good to be a backup fanatic :-)
The working version is Adobe Lightroom [1111918], build 1111918 from the get info on the application.
Eric
-
They are aware of the issue. It has happened to me several times.
jed
-
Joy! Another Lr update with yet another new bug.
-
::)
Hmm.. Maybe that's why I don't see the update.. Maybe they pulled it, for now??
Anyway.. Thanks for letting us know! I'll now be sure to create a restore point before trying to update, if/when it shows up here. I'll be sure to test out this TAT issue right away.
-
I am unable to duplicate this behavior in CC2015.10.1 with OSx 10.12.5. Both Target Adjustment Tools (Tone Curve and HSL) are functioning normally on my MBPr in Soft Proof mode. We will need to get more information from you to see if we can isolate the issue.
Can you provide more details please?
-
Rikk, thanks for speaking up. With your report I got over my reluctance to update and did it. I've seen no problems with T.A.T. either.
Mac OS 10.12.5
Mid 2012 MBP Retina
8GB RAM
256 GB SSD
-
I have not seen any issues either since updating yesterday.
MacBook Pro (Retina, 15-inch, Mid 2015
2.5 GHz Intel Core i7
16 GB 1600 MHz DDR3
AMD Radeon R9 M370X 2048 MB
Intel Iris Pro 1536 MB
Cheers!
Stu
-
Thanks for the replies. After seeing that other people had no problems, I went back and tried a bunch of things, from uninstalling and reinstalling LR, (ended up with the 2015 version!) to uninstalling all of it, from the Creative Cloud through Photoshop. The behavior is quite bizarre. Episodically it will work, then a few minutes later, it's back to the plus sign and no TAT.
There must be something wrong in the depths of my laptop. Still afraid to do my Mac Pro desktop but it's not really critical to my work so I'll wait for a while.
Only jedbest seems to have had a similar experience. I'd love to hear more from him. Not sure how to proceed since I've uninstalled and reinstalled multiple times to no avail, even had a failure to install event. If all else fails I'll call Adobe but have not had wonderful experiences in the past when doing that.
Eric
-
I too have this problem with the targetted adjustment tool for the tone curve and the HSL/Color adjustments and it also affects the selection of the detail window selection point.
Frequently (but not always) the cursor is just the hand and clicking zooms the image rather than the required function. I have not found any pattern to this as yet. Restarted several times no change, tried enabling/disabling graphic processor no change.
Running Retina 5K, 27-inch late 2015 iMac with 4GHz i7, 8GB memory, 500GB SSD AMD Radeon R9 M395 2MB and MacOS Sierra 10.12.5.
-
What's being reported with the + and weird behavior sounds like a memory leak or something that really impairs performance as well. May I ask if this happens only after you've been doing a lot of "editing" in Lr?
-
Hi Ron, In answer to your question, it happens right away, with the first image I pull up. I know this because trying it has been the first thing I do after uninstalling and reinstalling. I just decided to go back to LR 2015.10 until this sorts out. It appears that GerryinAus has the same problem. It's peculiarly reassuring that someone else has had the same problem, so maybe I'm not crazy after all.
-
More info, FWIW. Since it's so easy to go back, just trash the LR program and copy the older version from a older backup, I decided to upgrade my Mac Pro 2013 (64GB RAM, 3.5 GHz 6-Core Intel Xeon E5, Sierra 10.12.5), and the problem recurred. These machines share only the same wifi router, they have and have never been physically connected. So... same problem on two different machines albeit running the same OS X version and with everything else regarding Creative Cloud essentially the same.
Thanks for any thoughts from Adobe wizards or others?
Eric
-
Eric, you're definitely not imaging things. This sounds like a bug. Not easy to reproduce except on certain machines though.
By any chance are you using GPU acceleration in Lr?
-
Hi Ron, I just checked and I am, is it worth trying again with it off?
Thanks.
Eric
-
Hi Ron, I just checked and I am, is it worth trying again with it off?
Thanks.
Eric
It seems like it's always worth experimenting with turning Graphics Acceleration off in Lightroom. If you do have it turned off I believe it's sometimes turned on again after updates.
Good luck with your issues.
-
For me the graphics processor has been nothing but heartaches. Then again my machines are getting a bit long in the tooth. I have it OFF on both of my Macs. Works well on my wife's new 27" 5K iMac though.
-
Hi Ron, In answer to your question, it happens right away, with the first image I pull up. I know this because trying it has been the first thing I do after uninstalling and reinstalling. I just decided to go back to LR 2015.10 until this sorts out. It appears that GerryinAus has the same problem. It's peculiarly reassuring that someone else has had the same problem, so maybe I'm not crazy after all.
I was able to experience the T.A.T. funky cursor problem. I clicked on the T.A.T. then moved the cursor over the image and ouila the cursor was the + cursor. I clicked back to different things in T.A.T. dialogue box and back over the image and after a couple of tries it returned to normal.
This isn't right.
-
I was able to experience the T.A.T. funky cursor problem. I clicked on the T.A.T. then moved the cursor over the image and ouila the cursor was the + cursor. I clicked back to different things in T.A.T. dialogue box and back over the image and after a couple of tries it returned to normal.
This isn't right.
Yes, I've experienced this too and it's a real pain in the butt. I use this tool a lot and to have to deal with this new (negative) behaviour is very frustrating.
-
Hmmm.... any chance that others experiencing the T.A.T. tool issues are using 2 monitors? I am.
-
Single monitor. Also, it was episodically episodic, as in it reverted with a restart but then came back, definitely unreliable. I'm sticking with 2015.10 until the next update or until we hear of a fix from Adobe.
-
Have you submitted a bug report to Adobe?
-
We've since been able to reproduce the issue and have a bug filed for it.
-
Thanks so much Rikkflohr. It's nice to know Adobe is aware of the problem. I had not yet filed an official bug report. It's good to know Adobe pays attention to this forum.
Eric
-
We've since been able to reproduce the issue and have a bug filed for it.
Thanks, Rikk !!!
-
Sorry for not following this conversation but I have been away from the internet. I had filed a bug report with Adobe as soon as 6.10.1 was publicly available. In the interim, I uninstalled the program, ran disk utility on my Macbook Promand reinstalled LR. So far all is working. If the problem reappears, I will let the group and Adobe know.
Jed
-
Just fired up my laptop and the bug has reappeared.
Jed
-
I know that Rikk Flohr stated that Adobe is aware of the T.A.T. issue, but I need to add that I just now started having this issues.
It would work just fine with the first image after booting up Lightroom, however went to the second image and the issue started.
Hope Adobe comes up with a fix ASAP as this issue is becoming a real pain now.
---------------------------------------------------------------------------------------------
Just happened to find a temporary solution on this forum that this person posted:
https://www.lightroomforums.net/threads/problems-with-the-adjustments-in-the-develop-module-tat-tool.31129/
"If I want to use HSL and Luminance is marked (for example) and it doesn't´t work, I can choose any of the other two (Hue or Saturation) over and over again alternatively and almost every time it starts working normally and I can choose the one I need to go on working with"
----------------------------------------------------------------------------------------------
I did give it a try and it seems to work. At lease I don't have to keep rebooting.
Cheers,
Stu
-
This is really becoming a comedy of errors lately. Although it's not very humorous.
While I do not expect ANY software update to achieve pure perfection, this bad habit of introducing nearly as many new bugs that are squashed is indicative of a deeper problem ... unsatisfactory testing before release.
Adobe has not offered a public beta program in quite some time, because they don't need to, they have a multitude of pay-to-play beta testers more than willing to continue as lab rats so they don't have to invest the time and effort into proper testing.
I remember clearly that one of the selling points when CC was first introduced was that updates/upgrades would be delivered when they were ready ... not pushed out the door prematurely before they were properly vetted and tested. What are subscribers paying for when they must avoid updates until the early adopters give the all clear, or constantly roll back to known working versions? It's an extremely frustrating situation.
-
I totally agree !!!
This is really becoming a comedy of errors lately. Although it's not very humorous.
While I do not expect ANY software update to achieve pure perfection, this bad habit of introducing nearly as many new bugs that are squashed is indicative of a deeper problem ... unsatisfactory testing before release.
Adobe has not offered a public beta program in quite some time, because they don't need to, they have a multitude of pay-to-play beta testers more than willing to continue as lab rats so they don't have to invest the time and effort into proper testing.
I remember clearly that one of the selling points when CC was first introduced was that updates/upgrades would be delivered when they were ready ... not pushed out the door prematurely before they were properly vetted and tested. What are subscribers paying for when they must avoid updates until the early adopters give the all clear, or constantly roll back to known working versions? It's an extremely frustrating situation.
-
Simplest solution, for now...
On the assumption that one has an uncontaminated backup, at least with a Mac, just trash the new version, (simply drag the Lightroom application icon to the trash), then copy the old, 2015.10 release back onto the boot drive. I've not seen anything in the release notes that makes upgrading essential for most of us.
I hope the nice folks at Adobe will fix this soon. I remain puzzled that some machines have the problem and yet some folks report no issues. Also it is hard to understand how such a significant problem with such a commonly used tool as the TAT escaped the notice of the engineers.
Eric
-
Also it is hard to understand how such a significant problem with such a commonly used tool as the TAT escaped the notice of the engineers.
Eric
Engineers aren't the likely issue. How did it pass test? Did it fail during testing but was relegated to a very low priority that allowed it to be shipped? That's what things looked like when I was writing code. No one wants to ship a bug but the decision to ship is rarely in the hands of the engineers.
Disclaimer: I have no idea what Adobe's development and test processes are.
-
On the assumption that one has an uncontaminated backup, at least with a Mac, just trash the new version, (simply drag the Lightroom application icon to the trash), then copy the old, 2015.10 release back onto the boot drive. I've not seen anything in the release notes that makes upgrading essential for most of us.
True ... it is easy enough to backtrack and relatively few users would be in dire straights by sticking with a prior version ... but ... which version of bugs or workarounds are we supposed to revert to? There are some with each release.
What of the user who recently purchased one of the newly supported cameras that were brought into the fold by this recent update that were hoping to finally get off the DNG conversion workaround? when these issues have become so commonplace for the past several updates where does it end?
Don't we users deserve more forethought and consideration? After all, if we as CC subscribers MUST share our monetary support month after month, year after year, from here to eternity ... shouldn't Adobe be expected to hold up their end of the bargain? Why does only one side of the equation receive a pass for their failure to hod up their part of the deal?
I have been in business as a self-employed photographer/graphic designer for over 40 years. Over those decades I have had issues and mistakes. Some of my own making. Some the fault of others in my employ or that provided service to me. In all cases, I was the one who had to make it right with my customers. I had no alternative but to accept the responsibility for the mistake and make it up to my clients. If I didn't, they could quite easily seek out other options. I just don't get why Adobe should get more leeway than any other business.
Ideally, if Adobe insists upon such a lackadaisical pre-release testing policy, it may be much more wise to issue new camera RAW and lens profile support updates separately. I doubt that including support for the new Sony A9 cause the TAT code to break.
-
Disclaimer: I have no idea what Adobe's development and test processes are.
Agreed, we don't know the internal policies and/or the decision making behind each update version release. However, the results speak for themselves.
-
I was wondering what was happening with this issue so went to the Adobe Lightroom forum and found some discussions not unlike those here at https://feedback.photoshop.com/photoshop_family/topics/lr-cc-2015-10-1-develop-modul-softproofing-mode-tones-curve-activation.
The good news is that it will be fixed with the next LR update, the bad news is that there's no ETA on that. Here's the quote from RikkFlohr,
"Official Response
At this time a fix for the Target-Adjustment-Tool (TAT) issue will be waiting for the next Lightroom update.
In the interim, to avoid the issue you have two options:
1. Use Manual Controls rather than the TAT. The Tone Curve and Adjustments (HSL) panels should function normally in CC2015.10.1/6.10.1.
2. Revert to Lightroom CC2015.10/6.10 if the TAT is critical to your workflow. Reversion requires an uninstall of Lightroom and a manual install of the 6.0 version and then the 6.10 patch. See this document for links to the files: https://helpx.adobe.com/lightroom/kb/lightroom-downloads.html . You will need to enter your License Key or Adobe ID appropriately for your license after installation.
Resetting Preferences and restarting Lightroom will temporarily restore the tool to functionality but are temporary measures that will likely not last a session.
There are reports that toggling repeatedly between Hue/Saturation/Lightness will restore the TAT tool functionality but it is only temporary.
Any updates on this issue will be posted here.
Please note: this is a Mac-only issue. Windows TAT should be unaffected.
I do not have an ETA to share on the update yet"