[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]
2023-11: Warosu is now out of extended maintenance.

/3/ - 3DCG

View post   
File: 18 KB, 653x254, blender.png [View same] [iqdb] [saucenao] [google]
699685 No.699685 [Reply] [Original]

THE MADMEN ACTUALLY DID IT

https://wiki.blender.org/wiki/Reference/Release_Notes/2.81/Cycles

https://openimagedenoise.github.io/

>> No.699687
File: 67 KB, 692x858, comeonman.jpg [View same] [iqdb] [saucenao] [google]
699687

Denoise has been there since 2.76 I believe.

>> No.699689

>>699687
The intel denoiser is much better, tho.

>> No.699690

>>699689
Yeah this one was just to remove Cycles' trademark graininess, they gpt tired of all the bants hehe.

>> No.699691

>>699685
It's unironically really cool. I love how it's integrated into the compositor it's so simple to use and tune.

I might post some comparison pics later if I can be bothered to, there's heaps of 'reviews' of the denoiser on YouTube ATM though.

FlippedNormals did a good rundown of it, showing off different material types.
But, cos of YouTube compression you can lose a lot. Okay
You convinced me I'll post comparisons tomorrow.

>> No.699692

>>699685
>A new denoise node was added in the compositor
>A new denoise node
>in the compositor
>COMPOSITOR
>blendlets: Cycles is a compositor
>HAHA INDUSTRY BTFO CYCLES BEST RENDERER EVER
>make fun of blendlets for not even knowing how to read their own software's changelog
>blendlets: REEEEEEEEEEEEEEEEEEEEEEEE
>yet another gimped version of an old, established feature of industry software
>REEEEEEEEEEEEEEEEEEEEEEEEEEE
>Cycles is still stupidly slow
>REEEEEEEEEEEEEEEEEEEEEEEEEEE
>you can also literally plug any image into the denoiser node, because it's a comp node and not a "Cycles" thing
>REEEEEEEEEEEEEEEEEEEEEEEEEEE
The joke writes itself.

>> No.699693

>>699692
>He doesn't know

>> No.699696

The best way to reduce noise is to not make it in the first place. Denoisers are a crutch. Render optimization is the right way.

>> No.699701

>>699696
>just render for 48 hours bro

>> No.699703
File: 400 KB, 1920x1080, Donut noised.jpg [View same] [iqdb] [saucenao] [google]
699703

heres my brand new donut with noise

>> No.699705
File: 197 KB, 1920x1080, Donut denoised.jpg [View same] [iqdb] [saucenao] [google]
699705

>>699703
and denoised with the intel thing

>> No.699706

>>699701
Yeah, no. You look for the causes of the noise (by AOV) and use that info to reduce it, sampling extra only where needed -- a light, some material, a refraction component, etc.

>> No.699711

>>699685
I'm so lucky my old q9650 already supports SSE4.1! gosh!

>> No.699712

>>699706
Why not use both though

>> No.699716

>>699705
amaze

>> No.699728

>>699692
Rent free

>> No.699729

>>699705
now try the old built in denoise in the layer tab

>> No.699730
File: 688 KB, 1023x677, donut.png [View same] [iqdb] [saucenao] [google]
699730

This is the old built in denoise, to show the difference.

>> No.699731
File: 1.40 MB, 1023x677, donut1.png [View same] [iqdb] [saucenao] [google]
699731

Same without

>> No.699733

>>699730
>>699731
both 100 samples

>> No.699753

>>699706
dude, stop trying to educate blendlets, they literally do not even know how to read.

>> No.699781

>>699753
rent free

>> No.699803

>>699703
You're using too many samples bro.
Show them how it works with 4 samples, or hell, just 1.

>> No.699807
File: 704 KB, 894x1080, 5-Samples-Builtindenoise.jpg [View same] [iqdb] [saucenao] [google]
699807

>>699803
smart idea, built in denoiser 5s samples

>> No.699811

>>699807
kek, the dough became more realistic.

>> No.699817

>>699811
Shit it actually did hahaha
Take the cleaner shadows from the other render and out them with that one