maikm

Masks in a Stack Group are always hard-edged, by design, according to this old post from a Serif staff member: 
I haven't been able to find any documentation about that.

Ok, I didn't want to use my actual current file, as thats multiple GBytes, so I created a small new one, and discovered that this problem is specific to the way I created it. Here is how to reproduce:
Start with File/New Stack Select any two images and create the stack Select the top image in the layers panel and create a mask on it Select a soft brush, black color, and start painting on the mask Attached is a screen recording of me doing that, along with the sample document after creating the stack. Notice the hard edges of the black brush, as well as the strange rim around the white brush after I changed color. At the end of the recording, I pull the layers out of the stack group, and then things return to working as I expected.
MacBook Pro 16" M1Max, 64 GB RAM, 4 TB SSD, using a standard Apple mouse, macOS 13.6, Affinity Photo 2.2.0.

afphoto_stack.mp4 StackExample.afphoto

I'm actually worried about Affinity Photo's future if nothing happens in regard to AI-based tools. That's where the most meaningful current advances in imaging tech are, and Serif really needs to up their game here. Right now I can't even smoothly integrate external AI tools like those from DxO or Topaz which have Photoshop plugins that don't work with Affinity Photo.

Yeah, I can have DxO PureRaw 3 deliver the preprocessed DNG files to Affinity Photo, but I was unsuccessful trying to use the Topaz plugins like that, let alone DxO. I'm on a Mac though, so there is no simple EXE to point to, and no real documentation that helps in specific cases. My plugin prefs section looks different. Googling found me only other dudes with the same problem and no solution.

 

I'm actually worried about Affinity Photo's future if nothing happens in regard to AI-based tools. That's where the most meaningful current advances in imaging tech are, and Serif really needs to up their game here. Right now I can't even smoothly integrate external AI tools like those from DxO or Topaz which have Photoshop plugins that don't work with Affinity Photo.

I agree, and that is currently the only thing I envy my Photoshop pals about. They can get the selections done much faster, which puts me at an uncomfortable disadvantage.

Thanks for the samples. 
I think we've worked out what is happening. The White Balance Tool now affects Tint in some sort of negative way.
We are speaking with dev at the moment for a possible solution. 

Sure, here's a sample NEF file: maik_20221128_150459_z5_000069.nef

I'm also affected. Glad I didn't delete V1 yet. My converted Nikon Z5 images will now turn completely red when I use the WB picker in V2 develop persona, while it works fine in V1. It feels like there is a safeguard in place in V2 to protect from "unreasonable" values, which did not consider IR imaging.

I'm also affected. Glad I didn't delete V1 yet. My converted Nikon Z5 images will now turn completely red when I use the WB picker in V2 develop persona, while it works fine in V1. It feels like there is a safeguard in place in V2 to protect from "unreasonable" values, which did not consider IR imaging.

I'm also affected. Glad I didn't delete V1 yet. My converted Nikon Z5 images will now turn completely red when I use the WB picker in V2 develop persona, while it works fine in V1. It feels like there is a safeguard in place in V2 to protect from "unreasonable" values, which did not consider IR imaging.