Doom9's Forum - View Single Post - Using native VirtualDub filters (such as IVTC) in avs scripts

IanB · 6th July 2011, 22:39

No, the built in filters are, built in.

Most are fairly trivial to compile into a free standing .vdf's, Avery tends to write very good modular code, but someone of course must do the extract and compile.

The Avisynth .vdf host does not implement the full VirtualDub API and only supports RGB32 colour space, so some filters can not be used. Also VirtualDub's API has moved on a fair bit since Avisynth's .vdf host was written so many of the newer feature like changing frame-count and other colour spaces are not supported.

Have a good look around usually someone, somewhere has written an Avisynth filter similar to the VirtualDub filter you are trying to use.

6th July 2011, 22:39	#2 \| Link
IanB Avisynth Developer Join Date: Jan 2003 Location: Melbourne, Australia Posts: 3,167	No, the built in filters are, built in. Most are fairly trivial to compile into a free standing .vdf's, Avery tends to write very good modular code, but someone of course must do the extract and compile. The Avisynth .vdf host does not implement the full VirtualDub API and only supports RGB32 colour space, so some filters can not be used. Also VirtualDub's API has moved on a fair bit since Avisynth's .vdf host was written so many of the newer feature like changing frame-count and other colour spaces are not supported. Have a good look around usually someone, somewhere has written an Avisynth filter similar to the VirtualDub filter you are trying to use.