Plugins

With these functions you can add external filters (DLLs) to the AviSynth script environment.

Allow RGB24, RGB48, RGB64 besides RGB32
RGBP/RGBAP 8 bit: since this format is not supported directly by Virtualdub filters, LoadVirtualdubPlugin automatically converts 8 bit Planar RGB to/from RGB24, RGBAP to/from RGB32 (lossless)
RGB48/RGBP16/RGBAP16: since this format is not supported directly by Virtualdub filters, LoadVirtualdubPlugin automatically converts them to/from RGB64 (lossless)
YUV(A) 8 bits: YV12, YV16, YV24, YV411, YUVA420P8, YUVA422P8, YUVA444P8
YUV(A) 10-16 bits (properly set "ref_x" maximum levels, no autoconvert)

Supports prefetchProc2 callback (API >= V14 and prefetchProc2 is defined) for multiple input frames from one input clip
PrefetchFrameDirect and PrefetchFrame are supported. PrefetchFrameSymbolic not supported
Supports prefetchProc callback (API >= V12 and prefetchProc is defined)
Supports when filter changes frame count of the output clip
Supports specifying some colorspace properties. See rangehint

Usage example (ColorTools) – see here (doom9).
See FAQ using Virtualdub plugins for more information.

LoadVFAPIPlugin

Loads VFAPI plugins (eg, QTReader, TMPGEnc). These are distributed as special DLLs with the file extension .VFP.

LoadVFAPIPlugin (string filename, string filtername)

string filename =

The path of the .VFP file.

string filtername =

The name to be given to the plugin function after loading in AviSynth.

Plugin Autoload and Name Precedence

It is possible to put all plugins and script files with user-defined functions or (global) variables in an autoload directory, from which all files with the extension .AVSI and .DLL are loaded at startup, then unloaded and reloaded dynamically as the script needs them.

.AVSI scripts in this directory should only contain function definitions and global variables; they should not have a main processing section (else strange errors may occur). It also is not recommended to put other files in that directory.

The directory is stored in the registry. You can use double-clicking a .REG-file with the following lines to set the path (of course inserting your actual path):

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Avisynth]
"plugindir2_5"="c:\\program files\\avisynth 2.5\\plugins"

The order in which function names take precedence is as follows:

User-defined function (always have the highest priority)
Plugin (external) function (higher priority than built-in)
Built-in (internal) function

Inside those groups the function loaded last takes precedence; there is no error in a namespace conflict.
It follows that there is no harm in loading the same plugin more than once.^{[dubious – discuss]}

Plugin Autoload and Conflicting Function Names

A problem that may arise when multiple plugins have functions with the same name. You won't know which function will be called in your script, as this will depend on loading order. To call a particular function in this situation, AviSynth's DLLName_function() feature automatically creates prefix aliases; so for example, foo.dll's bar() function may be called as foo_bar(). This works both for auto-loaded plugins and for plugins loaded with LoadPlugin.

Suppose you have the plugins mpeg2dec.dll and mpeg2dec3.dll in your autoload directory; if you call

mpeg2source("F:\From_hell\from_hell.d2v")

you won't know which plugin will be used in your script, as both have an mpeg2source function.

To load the file with mpeg2dec.dll (which outputs YUY2), call

mpeg2dec_mpeg2source("F:\From_hell\from_hell.d2v")

or to load the file with mpeg2dec3.dll (which outputs YV12), call

mpeg2dec3_mpeg2source("F:\From_hell\from_hell.d2v")

Back to AviSynth Syntax.

Plugins

Contents

LoadPlugin

LoadCPlugin

LoadVirtualDubPlugin

LoadVFAPIPlugin

Plugin Autoload and Name Precedence

Plugin Autoload and Conflicting Function Names

Views

Personal tools

Navigation

community

in other languages

Search

Tools