deen.dll MarcFD

[GhostAFRippEr]

"I am looking for the source code of deen.dll created by MarcFD in order to port it to 64-bit. None of the denoisers I have used worked as efficiently as this one. I've tried them all—SMDegrain, MDegrain, KNLMeansCL, MiniDeen, dfttest, and FFT3DFilter—but I couldn't get results as high-quality as I did with deen.dll

[ChaosKing]

IIRC it was never open source.
But there is MiniDeen https://forum.doom9.org/showthread.php?t=176554

[real.finder]

IIRC it was never open source.
But there is MiniDeen https://forum.doom9.org/showthread.php?t=176554

he already mention MiniDeen :)

anyway, GhostAFRippEr, you have only two options:-

1- ask prunedtree/MarcFD in IRC (if he still use it, I think in #darkhold in Rizon)

2- Reverse engineering the .dll yourself :) like how SEt did it with aWarpSharp2 or TurboPascal7 with others prunedtree/MarcFD plugins

[ChaosKing]

Which version of "the best" deen is the latest, could you give me a link?

According to avs wiki, we have 2 versions and the older one is the better one?

Deen beta 2 is the older version, unfortunately is also the most known and used version (most of the scripts that use Deen use syntax that's specific to beta 2).
Deen v1.0 beta 1 is the updated version and it includes these changes:

Original meth parameter renamed to mode
Original mode parameter renamed to rad
New modes "c2d", "w2d", "w3d" ("m2d" is no longer supported)
ti (temporal influence) is now controlled independently by tthY and tthUV (luma/chroma), input value is now an integer (use to be float).
New parameters: min, scd, fcf, borderfix

Be aware that using the updated version as a drop-in replacement without adjusting the parameters to match the original can result in different behavior.

[qyot27]

1.0 beta 1, because it supports the w modes.

At this point I think it's sufficient to say that anyone complaining that the older version was the 'better' version wasn't talking about the quality (the wiki page doesn't mention that at all), but because the parameter naming changed and maybe some of the defaults, and people simply didn't want to update their scripts. After 23 years, IMHO it's perfectly safe to ignore that.

Thing is, deen was an offshoot of Convolution3D, which already has been updated and ported to modern AviSynth+ by pinterf (https://github.com/pinterf/Convolution3D). Back in 2003, most plugins likely didn't even include C/C++ reference implementations of the code, and used non-portable, MSVC-specific dialects of MMX, ISSE, etc. assembly directly. Knowing that deen was mostly just adapting and refining aspects of Convolution3D (the early comments on it basically just seemed like it was doing it faster...i.e. assembly optimizing, not so much algorithmic tweaking) would perhaps make more sense to just take hints from the description of the additional modes and base the work off what pinterf already did to bring up Convolution3D. It'd be way more transparent and portable, and way faster than either waiting for the original code to be released or to re-implement everything from scratch.

[DTL]

To save more from temporal artifacts with moving pictures I think it can be combined with standard motion compensating with mvtools (or other if present) and use typical interleave->process->selectevery sequence in script. At the times of active development of this filter mvtools not yet exist for AVS (?).

Though its proceessing may be close to something like 2D smoother + temporal smoother like vsTTempSmooth.

[ChaosKing]

I had some Fable tokens left. Here's a 64bit recomp of Deen v1.0 beta 1.

The process took around 70min on linux+wine for a bit exact output (pls test). + 40min for benchmarks & AVX2.

Without optimizations: 4-6x slower (depends on the mode)
With some AVX2 SIMD: 5-7x faster

1080p Source
Configuration │ Original MMX │ Recomp x86 AVX2 │ Recomp x64 AVX2 │ x64 AVX2 + 8T │
├───────────────┼───────────────┼─────────────────┼─────────────────┼───────────────┤
│ c2d rad2 │ 106 fps │ 740 fps │ 673 fps │ 508 fps not sure why, could be wine related │
├───────────────┼───────────────┼─────────────────┼─────────────────┼───────────────┤
│ c2d rad7 │ 13 fps │ 79 fps │ 82 fps │ 221 fps │
├───────────────┼───────────────┼─────────────────┼─────────────────┼───────────────┤
│ c3d rad2 │ 38 fps │ 221 fps │ 228 fps │ 370 fps │
├───────────────┼───────────────┼─────────────────┼─────────────────┼───────────────┤
│ w3d rad2 │ 27 fps │ 165 fps │ 157 fps │ 333 fps │
├───────────────┼───────────────┼─────────────────┼─────────────────┼───────────────┤
│ a3d rad2 │ 37 fps │ 147 fps │ 146 fps │ 306 fps │

Benchmarks are done on a Ryzen 9600x Linux via Wine.

There's a new parameter DEEN_THREADS=X

Binaries in attachment.