fft3dGPU 0.8.2

[StainlessS]

See Sendspace in sig beneath this post, Apr2006_D3DX9_30_DLL_(x86 & x64).7z
x86 and x64 dll's from Microsoft DirectX SDK (February 2010)

Files inside the 7z, [~2.5MB]

Apr2006_d3dx9_30_x64.cab
Apr2006_d3dx9_30_x86.cab

[Ceppo]

Thank you.

EDIT: Even after trying to copy the 64bit dll to both system32/SysWOW64, it still gives me the error "there is no function named fft3dgpu".

[Groucho2004]

Thank you.

EDIT: Even after trying to copy the 64bit dll to both system32/SysWOW64, it still gives me the error "there is no function named fft3dgpu".Run AVSMeter/AVSMeter64 (https://forum.doom9.org/showthread.php?t=174797) with the switch "-avsinfo" and report any errors it may show. Alternatively, run the Avisynth Info Tool (https://forum.doom9.org/showthread.php?t=176079). Also, do not place 64 bit binaries in SysWoW64.

[kedautinh12]

Thank you.

EDIT: Even after trying to copy the 64bit dll to both system32/SysWOW64, it still gives me the error "there is no function named fft3dgpu".

Don't copy 64 bit dll to system32/SysWOW64. Please copy both 64 bit dll amd .hsls file to Program File (x86)/Avisynth+/Plugin64+

[Ceppo]

AVSMeter says that it needs d3dx9_43.dll, so I guess d3dx9_30.dll doesn't do the job? Where can I get d3dx9_43.dll?

[Groucho2004]

Where can I get d3dx9_43.dll?Here you go (https://www.dropbox.com/s/rf1bt6izoaiu8s1/DX9_Files.zip?dl=1). And yes, the fft3dgpu.dll plugin belongs into your 64 bit plugin directory, not system32/SysWoW64.

[Ceppo]

I think I was misunderstood.

Now I get a "system exception: access violation" and I found out in the first post that the NVIDIA GEFORCE GTX is not supported. I'm I wrong?

[kedautinh12]

Are you copy copy both 64 bit dll and .hsls file to same folder???

[Ceppo]

Yes in the plugins64 folder.

[Groucho2004]

I think I was misunderstood.

Now I get a "system exception: access violation" and I found out in the first post that the NVIDIA GEFORCE GTX is not supported. I'm I wrong?It works on all my NVIDIA GTX cards. What card do you have? Also, what driver version?

[StainlessS]

If you copied directX dll into system32/SysWOW64 by mistake, then remove them.
[System32 is for 64 bit, SysWOW64 for 32 bit].
I dont remember needing any directx dlls when using GPU version fft3dfilter, but was a long time ago.
[also was I think slower than CPU, for me]

[kedautinh12]

AVSMeter says that it needs d3dx9_43.dll, so I guess d3dx9_30.dll doesn't do the job? Where can I get d3dx9_43.dll?

D3dx9_43.dll (ver x64) must in system32 folder not syswow64

[kedautinh12]

If you copied directX dll into system32/SysWOW64 by mistake, then remove them.
[System32 is for 64 bit, SysWOW64 for 32 bit].
I dont remember needing any directx dlls when using GPU version fft3dfilter, but was a long time ago.
[also was I think slower than CPU, for me]

I don't think so
https://github.com/pinterf/FFT3dGPU/issues/4#issuecomment-759949442

[StainlessS]

Last time I tried it was probably a decade ago.

[Ceppo]

It works on all my NVIDIA GTX cards. What card do you have? Also, what driver version?
I have a laptop so it has two:
1) Intel(R) HD Graphics 520
2) NVIDIA GeForce GTX 950M
The driver is the latest available.

[StainlessS]

Do you still need d3dx9_43.dll, I got the lot up to June 2010. [final directX 9c]

[Ceppo]

No, it was gently given in the post above. Thanks.

[pinterf]

