Trevor M Posted November 23, 2023 Posted November 23, 2023 Hi all new here. I'm getting to grips with affinity photo and generally really like it, but have recently noticed something strange (probably not understanding aspects of layers) I process a Raw file then hit develop so I can work on an image using layers in photo persona, all good. On the odd occasion with a pixel layer highlighted I click on the develop icon to return to the Raw to make adjustment and the return to Photo still all good. I've just become aware that if I use the "Merge Visible" option anywhere in the photo persona (it seemed the only way to get the nik plugins to work) when I return to the develop persona to make tweak to the Raw, my previous adjustments can be see but any changes I try to make have no effect making the process a destructive one. Is this correct? If so is there a work around or do I have to create a tiff to then use the nik or Topaz plugins so I don't need to use "Merge visible" It just makes the workflow take longer. Hope that makes sense any input wood be most welcome. Quote
walt.farrell Posted November 23, 2023 Posted November 23, 2023 Welcome to the Serif Affinity forums. Merge Visible doesn't delete any layers, and is non-destructive. But it encapsulates the data of all the visible layers that exist at the time you perform the operation, and if you were to return to an earlier (lower) layer in the Layers panel after that and make changes, they would not be reflected in the layer created by Merge Visible. This would apply whether you are simply painting on that lower layer, or changing Adjustment values, or going back into the Develop Persona. You're right that you need a Pixel layer to use the plugins, and so either you need to do Develop to a Pixel layer rather than a Linked or Embedded RAW layer, or you need to use Merge Visible, or you need to duplicate the RAW layer and Rasterize it. And then you cannot make further changes via the Develop Persona without re-doing your plugin work. 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.5, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.5
Trevor M Posted November 23, 2023 Author Posted November 23, 2023 Thanks for the quick reply walt that makes sense, unfortunately 🙂 Quote
walt.farrell Posted November 23, 2023 Posted November 23, 2023 You're welcome. 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.5, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.5
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.