Vapoursynth

[Myrsloik]

Hello,

can you tell me if my guesses are true. Can I compile zimg on debian?
if yes why can't I compile it? Not sure I actualy can.
System: Debian wheezy x64

Here is my error code: http://paste2.org/tgXKhezc

cheers in advance

You compiler is too old.

[Sm3n]

OK. And do you think I can upgrade it? I'm not very confortable with debian - that's why I ask but I can manage it eventualy.
I'm trying to look for it right now...

[Are_]

OK. And do you think I can upgrade it? I'm not very confortable with debian - that's why I ask but I can manage it eventualy.
I'm trying to look for it right now...
https://linuxconfig.org/how-to-upgrade-debian-linux-system-from-wheezy-to-jessie-stable-release

[Sm3n]

https://linuxconfig.org/how-to-upgrade-debian-linux-system-from-wheezy-to-jessie-stable-release

Thx a lot. :)

[Selur]

I'm trying to get Vapoursynth working on mac, using:
# Imports
import vapoursynth as vs
core = vs.get_core()
# Loading Plugins
core.std.LoadPlugin(path="/Users/selur/build-Hybrid-Desktop-Release/Hybrid.app/Contents/MacOS/vsfilters/SourceFilter/FFMS2/ffms2.dylib")
# Loading /Users/selur/Desktop/公演后感言.mp4 using FFMS2
clip = core.ffms2.Source(source="/Users/selur/Desktop/公演后感言.mp4",cachefile="/Users/selur/Desktop/temp/mp4_d59244d4d4de113a5823257ae88125fc_16807.ffindex")
# Output
clip.set_output()
I get:
Failed to evaluate the script:
Python exception: Failed to load /Users/selur/build-Hybrid-Desktop-Release/Hybrid.app/Contents/MacOS/vsfilters/SourceFilter/FFMS2/ffms2.dylib. Error given: dlopen(/Users/selur/build-Hybrid-Desktop-Release/Hybrid.app/Contents/MacOS/vsfilters/SourceFilter/FFMS2/ffms2.dylib, 1): image not found
Traceback (most recent call last):
File "src/cython/vapoursynth.pyx", line 1491, in vapoursynth.vpy_evaluateScript (src/cython/vapoursynth.c:26897)
File "/Users/selur/Desktop/temp/tempPreviewVapoursynthFile21_04_39_802.vpy", line 5, in <module>
core.std.LoadPlugin(path="/Users/selur/build-Hybrid-Desktop-Release/Hybrid.app/Contents/MacOS/vsfilters/SourceFilter/FFMS2/ffms2.dylib")
File "src/cython/vapoursynth.pyx", line 1383, in vapoursynth.Function.__call__ (src/cython/vapoursynth.c:25204)
vapoursynth.Error: Failed to load /Users/selur/build-Hybrid-Desktop-Release/Hybrid.app/Contents/MacOS/vsfilters/SourceFilter/FFMS2/ffms2.dylib. Error given: dlopen(/Users/selur/build-Hybrid-Desktop-Release/Hybrid.app/Contents/MacOS/vsfilters/SourceFilter/FFMS2/ffms2.dylib, 1): image not found


