11/29/2023 0 Comments Topaz denoise not showing in lightroom![]() In my tests, while the GPU is very busy, the CPU is very quiet during AI Denoise, with other background processes using more CPU than Lightroom Classic. That GPU model was released the same year as my laptop.) (I notice that D Fosse above only took 33 seconds using an RTX 3060 with 12GB VRAM. On the Windows side, I wonder if times are consistently faster using an NVIDIA GPU new enough to have their more recent AI acceleration hardware. The Neural Engine is only in Apple Silicon Mac processors, which might help explain why owners of older Intel CPU based Macs are similarly reporting much longer AI Denoise times in the minutes. And that machines with older AI acceleration hardware, or none at all, will have to take longer. ![]() My hardware list is at the end…really nothing special from a CPU/GPU point of view, so I strongly suspect it’s the Neural Engine machine learning hardware acceleration that cuts the times. I just did some tests and below is what I got. On my mid-range but recent laptop, I have so far never seen a Denoise time longer than a minute. Hardware acceleration specifically for machine learning/AI might be a missing link that helps explain why some computers can process AI features so much faster than others, and might help explain why older computers take much more time. I'm still testing but Adobe is looking very good.I think the Ian Lyons post that Victoria linked to may hold part of the answer to this. This gives me a starting point that still had some noise, and after finished editing I finalise the noise reduction(and sharpening) as a Photoshop layer using Topaz.Īs others have noted, DXO seems to extract a bit more detail than Adobe (as does Capture One), but, at the moment, I think I prefer the over all "look" of the Adobe denoising over DXO. In my previous test, I didn't use any default values but iterated different settings to try and get the best out of each program, and I can't really be bothered doing a proper comparison, but so far.Īt the end of last years testing I ended up using DXP Photolab 6 for with very low noise and lens correction values for initial processing (thus avoiding the sharpening artefacts with PR2) and exported as a linear DNG into either Capture One or Photoshop. ![]() So far I am finding the Adobe offering very good. I have been comparing Adobe with the tests I did last year (DXO, Topaz and ON1), using 11 different files. So, why the long time on my desktop pc? Well, it does have a rather ancient graphics card (GT1030) with just 2GB of RAM - I guess a new graphics card is on the horizon Overall, I think Adobe have made a good start along this road considering the time that Topaz have had to develop and refine DeNoise AI. Most of the extra time for the Topaz method was saving the image back into LRC. On my laptop both methods took pretty much the same time (with the LRC method coming in 35s quicker) and gave the same visual results. This took considerably longer to complete - 15:15 to be precise - and the subject still needed some sharpening afterwards (mask the subject and add sharpening to taste) but once completed I would have trouble telling the images apart. Time from start to finish was 1:17 and I got what I expected with well controlled noise and a small amount of sharpening. I have it set to initially go with its own suggested noise and sharpening and left it at that selecting the Clear option and saving back into LRC. So, first I used Topaz DeNoise which opened in the comparison view screen. I imported a NEF file shot at ISO 25,600 into LRC and then used both the new LRC Denoise and Topaz DeNoise AI to get a comparison, not just of the finished article but also which was quicker. I've just been playing with the new feature and initial results are quite positive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |