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

  • 1
  • Problem
  • Updated 3 months ago
  • (Edited)
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.
Photo of Robert Boyle

Robert Boyle

  • 34 Posts
  • 1 Reply Like

Posted 2 years ago

  • 1
Photo of Max Johnson

Max Johnson, Champion

  • 450 Posts
  • 208 Reply Likes
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
(Edited)
Photo of Robert Boyle

Robert Boyle

  • 34 Posts
  • 1 Reply Like
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.
Photo of Robert Boyle

Robert Boyle

  • 34 Posts
  • 1 Reply Like
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.
Photo of Max Johnson

Max Johnson, Champion

  • 443 Posts
  • 205 Reply Likes
Apology accepted. No hard feelings.
Photo of Robert Boyle

Robert Boyle

  • 34 Posts
  • 1 Reply Like
Sadism accepted.
Photo of Robert Boyle

Robert Boyle

  • 34 Posts
  • 1 Reply Like
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?)
Photo of SOS Blog

SOS Blog

  • 2 Posts
  • 0 Reply Likes
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?
Photo of John Maguire

John Maguire

  • 398 Posts
  • 83 Reply Likes
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?
Photo of Cristen Gillespie

Cristen Gillespie

  • 1261 Posts
  • 323 Reply Likes
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.
Photo of David Fabian

David Fabian

  • 76 Posts
  • 18 Reply Likes
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.
Photo of Robert Boyle

Robert Boyle

  • 34 Posts
  • 1 Reply Like
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.
Photo of Robert Boyle

Robert Boyle

  • 34 Posts
  • 1 Reply Like
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)
Photo of Cristen Gillespie

Cristen Gillespie

  • 1261 Posts
  • 323 Reply Likes
> 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.
Photo of Robert Boyle

Robert Boyle

  • 34 Posts
  • 1 Reply Like
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?
Photo of Cristen Gillespie

Cristen Gillespie

  • 1261 Posts
  • 323 Reply Likes
> 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.
Photo of Robert Boyle

Robert Boyle

  • 34 Posts
  • 1 Reply Like
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.
Photo of Cristen Gillespie

Cristen Gillespie

  • 1261 Posts
  • 323 Reply Likes
> 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>
Photo of Robert Boyle

Robert Boyle

  • 34 Posts
  • 1 Reply Like
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.
Photo of Cristen Gillespie

Cristen Gillespie

  • 1261 Posts
  • 323 Reply Likes
> 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.
Photo of Robert Boyle

Robert Boyle

  • 34 Posts
  • 1 Reply Like
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.
Photo of Robert Boyle

Robert Boyle

  • 34 Posts
  • 1 Reply Like
SOLUTION
It seems that the keyboard instruction set in CC has changed from CS6.
In CS6 the command to Merge Visible into a new Layer is Shift+Option+Command+E.
The changes in the keyboard commands have changed slightly in CC.
Merge Visible into a new Layer in CC is... Option+Command+E.

Apparently the addition of Shift to the keyboard command causes CC to Merge LAYERS (plural) that have masks or transparencies.
IF... your file setup contains only 1 layer with a mask or transparency (as mine did) the command fails to function because the addition of Shift is seeking More Than One Layer with a mask or transparency.

The solution to Merge Visible without resorting to History or Stamp Visible or Copy / Paste visible is...

