IPv6 Posted August 18, 2019 Share Posted August 18, 2019 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 fotojindra 1 Quote Link to comment Share on other sites More sharing options...
rimontecino Posted August 18, 2019 Share Posted August 18, 2019 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 Quote Link to comment Share on other sites More sharing options...
tims Posted August 18, 2019 Share Posted August 18, 2019 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 Quote Link to comment Share on other sites More sharing options...
n3x Posted August 18, 2019 Share Posted August 18, 2019 I can confirm the issue. Will be rolling back to 1.7.1: https://store.serif.com/en-gb/update/windows/photo/1/ Quote Link to comment Share on other sites More sharing options...
Arceom Posted August 18, 2019 Share Posted August 18, 2019 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. 2019-08-18 10-05-35.mp4 rimontecino 1 Quote Link to comment Share on other sites More sharing options...
Guy Alex Posted August 18, 2019 Share Posted August 18, 2019 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. :-( rimontecino and IPv6 2 Quote Link to comment Share on other sites More sharing options...
IPv6 Posted August 19, 2019 Share Posted August 19, 2019 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 Quote Link to comment Share on other sites More sharing options...
Staff Chris B Posted August 19, 2019 Staff Share Posted August 19, 2019 Hi everyone. I just wanted to let you all know that this is with the developers. I'll update you once I know more. tims, fotojindra, rimontecino and 5 others 8 Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
Michail Posted August 20, 2019 Share Posted August 20, 2019 rimontecino 1 Quote Link to comment Share on other sites More sharing options...
Shmuel Posted September 1, 2019 Share Posted September 1, 2019 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. Quote Link to comment Share on other sites More sharing options...
Tomáš Luža Posted September 19, 2019 Share Posted September 19, 2019 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. Quote Link to comment Share on other sites More sharing options...
Guy Alex Posted September 19, 2019 Share Posted September 19, 2019 Without checking, I do not believe it has been solved. No new version has been released, has it? Quote Link to comment Share on other sites More sharing options...
carl123 Posted September 19, 2019 Share Posted September 19, 2019 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 Chris B 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. Link to comment Share on other sites More sharing options...
Tomáš Luža Posted September 19, 2019 Share Posted September 19, 2019 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... Quote Link to comment Share on other sites More sharing options...
Staff Chris B Posted September 19, 2019 Staff Share Posted September 19, 2019 If you need the fix desperately, grab the Windows beta from here. Some other useful fixes are also available such as .abr import. IPv6 1 Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
Tomáš Luža Posted September 19, 2019 Share Posted September 19, 2019 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. Chris B 1 Quote Link to comment Share on other sites More sharing options...
Newoldschool Posted May 15, 2020 Share Posted May 15, 2020 Hello, so? there is any fix about this? 😪 Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted May 15, 2020 Share Posted May 15, 2020 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. 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.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
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.