aWarpSharp2 – rewrite of aWarpSharp

[real.finder]

I think I get why awarpsharp2 give different result

in original awarpsharp

int bm

Blur modes:

0 : hq 3-pass
1 : fast 3-pass
2 : fast 1-pass (Default)
3 : light blur

in awarpsharp2

int type

Type of blur:

0 : radius 6 blur (some kind of 13x13 average).
1 : radius 2 blur (some kind of 5x5 average), requires around 8x more passes than type=0 for the same effect (will be 2.5x slower), but will produce better quality.

for awarpsharp in awarpsharp2

Original aWarpSharp compatibility:

Mapping from original aWarpSharp parameters:

thresh = thresh*256
blur = blurlevel
type = (bm=0)->1, (bm=2)->0
depth = depth*blurlevel/2
chroma = 0->2, 1->4, 2->3

so the difference is the blur type, since there only 2 type in awarpsharp2

[Ben_Nicholls]

Any idea where "aWarpSharpMT_v1_0_0.7z" comes from? Googled away and can't find if it it is never than the 2016 versions...

[real.finder]

Originally Posted by Ben_Nicholls

Any idea where "aWarpSharpMT_v1_0_0.7z" comes from? Googled away and can't find if it it is never than the 2016 versions...

https://forum.doom9.org/showthread.php?t=175064