aWarpSharp2 – rewrite of aWarpSharp

[Reel.Deel]

Originally Posted by ryrynz

Yeah this is preventing me from using AVS+ 64 bit. I've mentioned it on jackoneill's Vapoursynth port thread.

You can find the 64-bit plugin here, but it's the 2012 version. You can use it with aWarpSharp4xx to provide the same functionality as the 2015 version. A 64-bit version of cretindesalpes updated aWarpSharp2 would be better though.

[ryrynz]

Originally Posted by Reel.Deel

A 64-bit version of cretindesalpes updated aWarpSharp2 would be better though.

Thanks, I've hit up cretindesalpes about it. I doubt SEt would be interested and jackoneill isn't, I guess that leaves one or two guys in the Avisynth+ thread, fingers crossed.

FWIW it seems the current 64 bit version doesn't appear to be entirely stable, I get crashes approximately 20% of the time using awarpsharp or awarp4 on file playback when using latest Avisynth+ through ffdshow. No problems with the 32 bit version.

[Reel.Deel]

Originally Posted by ryrynz

FWIW it seems the current 64 bit version doesn't appear to be entirely stable, I get crashes approximately 20% of the time using awarpsharp or awarp4 on file playback when using latest Avisynth+ through ffdshow. No problems with the 32 bit version.

Post your script. I've haven't had any problems so far but I'm not using ffdshow.

[pinterf]

Due to popular demand (ryrynz) , I updated this nice plugin for those who were missing only this chain before plunging into the 64 bit world.

aWarpSharp2-20160624, x64 / x86

Remark: does not work with Avisynth 2.5x interface.

[GMJCZP]

Thanks, it works in XP x86!

[Selur]

@pinterf:
using

aWarpSharp(depth=64.00,blurlevel=4)

I get:

aWarpSharp2: 'depth' must be -128..127

according to http://avisynth.nl/index.php/AWarpSharp depth for aWarpSharp should be a float in the range of 0.0 - 64.0

aWarpSharp(depth=64.00,blurlevel=3)

works fine
probably some internal mapping error, reported the error also to the issue tracker of the github project.

[Groucho2004]

Originally Posted by Selur

according to http://avisynth.nl/index.php/AWarpSharp depth for aWarpSharp should be a float in the range of 0.0 - 64.0

AWarpSharp != AWarpSharp2. AWarpSharp2 expects int for depth.

[Selur]

@Groucho: I know, I never said it was and I never assumed it,....
a. the description of http://avisynth.nl/index.php/AWarpSharp2 states that the dll implements multiple functions aBlur, aSobel, aWarp, aWarp4, aWarpSharp, aWarpSharp2 and the implementation of aWarpSharp should be compatible to the old dll (which it aside from the combination of depth=64 and blurlevel=4 does seem to be)
b. depth itself isn't the issue; my guess is aWarpSharp is implemented by mapping the calls internally to aWarSharp2 and that there is a mapping error in case of the mentioned parameter combination

[Selur]

Okay, but why does it only complain with blurlevel=4 and not blurlevel=3 ?

[Groucho2004]

Originally Posted by Selur

Okay, but why does it only complain with blurlevel=4 and not blurlevel=3 ?

Sorry, too early, need coffee.

[pinterf]

Originally Posted by Selur

@pinterf:
using

aWarpSharp(depth=64.00,blurlevel=4)

I get:

according to http://avisynth.nl/index.php/AWarpSharp depth for aWarpSharp should be a float in the range of 0.0 - 64.0

aWarpSharp(depth=64.00,blurlevel=3)

works fine
probably some internal mapping error, reported the error also to the issue tracker of the github project.

The mapping is: depth * blurlevel * 0.5.
This is 128, when depth=64.0 and blurlevel=4, so you get a 'depth' must be -128..127 error message.

[Selur]

shouldn't it be more like:
(depth * blurlevel * 0.5)-1
to not throw an error?

[pinterf]

I don't see the logic behind the re-mapping depth value -128..127 exactly. What do negative numbers mean there?
The source code uses the parameter as depth << 8 and a comment says it should be 0..7FFF
Anyway, depth(64)*blurlevel(4) may silently be mapped to 127. Is it a good idea? (And the error message is confusing, too, needs polishing)

[Selur]

Anyway, depth(64)*blurlevel(4) may silently be mapped to 127. Is it a good idea?

Probably a bit ugly, but personally I wouldn't mind as long as it doesn't break anything else.

[real.finder]

Originally Posted by pinterf

Due to popular demand (ryrynz) , I updated this nice plugin for those who were missing only this chain before plunging into the 64 bit world.

aWarpSharp2-20160624, x64 / x86

Remark: does not work with Avisynth 2.5x interface.

x64 work now

[TCmullet]

I've been using aWarpSharp for about a year. I just noticed there's an aWarpSharp2, and it allegedly has a function aWarpSharp built in in a way that lets you use the original parameters for aWarpSharp so that old scripts still work.

I got:
aWarpSharp2-20160624.7z

I copied the aWarpSharp.dll from the x86 folder and to my plugins folder of Avisynth. It blows up saying aWarpSharp not found.

What's going on? Of course my system is Windows 10, 64-bit. However, I always use x86 (32-bit) versions of all video processing software to ensure reliability. Is there REALLY an aWarpSharp (original version) built in to aWarpSharp2? It doesn't seem to work.

[Groucho2004]

Originally Posted by TCmullet

It blows up saying aWarpSharp not found.

You can always test your Avisynth installation and plugin functionality with AVSMeter:
Run "AVSMeter -avsinfo" and look for any error messages.

However, I'm quite certain that your problem is related to missing MS runtimes (VS2015 x86).

[TCmullet]

Yes, that was it. Thanks, and thanks or the link. When I refound the doc here:
http://avisynth.nl/index.php/AWarpSharp2
... it DOES say you need it. I hadn't bothered to read the "requirements" as I thought it would be the same as aWarpSharp "1". Also, the link there for the c++ runtime is broken, therefore especially thanks for a working link. I knew I had c++ runtime, but turns out it was 2013; obviously outdated.

[StainlessS]

Originally Posted by TCmullet

I knew I had c++ runtime, but turns out it was 2013; obviously outdated.

You need all runtimes specific to the software that you run, the latest dll's are of no use to software requiring earlier runtimes.

Here is an All-In-One installer:- http://repacks.net/forum/viewtopic.php?t=125

Get the latest version of above if you find you have similar problems with other s/ware.

EDIT: Although you do sometimes get later versions of a specific runtime, eg a later version of VS CPP 2015 runtimes,
but still called VS CPP 2015 runtimes even if released in 2016.

[real.finder]

I think it will be nice if there are depthV like internal avs Sharpen() amountV so that we can work with only horizontal halos or colour bled safely without hurt the vertical details by set depthV=0 or depthCV=0

edit: blurV also