Undot in every script?

[N_F]

@trbarry - For the past few months I've used undot() for every encode where I remembered to add it (no matter how clean or noisy it was). As far as I've can tell it works fine. I also use it in combination with other denoisers like C3D and Deen.

1) Would you say it's a good idea using undot() in every script one uses (as it doesn't affect speed)?

2) Is there any reason why it should be avoided together with other filters? I usually use it before other denoisers, but I can't really see that it'd make any real difference if I used it after instead, can you?


A small goal of this thread is to find out if it could be a good idea having undot() as a constant in every script generated by Gordian Knot.

[trbarry]

N_F -

UnDot doesn't really run in zero time, that only happens in quantum computing (and placebos). ;)

But I think it's measurements are sometimes less than 1% of the total job so the reports get truncated.

I'm not aware of any obvious downside placing it anywhere in a script or any particular interaction with other filters except that it should be operating on progressive material. This means it should be placed after TomsMoComp, Telecide, etc.

And my own feeling for it is maybe to have it precede smoothing type filters like Deen, C3D, UnFilter, etc. But I don't now if that is important.

- Tom

[N_F]

Originally posted by trbarry
UnDot doesn't really run in zero time, that only happens in quantum computing (and placebos). ;) Yeah, but close enough :)

A further question: Can you imagine any source or situation where it would do more bad than good? Denoisers like deen and C3D can always blur the picture too much if used with bad settings on the wrong source, but this shouldn't be the case with undot, right?

[trbarry]

Technically UnDot blurs the picture also. But it only modifies something I was willing to give up.

Imagine a pixel P happily surrounded by its 8 neighbors in the middle of a 3x3 square somewhere on the screen like so:

21 4 50
20 P 64
7 10 8

The max valued neighbor here is 64 and the minimum is 4. All UnDot does is clip the value of P to be 4 <= P <= 64. If you can imagine any situation where you would really want P to be allowed to stray outside that range then you would not want to use UnDot. But generally this helps things compress a bit and removes mosquito noise some.

That's all UnDot does.

- Tom

[N_F]

Thanks for your answers. I will suggest adding undot() as default to len0x.