Vapoursynth

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

[Myrsloik]

Originally Posted by 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...

How did you get the unhandled C++ exception? If you can describe it and provide the exact scripts you used it'd help a lot. It should never crash because of python exec...

[mastrboy]

Originally Posted by Myrsloik

How did you get the unhandled C++ exception? If you can describe it and provide the exact scripts you used it'd help a lot. It should never crash because of python exec...

Here here was my ep01.vpy

PHP Code:

import vapoursynth as vs
core = vs.get_core(threads=8)
vid = core.avisource.AVIFileSource('I:/ep01.avs')
exec(open('filter.vpy').read()) 


and here was my filter.vpy when it crashed:

PHP Code:

import vapoursynth as vs
core = vs.get_core(threads=8)
vid = core.avisource.AVIFileSource('I:/filter.avs')
vid = core.resize.Spline(clip=vid, width=960, height=540)
super = core.mv.Super(vid)
mvbw3 = core.mv.Analyse(super, isb=True, delta=3, overlap=4,blksize=8)
mvbw2 = core.mv.Analyse(super, isb=True, delta=2, overlap=4,blksize=8)
mvbw = core.mv.Analyse(super, isb=True, delta=1, overlap=4,blksize=8)
mvfw = core.mv.Analyse(super, isb=False, delta=1, overlap=4,blksize=8)
mvfw2 = core.mv.Analyse(super, isb=False, delta=2, overlap=4,blksize=8)
mvfw3 = core.mv.Analyse(super, isb=False, delta=3, overlap=4,blksize=8)
out = core.mv.Degrain3(clip=vid, super=super, mvbw=mvbw, mvfw=mvfw, mvbw2=mvbw2, mvfw2=mvfw2, mvbw3=mvbw3, mvfw3=mvfw3, thsad=275)
#out = core.hist.Luma(clip=out)
out.set_output() 


ep01.avs is:

PHP Code:

DGsource("ep01.dgi") 


As you can see, I forgot to comment some stuff out in filter.vpy when it crashed, also filter.avs did not exist since I renamed that to ep01.avs

[cybersharky]

What python path's are needed to install vapoursynth? What registry locations does the installer check?

On attempting to install I get:


my user and system paths start with:

C:\Python34\;C:\Python34\Scripts;

but they do also have:

C:\Enthought\Canopy32\User;C:\Enthought\Canopy32\User\Scripts;

I need Canopy's python 2 version for courses I'm doing.

Yes, I have installed python 3.4.3 for all users.

I'm on Windows 8.1 x64, all the latest updates installed.

[Are_]

We can't see your image because it looks like it's not public.

[Myrsloik]

Originally Posted by cybersharky

What python path's are needed to install vapoursynth? What registry locations does the installer check?

On attempting to install I get:


my user and system paths start with:

C:\Python34\;C:\Python34\Scripts;

but they do also have:

C:\Enthought\Canopy32\User;C:\Enthought\Canopy32\User\Scripts;

I need Canopy's python 2 version for courses I'm doing.

Yes, I have installed python 3.4.3 for all users.

I'm on Windows 8.1 x64, all the latest updates installed.

It check for HKCU/HKLM(32/64) SOFTWARE\Python\PythonCore\3.4\InstallPath. The standard keys written by the python installer.

[cybersharky]

Originally Posted by Myrsloik

It check for HKCU/HKLM(32/64) SOFTWARE\Python\PythonCore\3.4\InstallPath. The standard keys written by the python installer.

Thanks deleted the 64 bit references and was able to install vapoursynth

[hajj_3]

python 3.5.0 is out now.

[~ VEGETA ~]

Originally Posted by hajj_3

python 3.5.0 is out now.

Is it necessary to update from 3.4 to 3.5?

[hajj_3]

Originally Posted by ~ VEGETA ~

Is it necessary to update from 3.4 to 3.5?

when the creator of vapoursynth releases a new version you will need to upgrade to v3.5.

[Myrsloik]

Python 3.5 will be required for the next release (and the test versions before that from now on). If someone with VS2010 wants to step up and compile modules for older Pythons I won't object. The biggest reason I don't support multiple versions on windows is testing.

Theoretically 2.x could work too but once again, testing. And ancient compilers. From now on I will only use VS2015 (or later) to compile this project on windows.

So now we should all celebrate Python 3.5 and its switch to a modern compiler. I can finally remove that old crap from my computer.

Btw, you should all use VS2015 too, the community edition is free.

[feisty2]

Originally Posted by Myrsloik

From now on I will only use VS2015 (or later) to compile this project on windows.

I assume that would fix the mysterious vs2015 plugin vspipe crash?