Gnobelix Posted April 25, 2019 Share Posted April 25, 2019 Hello everybody, I wanted to replace the sky in a picture. I proceeded as follows: 1. open a TIFF-File (4000 pix * 6000 pix= 2. duplicate the Image 3. go to channels 4. select Background blue and create a Greyscale Layer 5. back to Layers 7. select the Greyscale Layer 8. got to Adjustments and select Brigtnees/Contrast (eg increase the contrast and merge) 9. got to Adjustments and select Levels (eg increase the black level/white level and merge) 10. activate the paint brush tool, set the Color on black, opacity on 100%, hardness on 0% and the blend mode on Overlay 11. paint the whole Image (repeat step 10 and 11 with the color white) (With this method I want to create a pure black and white mask.) The utilization of the CPU quickly reaches a value of almost 100%. It takes a felt perceived eternity until Affinity releases the previously requested performance. This is not the case in the current customer version. How the performance was in the last beta, I do not know anymore. I think a test with the last beta (.283) is no longer possible, the test phase will probably have expired. Can someone confirm the high utilization of the CPU? Chers IMGP4573.afphoto Affinity Photo 2.4: Affinity Photo 1.10.6: Affinity Designer 2.4: Affinity Designer 1.10.6: Affinity Publisher 2.4: Affinity Publisher 1.10.6: Windows 11 Pro (Version 23H2 Build (22631.3447) Link to comment Share on other sites More sharing options...
walt.farrell Posted April 25, 2019 Share Posted April 25, 2019 Your attached .afphoto file is corrupted (too short), according to Photo 1.7.0.293. I am curious whether you left a step out, as I can't figure out what painting the complete image with black then painting it again with white should accomplich. If you didn't make another layer in there, or switch to another layer, aren't you just going to have the same effect as simply painting with white in the first place? -- 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...
Gnobelix Posted April 26, 2019 Author Share Posted April 26, 2019 Sorry, why the file is corrupted I do not know, maybe there was an error uploading.I loaded two files into the dropbox here the link Cheers Affinity Photo 2.4: Affinity Photo 1.10.6: Affinity Designer 2.4: Affinity Designer 1.10.6: Affinity Publisher 2.4: Affinity Publisher 1.10.6: Windows 11 Pro (Version 23H2 Build (22631.3447) Link to comment Share on other sites More sharing options...
Staff Chris B Posted May 8, 2019 Staff Share Posted May 8, 2019 Seems fine in my slightly newer build. I've either missed something or something has improved in the build I have. Would you mind trying this again once you get the next beta build? Gnobelix 1 How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
Recommended Posts