I used to use a noise reduction software to which you could "teach" what NR settings to apply automatically according to the camera brand, the ISO, the aperture and the speed. The results were good, but the NR was still applied globally to the whole image, and sometimes I had to create several output images using different NR settings and use masks in order to achieve a good result.
Where the camera has an advantage is that it knows precisely how the sensor behaves, when and where it will create the most noise and what kind of noise, maybe even detect different kinds of surfaces and apply different noise reduction settings on different parts of a photo in order to preserve more details when possible. But of course this all relies on the camera's "AI" (I am not sure the word "AI" really applies here), the AI could guess incorrectly, and the user could achieve a better result with enough experience and time. Le dimanche 31 juillet 2022 à 23:57:13 UTC+2, GnomeNomad a écrit : > > > On July 31, 2022 9:27:10 AM HST, "[email protected]" < > [email protected]> wrote: > > > > > > On Sunday, July 31, 2022 at 2:49:59 PM UTC-4 [email protected] wrote: > > > > > I see, thank you for the detailed reply. Does that mean that you are > > > working with jpg files? I haven't dug into the code. Why not just use > some > > > temporary folder for the tiffs, and erase them when finished? > > > > > > I never think I'm "finished". I haven't yet gotten a single panorama > as > > correct as it looks like it could have been. So they are all sitting > > around waiting for me to try some improvement either to Hugin itself or > to > > my skill at using hugin. > > I do work mainly with the jpg files. The fact that RawTherapee (at least > > on default settings) doesn't do the noise reduction and interpolation as > > well as the camera does itself, combines with the inconvenience of > keeping > > the temp files around. > > In other cases, the jpg has lost too much detail in the darker sections > > (because 8 bits just isn't enough) so pre-converting to tiff is > necessary. > > Hmm, I shoot raw files (no jpg), and have no problems with Rawtherapee's > noise reduction. I do my conversions to 16-bit per channel TIFF in > Rawtherapee, then feed that into Hugin. > > In my experience, the amount and type of noise reduction needed varies > from image to image, even the same ISO. The amount of contrast in the > scene, how bright and dark things are, produces different types (and > degrees) of noise. > > My Sony A58 and my previous Minolta 7D both use 16-bit per channel > sensors, but only output 12-14 bit RAW files. I think in-camera noise > reduction is done on the 16-bit image data, right? I think that's the one > point where in-camera could do a better job, only with much less control > over how it's done. > > > -- > David W. Jones > [email protected] > exploring the landscape of god > http://dancingtreefrog.com > > Sent from my Android device with F/LOSS K-9 Mail. > -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/1aaea8c9-037c-42fa-9ce9-82faa196cc26n%40googlegroups.com.
