kanonji Posted May 27, 2024 Posted May 27, 2024 As the title, merging adjustment layers will change the appearance of the image. I ran into this problem with "Threshold". Other "Curves" changed the look as well. I have not tried other adjustment layers. Apps with the issue: Affinity Photo, Affinity Designer Version: 1.10.6.1665 for both How to reproduce 1. Open before-merge-adjustments-layer.afphoto, before-merge-adjustments-layer.afdesign 2. Merge adjustment layer Also attaching files that reproduces it on my env. * after-merge-adjustments-layer.afphoto * after-merge-adjustments-layer.afdesign before-merge-adjustments-layer.afphoto before-merge-adjustments-layer.afdesign after-merge-adjustments-layer.afphoto after-merge-adjustments-layer.afdesign Quote
Staff NathanC Posted May 30, 2024 Staff Posted May 30, 2024 Welcome to the forums @kanonji, The difference you're observing is likely because you're viewing and comparing the merged document with the non-merged document at a zoom level either greater or less than 100%, which is where Mipmap rendering is used to render the canvas to improve performance. With a singular document open, Set the zoom level to 100% (CTRL + 1) and then go to layer > merge visible. If you toggle the merged pixel layer on and off you should see that it's identical to the threshold adjustment + pixel layer below. Quote
walt.farrell Posted May 30, 2024 Posted May 30, 2024 1 hour ago, NathanC said: With a singular document open, Set the zoom level to 100% (CTRL + 1) and then go to layer > merge visible. If you toggle the merged pixel layer on and off you should see that it's identical to the threshold adjustment + pixel layer below Have you tried that with before-merge-adjustments-layer.afphoto document (above)? I was going to make a response similar to yours, but I found to my surprise that even using 100% zoom the Merge Visible layer was different. I vaguely remember a reason for that, but not whether it's correct or a bug. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
Staff NathanC Posted May 30, 2024 Staff Posted May 30, 2024 27 minutes ago, walt.farrell said: Have you tried that with before-merge-adjustments-layer.afphoto document (above)? I was going to make a response similar to yours, but I found to my surprise that even using 100% zoom the Merge Visible layer was different. I vaguely remember a reason for that, but not whether it's correct or a bug. Yeah, this is done using the before-merge file in V1 and V2, see recording below. If my Windows scaling was at a different value E.G 200%, I would need to match that zoom level in Photo. Merge Visible.mp4 Quote
walt.farrell Posted May 30, 2024 Posted May 30, 2024 Thanks, @NathanC! That's very interesting. All the statements I've seen have said tto view at 100% (or multiples such as 200%), bu it seems the recommendation should be to view at one's display scaling (at least on Windows). Based on your hint, I zoomed to 125% (matching my Windows Display Scaling of 125%) and at that zoom level there is no difference between the original view before merging, and the result of Merge Visible. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
kanonji Posted May 31, 2024 Author Posted May 31, 2024 Thank you guys for replying, @NathanC @walt.farrell I see. I have tried to merge the adjustment layers at 100% zoom in Affinity Photo (and also Windows Display Scaling), it looks the same. So the problem is that if there are adjustment layers that are not merged + zoomed out from 100%, it looks different than it actually is? I have been able to work around the problem, but it would be nice if it looks the same before merging as the actual image. For me, the look in that's Mipmap rendering was what I was looking for, so I had to re-set my adjustment layers. I'm using DeepL, so forgive me if there are any unnatural words. Quote
walt.farrell Posted May 31, 2024 Posted May 31, 2024 1 hour ago, kanonji said: So the problem is that if there are adjustment layers that are not merged + zoomed out from 100%, it looks different than it actually is? I have been able to work around the problem, but it would be nice if it looks the same before merging as the actual image. The problem is that you need to be viewing the image at 100% zoom (or, on Windows, at a zoom matching your Display Scaling) when you are applying the adjustment, and adjusting its settings, if you want to see the actual effect your adjustments will have on the final image. I don't think this is true for all adjustments, but certainly for Noise. And it is true for some Filters. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
Recommended Posts
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.