OTOY Forums

Just denoise.

EDIT: Made With NeatImage for After Effects. Really need to get the Photoshop plugin too. It will save time.

NeatImage looks promising, thanks.
Maybe some lightboxes will help too...

or, render high-res, bluring the image with inbuild tools that will get rid of the noise inside Octane Render without need of external programs - works good for me for certain scenes (but not always, not for all) wrote a bit 'bout it on my site http://tomglimps.com/lounge-chair-downl ... ne-render/

cheers

Octane render, pathtracing, 2048 bounces, 7114 samples, 1 hour, glossy walls, gtx 690, lited only by white environment.

also Nik tools - Dfine.. for denoising.. of course those can affect details, but with Nik tools you can easily affect regions instead of whole render..
- but anyways - your original render looks nice in a way - the noise is almost looking like grain - you can use some of those shitty instagram filters and it will look like its captered via smartphone - actually Nik tools is like instagram for grownups

- looks like it's time for octane to do a "grain" kernel, or do it in posteffects, and utilize that noise so it looks like old picture..

tomas_p wrote:Octane render, pathtracing, 2048 bounces, 7114 samples, 1 hour, glossy walls, gtx 690, lited only by white environment.

Hi Thomas_p,

nice test... and really noisefree!
So is it the "2048 bounces" setting, that eliminates noise with pathtracing?
Did you try the same scene with PMC?

Greetings,
ChrisVis

Neat Image did a pretty good job. Try to render it at 8k (DL diffuse) and then reduce it to 2k.

Hi ChrisVis

No, I don't try render this scene with PMC.
I think with PMC depends the rendertime on many things and setings.
But if you don't need the reflection of something in glass of windows, don't use the glass and use the portals instead of that and the render time will be much better. But if you render scene with lots of glass (for example 8 or more plates of glass) and lots of inner corners, chose PMC and set RR probability to 1,0. The rendertime will be terrible long, but the image will be relative noisefree in corners and axros the multiple glass. If you want render interiors with window glass, try compromis. Pathtracing with RR probability 0,0 and 24 bounces or PMC with RR probability betwen 0.85 - 0.95 and 24 bounces. Plus denoising. Or trie render it 2 times larger and than downsample it. But with the PMC will be the rendertime probably always longer than with pathtracing.

tomas_p wrote:Hi ChrisVis

No, I don't try render this scene with PMC.
I think with PMC depends the rendertime on many things and setings.
But if you don't need the reflection of something in glass of windows, don't use the glass and use the portals instead of that and the render time will be much better. But if you render scene with lots of glass (for example 8 or more plates of glass) and lots of inner corners, chose PMC and set RR probability to 1,0. The rendertime will be terrible long, but the image will be relative noisefree in corners and axros the multiple glass. If you want render interiors with window glass, try compromis. Pathtracing with RR probability 0,0 and 24 bounces or PMC with RR probability betwen 0.85 - 0.95 and 24 bounces. Plus denoising. Or trie render it 2 times larger and than downsample it. But with the PMC will be the rendertime probably always longer than with pathtracing.

Very interesting info. Is RR prob. documented anywhere or this comes from your experience?

Long time Octane fan here. Used it for my professional work over the last two years. I have to say that from my experience, Octane really isn't that fast compared to other cpu based engines (I'm in the process of switching to corona). Especially interior scenes. With PT it requires a bunch of trickery to get a high resolution, near noise free images. Even for exterior scenes with complex vegetation I get faster results with Corona.

Sure, you can probably make the case for Octane being the fastest engine, but that's with 2k+ worth of GPUs or with cloud rendering (which I'm eagerly awaiting)

That is just from my experience. Maybe I've been setting up my scenes the wrong way, but I've browsed the forums for solutions such as setting caustic blur to 1 and all the little hacks mentioned in this post. I just kind of gave up on it.