Michail Posted February 18, 2023 Posted February 18, 2023 Do the following: Open a non-RAW image (jpg, png ...). Open a RAW image, develop it and copy it to the clipboard: Ctrl+A > Ctrl+C. Paste the image from the clipboard into the already opened non-RAW image (step 1.). Go back to the RAW image. Result: The image content has disappeared, as if I had not copied but cut. The (empty) layer itself is still there. Quote
Michail Posted February 18, 2023 Author Posted February 18, 2023 49 minutes ago, Paul Mudditt said: You must rasterise all images before performing pixel operations. That doesn't sound logical to me: 1. Copying a complete layer is not a pixel operation in my opinion. 2. It works with placed images, although they are not rasterised either. I think I now know what the reason is. The effect apparently only occurs when RAW images are referenced during development.For me, the question now is whether this is what the developers intended. Paul Mudditt 1 Quote
Old Bruce Posted February 18, 2023 Posted February 18, 2023 1 hour ago, Michail said: I think I now know what the reason is. The effect apparently only occurs when RAW images are referenced during development.For me, the question now is whether this is what the developers intended. Same / Similar results here on Mac OS 11.7.4 I really don't think this can be intentional. At least I don't see what the reasoning behind it would be. Quote Mac Pro (Late 2013) Mac OS 12.7.6 Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that.
carl123 Posted February 19, 2023 Posted February 19, 2023 14 hours ago, Michail said: Do the following: Open a non-RAW image (jpg, png ...). Open a RAW image, develop it and copy it to the clipboard: Ctrl+A > Ctrl+C. Paste the image from the clipboard into the already opened non-RAW image (step 1.). Go back to the RAW image. Result: The image content has disappeared, as if I had not copied but cut. The (empty) layer itself is still there. Same here (Windows 11) also the same in V2.1 beta (Tested with Linked RAW output) Note: You can recover the image by going back into the Develop persona (nothing is displayed) and just clicking the Develop button again Definitely a bug! Dan C 1 Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.
Dan C Posted February 20, 2023 Posted February 20, 2023 Hi @Michail, Thanks for your report! I can confirm I've been able to replicate this issue here and I've logged this with our development team to be resolved. I hope this helps Michail 1 Quote
Staff Affinity Info Bot Posted February 28, 2023 Staff Posted February 28, 2023 The issue "Copying non-destructive RAW layer and pasting into a separate document renders the RAW layer invisible in the original RAW file " (REF: AFP-5970 ) has been fixed by the developers in internal build 2.1.0.1713This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.Customer beta builds are announced here and you can participate by following these instructions.If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us. Michail 1 Quote
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.