View Full Version : AWarpSharp2 for VapourSynth
jackoneill
6th October 2015, 20:47
As requested, a port of AWarpSharp2: https://github.com/dubhater/vapoursynth-awarpsharp2
The output is not 100% the same as the Avisynth plugin's, due to some differences in the way the margins are processed. If you crop away six pixels from the left and the right, then maybe the output will be identical. Then again maybe not, because I didn't bother writing any SSSE3 code.
The "chroma" parameter is a bit different now. There are also two new parameters, "planes" and "opt". It's all explained in readme.rst.
I merged the "aWarp" and "aWarp4" filters. There was really no reason to have a separate filter for the supersampled thing.
The "aWarpSharp" filter only existed for compatibility with old Avisynth scripts. That's not relevant here, so there is no such filter in this plugin.
BakaProxy
7th October 2015, 16:08
Dude, I love u.
feve
8th October 2015, 23:29
I love u.too
mastrboy
9th October 2015, 17:06
I didn't bother writing any SSSE3 code.
So we can assume this would be slower than the avisynth version?
Oh, and thanks by the way ;)
jackoneill
9th October 2015, 17:40
So we can assume this would be slower than the avisynth version?
Oh, and thanks by the way ;)
I don't know. Compare them? (Don't forget about the threads.)
Q3CPMA
9th October 2015, 22:55
Thanks a lot. One of my favourite plugins with BM3D.
ryrynz
7th June 2016, 13:44
Not sure if entirely relevant to this thread, but since the a 64 bit version has been done, what are the chances of 64 bit version for Avisynth+?
feisty2
7th June 2016, 13:47
Not sure if entirely relevant to this thread, but since the a 64 bit version has been done, what are the chances of 64 bit version for Avisynth+?
or maybe its just a perfect time to switch to vaporsynth
ryrynz
7th June 2016, 14:15
It still can't do real time post processing yet can it? I believe ffdshow raw and Avisynth is still the only option until madVR adds support.
jackoneill
7th June 2016, 16:44
Not sure if entirely relevant to this thread, but since the a 64 bit version has been done, what are the chances of 64 bit version for Avisynth+?
From me, very low. Maybe ask in the Avisynth+ thread.
~SimpleX~
10th June 2016, 08:50
Would it ever support >8bit clips?
jackoneill
10th June 2016, 10:09
Would it ever support >8bit clips?
Who knows.
jackoneill
10th June 2016, 19:09
Who knows.
Make that a "yes".
https://github.com/dubhater/vapoursynth-awarpsharp2/releases/tag/v2
The only notable change is the 16 bit support.
divxmaster
23rd July 2016, 04:51
I am having real trouble getting awarpsharp to load, all 64bit vs, definitely 64 bit libawarpsharp2.dll in plugins64. says no attribute with name warp exists. I have no trouble with any other plugins, qtgmc, fmtc, bm3d etc. any ideas? cheers Divxmaster
jackoneill
23rd July 2016, 10:11
I am having real trouble getting awarpsharp to load, all 64bit vs, definitely 64 bit libawarpsharp2.dll in plugins64. says no attribute with name warp exists. I have no trouble with any other plugins, qtgmc, fmtc, bm3d etc. any ideas? cheers Divxmaster
Load it manually so you'll get an error message:
core.std.LoadPlugin("B:/your/path/here/libawarpsharp2.dll")
divxmaster
23rd July 2016, 22:42
Ah, requires API 3.4, I'm currently on 3.2.
Thanks for the tip on LoadPlugin showing errors, vs autoload that supresses errors, that's useful to know.
edit: For those that want to know, Vapoursynth R30 or newer needed for API 3.4.
Cheers,
Divxmaster
trip_let
28th August 2016, 17:41
I think I found a bug. With AWarpSharp2 (did not test others), > 8 bit input, chroma=0, and planes=[1,2] (or 1 or 2, i.e. luma not processed for output), the output is garbled, with half the screen being totally wrong.
btw for bug reports in general do you prefer a notice here or on Github? Thanks, anyway. Really appreciate the work.
jackoneill
28th August 2016, 20:46
v3 fixes the bug. (https://github.com/dubhater/vapoursynth-awarpsharp2/releases/tag/v3)
I think I found a bug. With AWarpSharp2 (did not test others), > 8 bit input, chroma=0, and planes=[1,2] (or 1 or 2, i.e. luma not processed for output), the output is garbled, with half the screen being totally wrong.
btw for bug reports in general do you prefer a notice here or on Github? Thanks, anyway. Really appreciate the work.
I prefer Github, if you have an account there. If not, this is fine too.
jackoneill
15th June 2018, 10:41
v4 is here. (https://github.com/dubhater/vapoursynth-awarpsharp2/releases/tag/v4)
* Add parameter "cplace". Valid values: "mpeg1" and "mpeg2". Default: "mpeg1", same as in previous versions.
* Make the "depth" parameter an array so the depth can be set independently for each channel.
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.