Vapoursynth

[DJATOM]

for prop in clip.get_frame(0).props:
print(prop)
should print a list of valid props.

[edcrfv94]

Why? Maybe the key is not defined?

text.ClipInfo show Chroma Location: Unknown
But text.FrameProps or print show _ChromaLocation not defined.

[Yrosma]

OK this is not a vapoursynth issue but as I read about large pages here maybe some people know.

I few pages back some people mentioned large pages and that it could give some better performance. As I'm doing some 4K material now which is quite slow I thought about trying this out as some people did get some improvement. My systems do have 32GB of memory so that should be fine.
But when I enabled large pages in windows and did some tests only using ffmpeg to convert to h264 and h265 (so no vapoursynth yet) I got a pretty big performance hit. Avarage around 20% slower conversions times just in ffmpeg conversions.

Did other people run into the same issues? Seen it on intel system with 32GB and an AMD system with 32GB

Because if it's like this even if there is an improvement in speed in vapoursynth, if ffmpeg conversion is this much slower there won't be a netto win.

Or could I be doing something wrong?

[LigH]

According to StackOverflow (https://stackoverflow.com/questions/2876377/in-what-circumstances-can-large-pages-produce-a-speedup), this is a quite complex topic, much related to the sizes of CPU internal caches (and thus the CPU model), and video encoding may not even deal in general with the kind of RAM access which would benefit from large pages.

[Selur]

Are there any source filters which support mkv(av1) atm. ?

[LigH]

FFMS2 would have to be built freshly again.

And DirectShow, if VS could use e.g. LAV Filters, is even more Windows system dependent...

[Myrsloik]

R45 is almost done. People just keep reporting small bugs that only take a day to fix so it's dragging a little.

Now for the big question:
I've added VSRepo to the installer. Should I offer to install certain scripts or sets of plugins using it from the installer? If so, which ones/which sets?

[ChaosKing]

Hmm maybe some script collections: havsfunc, muvsfunc, mvsfunc , hnwvsfunc + source filters ffms2, d2v, lsmash. This should be enough.

[Myrsloik]

Lsmash has no compiled binaries and thus no package definition. The rest sounds reasonable I guess.

I also plan to allow vs to automatically fetch required plugins using vsrepo but that's a later project.

[hydra3333]

R45 is almost done. Thank you.

I've added VSRepo to the installer. Should I offer to install certain scripts or sets of plugins using it from the installer? If so, which ones/which sets?Not yet having looked into VSRepo ... for those of us that use portable VS, will there also be a portable VSRepo equivalent without an installer ?

[Wolfberry]

will there also be a portable VSRepo equivalent without an installer ?

commit 46da486 (https://github.com/vapoursynth/vapoursynth/commit/46da486e04898a9f06a10c39f4b5b537d320eb27) had added vsrepo to the portable package

[ChaosKing]

@hydra VSRepo is not tightly bundled with VS (it can run independently). Btw You can also just download the git version.

Portable mode with custom folders could look like this: .\vsrepo.py -p upgrade-all -b vapoursynth64\plugins -s ..\Scripts

[hydra3333]

Ah, that is great news. Cheers !

[rekweom]

Could somebody help me configure Lut2 so that it works the same way as Avisynth's Overlay function in SoftLight mode? Or maybe there is a better way to do it with some other function? I have a hard time figuring this out.

[Boulder]

Here's an interesting concept for an optimizer tool for Avisynth, and I asked about future VS compatibility. The tool has some prerequisites, could someone take a look and guide the author? Thank you :)

https://forum.doom9.org/showthread.php?p=1852583#post1852583

[Myrsloik]

R45-RC1 (https://www.dropbox.com/s/y22t99kwntcr6rg/VapourSynth-R45-RC1.exe?dl=1)

Go test it. I plan to do more VSRepo integration in R46.

Changes:
r45:
updated to zimg v2.8
updated visual studio runtimes in installer
avfs now uses utf8 filename support when available in avs+
avfs now prints the used mount point
windows binaries now use python 3.7
removed accept_lowecase setting from the python bindings
fixed frame duration calculation in clipinfo (dubhater)
fixed bug that prevented adding vertical margins in subtext (dubhater)
documentation updates

[amayra]

thank you Myrsloik finally i can say goodbye to filename problem and update my python setup

[ca18]

Can you please post VS Portable R45 64bit for Python 3.7 64bit Windows? :thanks:

[LigH]

There is no Release 45 yet. Only a first candidate (RC1 = "Release Candidate 1"). Patience, young padawan.

[ca18]

Extracted with uniextract2 now ... :rolleyes:

[Myrsloik]

Final release will be in a day or two. Just have to actually test the avfs changes properly so I didn't break everything.

[ca18]

NP m8, thank you, great job as always! :thanks: Need to get rid of this python 3.6 + 3.7 mess ASAP, everyone's been waiting for VS with 3.7 so time to finally bury 3.6 ;)

[Revan654]

Any update on the Final Release? I assume something broke since there no R45 release yet.

[DJATOM]

I have RC1 installed, no issues on my side.

[Myrsloik]

Any update on the Final Release? I assume something broke since there no R45 release yet.

Life happened. I'll stop dragging and simply release it tomorrow. It's always tomorrow...

[hydra3333]

great to hear you have a life :)

[Revan654]

Life happened. I'll stop dragging and simply release it tomorrow. It's always tomorrow...

Just wondering, Something broke my search path. Nothing in vs is working currently without crashing. I want to uninstall everything and re-install everything and try to get it working again.

Python Path: C:\ProgramData
VS Path: C:\Program Files (x86)
Encoder: Desktop

[Myrsloik]

R45 finally released. Maintenance and ironically avs+ improvements to avfs so unicode filenames are used.

VSRepo is bundled too but not particularly well integrated.

Changes:
r45:
updated to zimg v2.8
updated visual studio runtimes in installer
avfs now uses utf8 filename support when available in avs+
avfs now prints the used mount point
windows binaries now use python 3.7
removed accept_lowecase setting from the python bindings
fixed frame duration calculation in clipinfo (dubhater)
fixed bug that prevented adding vertical margins in subtext (dubhater)
documentation updates

[hydra3333]

changes:

windows binaries now use python 3.7

Thank you.
Was that 3.7.0 or 3.7.1 ?

[amichaelt]

Thank you.
Was that 3.7.0 or 3.7.1 ?

Wasn't 3.7.1 only just released a few hours ago?

[hydra3333]

Wasn't 3.7.1 only just released a few hours ago?

Just checked, I only see a date of today by the looks, so likely yes.

I guess that means it isn't "compatible" with 3.7.1 ?

[Selur]

I get 'Failed to initialize VapourSynth' in vsedit with R45 both Python 3.7.0 and 3.7.1 (used the portable version and embeddable download from https://www.python.org/downloads/release/python-370/ and https://www.python.org/downloads/release/python-371/).
-> am I missing something

[tuanden0]

I get 'Failed to initialize VapourSynth' in vsedit with R45 both Python 3.7.0 and 3.7.1 (used the portable version and embeddable download from https://www.python.org/downloads/release/python-370/ and https://www.python.org/downloads/release/python-371/).
-> am I missing something

I use installer on github and everything is OK with python 3.7.0 :D

[Selur]

Are you using the portable Python 3.7.0 or are you using a system wide install?

[hydra3333]

Well, I did the portable install (python 3.7.0 and R45) overwriting everything in the previously successful portable folder, and now when running vsedit:
2018-10-21 15:20:04.069
Failed to initialize VapourSynth environment!
Failed to initialize VapourSynth environment!
Failed to initialize VapourSynth environment!
Failed to initialize VapourSynth environment!
Failed to initialize VapourSynth environment!

[Selur]

That's what happening here too.
(I tried with a clean folder extracted the portable python 3.7.0, R45 and vsedit into it, same effect).
:(

[hydra3333]

A quick test with an old test script yields this
"C:\SOFTWARE\Vapoursynth-x64\VSPipe.exe" --y4m "test.vpy" - | "C:\SOFTWARE\ffmpeg\ffmpeg.exe" -threads 0 -i pipe: -threads 0 -an -threads 0 -map_metadata -1 -c:v h264_nvenc blah blah -movflags +faststart -y "test.VS.MP4"
Failed to initialize VapourSynth environment

[Selur]

Same, here. Hopefully Myrsloik can help. :)

[tuanden0]

Are you using the portable Python 3.7.0 or are you using a system wide install?

I'm using system wide install python 3.7.0

[Selur]

Okay, that doesn't help then. Seems to be a problem with portable Python and R45. :(

[DJATOM]

Yeah, Myrsloik forgot to edit path in the portable generation script, so you can have mine (confirmed working x64 portable): https://mega.nz/#F!6aAUUYwR!EskQeFhetoxTosSQafnTsw

[Selur]

I can confirm that this version works fine with portable Python.
Thanks DJATOM!

Cu Selur

[Revan654]

I get 'Failed to initialize VapourSynth' in vsedit with R45 both Python 3.7.0 and 3.7.1 (used the portable version and embeddable download from https://www.python.org/downloads/release/python-370/ and https://www.python.org/downloads/release/python-371/).
-> am I missing something

As nice as VS is, it's still a PIA sometimes to keep everything in the search path.

It doesn't help sometimes when VS2017 gets updates it screws everything up.

Wasn't 3.7.1 only just released a few hours ago?

3.7.1RC1 has been out for awhile. The final version was just released.

[ChaosKing]

Yeah, Myrsloik forgot to edit path in the portable generation script, so you can have mine (confirmed working x64 portable): https://mega.nz/#F!6aAUUYwR!EskQeFhetoxTosSQafnTsw
But your build is also "incomplete". avisource.dll is missing :D

[hydra3333]

Oh well, I feel sure Myrsloik will address it in due course. Vapoursynth is a beaut tool (and its name is even spelled in the right way) !

[Myrsloik]

Uploaded fixed portable binaries.

By python 3.7 I mean the 3.7-series which is ABI compatible.

[Selur]

Trying to create a blank clip, I tried:
blank = core.std.BlankClip(clip=inputClip, length=1, format=inputClip.format.id)
and
blank = core.std.BlankClip(clip=inputClip, length=1)
both times I get:
vapoursynth.Error: BlankClip: invalid format

-> How to create a BlankClip in the format of the inputClip ?

Cu Selur

[poisondeathray]

blank = core.std.BlankClip(clip=inputClip, length=1)


This works for me in Windows installed vapoursynth version; and everything is matching correctly in terms of parameters

[Selur]

Argh,... python cache,.. Thanks!

[Wolfberry]

Please update the doc (http://vapoursynth.com/doc/) to R45 :thanks: