Amir Curry Posted December 6, 2019 Share Posted December 6, 2019 So when you are trying to use the frequency separation it’s crashes. I start with a raw photo then duplicate it. Do minor corrections like hearing brush tool. I select filter for the frequency separation select the needed amount then it crashes the whole software. It will do this 8 of to 10 times before working. I am on the newest Mac ISO Catalina. Quote Link to comment Share on other sites More sharing options...
Staff Gabe Posted December 9, 2019 Staff Share Posted December 9, 2019 Hi @Amir Curry, Welcome to the forums. I cannot replicate this. Can you please attach a screen recording of this in action? Quote Link to comment Share on other sites More sharing options...
ChadR Posted December 24, 2019 Share Posted December 24, 2019 (edited) I am having the exact same issue. OS X 10.15.2. Affinity Photo 1.7.3. Every time I try to use Frequency Separation it crashes. Makes sure you set the Radius slider to the middle. If you leave the Radius slider all the way to the left then it won't crash. I have also attached a screen recording. The file I'm editing is a 26 megapixel tiff exported from Capture One. Originally it was a Fuji XT3 RAF (raw) file. Screen_Recording_2019-12-23_at_4_50.46_PM.mov Edited December 24, 2019 by ChadR DannyBCreative 1 Quote Link to comment Share on other sites More sharing options...
Pamei Posted December 28, 2019 Share Posted December 28, 2019 Even me I am facing the same issue. I restarted my machine multiple times and reset the studio as well but no luck.Please help. Quote Link to comment Share on other sites More sharing options...
Staff Gabe Posted January 2, 2020 Staff Share Posted January 2, 2020 I still cannot replicate it. Does it only happen with Tiff files from Capture one/Fuji? What are your mac specs? Quote Link to comment Share on other sites More sharing options...
ChadR Posted January 6, 2020 Share Posted January 6, 2020 My specs: I can reliably reproduce this issue. My workflow is to export TIFFs from capture one and edit them in Affinity Photo. Because this crashes so much I basically can't use Frequency separation at all. Quote Link to comment Share on other sites More sharing options...
Staff Gabe Posted January 7, 2020 Staff Share Posted January 7, 2020 Does it only happen with Tiff files from Capture one/Fuji? Does it crash with other(non-tiff) file types? Quote Link to comment Share on other sites More sharing options...
ChadR Posted January 8, 2020 Share Posted January 8, 2020 Not sure. Do you want an image that demonstrates the crash? Do you want a crash report? I would like to get this bug fixed as frequency separation is extremely important to anyone doing retouching with Capture One. Any ETA on a fix? Quote Link to comment Share on other sites More sharing options...
Staff Gabe Posted January 9, 2020 Staff Share Posted January 9, 2020 11 hours ago, ChadR said: Not sure What do you mean by this? Have you tried your workflow in Affinity Photo with a different file (not exported from Capture One, and not a TIFF)? What was the outcome? Since we can't replicate this issue on our end, we cannot say why it's crashing at this point. 11 hours ago, ChadR said: Do you want an image that demonstrates the crash? Yes. Can you zip the image and upload it here? Quote Link to comment Share on other sites More sharing options...
ipb Posted January 12, 2020 Share Posted January 12, 2020 I am also having this problem, Mac OS X 10.15.2 Affinity Photo 1.7.3. The image is a poor quality jpg from a scanned image that I am trying to improve. I tried setting the radius slider all the way to the left as advised above, but affinity photo still crashes every time I click apply. Quote Link to comment Share on other sites More sharing options...
Staff MEB Posted January 13, 2020 Staff Share Posted January 13, 2020 Hi ipb, Welcome to Affinity Forums Can you please try this: go to Affinity Photo Preferences, Performance section and disable/untick Enable Metal compute acceleration checkbox. Can you still reproduce the crash with Metal disabled? What's your system specs (namely the built-in a dedicated graphic card if you Mac have one)? Thanks. Quote A Guide to Learning Affinity Software Link to comment Share on other sites More sharing options...
ChadR Posted January 14, 2020 Share Posted January 14, 2020 I have confirmed it crashes on a Fuji RAF file. Previously I said it crashed on a TIFF generated from Capture One. It appears this bug has nothing to do with Capture One. File attached. It crashed for me when I set frequency separation radius to 39.8px. I have also confirmed that it appears to only crash when Metal is enabled. I tried multiple times. 0/2 crashes with Metal disabled. 2/2 crashes with Metal enabled. Hardware is attached. DSCF9048.RAF Quote Link to comment Share on other sites More sharing options...
ChadR Posted January 14, 2020 Share Posted January 14, 2020 I've uploaded a RAF and my system specs. If you need any additional data from my system please let me know. Happy to test a build if you are able to fix the bug. Quote Link to comment Share on other sites More sharing options...
ChadR Posted January 16, 2020 Share Posted January 16, 2020 @MEB were you able to reproduce this yet? I can use frequency separation with metal disabled, but it's very slow and painful. Really hoping we can get a fix soon. Thank you. Quote Link to comment Share on other sites More sharing options...
Staff Gabe Posted January 17, 2020 Staff Share Posted January 17, 2020 We're still struggling to replicate it here. Any chance you can attach a screen recording of this in action? Chris B 1 Quote Link to comment Share on other sites More sharing options...
ChadR Posted January 17, 2020 Share Posted January 17, 2020 @Gabe I sent you a screen recording on December 23. Please see above in this same thread. Quote Link to comment Share on other sites More sharing options...
ChadR Posted January 17, 2020 Share Posted January 17, 2020 @Gabe I’ve also sent the image file, steps to reproduce, hardware and OSX info. I’m software engineer so if there is anything I can do to help you let me know. I’m in California USA in case you have anyone out here who wants to see it happen live and debug it. I’m also willing to run a debug build if you have one that collects more info on the crash. Really want to get this fixed soon. Quote Link to comment Share on other sites More sharing options...
Staff Gabe Posted January 17, 2020 Staff Share Posted January 17, 2020 Sorry I missed that. We've not got public debug builds. Can you attach the crash report so I can log this with our developers? Also, any chance you can try and see if it crashes on a RGB/8 document? I see that you've not tried this yet. Quote Link to comment Share on other sites More sharing options...
ChadR Posted January 17, 2020 Share Posted January 17, 2020 3 hours ago, Gabe said: Sorry I missed that. We've not got public debug builds. Can you attach the crash report so I can log this with our developers? Also, any chance you can try and see if it crashes on a RGB/8 document? I see that you've not tried this yet. @Gabe do you have an email address I can send the crash report to? I don't want to post it publicly in case there is sensitive data in it. Quote Link to comment Share on other sites More sharing options...
Staff Gabe Posted January 20, 2020 Staff Share Posted January 20, 2020 Sure. You can upload it to our dropbox. It'a write-only folder and only staff can see the contents https://www.dropbox.com/request/swbMstDUA57P6XIf5T9x Quote Link to comment Share on other sites More sharing options...
ChadR Posted January 21, 2020 Share Posted January 21, 2020 @Gabe I've uploaded the crash report as requested. Quote Link to comment Share on other sites More sharing options...
Staff Gabe Posted January 23, 2020 Staff Share Posted January 23, 2020 Thanks. I logged this with our developers. Quote Link to comment Share on other sites More sharing options...
ChadR Posted January 23, 2020 Share Posted January 23, 2020 @Gabe how long will it take to get a response from the developers? I haven’t been able to use frequency separation reliably for the last couple months. Quote Link to comment Share on other sites More sharing options...
Staff Gabe Posted January 24, 2020 Staff Share Posted January 24, 2020 I'm afraid we don't have an ETA. Sorry The workaround, for now, is to disable Metal. Quote Link to comment Share on other sites More sharing options...
hotpurple Posted January 26, 2020 Share Posted January 26, 2020 Hi, I'm experiencing the same bug. I've tried turning off metal compute acceleration (I have a MacBook Pro Retina 15" from late 2013 with intel Iris Pro Graphics) and the problem remains. Is there a workaround for this? Quote 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.