Option+Command+E
(Alt+Control+E for lemons aka. PC's... since we must not compare Apples to Lemons... humor)

NOTE:
If you have more than one layer with a mask or transparency, then the keyboard command to Merge Visible into a new layer in CS6... AND... CC is:
Shift+Option+Command+E
Photo of Cristen Gillespie

Cristen Gillespie

  • 1261 Posts
  • 323 Reply Likes
>> Apparently the addition of Shift to the keyboard command causes CC to Merge LAYERS (plural) that have masks or transparencies.   IF... your file setup contains only 1 layer with a mask or transparency (as mine did) the command fails to function because the addition of Shift is seeking More Than One Layer with a mask or transparency.>>

No, it doesn't do that here. It won't merge the layers into each other no matter they have masks or any other transparency if you use Cmd-Opt-Shift-E.

However, what you are now coming up with is different yet again. In this instance, you can merge visible layers into a duplicate layer so long as you aren't attempting to merge a Background layer with a layer that does or does not have transparency. IOW, this command won't work with a single visible layer somewhere above a Background layer.

In fact, I am seeing something I think might be a bug. With Cmd-Opt-E, if I have a Background layer in the mix, it stamps the layers onto the Background layer (and the History panel names the action Stamp Layers). If I have a Layer 0 instead of a Background layer, it in fact leaves both layers alone and creates a new composite layer above the top selected layer.  This is unexpected behavior, so possibly a bug.

Further, this Stamp Layers command only works if you have selected all the layers you want to duplicate merged to a new layer.  It won't work as Cmd-Opt-Shift-E (Stamp Visible in the History Panel) does by merely highlighting the layer you want the Stamp Visible layer to be above. Take a look at the highlighted layers. This is quirky, to say the least. Cmd-Opt-Shift-E is quite stable here, and you only need one layer with or without transparency. The intervening invisible layers can be full image layers, or have transparency.

So are we thoroughly confused by now? I'm still seeing no change in behavior with Cmd-Opt-Shift-E. Cmd-Opt-E is a bit weird. Cmd-E  and Cmd-Shift-E also still function as expected. I'm still inclined to think there is an issue with your installation, corrupted preferences or something—either that or you have managed to construct a situation I can't follow from your written description of the setup.





Photo of Robert Boyle

Robert Boyle

  • 34 Posts
  • 1 Reply Like
Wow, that was a ton of work, thanks.
My test was very specific. (no smart objects, no groups)
Nice to see it works anyway as expected.

I may have neglected to mention that you must select the layers you wish to merge and turn off the layers (even if in groups) you don't want merged.
Woops.
(I am hardware engineer, software and I are not friends at all)

The History has no bearing on the keyboard commands used nor does Stamp Visible.
History is merely a report and undo function.
My thread has nothing to do with Stamp Layers.
This thread is for Merge Visible commands only.

I have been using these keyboard shortcuts for roughly a decade. (CS3 through CC)
CC was the first to present a slight change.

I have found no errors or problems with my installation (s) or system or computer (s), multiple computers, multiple systems. (I keep 8 complete computers as backup but only use 2)

I found the solution and posted it previously.
I tested the solution provided and have Zero Errors in function. (proof of no installation problems)

Don't know how Merge Visible became associated with Stamp Visible or Stamp Layers reported in History.
Merge Visible is in the Photoshop Help File. (keyboard shortcut also defined)
The Help Manual calls it Merge Visible. (aka "Merge visible layers" and also defines adding the Option key)

All that being said...
Seems I need to look into the History functions a bit.
Maybe???? I could learn a bit more than I do.
My History panel use is quite limited simply because I have many Terabytes of storage space and more than a 100 GB of Ram. (I save project file versions)

Final personal note.
I am not a "Pro" Photoshop user. (far from it)
I am a CAD user.
I use Photoshop for fun and on occasion, graphics for Copyright documents.
(I cannot justify engaging in any forms of debates on the subject)
All good?
Photo of Cristen Gillespie

Cristen Gillespie

  • 1261 Posts
  • 323 Reply Likes
> My test was very specific. (no smart objects, no groups)>

That isn't material. No Smart Objects, no groups, and it still works  exactly as I described. I tested both with and without.

> I may have neglected to mention that you must select the layers you wish to merge and turn off the layers (even if in groups) you don't want merged.>

I did that. It doesn't change the outcome. It is required if you use Cmd-Opt-E to select all the layers you want to merge, but you don't have to turn off the visibility of any layers you don't want to merge.

You don't have to select all the layers you want to merge with Cmd-Opt-Shift-E, but you DO have to turn off the visibility for any layers you don't want to merge.

This difference is actually very convenient as you can decide whether it's easier to select layers in the case of having only a few you want to copy to a new layer with Merge, or deselect layers in the case of having only a few you don't want to copy to a new layer with Merge. As many of us work with 30+ layers, even a little difference like that can be a big difference in how annoyed we get.

> The History has no bearing on the keyboard commands used nor does Stamp Visible.
History is merely a report and undo function.
My thread has nothing to do with Stamp Layers.
This thread is for Merge Visible commands only.>

You still are failing to understand what I'm saying. These are all under the broad umbrella of the Merge command. Adobe in its infinite wisdom frequently provided us with a single menu command that they then added modifier keys to in order to change the behavior of the command AND the result. Probably internally this is how they've always kept the commands straight, both to carry them out and to undo them. The History panel came well after the Merge commands, and a) either reflects the already-existing internal commands, or b) new short names were created to describe each command so anyone using the Edit History Log would know what had been performed—and that includes using it in a legal setting.

