VWI Posted January 22, 2022 Posted January 22, 2022 (edited) I am using lightroom and Affinity together. When editing in Affinity, I added a motion blur layer and masked part of the subjecty area (see affinity screen view below) - and it looked fine. When I saved it and went back into Lightroom, the lego-like pathway of the mask was clearly noticable . I tried merging visible layers and re-saving, but it did not help. Any ideas? Thanks! Vince Here's the Affinity screen view: Here is the image as shown in Lightroom (look for blocky pattern around her raised arm and following her body) Edited January 22, 2022 by VWI clarification Quote
thomaso Posted January 22, 2022 Posted January 22, 2022 What file format did you export in AP / open in LR? To me in a quick test it appears to works for a blur layer with soft edge mask without resulting in LR in such blocks shown in your screenshot. I used PSD + "preserve editability", I haven't tried another setting or format. Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1
VWI Posted January 23, 2022 Author Posted January 23, 2022 Hi Thomas I. I saved it as a tiff file with layers preserved. Do you think that may have made a difference? Lightroom doesn't read afphoto files. Thanks! Vince Quote
VWI Posted January 23, 2022 Author Posted January 23, 2022 Hi Thomas I. I saved it as a tiff file with layers preserved. Do you think that may have made a difference? Lightroom doesn't read afphoto files. Thanks! Vince Quote
thomaso Posted January 23, 2022 Posted January 23, 2022 I can't judge what exactly influences your experienced issue. Since I am not familiar to the workflow of mixing both apps my test can tell only that it seems to be possible to open an exported AP image with a masked motion blur adjustment in LR without getting this blocks. Like you I assume a possible reason in both the file format and its export setting details, so you could try several versions. What if you entirely flatten / rasterize the image before export? (I think you can't edit the mask in LR anyway, right?) Also I wonder if the issue occurs with every image / mask / adjustment. Your AP screenshot shows several layers, the top layer set to 75% opacity. (my test used 1 layer and opacity 100). May be the issue is influenced by an opacity setting? What if you open your exported, affected image in another image viewer app, does it show the issue, too, and in the same way? Can you upload an example to the forum, in low res, as .afphoto + affected export? Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1
ashf Posted January 23, 2022 Posted January 23, 2022 What happens if you turn off the Hardware Acceleration in the Preferences>Performance? Quote
thomaso Posted January 23, 2022 Posted January 23, 2022 47 minutes ago, ashf said: What happens if you turn off the Hardware Acceleration in the Preferences>Performance? That's a known issue in Affinity but rather not in LR where the issue occurs. Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1
VWI Posted January 23, 2022 Author Posted January 23, 2022 Hi Thomaso. I followed your suggestions and replaced the layer containing a mask screened back to 75%, and replaced it with the layer pulled back to 75% (leaving the mask at 100%). I don't know why, but that seemed to correct the problem. I also discovered that affinity will export as a PSD file. Thank you for your help! Vince thomaso 1 Quote
VWI Posted January 23, 2022 Author Posted January 23, 2022 (edited) I will also check turning off hardware acceleration. Thanks Ashf! Vince Edited January 23, 2022 by VWI Quote
ashf Posted January 23, 2022 Posted January 23, 2022 Another method you might wanna try is to flatten document before export. Quote
Ron P. Posted January 23, 2022 Posted January 23, 2022 6 hours ago, VWI said: Lightroom doesn't read afphoto files. FWIW, the afphoto files are proprietary working files, like pspimage, and cpt are Corel's working files for PaintShop Pro and Photo Paint. LR can not see or use them also. I still use the last perpetual release of LR, and will use Tiff and have used PSD to hand-off to other apps such as Affinity Photo. Quote Affinity Photo 2.5..; Affinity Designer 2.5..; Affinity Publisher 2.5..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD
VWI Posted January 23, 2022 Author Posted January 23, 2022 Hi Ron, I see. Thanks. I am continuing my search for a Lightroom alternative, but I do rely on tweaks after Affinity (b&w conversion, etc) but now and then like to go back into Affinity to adjust, or fix something and it's nice to see those changes ripple into Lightroom virtual copies as well. Thanks! Quote
thomaso Posted January 23, 2022 Posted January 23, 2022 9 hours ago, VWI said: I followed your suggestions and replaced the layer containing a mask screened back to 75%, and replaced it with the layer pulled back to 75% (leaving the mask at 100%). Thanks for the feedback and glad you managed to make it work. I am not sure if I understand correctly: Do you mean at first (in your screenshot) both layers, image and masked adjustment, were set to 75 % opacity – whereas a setup of image at 75 % and masked adjustment at 100 % did solve the issue of a blocky mask in LR? So, the solution was to keep the mask layer at 100%? – Or were mask + adjustment two separate layers in your affected example? Aside that I'd like to try to reproduce the issue with an affected file of yours. Can you upload any .afpub + .tif which results in a blocky mask issue in LR to you? Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1
Old Bruce Posted January 23, 2022 Posted January 23, 2022 14 hours ago, VWI said: Hi Thomas I. I saved it as a tiff file with layers preserved. Do you think that may have made a difference? Lightroom doesn't read afphoto files. Thanks! I am going to bet that if you save without layers preserved all will be well. Layers preserved means the layers will be correctly interpreted by Affinity applications. Another way of saying it is only Affinity applications will correctly interpret the layers. It is the nature of TIFF files. 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.
thomaso Posted January 23, 2022 Posted January 23, 2022 26 minutes ago, Old Bruce said: it is only Affinity applications will correctly interpret the layers. It is the nature of TIFF files. Doesn't TIFF always require to get saved not flattened (~maintaining layers) if it shall transfer 100% transparency? This is not a matter specifically of Affinity, right? Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1
walt.farrell Posted January 23, 2022 Posted January 23, 2022 5 minutes ago, thomaso said: Doesn't TIFF always require to get saved not flattened (~maintaining layers) if it shall transfer 100% transparency? This is not a matter specifically of Affinity, right? No. Usually TIFF files, even with transparency (even with 100% transparency), do not have layers. They are flat files, just like JPG and PNG files. 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.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
thomaso Posted January 23, 2022 Posted January 23, 2022 3 hours ago, walt.farrell said: No. Usually TIFF files, even with transparency (even with 100% transparency), do not have layers. They are flat files, just like JPG and PNG files. Alpha channel. Not a layer in terms of Layer panels of any app but as additional colour channel (layer in the Channels panel ;•) for TIF and PNG, respectively as a separate vector object (clipping path) inside of Adobe.jpgs. From this perspective understanding "flat" may vary. But since you are here: What would you suspect as culprit element of a blocky mask appearance if opened in another app? Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1
Old Bruce Posted January 23, 2022 Posted January 23, 2022 1 hour ago, thomaso said: But since you are here: What would you suspect as culprit element of a blocky mask appearance if opened in another app? I would suspect the the other application not being able to properly read the Affinity Photo proprietary Layers in the TIFF exported by Affinity Photo. 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.
walt.farrell Posted January 23, 2022 Posted January 23, 2022 16 minutes ago, Old Bruce said: I would suspect the the other application not being able to properly read the Affinity Photo proprietary Layers in the TIFF exported by Affinity Photo. I would certainly not expect any other application to read the Affinity Layers, but generally they would just be ignored by any application reading the file. (And, conversely, would be destroyed if any non-Affinity application read, updated, and rewrote the file.) 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.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
thomaso Posted January 23, 2022 Posted January 23, 2022 51 minutes ago, Old Bruce said: I would suspect the the other application not being able to properly read the Affinity Photo proprietary Layers in the TIFF exported by Affinity Photo. This is rather expectation (of a result) than suspectation of the culprit element (on the way to the result). Obviously, here Affinity exports are able to work under certain circumstances, as the thread tells. Instead of exporting a series of possible combinations of opacity settings of image and/or mask and/or adjustment + various possible file export settings of .TIF and/or .PSD I am seriously curios to get a more sensible, technical idea what exactly influences this blocky mask issue here. Wosven 1 Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1
Old Bruce Posted January 23, 2022 Posted January 23, 2022 1 minute ago, thomaso said: I am seriously curios to get a more sensible, technical idea what exactly influences this blocky mask issue here. Then you will need to ask people who use Lightroom. Best would be to ask the people who make Lightroom. 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.
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.