A new version of Cineversity has been launched. This legacy site and its tutorials will remain accessible for a limited transition period

Visit the New Cineversity
   
 
Denoiser only for C4D generated content?
Posted: 01 March 2020 08:52 PM   [ Ignore ]  
Avatar
Total Posts:  31
Joined  2018-10-15

One of Noseman’s ‘what’s new in R21’ videos outlined how one could import an existing noisy image, set it as a material for say a sky with frontal projection, then perform a render with the denoiser.  I was able to replicate this as he did in his video by first doing a render of a simple scene without the denoiser.  Saved that noisy image, created a new scene with a sky, etc.  Rendering that new scene with the denoiser and found it produced a very clean result.

I then edited the material to reference a still of a movie clip recorded on my camcorder that had a high amount of noise.  But no noise at all is removed.  I ensured to set the output resolution of the scene to match that of the video’s still frame (UHD 3840 x 2160).

Can arbitrary still images or even movie clips benefit from C4D’s denoiser? Or does the denoiser only recognize/work on specifiic noise in 3D renderings?  Perhaps it only works on luminance/monochromatic noise?  The still from my video clip contains mostly chromatic noise.

Profile
 
 
Posted: 01 March 2020 09:25 PM   [ Ignore ]   [ # 1 ]  
Administrator
Avatar
Total Posts:  12043
Joined  2011-03-04

Hi Ricky Sharp,

There is no mentioning that the Denoiser takes any “Noise Pattern” based analytics nor that it is a temporal function.
Manual:
This is where Denoiser comes in: this function attempts to reduce the noise via blurring.

Which excludes the idea of luminance and chrominance differentiated functions.

The manual states already a lot of hints how it works, for example, that the Denoiser uses more information than a standard 2D denoiser would:
Manual
Contrary to simple 2D filters, Denoiser can also use other criteria that can help it recognize edges. Multi-passes such as Albedo and normal shading, for example, can be evaluated, i.e., 3D information that is not necessarily visible in the final image.

This would be the first indicator that post denoising with this is not as effective as it could be based on the full data set of the scene.

The comparison with the standard and physical render clear another point:

Manual
Denoiser also works with the Standard and Physical renderers (albeit after the render process has been completed). Here, there are also functions that remove grainy results. For example, think about the Physical renderer with a low sample setting or QMC GI, or Area shadows, etc. Here, Denoiser can be of a lot of help as well. Please be aware of the fact that the results will not be as good as with ProRender. This is due to the fact that the Intel Open Image Denoiser expects a path tracer-typical noise, which older renderers cannot provide. Don’t let this scare you - very good results can be achieved here as well!

Given these quotes from the manual, it becomes clear that the quality of the denoising has dependencies. It is preferable during render in the ProRender, while it is a good idea to save the Raw image.

My personal view, since it requires an Anti Alias
Manual
(Catmull 0.5 and Box 0.5 for Standard and Physical renderers, respectively)
Any post denoising might lower the quality in the process. Which is, of course, a judgment call, based on that each image is different.

Is a complete noise-free image always wanted? Since we have moved more and more away from 8bit/channel renderings in the past 25 years, the dithering is less given for 10bit/c or 16bit/c channel material, of occurs. Perhaps the problem banding (after denoising) is something to consider, as some noise often helps here more than it causes trouble. Again, this needs to be evaluated carefully.

I think the best way for denoising is, to have a few tools available, and check which one works best in each case, some are great but slower, etc.
The differences, as you mentioned, are temporal, pattern analytic, luminance, and chrominance, as well as in size (i.e., noise v. grain).

In a nutshell, there is no general rule from my point of view, and to have the denoiser inside of Cinema 4d is undoubtedly a win.

Cheers

 Signature 

Dr. Sassi V. Sassmannshausen Ph.D.
Cinema 4D Mentor since 2004
Maxon Master Trainer, VES, DCS

Photography For C4D Artists: 200 Free Tutorials.
https://www.youtube.com/user/DrSassiLA/playlists

NEW:

NEW: Cineversity [CV4]

Profile
 
 
Posted: 03 March 2020 09:36 PM   [ Ignore ]   [ # 2 ]  
Avatar
Total Posts:  31
Joined  2018-10-15

Thank you, Dr. Sassi.  Sorry for the late reply.

I had a feeling that the denoiser wasn’t a more general-purpose solution for images/footage.  I had hoped it was in order to save me from having to spend on more Final Cut plugins smile

I do really like the denoiser as I primarily do CPU-based rendering and am enjoying the faster render times.

Profile
 
 
Posted: 03 March 2020 09:45 PM   [ Ignore ]   [ # 3 ]  
Administrator
Avatar
Total Posts:  12043
Joined  2011-03-04

You’re very welcome, Ricky Sharp, thanks for the reply!

Yes, there are many solutions available that are more specific to footage and their unique noise patterns. Some even allow printing a color-based reference that should be taken before and perhaps after the shot (if it is a longer “take”). From there, the algorithm can take better care of the problem. I think that these 3rd party options have improved as well, so it is not a waste of money to have one of those as well. Especially when they analyze the content and provide with a few sliders professional results.

The advantage of this build in denoiser is, of course, that it takes the scene content into account.

My best wishes for your production.

 Signature 

Dr. Sassi V. Sassmannshausen Ph.D.
Cinema 4D Mentor since 2004
Maxon Master Trainer, VES, DCS

Photography For C4D Artists: 200 Free Tutorials.
https://www.youtube.com/user/DrSassiLA/playlists

NEW:

NEW: Cineversity [CV4]

Profile