Skip to main content
Adobe Photoshop Family

6 Messages

 • 

146 Points

Sat, Nov 10, 2018 8:09 PM

Photoshop CC 2019: Adjustment Layer opacity setting carrying over from file to file when retouching multiple files

I have been retouching 3 separate files simultaneously (they're a set of 3 similar photos) and using adjustment layers on them (the AL's are pretty much the same on each photo). I copied and pasted (ctrl+c and v'd) a gradient map AL from one photo to the others. This seemed to trigger a bug that linked the opacity percentage setting on the gradient map AL from photo to photo (example: I would change the gradient map AL to 43% on photo #1, then I would switch over to photo #2 and its gradient map AL was now at 43%). I deleted all of the AL's and created them again, but the bug didn't go away. 

I noticed this bug happening the other day as well when retouching photos of my son (I ctrl+c'd a set of adjustment layers and pasted it onto another photo. The same thing seemed to happen with the color fill AL. The opacity percentage setting would carry over when switching from photo to photo. 

I have done as much as I can including updating to PS 2019 and uninstalling and reinstalling PS. I can do no more on my own, I need help! 

- Emily

Responses

204 Messages

 • 

4.1K Points

2 years ago

Well first of all, going to ps2019 is a big mistake that will cause you even more frustration.

The anomaly you describe does not happen on my ps2018 windoz 7.

Of course the first thing that any adobe rep will advise is to reset your prefs.

6 Messages

 • 

146 Points

2 years ago

That's the thing though, it happened before I updated to 2019. Is there any way I can get CC 2018 back?

204 Messages

 • 

4.1K Points

2 years ago

Yes to get back 2018 you need to open Creative Cloud to see all apps...
Find the Phptpshop app in the list.
Click the arrow next to Install or Open.
A dropdown will appear - click "manage" then "other versions"

You should really check forst if 2018 was overwritten when upgrading... it might still be on your system.

6 Messages

 • 

146 Points

2 years ago

I shall do that. And then, per the inevitable instructions of an Adobe rep, I should reset my prefs. I'll do that too.
I'm going to guess that if this is an actual bug in the program, there isn't much an Adobe rep can do for me, is there?

204 Messages

 • 

4.1K Points

2 years ago

Trouble is what you describe does not happen on my system and I have never heard it mentioned before, I am sure it would have been reported if it was a bug.... are you on Mac?

6 Messages

 • 

146 Points

Nope, windows. Windows 10... ugh. 
Could I have jacked something up by copying my AL's using ctrl+c and ctrl+v?

204 Messages

 • 

4.1K Points

Just tried it on my win10 laptop.. behaves as expected, each adjustment layer opacity remains independently set and does not affect the copy in the other images when changing any instance.

Copy / paste is a straigforward operation cant think of anything that could go wrong there.

6 Messages

 • 

146 Points

It seems to me, interestingly enough, that the problem is happening intermittently. It's happening on some files more than others, and it's not even happening consistently across files. It's as if it's getting stuck, unsticking itself, and then getting stuck again. 

I reinstalled PS 2018, restarted my computer, opened PS 2018 and reset my gradient maps, and it's still happening. I think I'm going to have to reinstall PS 2017. If it's happening their too, I guess I'm going to have to throw this computer in the river and start anew. 

Adobe Administrator

 • 

14.8K Messages

 • 

284.8K Points

2 years ago

Hi Emily, I can't reproduce offhand. Maybe try doing a screen recording showing the behavior. It might help us troubleshoot.

Sr. Product Manager, Adobe Digital Imaging

6 Messages

 • 

146 Points

Screen recording... I'm going to have to figure out how to do that. Stay tuned! :)

I have figured out that it may not have anything to do with PS at all. I have uninstalled and reinstalled PS 2019, 2018, and 2017 and recreated the issue across all three versions. I have reset my prefs, I have restarted my computer, etc etc. I don't think a PS bug would start randomly after years of use and carry across multiple versions of a program. 

Adobe Administrator

 • 

14.8K Messages

 • 

284.8K Points

Yeah, seems odd - but maybe it's certain steps that are triggering it. Finding those reproducible steps are key! Thanks.

Sr. Product Manager, Adobe Digital Imaging