Masks do not work! URGENT - HIGHEST PRIORITY

[IPv6]

18 hours ago, walt.farrell said:

Screenshots are nice, but an actual .afphoto file is usually better

There is already afphoto, demonstrating the issue. Clearly a bug, behaviour of groups with masks and adjustments without pixel layer drastically changed, comparing to 1.7.1

[rimontecino]

23 hours ago, Wosven said:

Sometimes it's easier to provide a sample file to help understand, when screenshots don't help. We're not pro or anti, we just want to help, and it's not always easy

 

I made a test file. I opened it in version 1.7.1 and 1.7.2 and as you can see, the result is different. I share a link to the file. Is this a bug? Is it the new way of interpreting masks?

LINK

https://drive.google.com/file/d/1zj9dKxKma_02xeRkDW_0vN36iqeNON-m/view?usp=sharing

[tims]

I am also experiencing this bug since updating from 1.7.1 to 1.7.2

For the configuration in my screenshot;

Old (1.7.1):

Lens filter and Exposure adjustments are applied to all layers below the group where the mask is white

New (1.7.2):

Black section of the mask clips all layers below the group. Lens Filter and Exposure adjustments are still applied to the remainder of the image

 

 

[n3x]

I can confirm the issue.

Will be rolling back to 1.7.1:

https://store.serif.com/en-gb/update/windows/photo/1/

[Arceom]

Can confirm, this happens even when there are no adjustment layers present, mask is behaving like a general mask.


Also, if you create some adjustment layers, then group them, then mask the group, then create some positive zones in the mask; you will get the behaviour mentioned above. But if you create a pixel layer (even an empty one) and put it at the bottom of the adjustments group; the adjustments will stop working. Here is a video demonstrating it.

[Guy Alex]

I completely agree that there must be a bug concerning the masking of groups of adjustments. I have just noticed it too, not only on my PC, but also on my iPad. The mask which should normally apply to the group of adjustments actually applies to pixel layers below. :-(

[IPv6]

Just checked 1.7.2 update on MacOS - this bug also here...  

Looks like (for me) latest fixes for rendering filters inside groups was overdone in some directions... And crushed old behaviour. But proper rendering of filters inside groups very important thing too, so hoping both functionalities - masks on groups without pixel data and proper rendering of grouped filters - will be preserved.

Anyway, i can imagine inner complexity of AP... Definitely not an easy task to keep all working at the same time. But that`s what make AP so useful.
Keep up good work! will wait for fixed beta for now

[Chris B]

Hi everyone.

I just wanted to let you all know that this is with the developers. I'll update you once I know more. 

[Michail]

 

[Shmuel]

I've also ran into this bug and it's frustrating to have a lot of my photos from 1.6 essentially unusable. I'll try going back to v1.7.1.404.

[Tomáš Luža]

Hey guys, is this bug already solved? I can't find any answer to that and I don't want to instal new version only to downgrade again. Thing is that everytime I open AF there is an updater that pops up to remind me to update to 1.7.2 but I can't do it unless this is solved.

 

 

[Guy Alex]

Without checking, I do not believe it has been solved. No new version has been released, has it?

[carl123]

It's fixed in the Windows 1.7.3 beta - released this week

But the 1.7.3 MAC beta has not been released as yet

[Tomáš Luža]

19 minutes ago, carl123 said:

It's fixed in the Windows 1.7.3 beta - released this week

But the 1.7.3 MAC beta has not been released as yet

I see,

good thanks for info.

PS OT: GL with Johnson...

 

[Chris B]

If you need the fix desperately, grab the Windows beta from here. Some other useful fixes are also available such as .abr import. 

[Tomáš Luža]

19 minutes ago, Chris B said:

If you need the fix desperately, grab the Windows beta from here. Some other useful fixes are also available such as .abr import. 

Thank you but I am good with 1.7.1 yet. I was just curious if it were safe to upgrade.

All good, I got info and I'll wait a bit, its not a problem.

 

[Newoldschool]

Hello, so? there is any fix about this? 😪

[walt.farrell]

51 minutes ago, Newoldschool said:

Hello, so? there is any fix about this? 😪

From the information above it was fixed in 1.7.3.

If you're having a problem you should probably post a new topic and describe your problem in detail.