Good noise reduction filter - Does it make sense?

[stax76]

A little "special" for a console tool

The documentation doesn't explain this well btw.

[Groucho2004]

Originally Posted by stax76

A little "special" for a console tool

Yes it is.

Originally Posted by stax76

The documentation doesn't explain this well btw.

That page merely gives a rough overview of the switches. The documentation is included in the distro. However, I'll probably "verbosify" this switch a bit.

[crystalfunky]

Originally Posted by stax76

@crystalfunky

I have enabled MCTempDenoise and opened the preview in staxrip, after that I started an application called Process Explorer and clicked on the search toolbar button, in the search field I entered gpu and clicked enter, this showed me that the staxrip process has successfully loaded a DLL named FFT3dGPU.dll.

This means it's working here and the problem is specific to your machine, this DLL has gpu in its name which implies it could be a missing GPU driver or hardware, or it could be a dependency.

Ok I did what you did.
After enabling the filter in staxrip I clicked on preview and got the same error that the module cannot be found.
Searched in process explorer for gpu and the program couldn't find anything.

I'm using a Radeon RX 460 with current drivers.

Do I need to install anything besides Staxrip and all the apps that are required by Staxrip (e.g. Avisynth, Visual C++, etc.), which will be installed automatically?

@Groucho
Tried your method. I attached the log.
I checked with avsmeter. Will the program give me any errors?

[Groucho2004]

Originally Posted by crystalfunky

@Groucho
Tried your method. I attached the log.
I checked with avsmeter. Will the program give me any errors?

It looks as if you did not use the "-c" switch. Anyway, according to stax, each plugin resides in its own directory which would make checking with AVSMeter rather cumbersome.

You can still use the second option I pointed out in post #12:
Run the script with AVSMeter ("AVSMeter script.avs -lf) and post the created log file.

[crystalfunky]

When I try to use the autoload script file "MCTemporalDenoise.avsi" renamed to avs at the end, with the command -lf then avsmeter tells me "invalid switch in this context: -lf"
I tried the -c command already and checked the MCTempDenoise folder, as well as the FFt3dGPU folder. Thats why I asked if the program will give me anything (errors, etc.), because it somehow just checked and gave me nearly nothing at the end.

Edit: Did everything again with your method. I hope it's all there now.

[Groucho2004]

Originally Posted by crystalfunky

When I try to use the autoload script file "MCTemporalDenoise.avsi" renamed to avs at the end, with the command -lf then avsmeter tells me "invalid switch in this context: -lf"
I tried the -c command already and checked the MCTempDenoise folder, as well as the FFt3dGPU folder. Thats why I asked if the program will give me anything (errors, etc.), because it somehow just checked and gave me nearly nothing at the end.

Edit: Did everything again with your method. I hope it's all there now.

The "-lf" was a typo, sorry about that. You simply run "AVSMeter script.avs -log". I don't know why you would rename "MCTemporalDenoise.avsi" and run that. You're supposed to run the script that staxrip created.

[crystalfunky]

ok, it just gave me the same error, which staxrip already gave me.
The module cannot be found (error 126). FFt3dgpu.dll

Edit: Just tried the whole thing on my laptop and I get the same error.
So either I'm missing something, or the problem is not my doing but in the program.
Used: Staxrip 2.1.1.2

[Groucho2004]

Originally Posted by crystalfunky

ok, it just gave me the same error, which staxrip already gave me.
The module cannot be found (error 126). FFt3dgpu.dll

I'll let stax take over from here, I don't know that gui at all. Still, can you post the script?

[crystalfunky]

Hat to rename the file from .avs to .txt

[crystalfunky]

Ok so it's getting interesting. I looked in the readme from FFT3dGPU folder. There was something about Dx9, so I installed that on my Windows 10 system.
It got me a new error in Staxrip 2.1.3.0 though. The last one (Error 126, file cannot be found) was gone.
The new one says: This is not an YV12 clip. Please convert to YV12 colorspace.
How the heck am I suppose to do that? It's a normal HDR 4K clip. The mediainfo says that it's YUV and 4:2:0 (Type 2).
If you know something guys, I would really appreciate your help.

[crystalfunky]

I guess this doesn't make sense any more.
I would delete this thread, since my original question is another.