Jump to content
You must now use your email address to sign in [click for more info] ×

White Balance Merge affects sharpness


Recommended Posts

Running latest Affinity Photo on Windows 11.

So I'm editing an image and it looks good except for white balance. I open White Balance (WB) and adjust the Tint. If I click on Merge, the sharpness appears to degrade. If while I'm in the WB window I instead do Document/Flatten the sharpness is not affected.

In the attached example, the top image is the starting point. The next image is a screenshot while the WB window is open. The WB changes but the sharpness is unchanged. The next image is the result of using Merge. The final image is the result of undoing the WB where Merge was used and repeating WB but using Document/Flatten while the WB window is still open.

How to explain?

Example.jpg

Link to comment
Share on other sites

This is a known issue when the lower layer is not pixel aligned (in essence, you used the move/transform tool on it).

workaround: rasterize the lower pixel layer before any merge down.

 

 

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

 

Link to comment
Share on other sites

I'm not sure I understand all this. Is the issue that I resized the image before doing the WB adjustment? As a test, I opened an image, cropped it as before and resized. Before doing WB, I right clicked on the background layer and selected Rasterize. (It was a bit confusing as the menu item is Rasterize... as if another window would open with options but none did). Anyhow, I then did the WB adjustment with Merge and it again blurred the image.

 

Link to comment
Share on other sites

Interesting. 
 

Blurring can occur from rasterizing / merging, but not from adjustments. Any chance you can upload an actual document, and provide an exact list of steps (or screen recording showing every single step)?

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

 

Link to comment
Share on other sites

I've been trying to provide an example but so far having trouble getting consistent results.

Meanwhile, can you explain why using Merge in the WB window gives different results from using Document/Flatten while the WB window is open? How is Merge different from Flatten?

 

Link to comment
Share on other sites

Merge down merges the visible result into the lower pixel layer. This has to be taken literally: in case the layer is rotated by 45 degree, the result keeps this rotation. If pixel position is fractional, all get blurred. If dpi of layer is lower, it will be used. In extreme case, you can create a pixel layer with 1 dpi, and all gets averaged into one single pixel.

all other merge / flatten operation create a new layer, unrotated, and using the canvas size and document dpi.

as a best practice survival tip:

  • never use merge down, unless you are absolutely sure it is perfectly pixel aligned, not rotated, and has same dpi as document. 
  • or you really know what you are doing. 

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.