Vapoursynth

[stax76]

Originally Posted by sneaker_ger

Save as UTF-8 without BOM.

works!

[foxyshadis]

Originally Posted by Myrsloik

Judging by the description only using utf-8-sig should always do the right thing. Correct me of I'm wrong.

Looks like it. Double-checked the source and it does handle it either way.

[Kupildivan]

Is there compiled FFT3DFilter.dll for VS?

[feisty2]

fft3d is old and obsolete cuz dfttest kicks its ass.

[Kupildivan]

Forgot to mention, dfttest is too slow for me. That's why I ask.

[feisty2]

then, no.
no one seems to, well, want to port fft3d...
but, you can pick smaller sb/so/tb/tosize values and speed dfttest up.

[Kupildivan]

OK then. Thanks for info.

[Reel.Deel]

Originally Posted by feisty2

no one seems to, well, want to port fft3d...

VFR-maniac ported FFT3DFilter (along with a few other plugins) but as usual he did not release any binaries.

[feisty2]

Originally Posted by Reel.Deel

VFR-maniac ported FFT3DFilter (along with a few other plugins) but as usual he did not release any binaries.

got not much luck with it

[Are_]

It compiles just fine with gcc.

[feisty2]

Originally Posted by Are_

It compiles just fine with gcc.

then you should probably post the binaries and do Kupildivan a favor
I'm just too newbie to be a gcc guy

[Are_]

Also I think Linux binaries will not be much useful to him. :/

[Myrsloik]

Don't forget to install all updates. Here's a friendly reminder.

[Myrsloik]

Now for a small poll. Should the next version be compiled for python 3.4 or 3.5?

This of course assumes python 3.5 will be released by then. It's probably less than a week away.

[stax76]

I would prefer 3.5.

[Khanattila]

Originally Posted by HolyWu

Unfortunately VS-FFT3DFilter's processing is single-threaded, which make it not significantly faster than DFTTest. More importantly, it supports only 8-bit input and will introduce banding after denoising. I'd recommend KNLMeans as one of the other choices if he has a decent GPU.

Without offending anyone, I'd recommend always KNLMeans

[Sparktank]

Originally Posted by Myrsloik

python 3.4 or 3.5?

I remember some time before when I first tried to install, VS was done using older python and I had already installed newest updates for python. I had decided to wait for VS to update to newest python, but by then a lot of time had passed and I forgot.

So, I would vote for the newest python, 3.5.
Anyone new looking into VS will be off to a very fresh start, as fresh as possible, at least.

[feisty2]

3.5, always not a bad thing tryna stay update

[Myrsloik]

Here's R28 test 2.

WARNING! The VS2015 runtime needs to be installed manually for now

Note that this build was made with VS2015 and without tcmalloc. Speed comparisons to R27 would be interesting to see. Apart from the compiler switch it's more or less purely a bugfix release.

r28:
get_core() can now be used in callbacks and other external functions in python
now returns an error message saying that windows needs to be updated in certain cases when plugin loading fails
fixed loop filter (nodame)
lut and lut2 can now output float as well
now accepts scripts that start with a BOM as well
fixed an image corruption bug with 9-16 bit input to rgvs when the c++ code is used
fixed division by zero issues in muldivrational in vshelper.h
blankclip can now create 0 (unknown/variable) fps clips
added float support to planedifference and planeaverage
added half support to addborders
relevant compile time options are now in the version string

Still uses python 3.4 obviously.

[mastrboy]

How do one use a similar function to avisynths import() ?

I tried the "python way": exec(open('filter.vpy').read()) but that just resulted in a error message: Unhandled C++ Exception...

Edit: Nevermind, I forgot to remove the source filter from the filter.vpy template, now it works...