Do I need to load the filter in another way ?
(I'm on mac osx, vapoursynth was installed using homebrew, ffms2 was separately compiled and copied to '/Users/selur/build-Hybrid-Desktop-Release/Hybrid.app/Contents/MacOS/vsfilters/SourceFilter/FFMS2/ffms2.dylib' )

[kolak]

Use L-SMASH Source- I found it more reliable than ffms2, which is far from being perfect.

[Selur]

haven't figured out to compile l-smash on mac and I'm not sure if I the loading script is correct,...

[jackoneill]

Do I need to load the filter in another way ?
(I'm on mac osx, vapoursynth was installed using homebrew, ffms2 was separately compiled and copied to '/Users/selur/build-Hybrid-Desktop-Release/Hybrid.app/Contents/MacOS/vsfilters/SourceFilter/FFMS2/ffms2.dylib' )

Are you sure you have the right file name? Are you sure that file is a library?

[kolak]

haven't figured out to compile l-smash on mac and I'm not sure if I the loading script is correct,...

Vapoursynth OSX installer has it. You can find post about it in vs section.

[Selur]

Are you sure you have the right file name? Are you sure that file is a library?
Ahhh it was a typo. :) Now I get a 'Video codec not found', but that is probably due to some mistake during the ffms2 compilation. (forgot the ffmpeg libs) Thanks totally didn't see the typo yesterday.
Vapoursynth OSX installer has it. You can find post about it in vs section.
Problem with that is that it interferes with the vapoursynth version I installed through homebrew to be able to compile my own vsedit version (contains some limited ipc capabilities).
+ There doesn't seem to be a way to uninstall it and it's r33 not r33.1

[Myrsloik]

I have too much other stuff to do and I think some of you could help me on the Python side.

Task 1:
If you do something like clip1 + clip2 + clip3 + clip4... this expands to Splice([Splice([Splice([clip1, clip2]), clip3]), clip4])...
It works but becomes a bit inefficient when hundreds of clips are involved and combining it into a single Splice[clip1, clip2, clip3, ...] would be better. Something like a delayed evaluation object for splice operations could be nice to have. Something similar for trim could also be useful. I guess.

The relevant code to modify can be found here (https://github.com/vapoursynth/vapoursynth/blob/master/src/cython/vapoursynth.pyx#L932). Needs cython to compile but works just like normal python.

Task 2:
I want to flatten things so you don't need to keep a core object around anymore like this:

import vapoursynth as vs
vs.std.BlankClip()

So basically also check the object returned from get_core() for all the attributes not found directly in the vapoursynth module. Cython unfortunately doesn't seem to like the usual Python tricks so I'm a bit stuck there too. Too bad __getattr__ doesn't exist on the module level.

[Sm3n]

Hi,

What would be the best, fastest and effective way to do a SelectRangeEvery like Avisynth does?
I read this https://forum.doom9.org/showthread.php?t=172277&highlight=selectrangeevery but the only thing I can do is a simple SelectEvery.

Should I trim some part of the clip then merge them together or is there an easiest way with the function above?

[Myrsloik]

Hi,

What would be the best, fastest and effective way to do a SelectRangeEvery like Avisynth does?
I read this https://forum.doom9.org/showthread.php?t=172277&highlight=selectrangeevery but the only thing I can do is a simple SelectEvery.

Should I trim some part of the clip then merge them together or is there an easiest way with the function above?

Why is my previously proposed solution not simple enough?
clip = core.std.SelectEvery(clip = clip, cycle = x, offsets = range(14))
This is functionally identical to SelectRangeEvery. If you want to change the initial offset just trim the input clip. Done!

[Sm3n]

My bad. The values for x and range was way to low. ^^'
It's definitely easy.

Is it possible to tweak QTGMC like in avisynth using mode to get the max speed or vapoursynth does it by itself automaticaly with vs.get_core?

The x264 process is slower with a vpy script than an avs script. It's a simple script:

import vapoursynth as vs
import havsfunc as haf
core = vs.get_core(threads=8)
core.avs.LoadPlugin(r'C:\Program Files (x86)\AviSynth+\plugins64\DGDecodeNV.dll')
video = core.avs.DGSource(r'H:\Videos1.dgi')+core.avs.DGSource(r'H:\Videos2.dgi')+core.avs.DGSource(r'H:\Videos3.dgi')+core.avs.DGSource(r'H:\Videos4.dgi')
video = haf.QTGMC(video, Preset='Medium', TFF=True, FPSDivisor=2).fmtc.resample(kernel="spline36", w=1280, h=720).fmtc.bitdepth(bits=8)
video.set_output()

I think I read that Spline36 resize method is much slower than a simple one. I'm also using it with avisynth. Is it slower than avs's and that would explain the difference of speed?

[Myrsloik]

My bad. The values for x and range was way to low. ^^'
It's definitely easy.

Is it possible to tweak QTGMC like in avisynth using mode to get the max speed or vapoursynth does it by itself automaticaly with vs.get_core?

The x264 process is slower with a vpy script than an avs script. It's a simple script:

import vapoursynth as vs
import havsfunc as haf
core = vs.get_core(threads=8)
core.avs.LoadPlugin(r'C:\Program Files (x86)\AviSynth+\plugins64\DGDecodeNV.dll')
video = core.avs.DGSource(r'H:\Videos1.dgi')+core.avs.DGSource(r'H:\Videos2.dgi')+core.avs.DGSource(r'H:\Videos3.dgi')+core.avs.DGSource(r'H:\Videos4.dgi')
video = haf.QTGMC(video, Preset='Medium', TFF=True, FPSDivisor=2).fmtc.resample(kernel="spline36", w=1280, h=720).fmtc.bitdepth(bits=8)
video.set_output()

I think I read that Spline36 resize method is much slower than a simple one. I'm also using it with avisynth. Is it slower than avs's and that would explain the difference of speed?

What mode? I don't know what you mean.

Bonus points for not saying how much slower it is so I can speculate why. Different code, different speed. I don't have much to add there.

Try another resizer and find out? Looks easy enough to do...

[Sm3n]

Avisynth can use MTMode so we can make QTGMC process much faster. Sure you already knew. ^^
Can we do that in vapoursynth? For exemple in avisynth QTGMC has this option: EdiThreads=3. Vapoursynth hasn't.

My speed tests:
Avs (QTGMC=medium, spline36) + x264 (veryslow) = 5min to achieve 5.30fps
Vpy (QTGMC=medium, spline36) + x264 (veryslow) = 5min to achieve 4fps

Very significant. I assume CPU doesn't assing the same % to the pipe process.
Sure I can try all I know but I rather ask for all I don't. Maybe there is some options I don't know yet or what.

[Myrsloik]

Avisynth can use MTMode so we can make QTGMC process much faster. Sure you already knew. ^^
Can we do that in vapoursynth? For exemple in avisynth QTGMC has this option: EdiThreads=3. Vapoursynth hasn't.

My speed tests:
Avs (QTGMC=medium, spline36) + x264 (veryslow) = 5min to achieve 5.30fps
Vpy (QTGMC=medium, spline36) + x264 (veryslow) = 5min to achieve 4fps

Very significant. I assume CPU doesn't assing the same % to the pipe process.
Sure I can try all I know but I rather ask for all I don't. Maybe there is some options I don't know yet or what.

The mtmode stuff only exists in avisynth because there threading is one big hack. Or at least used to be.

What's the cpu usage like? is it 100% for both or less for VS?

[Sm3n]

The mtmode stuff only exists in avisynth because there threading is one big hack. Or at least used to be.

What's the cpu usage like? is it 100% for both or less for VS?

Yup, 100% both.

I ran a new test. Vpy = 4.90fps
Now sure for some, difference could be nothing but during an encode taking hours, at the end it might have time wasted.

Thx for your help.

[Myrsloik]

Yup, 100% both.

I ran a new test. Vpy = 4.90fps
Now sure for some, difference could be nothing but during an encode taking hours, at the end it might have time wasted.

If the difference is that big between runs you really need a better way to measure things. Seriously. With that kind of variation you can't even say that one is faster than the other.

[Sm3n]

If the difference is that big between runs you really need a better way to measure things. Seriously. With that kind of variation you can't even say that one is faster than the other.

I'm doing lot of comparison. Have you a good method to measure things to me? Using Avsmeter, encoding 2h show at least once a week et cetera. My knowledge is limited but for that purpose I think I know how my system runs and I'm able to say this is more fastest than that or not. I ran lot of encode I think I understand what is the limit of the speed on case by case.
In fact, next project I have to do I'll be using a vpy script. Usualy an encode takes a bit less than 8h. It will be easy to see the difference I'm sure.

If my cpu can handle X fps in x min using avs vs Y fps in x min using vpy where Y is slowest, I'm pretty sure that avs+x264 process will finish sooner than vpy+x264. Maybe I'm wrong but it makes sense to me.

[TheFluff]

https://zedshaw.com/archive/programmers-need-to-learn-statistics-or-i-will-kill-them-all/

see especially the part about confounding

[Myrsloik]

R34 RC1 YO! Check it out! Basically it fixes the horrible buggy untested mess that R33 was. Should be a safe to use. Just note that the abomination that is temporalsoften no longer is an included plugin.

Installer (https://dl.dropboxusercontent.com/u/73468194/VapourSynth-R34-RC1.exe)
Portable 64bit (https://dl.dropboxusercontent.com/u/73468194/VapourSynth64-Portable-R34-RC1.7z)
Portable 32bit (https://dl.dropboxusercontent.com/u/73468194/VapourSynth32-Portable-R34-RC1.7z)

Changes:
r34:
it's now possible to skip installing the visual studio runtimes in the installer to reduce online dependency of installer (installation may not work until manually installed, obviously)
temporalsoften plugin is no longer included in the windows installer, it has been replaced by the misc plugin containing various functions useful for avisynth compatibility
the default max memory usage is now 4GB on 64bit systems
fixed several unpacking issues in avisource introduced in the previous version
added warning if there are any nodes or frames still in use when the core is free
improved avfs prefetch logic for vpy
added premultiplied blending mode to maskedmerge
added premultiply filter to premultiply a clip with alpha
makediff and adddiff no longer pointlessly clamp float to a limited range since there's no good reason to do so
fixed memory leak when the core is freed introduced in the previous version
fixed memory leak in avfs introduced in the previous version
removed rshift and replaced it with a scale argument in sobel and prewitt
fixed sobel and prewitt wrongly passing through the input pixel values
added support for hdr formats and dci-p3 in zimg
optimized planestats
added float support to pemverifier
fixes active region offset and height for interlaced resizing
added support for more different subsampled input formats for vfm (jackoneill)

[~ VEGETA ~]

I am using R33-1 and it is working fine. I use the x64 portable version with python352 and the editor all in one folder as recommended. Now, for updating to newer versions, should I just copy and replace VS files (excluding plugins folder)?

[Myrsloik]

I am using R33-1 and it is working fine. I use the x64 portable version with python352 and the editor all in one folder as recommended. Now, for updating to newer versions, should I just copy and replace VS files (excluding plugins folder)?

Including the plugins dir. Overwriting an existing version is fine.

[dipje]

The HDR stuff seems to work nicely. Able to convert some clips to something that is quite OK to look at on regular screens. I do a little gamma tweak (like 1.2 or 1.3) to lift the shadows a bit at the end with a nominal luminance somewhere between 400 and 600 and so far so good.

That being said, can someone help me to get something like highlight compression or shadow boosting without altering the entire gamma?
A bit like Photo-correcting software does.

Is something possible? with Expr or something? Or make / define a curve myself with float values that map values close-to 1.0 and over 1.0 to a sane value within the 0.0 - 1.0 range?

And / or, is it possible to load and apply 3d Cube lut files?

[Myrsloik]

The HDR stuff seems to work nicely. Able to convert some clips to something that is quite OK to look at on regular screens. I do a little gamma tweak (like 1.2 or 1.3) to lift the shadows a bit at the end with a nominal luminance somewhere between 400 and 600 and so far so good.

That being said, can someone help me to get something like highlight compression or shadow boosting without altering the entire gamma?
A bit like Photo-correcting software does.

Is something possible? with Expr or something? Or make / define a curve myself with float values that map values close-to 1.0 and over 1.0 to a sane value within the 0.0 - 1.0 range?

And / or, is it possible to load and apply 3d Cube lut files?

1. Loading cube luts (http://wwwimages.adobe.com/content/dam/Adobe/en/products/speedgrade/cc/pdfs/cube-lut-specification-1.0.pdf) is eternally on my todo list but don't wait for it

2. If you only want 1d adjustment you can definitely do that with expr if you don't mind creating your own expression

3. I have no idea what algorithm photo correction software uses (and I can't google my way to it since you didn't list software+mode) but I suspect it's closer to local constrast enhancement than a 1d lut adjustment

[~ VEGETA ~]

Including the plugins dir. Overwriting an existing version is fine.

Well, I have done some effort collecting plugins into that folder, and I have another folder called "scripts" beside it.

The plugins folder comes empty anyway. If you mean the core plugins then fine, I can replace it.

[Myrsloik]

Well, I have done some effort collecting plugins into that folder, and I have another folder called "scripts" beside it.

The plugins folder comes empty anyway. If you mean the core plugins then fine, I can replace it.

Yes, that's what I meant.

[VS_Fan]

That being said, can someone help me to get something like highlight compression or shadow boosting without altering the entire gamma?
A bit like Photo-correcting software does.
Some time ago I got amazing results in AVIsynth with the "HDR AGC plugin (http://forum.doom9.org/showthread.php?t=93571)".

Also, have you tried "Retinex" (http://forum.doom9.org/showthread.php?t=171307) plugin for VapourSynth?

[Myrsloik]

Changes from RC1:
Pismo PFM runtime included in the installer to make AVFS usage easier
AVFS supports avs+ high bitdepth output
Super minor fixes nobody will ever notice

R34 RC2 (https://dl.dropboxusercontent.com/u/73468194/VapourSynth-R34-RC2.exe)
Portable 64bit (https://dl.dropboxusercontent.com/u/73468194/VapourSynth64-Portable-R34-RC2.7z)
Portable 32bit (https://dl.dropboxusercontent.com/u/73468194/VapourSynth32-Portable-R34-RC2.7z)

[Myrsloik]

R34 released. Post about stuff (http://www.vapoursynth.com/2016/10/r34-being-nice-to-avisynth/). Finally got everything tested. Use the donation button so you can say you've contributed to real donationware!

Changes:
r34:
avfs can now output the same high bitdepth formats for avisynth+ as for vapoursynth
it's now possible to skip installing the visual studio runtimes in the installer to reduce online dependency of installer (installation may not work until manually installed, obviously)
temporalsoften plugin is no longer included in the windows installer, it has been replaced by the misc plugin containing various functions useful for avisynth compatibility
the default max memory usage is now 4GB on 64bit systems
fixed several unpacking issues in avisource introduced in the previous version
added warning if there are any nodes or frames still in use when the core is freed
improved avfs prefetch logic for vpy
added premultiplied blending mode to maskedmerge
added premultiply filter to premultiply a clip with alpha
makediff and adddiff no longer pointlessly clamp float to a limited range since there's no good reason to do so
fixed memory leak when the core is freed introduced in the previous version
fixed memory leak in avfs introduced in the previous version
removed rshift and replaced it with a scale argument in sobel and prewitt
fixed sobel and prewitt wrongly passing through the input pixel values
added support for hdr formats and dci-p3 in zimg
optimized planestats
added float support to pemverifier
fixes active region offset and height for interlaced resizing
added support for more different subsampled input formats for vfm (jackoneill)

[bin.n2f]

:thanks: Myrsloick
========
GenericFilters is no longer included because the core functions plus the TCanny plugin can now replace 99% of its uses
========
i want to use GBlur,2.83 in R34

what is alternative for that at same strength?

& thanks again

[Myrsloik]

:thanks: Myrsloick
========
GenericFilters is no longer included because the core functions plus the TCanny plugin can now replace 99% of its uses
========
i want to use GBlur,2.83 in R34

what is alternative for that at same strength?

& thanks again

It should be about the same I guess? I haven't really compared the details and it's a better question for the TCanny author. Or just experiment until it looks the same. That's rarely wrong.

[lansing]

how do you unmount the script in the new version?

EDIT: ok I figured that the file unmount itself when I close the cmd window.

other problems I have, there're no check on the files that you're going to mount, I can type in whatever filename at the end of the cmd and the program will still sees it as a file and mounted it.

And I have a video file that gives me garble images after mount, which it has not happen before.

[Myrsloik]

how do you unmount the script in the new version?

EDIT: ok I figured that the file unmount itself when I close the cmd window.

other problems I have, there're no check on the files that you're going to mount, I can type in whatever filename at the end of the cmd and the program will still sees it as a file and mounted it.

And I have a video file that gives me garble images after mount, which it has not happen before.

What's the output format of the images and what do you try to open them with?

[lansing]

What's the output format of the images and what do you try to open them with?

The output format YV12 in avi container. The script previewed normal in the vapoursynth editor, but when I open it with Adobe Premiere or Virutaldub after mount, they all give me garble images. I tried mounting different video files with the same script and they were all fine.

[Myrsloik]

The output format YV12 in avi container. The script previewed normal in the vapoursynth editor, but when I open it with Adobe Premiere or Virutaldub after mount, they all give me garble images. I tried mounting different video files with the same script and they were all fine.

Can you cut a sample that reproduces it or take a screenshot of the garbled output?

[littlepox]

:thanks: Myrsloick
========
GenericFilters is no longer included because the core functions plus the TCanny plugin can now replace 99% of its uses
========
i want to use GBlur,2.83 in R34

what is alternative for that at same strength?

& thanks again

Simply use:

res = core.tcanny.TCanny(src,sigma=2.83,mode=-1)

[lansing]

Can you cut a sample that reproduces it or take a screenshot of the garbled output?

Okay after more testings, I found out that the problem came from the cropRel function in my script


clip = core.std.CropRel(clip, left=12, top=0, right=10, bottom=10)

clip = core.std.CropRel(clip, left=12, top=0, right=12, bottom=12)


The top one gives my garbage image after mount, the bottom one works fine

[littlepox]

Okay after more testings, I found out that the problem came from the cropRel function in my script


clip = core.std.CropRel(clip, left=12, top=0, right=10, bottom=10)

clip = core.std.CropRel(clip, left=12, top=0, right=12, bottom=12)


The top one gives my garbage image after mount, the bottom one works fine

Is it because of mod4/mod8/mod16 issue?

I believe for the top one you get a video with width or height not divisible by 4, which may be problematic in certain cases.

[Myrsloik]

Okay after more testings, I found out that the problem came from the cropRel function in my script


clip = core.std.CropRel(clip, left=12, top=0, right=10, bottom=10)

clip = core.std.CropRel(clip, left=12, top=0, right=12, bottom=12)


The top one gives my garbage image after mount, the bottom one works fine

That is kinda odd. I can reproduce it but I have no idea why it happens. Oddly enough mpc-hc seems to play the file right. That makes it even weirder.

[Myrsloik]

R35-RC1 (https://dl.dropboxusercontent.com/u/73468194/VapourSynth-R35-RC1.exe)

Should fix the avfs issues. Report any other bugs you find.

r35:
fixed avfs frame packing so it matches vfw behavior
fixed one frame leak on script reload in avfs
fixed 8bit 3x3 convolution where the upper left pixel wouldn't be taken into account correctly on x86

[lansing]

yes problem fixed, thanks

[bin.n2f]

Simply use:

res = core.tcanny.TCanny(src,sigma=2.83,mode=-1)

:thanks:

[Myrsloik]

R35 released. Same changes as for RC1 a few posts up. Now we're back to regular stable maintenance releases again I guess since AVFS, optimizations and other big refactoring has been tested now.

[Selur]

Got an invalid syntax error and I'm not sure what I'm doing wrong,..
(I'm on Ubuntu 14.04)

trying to load:
# Imports
import os
import sys
import vapoursynth as vs
core = vs.get_core()
# Import scripts folder
scriptPath = '/usr/lib/python3/dist-packages'
sys.path.append(os.path.abspath(scriptPath))
# Import scripts
import vs-havsfunc as havsfunc
# Loading /home/selur/Desktop/Test-AC3-5.1.avi using LWLibavSource
clip = core.lsmas.LWLibavSource(source="/home/selur/Desktop/Test-AC3-5.1.avi", cache=0)
# stabilizing using Stab
clip = havsfunc.Stab(clp=clip)
# Output
clip.set_output()

I get:
Failed to evaluate the script:
Python exception: invalid syntax (test.vpy, line 10)
Traceback (most recent call last):
File "src/cython/vapoursynth.pyx", line 1490, in vapoursynth.vpy_evaluateScript (src/cython/vapoursynth.c:26958)
File "/home/selur/Desktop/test.vpy", line 10
import vs-havsfunc as havsfunc
^
SyntaxError: invalid syntax

havsfunc is present inside '/usr/lib/python3/dist-packages/vs-havsfunc.py'

-> How would I properly load the havsfunc script?

[Are_]

The problem is you are using a dash character in the module's name. Why?

Convert it to an underscore or even better, use the original name.

[Selur]

got the script from a ppa where the dash was inside the name. :)
Thanks for the info. :)

[Khanattila]

Feature request: native support for OpenCL platform.




Really, it's not a joke.

[Selur]

native support for OpenCL platform.
What OpenCL support is there aside from native?