AviSynth 2.6 - safe for work?

[LigH]

There are already tools which require AviSynth 2.6, so I wonder:

Is AviSynth 2.6 already in a state I can trust? Is it "mostly" compatible with usual AviSynth 2.5 plugins, or are there any known incompatibilities (are specific 2.6 plugins just advanced in features)? And finally - is there any more recent recommendable version than Alpha 2 from SF (I mean ... 2009 ...)?

[Chikuzen]

If you are not a complete newbie, you will be able to use 2.6.0alpha almost without trouble.

Some functions have not sufficed for 2.6.0 yet.
for example...
When colorspace of clip is YV16, you can't convert it to RGB directly.
If you want to convert YV16 to RGB, you should convert it to YUY2 once.
SDKs and Docs are also incomplete.
Thus I think that official release will be the considerable future :(

However, you can use all features and plugins that exists in 2.5.8 on present alpha release.
and some bugs exists in 2.5.8 was already removed.
I have never experienced uncertain cause crash and compatibility issue during a half year.
I think that 2.6.0alpha is safer than AvisynthMT/64.
(of course, I didn't try all plugins...)

and, 2.6.0alpha is much faster than 2.5.8.
This is a result of the benchmark that I did several months ago.
http://pastebin.com/LBsbY6qK
(http://pastebin.com/LBsbY6qK)
If you want to get more resent build than 090927, check what JEEB (http://forum.doom9.org/showpost.php?p=1474204&postcount=134) or XhmikosR (http://xhmikosr.1f0.de/index.php?folder=YXZpc3ludGg=) distribute.

[LigH]

I believe I will have a look for AviSynth 2.6 MT for testing only, but possibly prefer the generic one.

Most projects will be based on 2.5 features only, even though the different color modes sound interesting.

Thank you for your reply.

[GrofLuigi]

Using Avisynth 2,6 from SF since it appeared, very light usage with simple scripts (effectively same usage as with 2,58), and had no problem ever (excluding crashes with Dust :)).

GL

[LigH]

A question to multi-threading: If I understood correctly, AviSynth 2.6 supports the MT plugin (currently version 0.7) without exchanging the main DLL?

[SubJunk]

If you want to get more resent build than 090927, check what JEEB (http://forum.doom9.org/showpost.php?p=1474204&postcount=134) or XhmikosR (http://xhmikosr.1f0.de/index.php?folder=YXZpc3ludGg=) distribute.Personally I would stay away from XhmikosR's builds, every time I benchmark them they are slower than others. Results may vary with different computers though, AviSynth is mysterious like that :p
I use SET's build since I find that to be the fastest and most stable.

A question to multi-threading: If I understood correctly, AviSynth 2.6 supports the MT plugin (currently version 0.7) without exchanging the main DLL?Yes, you don't have to use mt.dll with 2.6

[LigH]

SEt's builds (http://forum.doom9.org/showthread.php?p=1312666#post1312666) ... not updated since September 2009? Well, I will have to test them on my own...

[Gavino]

A question to multi-threading: If I understood correctly, AviSynth 2.6 supports the MT plugin (currently version 0.7) without exchanging the main DLL?
Vanilla Avisynth 2.6 (ie 2.6 alpha) does not support multithreading at all, neither via SetMTMode nor via the MT plugin/function. The SetMTMode command is not recognised, and using the MT() function produces a crash (access violation).
Yes, you don't have to use mt.dll with 2.6
Wasn't the question about avisynth.dll, not mt.dll? You never had to use mt.dll (unless of course you want to use the MT function), even on 2.58MT. SetMTMode does not require mt.dll, but mt.dll requires SetMTMode, which requires a modified avisynth.dll.

[SubJunk]

SEt's builds (http://forum.doom9.org/showthread.php?p=1312666#post1312666) ... not updated since September 2009? Well, I will have to test them on my own...Yes that's them, but AFAIK XhmikosR's builds also haven't changed the code since September 2009, they are just recompiles of that same code, at least that is what I have read.

Wasn't the question about avisynth.dll, not mt.dll?Yes, I think I misread the question :)

[LigH]

This way you are adding just more confusion ... so which 2.6 build supports MT?
__

Obviously only SEt's build, according to a string search in the DLLs.

[JEEB]

Pretty much, since MT was removed from the avs2.6 trunk as it was IIRC deemed that multithreading should be done quite differently (there is a separate TSP_MT branch still on the avisynth repo, but that one hasn't been updated for quite the while).

[jmac698]

See Known Issues
http://avisynth.org/mediawiki/Known_Issues
If you are aware of any other crashes, let me know.

[Wilbert]

@jmac698, all those issues are solved in 2.6 csv.

[jmac698]

I guess someone should update the wiki then :)

[Wilbert]

I will update it a bit.

[LigH]

A few links mainly for myself to remember...
__

Current installer (SEt's source of AviSynth-MT 2.58 r22 compiled by XhmikosR using MSVC 2010): http://code.google.com/p/avisynth-mt/ — deprecated

AviSynth-MT 2.58, 64-bit: http://forum.doom9.org/showthread.php?t=152800 (compiled by JoshyD, incl. a few 64-bit plugins)

AviSynth-MT 2.6 by SEt: http://forum.doom9.org/showthread.php?t=148782 (archiving different versions on MediaFire) to replace a v2.60 installation, currently: AVS 2.6.0 Alpha 3 [110525] (http://sourceforge.net/projects/avisynth2/files/AviSynth_Alpha_Releases/)

[SEt]

Do not use 2.58 MT it's seriously outdated and less stable compared to 2.6 MT.

Personally, I think that 2.58 MT 64-bit should not have my name in it: I did no direct contribution to that version – it's pure JoshyD's work.

[StainlessS]

v2.6(a3) is considerably more stable than 2.58 and has been for some time.
There is the occasional hiccup but at least you know that they will at some time be fixed.
Been using 2.6 since about a1, only use 2.58 on occasion to test compatibility.
I avoid v2.6 plugins as they tend to break old scripts.

Recommend 2.6a3+, but see known 2.6a3 issues.

[LigH]

@ StainlessS:

Remember, the point of interest in this thread is the multi-threaded variant. I see that it is still regularly being updated; for the generic installer, there was no newer release for almost one and a half year now.

[StainlessS]

Sorry, I was just addressing the leading post which made no mention of MT, I have never used it.

no newer release for almost one and a half year now

Makes you think, "It's gotta be soon".
EDIT: Oh lordy lordy, let Mr B make it so.

[LigH]

:o Uh, you are right, I didn't even start with it...