893 Messages
•
13.7K Points
Thu, May 25, 2017 9:18 AM
Solved
Lightroom CC 2015.10.1: Develop module: Target Adjustment Tools not working
Bonjour à tous, suite à la mise à jour de LR CC 2017.10.1 je m’aperçois d'un petit soucis qui pourrait s'avérer fort gênant :
- Développement, mode normal, Courbe de tonalité, activation de cette option, on active la correction "sur l'image" par déplacement du curseur, tout est OK.
- Développement, Epreuvage, création d'une copie virtuelle, Courbe de tonalité, activation de cette option, on active la correction "sur l'image" par déplacement du curseur, le curseur n'est plus fonctionnel ?
Remarquez, la barre sous l'image n'apparaît plus non plus quand on active cette fonction.
Si on passe à nouveau en mode "Normal" sans épreuvage ou vers une autre photo, le comportement normal de cette fonction ne revient pas :( Il faut relancer LR.
J'ai rechargé la version 2017.10, ce bug n'existe pas :(
Donc Adobe à ajouté un bug en plus des corrections......
macOS 10.12.5.
Hello everyone, following the update of LR CC 2017. 10. 1 I realize a little worry that could prove very troublesome:
- Development, normal mode, Tone curve, activating this option, the correction on the photo is activated by moving the cursor, this is OK.
- Development, SoftProofing mode, creation of a virtual copy, Tone curve, activation of this option, the correction on the photo is activated by moving the cursor, the cursor is no longer functional?
Notice, the bar below the image no longer appears when you activate this function.
If you switch back to 'Normal' mode without proofing or to another photo, the normal behavior of this function does not return :( LR must be restarted.
I reloaded version 2017. 10, this bug does not exist :(
So Adobe added a bug in addition to the fixes. . . . . .
MacOS 10. 12. 5.

- Développement, mode normal, Courbe de tonalité, activation de cette option, on active la correction "sur l'image" par déplacement du curseur, tout est OK.
- Développement, Epreuvage, création d'une copie virtuelle, Courbe de tonalité, activation de cette option, on active la correction "sur l'image" par déplacement du curseur, le curseur n'est plus fonctionnel ?
Remarquez, la barre sous l'image n'apparaît plus non plus quand on active cette fonction.
Si on passe à nouveau en mode "Normal" sans épreuvage ou vers une autre photo, le comportement normal de cette fonction ne revient pas :( Il faut relancer LR.
J'ai rechargé la version 2017.10, ce bug n'existe pas :(
Donc Adobe à ajouté un bug en plus des corrections......
macOS 10.12.5.
Hello everyone, following the update of LR CC 2017. 10. 1 I realize a little worry that could prove very troublesome:
- Development, normal mode, Tone curve, activating this option, the correction on the photo is activated by moving the cursor, this is OK.
- Development, SoftProofing mode, creation of a virtual copy, Tone curve, activation of this option, the correction on the photo is activated by moving the cursor, the cursor is no longer functional?
Notice, the bar below the image no longer appears when you activate this function.
If you switch back to 'Normal' mode without proofing or to another photo, the normal behavior of this function does not return :( LR must be restarted.
I reloaded version 2017. 10, this bug does not exist :(
So Adobe added a bug in addition to the fixes. . . . . .
MacOS 10. 12. 5.
Problems
•
Updated
3 years ago
33
36
Helpful Widget
How can we improve?
Tags
No tags available
Responses
yvonne_richard
4 Messages
•
112 Points
4 years ago
LR CC.10.1 After saving from PS and coming back to LR, in the Develop module, HSL, the target adjustment tool is not available. If I click on it, I get the zoom loupe.
0
0
jonathan_levy_ko1hnfjr0q92l
7 Messages
•
154 Points
4 years ago
0
0
yvonne_richard
4 Messages
•
112 Points
4 years ago
0
0
peter_vancar
2 Messages
•
90 Points
4 years ago
0
0
mcmorrison
2 Messages
•
72 Points
4 years ago
0
0
andy_delgiudice
33 Messages
•
676 Points
4 years ago
0
0
ellisvener
23 Messages
•
550 Points
4 years ago
The t.a.t. does work for targeted tone curve adjustments.
EDIT: and now the t.a.t. control in the H/S/L panel is back to working. The only thing I did was move from Lightroom to Chrome to write my note and then I went back inot into Lightroom. Very strange.
0
0
Rikk
Adobe Administrator
•
9.2K Messages
•
128.3K Points
4 years ago
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.
Quality Engineering - Customer Advocacy
4
mcmorrison
2 Messages
•
72 Points
4 years ago
Do you think we are talking weeks or months till the next update?
Thanks, Michael
0
0
steve_gandy
237 Messages
•
4.7K Points
4 years ago
This problem surfaced for me after updating to 2015.10.1. I've seen it on my iMac and my MacBook Air. One of my clients asked about it recently as well.
Quickly, on going to the Dev Module and opening the HSL/Color/B&W panel the targeted tool will not be selected. The cursor remains set to the zoom tool. It appears to be a bit intermittent. Just now it happened 3 out of 4 times as I tried to isolate the problem. If you click between the Sat, Hue, and Luminance you can get the tool to activate but I can't figure out the exact work around.
Anyone else seeing this?
Note: This conversation was created from a reply on: Lightroom 6: HSL target adjustment tool does not work.
--Steve Gandy - stevegandy.com/photography
0
0
Rikk
Adobe Administrator
•
9.2K Messages
•
128.3K Points
4 years ago
Hi folks,
I have the problem. I am working on a MacBook Retina (2013 vintage) running OS 10.12.5 and LR 2015.10.1 with CR 9.10.1.
I just updated my OS because after updating LR with OS 10.11 I started to get the blanked out side panels.
If I use the HSL TAT tool and then use the Detail panel select zoom tool, the zoom tool can turn into the TAT or turns into the enlarge cursor. The TAT in the Tone Curve panel is also affected.
The solution seems to be to go back to the HSL panel change HSL mode, and then turn on and turn off the TAT.
I have reset Preferences but the problem persists.
Any help would be much appreciated.
Questions cheerfully answered.
Henry
Note: This conversation was created from a reply on: Lightroom: Using HSL Adjustment with arrows stops working.
Quality Engineering - Customer Advocacy
0
adam_geldhof
4 Messages
•
102 Points
4 years ago
There is a bug I discovered in LR. When adjusting HSL levels using the adjustment up/down arrow (as opposed to the sliders) the up/down arrow stops working when leaving the Develop module going to the Library module than back to the Develop module. The only workaround is to restart the LR program.
0
0
sargon_kelaita
1 Message
•
64 Points
4 years ago
0
0
JeffreyTranberry
Adobe Administrator
•
15.9K Messages
•
295.2K Points
4 years ago
Sr. Product Manager, Adobe Digital Imaging
9
0
protagonisto
40 Messages
•
516 Points
4 years ago
POSSIBLE WORKAROUND...
As many of us already know, The TAT (targeted adjustment) tool isn't working properly in the latest release (2015.10.1 / 6.10.1). Somehow Adobe broke it in this latest release.
For those of you that don't already know, there's a workaround. Just adjust the UI so you're only displaying one TAT at a time instead of all three. This workaround has worked 100% of the time since Adobe introduced the bug in the latest upgrade.
Hopefully Adobe engineers will get around to fixing this quickly. I would also be nice if Adobe could share the depth and breadth of testing performed before certifying and approving the upgrade to the public.
Cheers,
~Paul
0