Skip to main content
Adobe Photoshop Family

34 Messages

 • 

450 Points

Fri, Nov 4, 2016 4:46 PM

Photoshop CC 2015, 2017: Will not "Merge Visible"

Use of "Merge Visible" into a new layer is not functioning right.
The keyboard command is, Shift+Option+Command+E. (Control for PC)

This "Merge Visible" SHOULD create a new Layer that contains visible items.
NOTE: (CS6 does this without any problems)

The idea or use is to turn off all layers that need not be visible and merge into a final layer product WITHOUT merging all layers.
This is extremely useful when masking and compositing.

I discovered that CC will not allow this, in fact Shift+Command+E is not working properly either.
IF.... you make a duplicate layer of a layer that has a mask and select both those layers, you can get it to work. (if you wish to call that "working")
HOWEVER.... if you turn off unneeded layers and select all layers neither Shift+Option+Command+E OR Shift+Command+E functions properly. (no reaction)

Tested on Mac Pro running latest version of OSX Yosemite and verified on two separate computers. (not a computer hardware problem)
At the moment, I have not tested Mavericks or El Capitan but will later.

Responses

Champion

 • 

623 Messages

 • 

14.6K Points

4 years ago

You can replicate by doing a Copy Merged and paste... two hotkeys instead of one, but it gets the job done:

cmd-a

cmd-shift-c

cmd-v

34 Messages

 • 

450 Points

4 years ago

Your response is non-sequitur / irrelevant.
Merge Visible is a keyboard command that is not working.

My message has nothing to do with "Copy Merged".
I specifically defined "Merge Visible".
Who cares about using 3 keys instead of four,???? AND... Shift+Command+E is the same number of keystrokes.

I am specifying a software Bug.
A proven software bug that does not exist in CS6 but is a bug in CC.

Thank you for the response, but the response is not helpful or useful.
Working around a software bug does not solve the bug.

Champion

 • 

623 Messages

 • 

14.6K Points

I was trying to help un-block your workflow, not dismiss your post or say it was not a bug.

It was absolutely relevant to YOU as a potential way to be productive in spite of the reported bug and it was not a non-sequitur since it mimics the end result you are trying to achieve UNTIL SUCH TIME as the bug can be addressed.

But if you are more interested in lashing out and complaining than looking for practical solutions, I can't stop you.

"Who cares about using 3 keys instead of four,???? AND... Shift+Command+E is the same number of keystrokes." - Merge Visible was a single hotkey combo. My workaround requires 3 different hotkey combos. Less convenient. Thus I was implying that it was less desirable as a solution and the bug should still be fixed.

34 Messages

 • 

450 Points

Very odd response.
Nobody "lashed out", there was no emotion implied or inferred.
Odd how some people assign their own emotions to statements.
Those were certainly not my emotions nor my intent.
Obviously your mind reading skills need some work.
Suggest not reading minds at all. (it is after all, impossible)
I am a physicist not a politician.
Professionals such as myself find no need to spew forth opinions or emotions or psychological judgments.
An apology for your accusation and false judgment is in order.

Champion

 • 

623 Messages

 • 

14.6K Points

Apology accepted. No hard feelings.

34 Messages

 • 

450 Points

Sadism accepted.

34 Messages

 • 

450 Points

Thank you for liking my comment.
I accept the sadism that has become so common.
It includes malice, disrespect, denigration, obfuscation, and outright lies.
What I don't hear is, I was wrong, or I'm sorry.
Easiest to say, "sadism accepted".
Does not imply appreciated or condoned or practiced.
I must simply accept the behavior that become so common.
I do not deserve it, but... merely accept it. (or should I say expect it?)

2 Messages

 • 

70 Points

Robert Boyle you're right, I have the same problem in photoshop about merging visible layers. Indeed having one layer about what I see on the screen. Some changes are not here after, and a comparison between the before and after merging (Alt+COntrl+Shift+E) shows there is a difference and I don't understand why!Does someone have an explanation and a solution to get this final layer correct?

396 Messages

 • 

6.5K Points

4 years ago

