So a few nights ago, after shooting the very dark Lunar Eclipse at ISO 3200, leaving me with a fair bit of noise to clean up, I tried Topaz Photo AI, using a trial license, and was once again amazed at how well it dealt with the noise in my image. Since that review, though, I have, on several occasions, missed the pretty amazing noise reduction that the Topaz tools provided. I was going for a somewhat dimensional look vs 2D flat look to the processed image.īefore/After PAI snips (in the PAI UI) & Ps layer stack w/PAI output just above Bkgrnd Layer (labelled in the stack) snip.In April this year, I tried the Topaz Labs suite of tools and ended up requesting a refund because there were some nasty color casts in the DNG files that Topaz created after I processed some raw files from my Canon EOS cameras and viewed them in Capture One Pro. I didn’t add her to the set of subjects (purposefully) so you can see how she was treated differently than the others wrt expos., vibrance, etc. Interestingly, Ps “Select Subject” didn’t like (or pick up) the girl with the sax at far left either (perhaps all these AI robots are primarily acoustic fans and not brass?). Able to do add’l post-processing in Ps to add exposure to the subjects in foreground and desat & depth blur objects in background. Slight pixel shift (down & to the right) on the returned layer. Was able to save back to the Ps layer okay. I forget if there’s a way to add missed faces, vs just turning on/off detected faces. There are evident facial features on them and they’re in the same focal plane as the others. They are in a bit more shadow than the others, but should still be detected. I understand why it wouldn’t pick up girls with hair or pom poms across their faces… but PAI Face Detect didn’t get the girl whose face is fairly clear at far left (with the sax) nor the guy just above and to her left (camera right - with the trumpet). It said it was able to detect 18/19 faces. This group shot of the Stanford (Univ.) band (sorry, no tree in this image…) has a lot of small faces. So always have Face Detection set to Off by default. And processing time was faster than last night’s tree image too - it went relatively fast until I turned on Face Detect it needed a few moments to regroup itself and then kicked in. About 4 secs to open from Ps into the PAI plugin. This i mage behaved more like how the past couple months’ plugins were wrt launch and processing time. Image launched from layer stack into PAI plugin. ARW orig image opened into Ps 2023 via ACR (no adjustments in ACR). And, to use something other than a bird (which Topaz seems to like to use to prove product efficacy). I chose this to test b/c of all the fine details on the bloom & branch. or anything that will be aggravated by further post-processing in Ps or other 3rd party filters…īTW, this jpg snip looks softer here than it does on my monitor. That’s why I don’t want pixel shifts, etc. But I typically do more processing on all my Topaz plugin output layers. I enhanced what was produced with some Structure slider adjustments in Nik Viveza (also as a Ps plugin). It didn’t over-sharpen and/or create halos. The sharpening it did on the image I used I think did a realistic, natural job. This felt like a major step backwards wrt speed of ops. Not this release! Certainly not this run of it. And in the past couple months, the preview generating speed had been getting exponentially faster. The plugin product launched virtually immediately from Ps in all the recent several months releases. Or, take as l ong to generate a preview (12-15+ secs) since the alpha days… I don’t remember PAI plugin being this slow to load (min.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |