Poll: Avisynth Version Usage 2017 (what do you usually use)

[Andouille]

That's pretty vague...
High bit depth ? Don't really care.
New plugins ? Didn't see interesting ones since a long time.
The only thing that I have to worry is my RAM usage being on 32bit XP.
All work fine here.

[rjd0309]

Publicly named, but not shamed.

If there were a clean upgrade path to 2.6.0, then fine. But I'm reluctant to navigate the minefield of different versions and dependencies.

[tebasuna51]

Maybe is good resume some reasons posted here:

1) Seems XP users are more comfortable with Avs 2.6 standard.
I can't refuse that, but they know than there are improvements than not support XP anymore, if remain with XP is their respectable choice (mainly by hardware limits).

2) Other reasons are derived by plugins versions.
When a user need a complex script, and found the exact plugins needed than work fine, is dificult try other Avs option than, maybe, need other plugin pack or don't work at all.

But, like a non-expert AviSynth user (at least in video management, the audio management don't need complex scripts) I want know the differences of use Avs standard and Avs+, not related with OS or plugins.

- Avs standard can do anything still not implemented in Avs+?
There are speed differences?

- Avs MT mode differences with Avs+ MT?

Thanks.

[StainlessS]

AVS 2.6 Standard can be used as a better 2.58, there is no minefield if just opting for 2.6 standard.
Just about any script [EDIT: Or plugin] will run as it did on 2.58, but perhaps better, faster and with some bugs fixed.
There is little reason I can think of to stay with 2.58, and I'm a real Stick-In-the-Mud.

EDIT: I'm on XP32 with Dual Core 2.4 GHz Core Duo. + several P4 machines.

EDIT: "Named and Shamed", I was just being naughty, it caused no fatalities I hope.

EDIT: The only significant script that I can think of that will fail under v2.6 is InPaintFunc().
InPaintFunc relies upon a Levels bug that was fixed in 2.6, but that can be corrected to behave like bugged v2.58
with a call to Masktools prior to Levels.
EDIT: Here bug noted, and bug fix for InPaintFunc():- https://forum.doom9.org/showthread.php?t=172208&highlight=InpaintFunc

[Andouille]

EDIT: "Named and Shamed", I was just being naughty, it caused no fatalities I hope.


I will just burn the entire forum for this :devil:

To be serious, I see no reason to update when all work as I want.
The MT version I have never crashed even with complex functions and is fast enough for me.
XP looks like I want and does what I want.

[StainlessS]

The MT version I have never crashed even with complex functions and is fast enough for me.

I did not give v2.5.8 MT option, sorry bout dat.

XP looks like I want and does what I want.
Cant argue with that, I'm of same view.

EDIT: At least there were no pre 2.58 votes, coupla years back there was.

[tebasuna51]

The MT version I have never crashed even with complex functions and is fast enough for me.
I was using 2.58 MT like you for MDegrainX (mvtools2.dll) with MT.dll without problems.

I tried 2.60 MT (without support for MT.dll) and I have some problems (maybe my fault).

But I changed to Avs+ 64 and new plugins versions (only a few months ago) without problems and fast MT encodes.

XP looks like I want and does what I want.
Of course is a respectable choice.

But I want test some improvements, not only for AviSynth, and XP don't work (I have a VirtualBox with XP for some old soft).

I changed only to W7 and I hope remain without change some time.

[Andouille]

I don't use MT (). It splices frames and you cleary see this when denoising or even using qtgmc.
No I simply use setmtmode().