Am not saying your doesn't work but I just tried it in 2017 with a 34 layer file and it worked fine. have you tried a preference rest?

2K Messages

 • 

35K Points

4 years ago

It's been working without fail on both my computers running Yosemite and El Capitan. I use it all the time. It does sound like, from the various threads, that this update really wants us all to start off by deleting our preferences or it will throw oddities at us.

78 Messages

 • 

1.4K Points

4 years ago

Not sure if it works this way in CS6, but as long as I have a visible layer selected PS 2017 will merge all visible layers. If my selected layer is not marked as visible, the "Merge visible" is grayed out.. I don't have CS6 to check.

34 Messages

 • 

450 Points

4 years ago

Thanks to all for the responses.
To answer, I tried Reset Preferences with no change.

To be a bit more specific...
I have a file with a Background, 2 non masked layers, and 1 masked layer.
4 layers total.
I select all layers.
I turn off the non masked layers and attempt to Merge Visible onto a new layer.

This fails every time in CC and using the exact same file on the exact same computer and version of OSX it works every time flawlessly in CS6.
(tested on two different DESKTOP Macs for verification)

The strange part is...
If I duplicate the masked layer and repeat the keyboard command it works.
I also created a layer and filled it with black, then... masked the whole thing. (basically a new transparent layer)
This also works.
It seems that for Merge Visible to work in PS CC you must have more than one masked layer.
This is not true for CS6.
That IS... a Bug.
Essentially I cannot use Merge Visible unless there is more than one masked layer.
That will never do.

To witness this bug, you would have to do exactly as I described. (exact same file setup)
If this is not done as defined, the bug will not appear.

34 Messages

 • 

450 Points

4 years ago

EXTRA NOTE:
As an experiment I tried making a new transparent layer in my file / layer setup. (as defined previously)
If I add a transparent layer I can use PS CC Merge Visible new layer. (Shift+Option+Command+E)
This does not eliminate the obvious bug. (does not exist in CS6)

It seems that PS CC will NOT Merge Visible unless, there is more than one layer with a mask or transparency.

This presents itself as a bug because I often Place files into my PS projects that have no transparency then create a Merge Visible layer as a template (of sorts) and save the layers in Groups for future alterations.