DirectX 9 is old stuff. This FFT3dGPU explicitely needs the above mentioned DirectX 9 even if we have DirectX 12 since then.
For some reasons Microsoft has removed the link, but if you search for "DirectX 9 Redistributable June 2010 download" then you get some links to the install package.
When you are successful with it, all you need is FFT3dGPU.DLL and the .hlsl file next to it (in the appropriate plugins folde).

[Ceppo]

Installing the whole thing makes it work. Thank you.

[Arx1meD]

When I used FFT3dGPU v0.8.6 (https://github.com/pinterf/FFT3dGPU) I noticed that when plane = 0 or 4 and sharpen > 0 a small mesh appears. Is this a bug in the filter or not?

Examples:
https://images2.imgbox.com/fd/0d/cD7KgODK_o.png
https://images2.imgbox.com/1d/20/TUbe1dOm_o.png

[poisondeathray]

When I used FFT3dGPU v0.8.6 (https://github.com/pinterf/FFT3dGPU) I noticed that when plane = 0 or 4 and sharpen > 0 a small mesh appears. Is this a bug in the filter or not?


probably a bug; the same call with fft3dfilter does not produce the grid

bt=1 (spatial only) instead of bt=3 does not produce grid either , at least on that single still image that was looped with imagesource

[Fjord]

When I used FFT3dGPU v0.8.6 (https://github.com/pinterf/FFT3dGPU) I noticed that when plane = 0 or 4 and sharpen > 0 a small mesh appears. Is this a bug in the filter or not?
probably a bug; the same call with fft3dfilter does not produce the grid

bt=1 (spatial only) instead of bt=3 does not produce grid either , at least on that single still image that was looped with imagesource

@Arx1meD, I suggest that you open an issue on Pinterf's FFT3dGPU github site: https://github.com/pinterf/FFT3dGPU/issues, to make sure he is aware of this.

[Dogway]

Is there a way to match FFT3DGPU to fft3dfilter? The following calls give me very different results FFT3DGPU being worse with blurrier lines and also some halo. precision=0 is ok if the pipeline is in HBD.
fft3dfilter(sigma=16,sigma2=6,sigma3=1,sigma4=0,bw=12,bh=12,ow=6,oh=6,bt=4,plane=4,ncpu=4)
FFT3DGPU(sigma=16,sigma2=6,sigma3=1,sigma4=0,bw=12,bh=12,ow=6,oh=6,bt=4,plane=4,precision=0)

[StainlessS]

Doggy, methinks that FFT3dFilter and the gpu version will often if not always give differing results, I seem to remember that
one good reason not to use gpu version was thats it uses less precision, and maybe truncation rather than rounding.
Although visible blurring and halo does sound disturbing.

[pinterf]

Less precision means that in 8 bits the default precision is using only 16 bit floating point type (half). At least for part of the algorithm. I suppose this was chosen because of speed reasons. For 10+ bits I made it using 32 bit float always as I remember. See docs.
I cannot tell you about other comparisons, I never used the plugin. I guess fft3dgpu was based on an earlier version of fft3dfilter but I don't know when this happened.

[Reel.Deel]

Is there a way to match FFT3DGPU to fft3dfilter?...

Does changing the values of bw,bh,ow,oh to a power of 2 change anything?

fft3dfilter 1.8.5 that the current version of fft3dgpu is based on (expect bw,bh,ow,oh value as they need to be a power of two in fft3dgpu)

Also there have been reports of decreased quality (https://forum.doom9.org/showthread.php?p=1026076#post1026076) in fft3dgpu when bt=4 and/or precision=2 (in pinterf's mod precision is always set to 2 when bitdepth is greater than 8).


--------

I guess fft3dgpu was based on an earlier version of fft3dfilter but I don't know when this happened.

According to tsp, fft3dgpu is based on fft3dfilter v1.8.5 (post #683) (https://forum.doom9.org/showthread.php?p=1049219#post1049219). But aside from delaho, it seems that most changes to fft3dfilter after v1.8.5 were optimizations and bug fixes:

v1.8.5 - 2005/12/04 - fixed bug with memory leakage (thanks to tsp).
v1.9.0 - 2006/04/25 - added dehalo options; corrected sharpen mode;
- re-enabled SSE optimization for degrid=0;
- added SSE optimization for bt=3,-1 with degrid>0 (faster by 15%)
v1.9.1 - 2006/05/10 - added SSE optimization for bt=4 with degrid>0 (faster by 30%).
v1.9.2 - 2006/09/11 - changed default bw=bh=32; added mode bt=5
v2.0.0 - 2006/11/29 - added experimental internal motion compensation mode;
- window reorganized; internal multithread support
v2.1.0 - 2007/01/17 - removed (temporary ?) experimental internal motion compensation mode.
v2.1.1 - 2007/02/20 - fixed bug with bw not mod 4 (restored v1.9.2 method).

[Dogway]

Thanks Reel.Deel, has some time to check what's going on.

So power of 2 only, 4, 8, 16... that leaves out 12.
FFT3DGPU(sigma=16,sigma2=6,sigma3=1,sigma4=0,bw=16,bh=16,ow=8,oh=8,bt=4,plane=0,precision=0)
fft3dfilter(sigma=16,sigma2=6,sigma3=1,sigma4=0,bw=16,bh=16,ow=8,oh=8,bt=4,plane=0,ncpu=2)
Yes, this is a match.

This one though isn't:
FFT3DGPU(sigma=16,sigma2=6,sigma3=1,sigma4=0,bw=8,bh=8,ow=4,oh=4,bt=2,plane=0,precision=0)
fft3dfilter(sigma=16,sigma2=6,sigma3=1,sigma4=0,bw=8,bh=8,ow=4,oh=4,bt=2,plane=0,ncpu=2)
This call just outputs garbage (bug?)
FFT3DGPU(sigma=16,sigma2=6,sigma3=1,sigma4=0,bw=16,bh=16,ow=6,oh=6,bt=2,plane=0,precision=0)
And here a comparison between fft3dfilter and FFT3DGPU, very different, background is blurred more on fft3dfilter, and lineart is cleaner. On FFT3DGPU you can see some halo and ringing, easily seen on the inner side of the glasses.
FFT3DGPU(sigma=16,sigma2=6,sigma3=1,sigma4=0,bw=12,bh=12,ow=4,oh=4,bt=2,plane=0,precision=0)

fft3dfilter
https://i.imgur.com/vjo1FOg.png
FFT3DGPU
https://i.imgur.com/RBxiplM.png

[minusthebear]

I'm a bit at a loss for how to install and use FFT3dGPU. Does it replace FFT3d entirely? Does it only work with some plugins?

I'm looking to speed up my workflow in any way possible, can someone please direct me to a good guide/resource for using and installing FFT3dGPU?

Thanks!!

[Reel.Deel]

I'm a bit at a loss for how to install and use FFT3dGPU. Does it replace FFT3d entirely? Does it only work with some plugins?

I'm looking to speed up my workflow in any way possible, can someone please direct me to a good guide/resource for using and installing FFT3dGPU?

Thanks!!

To autoload FFT3dGPU, copy both fft3dgpu.hlsl and FFT3dGPU.dll into the appropriate folder. Or load the plugin manually with LoadPlugin, just make sure fft3dgpu.hlsl is in the same folder as the dll. It does not replace FFT3DFilter since the function names are different. You can have both plugins installed/loaded and even used in the same script. Not sure what you mean by "Does it only work with some plugins?" but it works like a normal plugin and it is not dependent on what other plugins you use or not.

[Lan4]

The bug happened several times. At first, encoding with the FFT3DGPU filter proceeds normally. Then the encoding time starts to increase, from several seconds to several minutes. This problem has been around for about 2 months. This may be due to a video driver update. Has anyone had the same problem? And what could be its reason?

[romangal]

Yes, FFT3DGPU with bt=4 just stops filtering. Dots and crowls are present again. So the best settings ive got with fft3dgpu
are: bw-16, ow-8, bt-3. Never please set bt above 3 if you dont want just waste a time.