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

Affinity Photo 2.10: Layer Blend Options stop working if I add a mask


Recommended Posts

I'm not sure if this is supposed to happen, but if I add a mask layer to my adjustment layer, the blend range I've set in the Layer Blend Options suddenly stop working. It's as if I've hit the Reset button in Blend Options. As soon as I remove the mask layer, my custom blend ranges work again. Is this normal? I don't remember this happening a few versions back. Is there a way to have both a custom blend range and a mask at the same time?

layer_blend_options.webp.62bd01c229230555047b3bc6a5246ce6.webp

Aleksandar Mitov
www.renarvisuals.com CGI and 3D rendering services
email: office@renarvisuals.com

Affinity Photo 2.5.0  Windows 10 Pro x64 ver. 22H2  AMD Ryzen 7950X 16-core + 64 GB DDR5  GeForce RTX 3090 24GB + driver 551.86

Link to comment
Share on other sites

Known bug

 

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

26 minutes ago, Alex_M said:

I'm not sure if this is supposed to happen, but if I add a mask layer to my adjustment layer, the blend range I've set in the Layer Blend Options suddenly stop working. It's as if I've hit the Reset button in Blend Options. As soon as I remove the mask layer, my custom blend ranges work again. Is this normal? I don't remember this happening a few versions back. Is there a way to have both a custom blend range and a mask at the same time?

This sounds like you have simply masked the adjustment layer.

There are a lot of ways to setup a document which has an adjustment layer and a mask. A document would be quite useful to figure out where you have the Adjustment layer and where the Mask is.

Mac Pro (Late 2013) Mac OS 12.7.4 
Affinity Designer 2.4.1 | Affinity Photo 2.4.1 | Affinity Publisher 2.4.1 | Beta versions as they appear.

I have never mastered color management, period, so I cannot help with that.

Link to comment
Share on other sites

25 minutes ago, Old Bruce said:

This sounds like you have simply masked the adjustment layer.

There are a lot of ways to setup a document which has an adjustment layer and a mask. A document would be quite useful to figure out where you have the Adjustment layer and where the Mask is.

I have my mask inside the adjustment layer (White Balance). Pretty simple setup. No need to share the document, I think. Interestingly, @NotMyFault says it's a known bug. I went to his thread and learned that having Hardware Acceleration turn on causes this. So I disabled it from the settings and voila! I can use blending ranges with masks again. Seems like there's always something that Hardware Acceleration breaks with the software. If I were the developers, I would put a big warning on this option warning people that it's unfinished and may cause bugs like these. It's the right thing to do. Who knows what else is bugged when this option is turned on. From now on, I'm not going to use or recommend Hardware Acceleration. Too many headaches. Thanks for the tip, @NotMyFault !

Should I report this issue in the Bugs forum section?

27 minutes ago, NotMyFault said:

Known bug

 

 

Aleksandar Mitov
www.renarvisuals.com CGI and 3D rendering services
email: office@renarvisuals.com

Affinity Photo 2.5.0  Windows 10 Pro x64 ver. 22H2  AMD Ryzen 7950X 16-core + 64 GB DDR5  GeForce RTX 3090 24GB + driver 551.86

Link to comment
Share on other sites

7 minutes ago, Alex_M said:

Seems like there's always something that Hardware Acceleration breaks with the software.

From what I have read on the forums, it works fine for some users but causes problems for others. But it is hard to say what fraction of the user base actually has problems because users with problems are much more likely to post comments about that than those experiencing no problems.

All 3 1.10.8, & all 3 V2.5.2 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

1 hour ago, Alex_M said:

No need to share the document, I think.

How about a Screen Shot of the layer's panel. Here are a few possibilities based on your description.

ScreenShot2023-06-18at11_34_49AM.png.ee36437cb3639190c4634fd90f66c522.png Using the integrated / built in mask.

ScreenShot2023-06-18at11_32_45AM.png.147588dc27b035bbc5b8075fac4fa276.png Additional Mask inverted.

ScreenShot2023-06-18at11_29_31AM.png.ce61f68f890a29a327c26a457b44b20e.png Additional Mask not inverted.

With one of these I don't see what you describe, with another of these I do see what you describe.

Mac Pro (Late 2013) Mac OS 12.7.4 
Affinity Designer 2.4.1 | Affinity Photo 2.4.1 | Affinity Publisher 2.4.1 | Beta versions as they appear.

I have never mastered color management, period, so I cannot help with that.

Link to comment
Share on other sites

2 hours ago, R C-R said:

