I’ll have to check that out, Terry.
Yes, I always DeNoise 1st before doing any other processing. Just to be sure I’m not sharpening noise or other artifacts I don’t want to draw attention to (or make them more difficult to eliminate from an image either). Also, I love creating composites so I like all potential elements that will become part of a composite to start from a consistently clean (no noise & no distracting details) yet flat base. I do all dodging, burning, sculpting for visual dimension and color toning/grading after the components are together.
I typically am highly critical of my own photography. Therefore I generally select the very few images I feel best about to process from any given shoot (or, travel). The result is that I end up with a small number of options I think deserve the ‘full Ps treatment’.
With that approach in mind, it didn’t occur to me to run a batch process for the full quantity of images I gen in any situation. But I’ll consider it.
Before Adobe updated Raw (in the past…) to support new cameras of mine, I’d run their DNG converter on my entire batch of images (I also wasn’t a fan of sidecar files & that was another motivation for doing so, but I digress). At some point I said to myself (yes, I talk to myself - but I don’t hear voices!), “Self, why are you doing this & generating so much more info for your (now Win 10) PC to store?? Especially if you aren’t planning to process all that.”
The reason I mention that is, I - possibly wrongly - assumed that running a batch DeNoise would gen a whole duplicate set of files (since there’s no way in ‘heck’ I’d save over the originals). If I’m only going to feel that maybe 5 -10 of my images are process-worthy then that’s gen’ing more memory content then I want to consume on my PC. Just like my DNG example above.
Perhaps, now that my PC is finally not only working in Win 10 (I had to do some other gyrations when it started plunking an error msg re: “Failed to Create Conexant Audio Factory…SmartAudio….” over every screen & app in the past few days) but I’ve also ported over my 3rd party plugins (including Topaz!) for use via my now also updated in the past wk Ps CC 2020 Filters menu, I can go back to testing some of these other new capabilities.
What you say makes a lot of sense. Besides my own inner critic motivations for not seeing the need - personally - for running batch processes, I think I may also have niched that type of processing as being most useful to wedding, lifestyle portrait and commercial photographers who shoot a lot and need to be able to provide a broad mix of images shot in similar (or the same) light. I rarely shoot the quantity I expect they do in order to come up with keepers that must look consistent. But I"m ready to give your suggested process a go for new adventures purposes if nothing else. And, will be excited if it saves me a step along the way! Thx for the updated note. It sounds like cool stuff for previous posters in this thread to think about too!