[Neo] FFT3D / DFTTest

[MeteorRain]

I was adding back ncpu as I noticed a misunderstanding on fftw multithreading.

Regarding your ticket, yes somehow the repo was not in my watch list. I'll test when I finish my work.

Currently working on soxfilter.

[Atlantis]

I have a suggestion for Neo FFT3D y, u, v values. Things should be intuitive and simple and make sense.
I propose. for Y U V use
0 - Copy from origin
1 - Process
2 - Do not touch, leaving garbage data

for example this
neo_fft3d(y=3, u=2, v=2, sigma=6)
neo_fft3d(y=2, u=3, v=3, sigma=3)

That is hard to follow, this below makes much more sense and easier to read.

neo_fft3d(y=1, u=0, v=0, sigma=6)
neo_fft3d(y=0, u=1, v=1, sigma=3)

You already deleted planes because they were hard to read and YUV are easier names. So the values they get should follow the same rule and not be something like 1 for something that not many people use.

[crystalfunky]

Can somebody give me good values I can use for 4K HDR encoding,
x264 normal movies and also for b/w movies like 12 angry men?
Would appreciate it!

[Atlantis]

Every movie is different and you can't have good values for all. You have to try different things and see what you like.

I personally try to make it as simple as possible, so I just change the sigma value only and see what I like. I go from 1 to even 6.

[crystalfunky]

Are the commands and their values in the neo versions from dftest and fft3d different from the old versions?
If not, I need to understand them, so I can test different values and finally use the filters.

[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)

[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)

sneo_dfttest is warper I made to make it use neo_dfttest and if there are no neo_dfttest loaded it will use old dfttest

[Dogway]

Originally Posted by real.finder

sneo_dfttest is warper I made to make it use neo_dfttest and if there are no neo_dfttest loaded it will use old dfttest

Yes I know, I use neo_dfttest through your wrapper (didn't actually check what was doing though), but the filter has issues as depicted by the linked video with random color spots.

I spent 2 days trying different things to find the culprit and it actually was neo_dfttest, so for now I cannot recommend it to anyone.

[ajp_anton]

Your filters neo_dfttest and neo_fft3d don't pass through audio. Is that by design?

[StainlessS]

To not do anything for audio, do not define GetAudio() [in the filter class, think thats what its called] member function, will use default behaviour, ie pass-though.

Mobile:

[l33tmeatwad]

This probably won't get any traction, but the way FFTW3 is being loaded by this plugin is causing FFTW3 to hard crash on macOS. I've tried to narrow down what is causing it, it appears to be crashing when calling it a second time (past validating that it exists). Crash will happen when attempting to seek or advance by a single frame. I know Catalina (the only version this will compile on) has caused issues for a lot of similar issues with other plugins, but I'm not sure what to do about fixing it.

[kedautinh12]

Can anyone compile neo-fft3d with this commit??
https://github.com/HomeOfAviSynthPlu...1e098280d5d884

Thanks

[real.finder]

I already did both http://www.solidfiles.com/v/xZn85B3knMGAy and http://www.solidfiles.com/v/55WKMW38dpX42

[kedautinh12]

Thanks

[LeXXuz]

Originally Posted by Dogway

I get artifacts with this filter (check link)

What kind of artifacts are you referring to? All I see is mosquito noise around the letters (which is probably in the source video too, but masked by noise) and a little bit of banding.

[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

[Selur]

@realfinder: will the ncpu support make it to the git (https://github.com/HomeOfAviSynthPlu...tion/neo_FFT3D) any time soon? because the release there does not support 'ncpu'.

Cu Selur

[real.finder]

Originally Posted by Selur

@realfinder: will the ncpu support make it to the git (https://github.com/HomeOfAviSynthPlu...tion/neo_FFT3D) any time soon? because the release there does not support 'ncpu'.

Cu Selur

it's up to MeteorRain I am not a plugins Developer nor having access to https://github.com/HomeOfAviSynthPlusEvolution

[Selur]

okay, thanks for the info,..

[kedautinh12]

Originally Posted by Selur

@realfinder: will the ncpu support make it to the git (https://github.com/HomeOfAviSynthPlu...tion/neo_FFT3D) any time soon? because the release there does not support 'ncpu'.

Cu Selur

In neo_FFT3D compiled by realfinder have ncpu function