I am not using the History panel to do anything except what it does best—distinguish between the various possible ways to merge layers. So you have:

Cmd-E: Merge Down, which merges the selected layer to the layer immediately beneath it. There are conditions when that won't work.
 
Cmd-Shift-E: Merge Visible. It will merge all visible layers and it will behave differently depending upon whether or not the bottom layer can contain transparency or not. If it can create transparency, all the layers are merged without copy to the topmost layer. If the bottom layer is a Background layer, it will merge all layers without copy to the Background layer.

Cmd-Opt-E: Stamp Layers (Stamp is another way of saying "make a copy and stamp it onto a layer). This is NOT found in the Layers menu or in the Layers panel menu. It is one of Adobe's many secret handshakes. If all layers can contain transparency, it creates a copy that it merges to a new layer, OR merges a copy of all the selected layers to the Background layer, changing the Background layer itself.

Cmd-Opt-Shift-E:  Stamp Visible. This is also NOT found in the Layers menu or in the Layers panel menu. This also will copy all the visible layers and "stamp" them to a new layer above the topmost  selected layer. If the topmost selected layer is the bottom layer, Stamp Visible will copy the visible layers to a new layer directly above the bottom layer.

> I have been using these keyboard shortcuts for roughly a decade.>

Well, I haven't been using them much longer than you. Only since Photoshop 5. No CS quite yet. And before this, I hadn't ever tried Cmd-Opt-E with a Background layer, and haven't used it all that often either. Oddly enough, I did have cause to use it just the other day when I wanted to make one cast shadow from two objects that themselves were composited from a few layers that I didn't want to disturb. And I already had a LOT of layers, so it was the easiest route to take. The Background layer vs Layer 0 behavior  was completely unexpected, but I have to admit it does fall in line with Cmd-Shift-E.  I'm always learning.

> Don't know how Merge Visible became associated with Stamp Visible or Stamp Layers reported in History.>

I hope now I've explained that. History can't muddle several different commands into one, even if they are closely related. Please don't think I'm performing any actions in the History panel. One can do quite a lot with it in conjunction with various tools, but that's not relevant to this. I'm merely seeing what it says I have done, and to keep what I've done straight through a variety of experiments, it's been necessary to see the panel indeed reflects the action taken.

I still think if you're getting unexpected results, it could be something in your installation, something in your Preferences (corrupted in the transition), or there's something going on in your Mac system that isn't present in mine—and yes, that could be a bug. But before Adobe will spend resources trying to replicate it, I expect they'll want details (those screenshots I mentioned), and they'll very likely want you to first delete your Preferences and/or uninstall/reinstall, deleting preferences, in order to be sure there isn't something corrupt in your installation.
Photo of Chuck Kimmerle

Chuck Kimmerle

  • 3 Posts
  • 0 Reply Likes
It does work on my PC. Doesn't help you Mac folks, tho.
Photo of Robert Boyle

Robert Boyle

  • 34 Posts
  • 1 Reply Like
As it works out... all of this does work on Mac, but am happy to hear it works on PC as well.
Photo of Robert Boyle

Robert Boyle

  • 34 Posts
  • 1 Reply Like
Thank you Cristen.
Seems that Semantics is part of the discussion problem, although the problem is solved.

1. Cmd-Opt-E: Stamp Layers (Stamp is another way of saying "make a copy and stamp it onto a layer). This is NOT found in the Layers menu or in the Layers panel menu. It is one of Adobe's many secret handshakes. If all layers can contain transparency, it creates a copy that it merges to a new layer, OR merges a copy of all the selected layers to the Background layer, changing the Background layer itself. 
In the manual, Option+Command+E is defined as Merge Visible, not Stamp Layers.

2. Cmd-Opt-Shift-E:  Stamp Visible. This is also NOT found in the Layers menu or in the Layers panel menu. This also will copy all the visible layers and "stamp" them to a new layer above the topmost  selected layer. If the topmost selected layer is the bottom layer, Stamp Visible will copy the visible layers to a new layer directly above the bottom layer.
In the manual, Shift+Option+Command+E is defined as Merge Visible, not Stamp Visible.

I would need to look, but evidently the History panel call these commands "Stamp".
I see how that could create some confusion.

3. I still think if you're getting unexpected results, it could be something in your installation, something in your Preferences (corrupted in the transition), or there's something going on in your Mac system that isn't present in mine—and yes, that could be a bug.
As I stated (and tested very thoroughly in duplicate) there is nothing wrong with my Macs or installations or anything else.
When I posted my "Solution" I thought I made that clear,... evidently not.
I also stated that I performed Preferences Reset. (no change at all)
The only thing that has happened is a slight change in operation between CS6 and CC.
It is slight and I can no longer even suggest this is a "bug".
All is well and working just fine to the best of my knowledge at this time.

THANK YOU
Your post clarifies use of the Merge commands for any who may read this.
Photo of Cristen Gillespie

Cristen Gillespie

  • 1261 Posts
  • 323 Reply Likes
I'm relieved to hear that you're not going to be continually frustrated by this feature. I use these commands daily, they're that critical to functioning with layers.

> In the manual, Shift+Option+Command+E is defined as Merge Visible, not Stamp Visible.>

Yeah, I've been something of an outspoken critic of the "manual" and online Help in general for some time now. I have to work with it too often in various of the apps to be able to trust it anymore to be relevant to the current version or accurate. It could be a valuable resource—but I'm afraid, not so much. You still have to do all your own testing, and when the manual can't bother to include an index or state why and when someone might want a feature, or even clarify naming between history states that people might look up and the ostensible command that invokes it, a lot is going to be missed by the users.

> Your post clarifies use of the Merge commands for any who may read this.>

That's why I took the time to write it out. I was thinking that these threads seem to survive the ages, so it might be useful to someone in the future—unless by that time Adobe has changed it all again.  LOL
Photo of Robert Boyle

Robert Boyle

  • 34 Posts
  • 1 Reply Like
My hardware engineering skills are respectable.
My writing and typing skills are grade school level.
Quite often I need help in explaining because I am just lousy at those skills.
I have dozens of Federal Energy Physics Copyrights but all were produced at the cost of a great deal of time. (decades)
I never learned how to type and in my old age, not likely I ever will.
I still type with two fingers and hunt and peck method.
A 12 year old could run circles around me.

Again, thank you.
Photo of SOS Blog

SOS Blog

  • 2 Posts
  • 0 Reply Likes
Hy everyone, I'm french and trying to understand all what you're explaining.
Can someone simply esplain how to get a final layer with what I see on the screen.

For instance, I have several layers about curves, and add a low pass filter with a clipping curve to boost the dynamic contrast, and after that I do Contrl+Alt+Shift+E and get a new layer that is a bit different when I try to see the before and after. I don't understand where this difference comes from!
Does someone have an explanation and a simple solution?
Thank you all!