View Full Version : Vapoursynth
Kupildivan
9th March 2015, 21:41
OK. Where to download all compiled plugins for QTGMC?
jackoneill
9th March 2015, 23:38
OK. Where to download all compiled plugins for QTGMC?
https://github.com/HomeOfVapourSynthEvolution/VapourSynth-DFTTest/releases/
http://ldesoras.free.fr/src/vs/fmtconv-r8.zip
https://github.com/dubhater/vapoursynth-mvtools/releases/
https://github.com/dubhater/vapoursynth-nnedi3/releases
http://www.mediafire.com/download.php?dnld4p98i333idp or http://uloz.to/x6gvxpbB/scenechange-win64-7z
Kupildivan
19th March 2015, 17:38
Script evaluation failed:
Python exception: No attribute with the name scd exists. Did you mistype a plugin namespace?
Traceback (most recent call last):
File "vapoursynth.pyx", line 1488, in vapoursynth.vpy_evaluateScript (src\cython\vapoursynth.c:25136)
File "VSQTGMC.vpy", line 7, in <module>
v = haf.QTGMC (v, Preset='Medium', TFF=True)
File "C:\Python34-64\lib\site-packages\havsfunc.py", line 871, in QTGMC
if TR0 > 0: ts1 = TemporalSoften(bobbed, 1, 255, CMts, 28, 2) # 0.00 0.33 0.33 0.33 0.00
File "C:\Python34-64\lib\site-packages\havsfunc.py", line 3238, in TemporalSoften
clip = set_scenechange(clip, scenechange)
File "C:\Python34-64\lib\site-packages\havsfunc.py", line 3260, in set_scenechange
sc = core.scd.Detect(sc, thresh)
File "vapoursynth.pyx", line 1109, in vapoursynth.Core.__getattr__ (src\cython\vapoursynth.c:19250)
AttributeError: No attribute with the name scd exists. Did you mistype a plugin namespace?
Some plugin is absent? But which?
Myrsloik
19th March 2015, 17:52
Script evaluation failed:
Python exception: No attribute with the name scd exists. Did you mistype a plugin namespace?
Traceback (most recent call last):
File "vapoursynth.pyx", line 1488, in vapoursynth.vpy_evaluateScript (src\cython\vapoursynth.c:25136)
File "VSQTGMC.vpy", line 7, in <module>
v = haf.QTGMC (v, Preset='Medium', TFF=True)
File "C:\Python34-64\lib\site-packages\havsfunc.py", line 871, in QTGMC
if TR0 > 0: ts1 = TemporalSoften(bobbed, 1, 255, CMts, 28, 2) # 0.00 0.33 0.33 0.33 0.00
File "C:\Python34-64\lib\site-packages\havsfunc.py", line 3238, in TemporalSoften
clip = set_scenechange(clip, scenechange)
File "C:\Python34-64\lib\site-packages\havsfunc.py", line 3260, in set_scenechange
sc = core.scd.Detect(sc, thresh)
File "vapoursynth.pyx", line 1109, in vapoursynth.Core.__getattr__ (src\cython\vapoursynth.c:19250)
AttributeError: No attribute with the name scd exists. Did you mistype a plugin namespace?
Some plugin is absent? But which?
Scenechange. Linked in the previous post.
Kupildivan
19th March 2015, 18:04
Fixed. I had mistakingly copied 32-bit version of that scenechange into 64 folder.
But then appeared another error:
Python exception: nnedi3: Couldn't open file 'C:/Program Files (x86)/VapourSynth/plugins64/nnedi3_weights.bin'. Error message: No such file or directory
captainadamo
19th March 2015, 18:14
Fixed. I had mistakingly copied 32-bit version of that scenechange into 64 folder.
But then appeared another error:
Python exception: nnedi3: Couldn't open file 'C:/Program Files (x86)/VapourSynth/plugins64/nnedi3_weights.bin'. Error message: No such file or directory
You need to download the renamed weights file for NNEDI3 v4.
https://github.com/dubhater/vapoursynth-nnedi3/blob/master/src/nnedi3_weights.bin?raw=true
Kupildivan
19th March 2015, 18:18
Thanks. I have done that already after looking at download page more attentively.
Now it works.
How about importing avisynth plugins in 64-bit vapoursynth? It always shows me the same error: "No attribute with the name avs exists".
RTW47
20th March 2015, 11:14
How about importing avisynth plugins in 64-bit vapoursynth? It always shows me the same error: "No attribute with the name avs exists".
64-bit version of VapourSynth cannot load 64-bit AviSynth plugins. You have to either work in 32-bit mode or port particular avs plugin.
Picky_editor
24th March 2015, 20:31
When I click on the link for the file below, Avast Antivirus is reporting that the file below is a "Suspicious Item".
https://github.com/vapoursynth/vapoursynth/releases/download/R26/vapoursynth-r26.exe
It lists the URL as:
https://s3.amazonaws.com/github-cloud/releases/11136031/1c246d40-a680-11e4-93c3-543cf55e
with the remainder of the link truncated.
Please advise
Myrsloik
24th March 2015, 20:43
When I click on the link for the file below, Avast Antivirus is reporting that the file below is a "Suspicious Item".
https://github.com/vapoursynth/vapoursynth/releases/download/R26/vapoursynth-r26.exe
It lists the URL as:
https://s3.amazonaws.com/github-cloud/releases/11136031/1c246d40-a680-11e4-93c3-543cf55e
with the remainder of the link truncated.
Please advise
All antivirus is shit. I find your post suspicious.
You have been advised.
LoRd_MuldeR
24th March 2015, 20:44
When I click on the link for the file below, Avast Antivirus is reporting that the file below is a "Suspicious Item".
https://github.com/vapoursynth/vapoursynth/releases/download/R26/vapoursynth-r26.exe
It lists the URL as:
https://s3.amazonaws.com/github-cloud/releases/11136031/1c246d40-a680-11e4-93c3-543cf55e
with the remainder of the link truncated.
Please advise
Check the file again with multiple anti-virus engines, which will probably show that this is a False Positive (http://en.wikipedia.org/wiki/Antivirus_software#Problems_caused_by_false_positives):
https://www.virustotal.com/
If so, please report the problem to the developer of your so-called "anti-virus" software!
Picky_editor
24th March 2015, 22:21
I can't actually download the file to be able to check it with other software. It is blocked as soon as I click in the download link, before I indicate where to save the file.
I was hoping that someone else could check the link and see if they are getting a warning as well.
LoRd_MuldeR
24th March 2015, 22:41
I can't actually download the file to be able to check it with other software. It is blocked as soon as I click in the download link, before I indicate where to save the file.
If your "anti-virus" software really doesn't allow you to manually ignore/override the (false) alarm, I suggest to get something less intrusive...
I was hoping that someone else could check the link and see if they are getting a warning as well.
See here:
https://www.virustotal.com/en/file/2abb6e45400796e06d3375bfd22f67563d3234ceeece22f95abbd4a6bfadaf71/analysis/1427233228/
SHA256: 2abb6e45400796e06d3375bfd22f67563d3234ceeece22f95abbd4a6bfadaf71
File name: vapoursynth-r26.exe
Detection ratio: 0 / 57
Analysis date: 2015-03-24 21:40:28 UTC ( 2 minutes ago )
Kupildivan
25th March 2015, 18:46
When piping the script with --y4m to x264 or ffmpeg they don't know total number of frames. Remaining encode time is unknown. How it should be fixed?
captainadamo
25th March 2015, 18:50
Tell x264 the number of frames using the --frames switch.
Kupildivan
25th March 2015, 19:01
It works, but requires its manual adding every time to new script.
I'm asking about automatical defining.
So
v.output (sys.stdout, y4m=True)
for me worked nice before, but something has changed. Don't know what but now it has no effect.
sl1pkn07
25th March 2015, 19:13
i use scripting with vspipe --info
this is for linux. but you can adapt to your system
_frames="$(vspipe --info "${1}" - | grep Frames | cut -d ' ' -f2)"
vspipe -y "${1}" - | "${x264}" - --output "${2}" --frames "${_frames}" --stdin y4m --foo
'$1' is the vpy script and '$2' the output file
sneaker_ger
25th March 2015, 19:14
While we're at it: it's a bit strange for "--info" to require an output file name.
Myrsloik
25th March 2015, 19:18
While we're at it: it's a bit strange for "--info" to require an output file name.
You're the first one to mention it. I guess it is slightly unusual. Other opinions?
LoRd_MuldeR
25th March 2015, 20:13
It works, but requires its manual adding every time to new script.
I'm asking about automatical defining.
You could use a GUI like the Simple x264/x265 Launcher, if you are not too much into scripting ;)
http://forum.doom9.org/showthread.php?t=144140
Sangan
31st March 2015, 18:29
You could use a GUI like the Simple x264/x265 Launcher, if you are not too much into scripting ;)
http://forum.doom9.org/showthread.php?t=144140
... I would like to use that too... on a Mac, not in Wine, because in Wine (the up to date one via Homebrew) neither VS 25 nor 26 will install...
shekh
5th April 2015, 11:43
Hi,
What do you think about outputting b48r, b64a from vfw interface?
I am developing VirtualDub modification with 16bit pipeline, and it seems interesting to support VapourSynth.
Also I noticed this:
when I open in VirtualDub vpy script with utf8 BOM, it is not interpreted (error message complains on bad 1st character). Python commandline does interpret it fine.
Myrsloik
5th April 2015, 14:35
Hi,
What do you think about outputting b48r, b64a from vfw interface?
I am developing VirtualDub modification with 16bit pipeline, and it seems interesting to support VapourSynth.
Also I noticed this:
when I open in VirtualDub vpy script with utf8 BOM, it is not interpreted (error message complains on bad 1st character). Python commandline does interpret it fine.
Output to other formats is easy to add. The biggest reason I didn't add those formats yet is that no applications that accept them use the normal vfw code for reading files.
The bom problem is odd. It should work exactly the same.
lo1t3yu
12th April 2015, 05:43
Hello.
When lsmash lib loading vs give error:
>>> core.std.LoadPlugin('/home/user/liblsmash.so.2')
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "vapoursynth.pyx", line 1387, in vapoursynth.Function.__call__ (src/cython/vapoursynth.c:23550)
vapoursynth.Error: No entry point found in /home/user/liblsmash.so.2
>>> core.std.LoadPlugin('/home/user/libvslsmashsource.so.')
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "vapoursynth.pyx", line 1387, in vapoursynth.Function.__call__ (src/cython/vapoursynth.c:23550)
vapoursynth.Error: Failed to load /home/user/libvslsmashsource.so.. Error given: /home/user/libvslsmashsource.so.: undefined symbol: avcodec_default_get_buffer2
Maybe lsmash vs plugin compiled without required libs/codecs?
Solved. Vapoursynth's lsmash plugin has been compiled with old libav* inc headers, but now vs break error:
import vapoursynth as vs
#import havsfunc as haf
core = vs.get_core()
core.std.LoadPlugin('/home/user/libvslsmashsource.so.')
v = core.LWLibavSource('/home/user/1.ts')
AttributeError: No attribute with the name LWLibavSource exists. Did you mistype a plugin namespace?
What func name need to use?
RTW47
12th April 2015, 15:01
AttributeError: No attribute with the name LWLibavSource exists. Did you mistype a plugin namespace?
What func name need to use?
you need to additionally specify lsmas namespace eg:.
v = core.lsmas.LWLibavSource(source=r'D:\video.m2ts')
lo1t3yu
12th April 2015, 15:41
you need to additionally specify lsmas namespace eg:.
v = core.lsmas.LWLibavSource(source=r'D:\video.m2ts')
Thanks! It works.
Myrsloik
26th April 2015, 18:37
Just go to the FFMS2 thread to find links instead.
Myrsloik
6th May 2015, 20:54
Here's R27 RC1 (https://www.dropbox.com/s/a6yobbz7xz5nkf9/vapoursynth-r27-rc1.exe?dl=1). It's needed to use plugins such as the new FFMS2 compiles by me and fmtconv r9.
The big news is that genericfilters no longer will be a separate plugin. Instead most of it has been rewritten (and corrected) and integrated into the core. Simply replace stuff like core.generic.Maximum() with core.std.Maximum(). The new versions may be slightly slower but also have less unexpected bugs to find.
Changes:
r27:
added a rewritten version of genericfilters to the core (nodame)
fixed the not (required two operands instead of one, asm broken) and swap (only required one operand instead of two) operators in the expr filter
renamed the x and y arguments in cropabs to left and top to be clearer and match croprel
addborders now rejects negative borders properly and passes through clips unchanged when all borders are 0
several bugfixes to the bundled genericfilters
added compile time option to have additional guard memory around frames to detect out of bounds writes in filters
added setframeprop filter (nodame)
the framerate and the frame duration property should now be a normalized number
all internal filters now return an error if the returned clip is longer than INT_MAX instead of undefined behavior
"unknown" length clips have been deprecated and a fatal error will happen if any plugin returns them, this change is because it was complicated, annoying and accomplished nothing compared to INT_MAX length clips
freezeframes now doesn't need to have the ranges specified in ascending order
interleave, separatefield and selectevery now properly adjusts the framerate including the durations
changed the meaning of _FieldBased to be able to signal progressive/bff/tff material, this is now used by ffms2, eedi3 and separatefields
fixed memory leak in assvapour destructor
the identifiers used for keys in vsmap can only be alphanumeric and _, anything else will be rejected
the expr filter now does constant folding which makes it faster in many cases (nodame)
vspipe can now output timecode v2 files (nodame)
splice and interleave now properly reject clips with mismatched fps unless mismatch is set
fixed possible bad behavior/crash in FrameEval under rare circumstances
fixed truncation of last digit of integers in text.FrameProps
speedyrazor
9th May 2015, 10:36
Hi, I currently write python applications which then call on and create avisynth avs files which use Quicktime Prores files as an input and feed the avs files to ffmpeg, this works, but is very slow, as avisynth is. I came upon this post and wondered if I could switch to using VapourSynth instead. I primarily do conversions between HD and SD and speed change the video, so for example going from HD 23.98 to SD PAL 25 via a speed change, pitch correcting the audio so it remains the same pitch. Below is the sort of script I currently use in Avisynth, so my question is can I achieve the same thing in VapourSynth?
Avisynth Script:
QTInput("test.mov", quality=100, audio=2)
ColorMatrix(mode="Rec.709->Rec.601", clamp=0)
Spline36Resize(720, 576)
TimeStretch(tempo = 25.0/24.0*100.0)
AssumeFPS(25, 1)
Kind regards.
Myrsloik
9th May 2015, 13:46
No, you can't. The audio support isn't there yet.
Myrsloik
11th May 2015, 15:23
It's time for R27 RC4 (https://www.dropbox.com/s/wswdr9lvfdwj34z/vapoursynth_r27-rc4.exe?dl=1)!
It will probably be the last RC unless huge bugs are discovered. Changes from RC1:
Fixed PropToClip crash on certain errors
Improved ClipInfo to show more useful information
An updated version of generic filters with a few more bugs fixed
Btw, you should stop using the old generic filters and instead use the new one integrated into the VS core.
sl1pkn07
11th May 2015, 16:50
what is the default icon for .vpy files in windows?
is for copy to my linux installation
buchanan
11th May 2015, 16:55
Hi Myrsloik,
Since R27 RC1, it seems to me there is a memory bug with Selectevery. Simply load a 1920*1080 clip, apply vid=core.std.SelectEvery(clip=vid, cycle=2, offsets=1) and output the clip : vspipe.exe memory consumption is constantly increasing
Myrsloik
11th May 2015, 17:03
There is no official icon. Contributions welcome.
Hi Myrsloik,
Since R27 RC1, it seems to me there is a memory bug with Selectevery. Simply load a 1920*1080 clip, apply vid=core.std.SelectEvery(clip=vid, cycle=2, offsets=1) and output the clip : vspipe.exe memory consumption is constantly increasing
Fixed, a line of code disappeared by mistake... I've updated the rc4 installer.
jackoneill
12th May 2015, 19:58
PSA: If you're writing a script and you want it to be usable forever, pass filter parameters using their names.
Good:
core.ns.Filter(clip=asdf, param=value, etc=etc)
Bad:
core.ns.Filter(asdf, value, etc)
Filter parameters may be rearranged to look better in the source, new parameters may be added, who knows.
splinter98
12th May 2015, 22:18
PSA: If you're writing a script and you want it to be usable forever, pass filter parameters using their names.
Good:
core.ns.Filter(clip=asdf, param=value, etc=etc)
Bad:
core.ns.Filter(asdf, value, etc)
Filter parameters may be rearranged to look better in the source, new parameters may be added, who knows.
...Although parameters may also be renamed so no guarantees for forever reuse... (Some form of depreciation warning system might be useful to implement)
At least it ensures you no transposed arguments get unnoticed. :(
Myrsloik
13th May 2015, 20:28
R27 is released! Links and changelog in the first post as usual.
Here's my blog post about the important compatibility changes (http://www.vapoursynth.com/2015/05/r27-revising-stuff-and-things/).
Start switching to the internal version of GenericFilters because the plugin version will disappear in R28.
foxyshadis
13th May 2015, 21:33
Thanks! I changed the title of the GenericFilters thread to reflect that.
lo1t3yu
19th May 2015, 09:04
What namespace is using in newer VapourSynth?
Try use
import vapoursynth as vs
import havsfunc as haf
core = vs.get_core()
v = core.ffms2.Source(source='1080i_25.ts', fpsnum=25, fpsden=1)
File "vapoursynth.pyx", line 1469, in vapoursynth.vpy_evaluateScript (src/cython/vapoursynth.c:24726)
File "script.vpy", line 5, in <module>
v = core.ffms2.Source(source='1080i_25.ts', fpsnum=25, fpsden=1)
File "vapoursynth.pyx", line 1090, in vapoursynth.Core.__getattr__ (src/cython/vapoursynth.c:18928)
AttributeError: No attribute with the name ffms2 exists. Did you mistype a plugin namespace?
VapourSynth R27 and ffms2 2.21. VS and ffms2 have been successfully compiled with latest ffmpeg/libav libs.
Myrsloik
19th May 2015, 09:32
What namespace is using in newer VapourSynth?
Try use
VapourSynth R27 and ffms2 2.21. VS and ffms2 have been successfully compiled with latest ffmpeg/libav libs.
It's the same namespace. Are you sure you placed the plugin in the right location for it to be autoloaded?
lo1t3yu
19th May 2015, 17:08
It's the same namespace. Are you sure you placed the plugin in the right location for it to be autoloaded?
Yep. I try to set plugin path in $HOME/.config/vapoursynth/vapoursynth.conf, but it doesn't works.
Also, using R27 plugins in system dir (/usr/lib/vapoursynth) aren't loading. However,
nobody talks about the issues with plugins autoloading. Maybe, this depends on the system libs and bashrc configs? Now is clean.
captainadamo
19th May 2015, 17:52
Did you try doing a manual loading of the plugin to make sure there is not some other issue at play?
lo1t3yu
20th May 2015, 07:36
Did you try doing a manual loading of the plugin to make sure there is not some other issue at play?
Sure. If plugin load in script then it works fine.
feisty2
22nd May 2015, 16:10
@Myrsloik
can you add "mt_luts" and "mt_lutsx" from masktools to vs core as well, I want them for "masking" stuff
Myrsloik
22nd May 2015, 16:14
@Myrsloik
can you add "mt_luts" and "mt_lutsx" from masktools to vs core as well, I want them for "masking" stuff
No, never going into the core. They're simply far too specific operations.
feisty2
22nd May 2015, 16:21
No, never going into the core. They're simply far too specific operations.
okay, that's true... how about getting them into "GenericFilters", I would've done it if I wasn't a C/C++ numb..
lanzorg
24th May 2015, 01:02
Does someone know if it's possible to use vapoursynth with mpc-be x64 on windows ?
If yes, how to ?
8-BaLL
29th May 2015, 13:07
Hey guys,
I would like to ask you something about vapoursynth. Right now im using qtgmc preset very slow + spline64 resize (1280x720) To rncode my hdtv caps using avisynth 2.6.
The encoding speed is 1.75 fps on my system, but the cpu load is only around 45-50% only
Will the vapoursynth use the 4 cores of the cou better when using qtgmc and does it have a qtgmc preset very slow for vapoursynth?
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.