Before somebody mentions it...
The "equivalent" of Merge Visible can be created as an independent File with Export File.
This makes a mess of folders and eats up HD space of course.
Merge Visible is far more useful and organized.
(really don't want to detail the reasons to use Merge Visible, suffice to say, it is Very Useful)

2K Messages

 • 

35K Points

4 years ago

> I have a file with a Background, 2 non masked layers, and 1 masked layer.
4 layers total.
I select all layers.
I turn off the non masked layers and attempt to Merge Visible onto a new layer.>

I tried that. Perhaps if you show us a screenshot of your exact layers? Because I created a file with 4 image layers, one a background, one a masked layer. I could either select them all, turn off the 2 without a mask, then use the Stamp Visible command, or I could do as I usually do, simply turn off the layers I don't want to include, target the top visible layer, then invoke Stamp Visible.

I can't recall ever being able to Stamp Visible if the top layer selected was turned off. Perhaps we could at one time. But while it may be changed behavior, I don't see it as a bug since you don't want the invisible layers to contribute to the stamp visible layer, so there's really no point in selecting it in the first place. If your invisible layer is at the top of the stack, you'll have to drag the stamp visible layer to the top if that's where you want it, but I don't quite see why that would be too difficult to handle.

So perhaps I'm still missing something, which is why attaching a screenshot here of your layers panel before you attempt to create a Stamp Visible layer would be helpful.

34 Messages

 • 

450 Points

4 years ago

Good suggestion.
This will take me a bit of time but I can make screen shots of both CC and CS6 using / invoking Merge Visible. (be patient please)

Just for sake of conversation...
Did you try Merge Visible on the file you set up?
Did it work?

2K Messages

 • 

35K Points

4 years ago

> Just for sake of conversation...
Did you try Merge Visible on the file you set up?>

I created a Stamp Visible layer (named so in History, not the Layers panel), so long as the topmost targeted layer was visible. If the topmost selected layer was invisible, then no, the command won't work. As I said, I don't recall if or when it ever did if the top targeted layer were invisible.

I can be plenty patient. I'm interested. And frankly, I really can't remember how CS6 worked. It's been way too long since I used it—but come to think of it,  I reinstalled it to help someone who was using CS6, and I don't think I uninstalled it. Nope, I haven't, and my file still works so long as the topmost selected layer is visible, and doesn't work if it's invisible. Nor do I have to target more than the topmost visible layer to get the command to work.

So I'm seeing the same behavior in 2017 as in CS6.

34 Messages

 • 

450 Points

4 years ago

Thanks again.
I do not use Merge Visible (to my best recall) if the top layer is invisible.
Guess I should try that.

My purposes do not make use of Stamp Visible at least for now.
I use Merge Visible as shown in the Help Manual. (with Option key added to create a new layer)
CS6 works, CC does not. (tried both 2015 and 2017)

Obviously I have found a way around this bug by adding a transparent layer or another masked layer.
But that does not solve the bug.

Should have some screen shots late tomorrow if I don't get distracted.
Us gray haired old retirees tend to get side tracked quite a bit.

2K Messages

 • 

35K Points

4 years ago

> My purposes do not make use of Stamp Visible at least for now.>

I find Merge Visible a confusing term. What it means is to merge the visible layers into one layer. Only with the Option/Alt key does it mean to leave all the original layers alone and duplicate them, merged, onto a new layer. That's why the History state for that is Stamp Visible. So we're talking about the same thing. I'm just trying to ensure we're not talking about merging all visible layers into a single layer, although that shouldn't require two masked layers to work, either.

> Obviously I have found a way around this bug by adding a transparent layer or another masked layer.>

That just seems odd. That's why I'm wondering what layers you're dealing with and in what order.

> Us gray haired old retirees tend to get side tracked quite a bit.>

I understand. <G>

34 Messages

 • 

450 Points

4 years ago

I am not using the History to produce a Merge Visible.
I am talking about merging all visible layers into a layer.
The only difference is the Option key added to the keyboard command.
(I am using OSX / Mac)
Merge is Command+E
Merge Visible is Shift+Command+E
Merge Visible onto a new layer is Shift+Option+Command+E

Those commands are very important when defining this CC bug.
As with all software problems, no changes or alterations can be made when checking for the bug.
I am a hardware engineer who did R&D for the government.
When it comes to software bugs (endless) the software engineer ALWAYS blames the hardware first.
This behavior persists today in the consumer industry and especially customer help.
It's always the computer hardware that is blamed first.

To prevent this, I double and triple check before reporting a bug.
This includes test on multiple computers both with same hardware and different hardware.
Then... if possible... I test against alternate versions of the software. (most "upgrades" contain bugs)

I will get screen shots prepared today, However... Merge Visible is the test and bug I am defining.
(not Stamp Visible)
The screen shots will not help in any way but they will show the test that defines the bug.

2K Messages

 • 

35K Points

4 years ago

> I am not using the History to produce a Merge Visible.
I am talking about merging all visible layers into a layer.
The only difference is the Option key added to the keyboard command.>

I'm sorry. I seem to be assuming too much. Open the History panel, set up the layers, do what you do to Merge Visible with the Option key held down, then look at the history panel state, the action you just performed. It will say "Stamp Visible." I forget that not everyone works with the History panel open and spends a lot of time looking at it, as I do.

Merge Visible is indeed the name of the command, and the Alt/Option modifier key does alter the results of the command. But as you can see, terminology when merely written can begin to confuse the reader. The History State names the action "Stamp Visible," while merely using the Merge Visible command, with or without using the keyboard shortcuts, names the action "Merge Visible." Try it.

34 Messages

 • 

450 Points

4 years ago

I understand completely.
However... modifying the software test causes a failure of the test.
My thread excludes ALL other tests or workarounds.
The idea is Not to find a workaround, it is to define a problem with a specific part of the software and no other.
You did a lot of work providing these images, my many thanks and respect.
See next post.