[Neo] FFT3D / DFTTest

[real.finder]

Originally Posted by Dogway

I get artifacts with this filter (check link) and had to roll back to plain dfttest. Probably an issue with HBD but I'm not sure. It gave me headaches for the last few days debugging my script.

This is my function call:

sneo_dfttest(slocation="0.0:5.0 0.2:4.0 1.0:1.0",tbsize=3,u=3,v=3)

this should be fixed on last update in sneo_dfttest in Community tree

Originally Posted by LeXXuz

I get quite different filesizes in direct comparison between dfttest and neo-dfttest with AVS+.


Have there been any changes to the default filtering method or have the sigma values been reworked?

I used these script lines for dfttest/neo-dfttest:

dfttest(Y=true, U=true, V=true, sigma=64, tbsize=5, dither=0, threads=8, opt=4)

and

neo_dfttest(Y=3, U=3, V=3, sigma=64, tbsize=5, dither=0, threads=8, opt=3)

Shouldn't filesizes roughly be the same with both filters

maybe those because neo_dfttest is based on VS dfttest port which has some default settings changes

neo/vs -> original avs dfttest

sigma/sigma2
8.0 -> 16.0

sbsize
16 -> 12

sosize
12 -> 9

tbsize
3 -> 5

so I think these need to be added in

Originally Posted by MeteorRain

Difference compared to pinterf/dfttest

• Dual interface, supporting AviSynth+ and VapourSynth
• Parameter names and opt levels follow VapourSynth-DFTTest
• Removed Y, U, V options, added y, u, v options for plane control
• Removed hacked 16 bit I/O
• Replaced internal multi-threading with C++ Parallel STL, removed Windows specific APIs
• Improved precision of floating point reciprocal using Newton Raphson method

edit: sigma/sigma2 was mentioned https://forum.doom9.org/showpost.php...02&postcount=4 but others are not

[LeXXuz]

I have a general question regarding dfttest. But the original thread I found is rather ancient so maybe this is a better place.

My question is regarding frequencies with the sstring-parameter. I would like to understand this better.

From the Wiki:

string sstring, ssx, ssy, sst = ""

Used to specify functions of sigma based on frequency.

If you want sigma to vary based on frequency, then use 'sstring' instead of sigma. sstring allows you to enter values of sigma for different normalized [0.0,1.0] frequency locations.
Values for locations between the ones you explicitly specify are computed via linear interpolation. The frequency range, which is dependent on sbsize/tbsize, is normalized to [0.0,1.0] with 0.0 being the lowest frequency and 1.0 being the highest frequency.

I'd like to understand better what is meant by frequencies in this case. After Fourier transform higher frequencies represent higher/finer structures or detail in the picture while lower frequencies represent low details, right?

Noise is usually somewhat fine detail, so higher frequencies should be filtered maybe more, than lower ones?

I ran some tests on a sample with very fine/ high pitched noise and these sigma strings:
1) sstring="0.0:0 0.7:0 0.8:64 1.0:64" (strong filtering for hf and no filtering for lf)
and vice versa
2) sstring="0.0:64 0.2:64 0.3:0 1.0" (no filtering for hf and strong filtering for lf)

According to the Wiki, the first string should filter that very fine noise much better than the second. But the opposite seems to be the case. So I was wondering if that maybe a typo in the Wiki or I made a mistake.

Can someone test and either confirm or disprove this?

[real.finder]

seems both plugins here have same problem as https://github.com/HomeOfAviSynthPlu...f3kdb/issues/7 (at least in avs+)

[kedautinh12]

real.finder updated new commits to fix Update AVS headers and copy frame properties for AVS+ and VS. If anyone interested
https://github.com/HomeOfAviSynthPlu...commits/master
https://github.com/HomeOfAviSynthPlu...pull/6/commits

[kedautinh12]

After tested with new commits from real.finder. I seen speed was increased

[tormento]

Originally Posted by kedautinh12

After tested with new commits from real.finder. I seen speed was increased

Where to find the Windows build?

[kedautinh12]

Here only x64 built by real.finder, need x86 build by someone, thanks
https://github.com/HomeOfAviSynthPlu...28/neo-x64.zip

[GMJCZP]

Originally Posted by kedautinh12

Here only x64 built by real.finder, need x86 build by someone, thanks
https://github.com/HomeOfAviSynthPlu...28/neo-x64.zip

Thanks, we will be waiting for the x86 version to test it.

[kedautinh12]

Originally Posted by StvG

Sorry for the late reply.
Used script:

LoadPlugin(".\NeoFFT3D_r7\clang-x64\neo-fft3d.dll")
ColorBars(1920,1080, pixel_type="rgbp16") #tested rgbp, rgbps, yv12, yuv420p16, yuv420ps, yuv444ps (same behavior always)
n=3
a=neo_fft3d(sigma=1.0, beta=1.0, bw=48, bh=48, sharpen=0.040, scutoff=0.01, y=3, u=2, v=2, bt=5, opt=n)
b=neo_fft3d(sigma=1.0, beta=1.0, bw=48, bh=48, sharpen=0.040, scutoff=0.01, y=3, u=2, v=2, bt=5, opt=1)
Compare(a,b)
Subtitle("neo_fft3d(sigma=1.0, beta=1.0, bw=48, bh=48, sharpen=0.040, scutoff=0.01, y=3, u=2, v=2, bt=5, opt="+string(n)+")"+"\n"+"neo_fft3d(sigma=1.0, beta=1.0, bw=48, bh=48, sharpen=0.040, scutoff=0.01, y=3, u=2, v=2, bt=5, opt=1)", lsp=1, y=1040)

Fixed
https://github.com/HomeOfAviSynthPlu...FFT3D/releases

[kedautinh12]

Originally Posted by GMJCZP

Thanks, we will be waiting for the x86 version to test it.

Had x86 ver

[bruno321]

I'm trying to load the plugin but failing. Here's what avsmeter reports:

Cannot load file 'C:/Program Files (x86)/AviSynth+/plugins64/neo-fft3d.dll'. Platform returned code 126:
The specified module could not be found.

Dependencies that could not be loaded:
MSVCP140_ATOMIC_WAIT.dll

Visual C++ Redistributable for Visual Studio 2015 is already installed, is there something else I should be installing? Thanks.

[kedautinh12]

You can download latest ver here:
https://github.com/abbodi1406/vcredist/releases

[kedautinh12]

Neo-DFTTest updated r8
https://github.com/HomeOfAviSynthPlu...TTest/releases

[FranceBB]

Thanks for the heads up.
Github is on drugs this morning, though:

<Code>ServerBusy</Code>
<Message>Egress is over the account limit. RequestId:59449abb-501e-005b-2704-bd1b5e000000 Time:2022-08-31T06:40:34.5336533Z</Message>

EDIT: And now is back.


EDIT2: If you're using Windows XP please note that r8 x86 build will NOT work on Windows XP!