Vapoursynth

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

[Myrsloik]

Originally Posted by feisty2

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

It should already be fixed in R28 test 2 actually.

[Boulder]

In MVTools for Vapoursynth,

bv3 = core.mv.Analyse(clip=superanalyse, dct=dct, blksize=blksize, overlap=overlap,
search=search, searchparam=searchparam, pelsearch=pelsearch, isb=true, lambda=lda,
chroma=chromamotion, delta=3, truemotion=truemotion, lsad=lsad, global=true, pnew=pnew,
badsad=badsad, badrange=badrange)

causes a syntax error (SyntaxError: invalid syntax) pointing around "search". If I remove that, it points to the next item around the same position. Is there some weird overflow going on?

[jackoneill]

Originally Posted by Boulder

In MVTools for Vapoursynth,

bv3 = core.mv.Analyse(clip=superanalyse, dct=dct, blksize=blksize, overlap=overlap,
search=search, searchparam=searchparam, pelsearch=pelsearch, isb=true, lambda=lda,
chroma=chromamotion, delta=3, truemotion=truemotion, lsad=lsad, global=true, pnew=pnew,
badsad=badsad, badrange=badrange)

causes a syntax error (SyntaxError: invalid syntax) pointing around "search". If I remove that, it points to the next item around the same position. Is there some weird overflow going on?

I don't know about "search", but "lambda" and "global" are Python keywords. Prefix them with an underscore:

_lambda=lda, ... _global=True

Oh, and maybe it's pointing at "search" because it's on a new line. Maybe Python needs all of that on a single line.

[Are_]

The auto indentation of my IDE indents it like this:

bv3 = core.mv.Analyse(clip=superanalyse, dct=dct, blksize=blksize, overlap=overlap, 
                      search=search, searchparam=searchparam, pelsearch=pelsearch, 
                      isb=true, _lambda=lda, chroma=chromamotion, delta=3, truemotion=truemotion, 
                      lsad=lsad, _global=true, pnew=pnew, badsad=badsad, badrange=badrange)

Remember indentation is part of the syntax in python.

[Boulder]

I put it on a new line due to readability here, in my script it's all on the same line. Using the underscore seems to help, thanks The error message really didn't help there..

You might want to update the docs on the MVTools page to reflect this one.

[foxyshadis]

Since those arguments already break avisynth compatibility, by requiring an underscore, it'd be better to just rename them from the get-go. This is a pretty serious submarine problem that's just going to catch more people out over time.

[Myrsloik]

Here's R28 test3. It's mostly for the brave only.

Changes from test2 is that it needs a python 3.5 installation made for all users (next test will also support per user installations).

The new compile of assvapour is completely untested so report your findings there if you dare. It no longer uses fontconfig so if it works it should start up much quicker.

The expr filter has also been greatly sped up and now uses runtime code generation. Log, exp and pow currently aren't implemented though and will probably crash it if you try to use them. Everything else should work as expected.

Report your findings there as well.

Speed comparisons with R28 test2 (or R27) welcome.

[Boulder]

I just ran into a deadlock situation with R27, trying to use contrasharpening with 16-bit input.

import vapoursynth as vs
import scoll

core = vs.get_core()
cs = scoll.SColl()

clp = core.ffms2.Source(source='c:/x265/hotfuzz.vc1')

clp = core.fmtc.bitdepth(clp, bits=16)
clp = cs.contrasharpening(clp,clp)

clp.set_output()

SColl is from here: https://github.com/4re/vapoursynth-m...aster/scoll.py

When using vspipe to display clip info, it utilizes one CPU thread at 100% and the Task Manager shows that memory usage just keeps on increasing (it went over 2GB before I interrupted the execution). If I remove the conversion to 16-bit video, there's no problem.

Don't worry about the silly contrasharpening line, it's just to reproduce the problem.

[jackoneill]

Originally Posted by Boulder

I just ran into a deadlock situation with R27, trying to use contrasharpening with 16-bit input.

import vapoursynth as vs
import scoll

core = vs.get_core()
cs = scoll.SColl()

clp = core.ffms2.Source(source='c:/x265/hotfuzz.vc1')

clp = core.fmtc.bitdepth(clp, bits=16)
clp = cs.contrasharpening(clp,clp)

clp.set_output()

SColl is from here: https://github.com/4re/vapoursynth-m...aster/scoll.py

When using vspipe to display clip info, it utilizes one CPU thread at 100% and the Task Manager shows that memory usage just keeps on increasing (it went over 2GB before I interrupted the execution). If I remove the conversion to 16-bit video, there's no problem.

Don't worry about the silly contrasharpening line, it's just to reproduce the problem.

It uses std.Lut2 inside. With two 16 bit clips, that means there will be a table of 65536 * 65536 elements, which is over 4 billion. With 2 bytes per element, that requires 8 GiB of RAM and probably takes a while to initialise.