jportraits Posted February 11, 2023 Posted February 11, 2023 when using frequency separation, low frequency with gaussian blur looks not correct. there are some artifacts - colorful stripes. they are not on whole image, only on part. it is the same when just applying filter gaussian blur to layer. live filter don't have this problem Quote
Lisbon Posted February 11, 2023 Posted February 11, 2023 Hi @jportraits Im a windows user. I don't know if I understood correctly but are you saying that you don't have any problems if you use Live Gaussian Blur? Quote
jportraits Posted February 11, 2023 Author Posted February 11, 2023 im also windows user, i hate mac os. but now i work on mac. yes, on live gaussian filter i dont see any problem. also frequency separation with median blur works fine. Quote
Lisbon Posted February 11, 2023 Posted February 11, 2023 1 minute ago, jportraits said: yes, on live gaussian filter i dont see any problem. That changes everything. While they solve the problem use this macro (Download at the end). See if this works on Mac: 1) Run the macro 2) Adjust the Gaussian Blur and Merge with the "Low Freq." layer 3) Turn the Visibility On of the "High Freq." group and rasterize the group Frequency Separation.afmacros Quote
Dan C Posted February 13, 2023 Posted February 13, 2023 Hi @jportraits, Thanks for your report and I'm sorry to see you're having trouble! I've tried this using with multiple images and I'm yet to be able to replicate the issue shown in your screenshot. Are you able to provide a copy of the source image shown above, or a copy of your .afphoto file before the blur is applied, that I can investigate further with here? Many thanks in advance Quote
jportraits Posted February 13, 2023 Author Posted February 13, 2023 it is a client shoot so im not sure. but maybe i will send a cropped affinity file with layer before blur and layers after Quote
Dan C Posted February 13, 2023 Posted February 13, 2023 No problem at all, I certainly understand! You can upload this file to the below link, such that it remains private with the Affinity team - https://www.dropbox.com/request/bSUoRWIUyjrwMvrkONX7 Quote
Staff MEB Posted February 13, 2023 Staff Posted February 13, 2023 This is a known issue that's already logged to be looked at.@jportraits, Out of curiosity, are you using a Mac with an M1 or M2 chip? Dan C 1 Quote A Guide to Learning Affinity Software
jportraits Posted February 13, 2023 Author Posted February 13, 2023 oh great so i dont need to send you my file? im on m2 mac mini i hope it is logged to be fixed not only looked ;D MEB 1 Quote
Staff Affinity Info Bot Posted February 22, 2023 Staff Posted February 22, 2023 The issue "Frequency Separation, destructive Gaussian Blur and High Pass: corruption/thin colored lines" (REF: AFP-5936) has now been fixed by the developers. This fix is included in build 2.1.0.1709 (or later) which is already available as a customer beta and will be included in the next release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us. Quote
Fat Bob Posted March 20, 2023 Posted March 20, 2023 Hello @Serif Info Bot I am still having this issue on a MacBook Air M2. Example attached. Very frustrating! Quote
walt.farrell Posted March 20, 2023 Posted March 20, 2023 30 minutes ago, Fat Bob said: I am still having this issue on a MacBook Air M2. Welcome to the Serif Affinity forums. Which application and release is that screenshot from? 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
walt.farrell Posted March 20, 2023 Posted March 20, 2023 5 minutes ago, Fat Bob said: This one. Downloaded and installed today. Thanks. As the Serif Info Bot said, On 2/22/2023 at 11:20 AM, Serif Info Bot said: This fix is included in build 2.1.0.1709 (or later) You're still on 2.0.4, the retail release. The fix is only in the beta test release for now, but will be in the next retail release, 2.1.something. 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
Fat Bob Posted March 20, 2023 Posted March 20, 2023 Ok - maybe I am an idiot. I am a little confused. This is what I get when I say check for updates... Which seems different from the 2.0.4 above. Anyway the system says I am up to date! Not sure what to do. Quote
jportraits Posted March 20, 2023 Author Posted March 20, 2023 just wait, it is not yet fixed but should be soon. fixed only in beta. for frequency separatuon you can use median blur which works ok. using beta version is an option too. Quote
Staff Chris B Posted March 20, 2023 Staff Posted March 20, 2023 As jportraits says, we are currently running a beta for anyone who has a purchased copy of V2 which includes regular fixes. You can request to participe here. If it suits, you can just download the beta and participate if you need the fix but be careful about opening V1 files in V2 (and possibly V2 release files). I would work from a copy to be save. Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials
jportraits Posted March 20, 2023 Author Posted March 20, 2023 yeah and i do work on beta version a bit and i can recommend doing so. if you need that fix. Chris B 1 Quote
Fat Bob Posted March 21, 2023 Posted March 21, 2023 Did what I needed to do in the Beta version. Thank you for the fast and helpful replies. Chris B 1 Quote
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.