Here is a package of plugins for QTGMC using the
latest Avisynth 2.6 interface. They may provide better multi-threading stability:
QTGMC 32-bit Plugins [Vit-2.6] (mirror1 | mirror2)
Thanks to SubJunk for the filehost-free mirror!
These plugins have been updated to the latest 2.6 interface:
-
MVTools, MaskTools, NNEDI3, EEDI3, RemoveGrainSSE2, RepairSSE2, dfttest, FFT3DFilter, AddGrainC, VerticalCleanerSSE2, TDeint
The dlls are named as normal (for now).
These plugins are provided in their original form (not updated because they have no source code; or are legacy; or use the C interface).:
- Yadif, SSE2Tools, NNEDI2, EEDI2, NNEDI
The updated plugins will only work with versions of Avisynth 2.6 that support the new interface. Currently I believe that's only SEt's latest Avisynth 2.6MT build.
The new interface removes some code that was embedded in every plugin that could cause multi-threading problems. So these plugins may be more stable, although many multi-threading issues are memory-related these days. It's fine to use some updated plugins and some older ones. But the more new versions you get, the better for MT stability.
This package is provided for test purposes only, it's not "official" yet. Partly because these plugins are no longer "modded", they're just up to date, and I hope that some of the original authors will provide "official" builds eventually. Also there's a dll versioning problem now - we have 2.5 plugins, 2.6-old-interface plugins, modded versions of those, and 2.6-new-interface plugins. Added to that there are cretindesalpes' more recent versions of MVTools and dfttest...
In the longer term we need two just versions of each, a 2.5 compatible and a 2.6 new interface. I'm hoping cretindesalpes will provide 2.6 new interface versions resolving that issue. Then I'll provide just two packs, 2.5 & 2.6, and expect all MT users to switch to 2.6 and SEt's latest. I'm open to opinion about whether the different versions of the plugins should be renamed or not (as masktools does it). Seems to me there are potential problems either way. In any case I'm gonna wait a little before "officially" releasing these things...