From what I have read on the forums, it works fine for some users but causes problems for others. But it is hard to say what fraction of the user base actually has problems because users with problems are much more likely to post comments about that than those experiencing no problems.

We need to distinguish between 2 categories:

  • Actual bugs in Affinity, causing wrong rendering with OpenCL active. The issue of this threads falls into this category. These bugs are few.
  • Bugs, including crashes, caused by faulty GPU drivers, especially for certain GPU types. These bugs affect many users, and caused the bad reputation of HW acceleration for Affinity apps.

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

2 hours ago, R C-R said:

From what I have read on the forums, it works fine for some users but causes problems for others. But it is hard to say what fraction of the user base actually has problems because users with problems are much more likely to post comments about that than those experiencing no problems.

It affects iPad, too.

use the test image from my link

 

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

10 minutes ago, NotMyFault said:

Actual bugs in Affinity, causing wrong rendering with OpenCL active. The issue of this threads falls into this category.

I'm curious how we know that? I've never figured out how to tell when it's Affinity vs the GPU causing a problem.

Why do we know that Affinity is doing something wrong, rather than the GPU drivers handling the requests that Affinity makes incorrectly?

Also, given the post you just made that it also affects iPad: Does the iPad version even have OpenCL support?

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.5, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.5

Link to comment
Share on other sites

17 minutes ago, walt.farrell said:

Does the iPad version even have OpenCL support?

I don't think so.

All 3 1.10.8, & all 3 V2.5.2 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

3 minutes ago, R C-R said:

I don't think so.

Thanks.

I suppose that does lend credence to the idea that it's a flaw in the Affinity code, if it can't be related to issues in OpenCL implementations :)

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.5, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.5

Link to comment
Share on other sites

This issue is related to HW acceleration in general. You can check this by enabling the WARP renderer (pure SW, never GPU). If the results differ from those using HW acceleration you can distinguish the case, especially when comparing multiple Platforms (Windows, Mac, iPad). Especially iPad does not allow to disable HW acceleration.

 

Sometimes the rendering differs between Photo and Designer (who does not use Metal in the same ways as Photo).

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

4 minutes ago, NotMyFault said:

You can check this by enabling the WARP renderer (pure SW, never GPU).

?? What does that have to do with either the iPad or Mac versions of the apps? AFAIK, neither one supports a WARP renderer.

All 3 1.10.8, & all 3 V2.5.2 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

  • 10 months later...

Any news about fixing this behavior with mask layer and bland ranges applied to adjustment layer?

Blend ranges are working correct when applied to adjustment layer with built-in mask but stop working with separate mask layer. Strange thing is why it is not working for mask layers but works with built-in masks...

I've checked this with OpenCL turned off (Photo 2.4.2 and beta 2.5.0.2449 under Windows 10) and the issue is gone.

I usually use separate mask layer in adjustment layers because I can turn off that mask layer and compare the difference of adjustment layer with or without a mask. This is not possible with built-in masks. And I use this grouping walk-around but it is a bit tedious on a daily basis with nesting many layers, adjustments and masks, especially when in the end I want to apply blend ranges to one of my layers...

 

Mask and blend ranges1.png

Mask and blend ranges2.png

Mask and blend ranges3.png

Mask and blend ranges4.png

Desktop 1: i7 2600k @4,3 GHz, RTX 4070 12GB, 16GB Ram, SSD + HDD, Win10 Pro 22H2, Wacom Bamboo
Desktop 2: i7 3770k @4,2 GHz, RTX 2060s 8GB, 16GB Ram, SSD + HDD, Win10 Home 22H2, Wacom Intuos 4

Latest Affinity V2 + Affinity V2 Beta

Link to comment
Share on other sites

@Bartosz Borecki Agreed....good catch. Blend ranges seem to work fine when used in conjunction with an Adjustment Layer's "built-in mask", with or without Metal Acceleration enabled on my 2017 MacBook Pro.

Blend ranges do NOT seem to work when combined with a mask that I add manually, at least with Metal Acceleration turned on. When I turned Metal OFF, it worked with the built-in mask or with a separately added mask. I generally prefer to add my own mask manually for added flexibility. Seems to me this is a bug and needs to be fixed.

2017 15" MacBook Pro, 16 MB RAM, Ventura v13.6.6, Affinity Photo/Designer/Publisher v1 & v2, Adobe CS6 Extended, LightRoom v6, Blender, InkScape, Dell 30" Monitor, Canon PRO-100 Printer, i1 Spectrophotometer, i1Publish

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.