Staff Justin Posted July 21, 2020 Staff Share Posted July 21, 2020 Thanks for trying that Brad. I think this suggests the data has already been corrupted by the time it does the noise reduction and corrupted in such a way that the noise reduction code doesn't cope with it, which narrows things down a bit. Quote Link to comment Share on other sites More sharing options...
Brad Brighton Posted July 21, 2020 Author Share Posted July 21, 2020 48 minutes ago, Justin said: Thanks for trying that Brad. I think this suggests the data has already been corrupted by the time it does the noise reduction and corrupted in such a way that the noise reduction code doesn't cope with it, which narrows things down a bit. Glad to help. If you need additional info, just ask. Quote https://bmb.photos | Focus: The unexpected, the abstract, the extreme on screen, paper, & other physical output. Tools: macOS (Primary: Ventura, MBP2018), Canon (Primary: 5D3), iPhone (Primary: 14PM), Nikon Film Scanners, Epson Printers Link to comment Share on other sites More sharing options...
Staff Justin Posted July 21, 2020 Staff Share Posted July 21, 2020 Brad, could you try turning off hardware acceleration in Preferences|Performance please? Thanks Justin Chris B 1 Quote Link to comment Share on other sites More sharing options...
Brad Brighton Posted July 22, 2020 Author Share Posted July 22, 2020 17 hours ago, Justin said: Brad, could you try turning off hardware acceleration in Preferences|Performance please? Thanks Justin Turning off Hardware Acceleration appears to have eliminated the image result corruption in the 1-test-pass-per-version (production and beta) against the same dataset. Chris B 1 Quote https://bmb.photos | Focus: The unexpected, the abstract, the extreme on screen, paper, & other physical output. Tools: macOS (Primary: Ventura, MBP2018), Canon (Primary: 5D3), iPhone (Primary: 14PM), Nikon Film Scanners, Epson Printers Link to comment Share on other sites More sharing options...
Staff Justin Posted July 23, 2020 Staff Share Posted July 23, 2020 Hi Brad We've fixed a bug that was probably causing your issue so you might want to try it again when the next beta is released, which shouldn't be too long. Cheers Justin Brad Brighton and Chris B 1 1 Quote Link to comment Share on other sites More sharing options...
Brad Brighton Posted July 23, 2020 Author Share Posted July 23, 2020 52 minutes ago, Justin said: Hi Brad We've fixed a bug that was probably causing your issue so you might want to try it again when the next beta is released, which shouldn't be too long. Cheers Justin I'll keep an eye out, thanks! Chris B 1 Quote https://bmb.photos | Focus: The unexpected, the abstract, the extreme on screen, paper, & other physical output. Tools: macOS (Primary: Ventura, MBP2018), Canon (Primary: 5D3), iPhone (Primary: 14PM), Nikon Film Scanners, Epson Printers Link to comment Share on other sites More sharing options...
Brad Brighton Posted August 3, 2020 Author Share Posted August 3, 2020 @Justin @Chris B @MEB Recreating the test with Beta 1.8.4.186, Metal accelerator on: Crash: NO Corruption: NO (at least none seen through my 2x QuickLook scan of the 487 images, the same visual scan that easily found errant images in the past) Looks good. Quote https://bmb.photos | Focus: The unexpected, the abstract, the extreme on screen, paper, & other physical output. Tools: macOS (Primary: Ventura, MBP2018), Canon (Primary: 5D3), iPhone (Primary: 14PM), Nikon Film Scanners, Epson Printers Link to comment Share on other sites More sharing options...
titan3025 Posted May 27, 2022 Share Posted May 27, 2022 Hi all, I am seeing these corruptions as well with Affinity 1.10.5. My hardware setup: AMD 3800X and a nVidia RTX 2060 When I try do batch convert a bunch of images I see the same type of corruption in the files if I do parallel porcessing. If I disable parallel processing the corruption artifacts are gone. Is this know and is a patch already in the works? Cheers Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted May 27, 2022 Share Posted May 27, 2022 54 minutes ago, titan3025 said: Hi all, I am seeing these corruptions as well with Affinity 1.10.5. My hardware setup: AMD 3800X and a nVidia RTX 2060 When I try do batch convert a bunch of images I see the same type of corruption in the files if I do parallel porcessing. If I disable parallel processing the corruption artifacts are gone. Is this know and is a patch already in the works? Cheers Welcome to the Serif Affinity forums. You have replied to an old topic, about a bug that was already fixed, and was occurring on Mac systems. As that one was fixed, and as you're not on the same OS, it would be better for you to post your own new topic, I think, in Photo Bugs found on Windows and give full details of the problem you're seeing (including your OS, and whether you have Hardware Acceleration enabled in your Photo Preferences). Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
titan3025 Posted May 27, 2022 Share Posted May 27, 2022 Hi Walt, ok. Will post in the Windows forum. Cheers walt.farrell 1 Quote Link to comment Share on other sites More sharing options...
.thumb.jpg.6800ee623273eed4cf93a311483f65f9.jpg)
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.