MCTemporalDenoise port?!

[asarian]

Is there ever a chance to get MCTemporalDenoise ported?! Then I could completely switch to a 64-bit VapourSynth environment! :)

[Mystery Keeper]

Not MCTemporalDenoise, but works for me.
http://forum.doom9.org/showthread.php?t=169782

[Boulder]

I think SMDegrain is also quite close to MCTD.

[asarian]

I think SMDegrain is also quite close to MCTD.

Thx. :) Looks like I may have to use SMDegrain then. :)

[asarian]

I think SMDegrain is also quite close to MCTD.

Actually running a project with MCTD right now (on 'medium', which is pretty strong); and I had forgotten how slow it is. As in: it only taxes my i7 980X for like 25% (full-HD). I really hope VapourSynth will improve on this. :)

[~SimpleX~]

What do you need from MCTD? I've ported the denoising stage (only 1-pass) with MDegrain. No pp at all, no deblock. FFT3DFilter doesn't support >8bit so I used dfttest.

https://gist.github.com/SX91/ef4f80d97e8bce083216733d8d90dfef


mctd_args = mctd.defaults("medium")
mctd_args["thsad"] = 300
mctd_args["thscd1"] = 300
mctd_args["thscd2"] = 100
mctd_args["sigma"] = 3
mctd_args["bt"] = 3

mctd.mctd(clip, **mctd_args)

[asarian]

What do you need from MCTD?[/CODE]

That was a long time ago, in a galaxy far far away. :) I'm primarily using KNLMeansCL, nowadays.

[~SimpleX~]

To me MCTD is more precise. KNLMeans blurs too much on fades. MCTD have some limiting (which makes it less efficient than SMDegrain, but preserves more details).

Does KNLMeans replace MDegrain?

[GMJCZP]

I have not used it, but how about TNLMeans (Groucho 2004)?

[Joachim Buambeki]

I too would love to see MCTD ported, I remember the results to be very comparable to commercial software back when I used it in AVS and would love to see how it stacks up against today's iterations of commercial denoisers. :thanks:

If anyone is going to port it, please consider adding frequency separation as discussed in this post and the following ones (https://forum.doom9.org/showthread.php?p=1806167#post1806167).

[feisty2]

No, vbm3d is (roughly) the best, if u leave out machine learning based algorithms

[asarian]

I noticed MCTemporalDenoise got ported to VS now. :) Very good to see! Typically, MCTemporalDenoise wasn't very stable, though, and had to run inside at least SetMTMode(3) (on AviSynth, of course). So, how has VapourSynth solved this matter?

[Boulder]

VS is simply super stable what comes to multithreading. I don't recall ever causing it to crash unless some plugin itself did that.

[asarian]

VS is simply super stable what comes to multithreading. I don't recall ever causing it to crash unless some plugin itself did that.

Thank you! :)

I also remember I used to multi-thread it, like

MT("""MCTemporalDenoise(settings="medium")""", threads=6, overlap=8)

I suppose that sort of thing can't be done in VS, right?

[Boulder]

I suppose that sort of thing can't be done in VS, right?

There's no need to, VS will automatically use multiple threads according to what it detects and which plugins are used.

[asarian]

There's no need to, VS will automatically use multiple threads according to what it detects and which plugins are used.

Even better! :) Thank you for the swift replies!