what makes the virtualdub integration so special

[jordanh]

I have spent some time in order to find out what its about, but i have to give up now.
What makes avisynt-virtualdub combination so "native"?
It seems that vdub just uses the vfw/directshow (isnt it actually pure directshow?) interface of avisynth.

Basically i only found a few words about special error handling (bring the message in a popup instead of the video) within virtualdub source code and on the other hand, a lot of code within avisynth that looks like support usage of virtualdub filters within avisynth environment.

Do they really only invoke the Directshow Interface and pull frames from it?

What about the other programs on the market that claim to have native avisynth support, does any of them invoke the scritp on its own and call getframe?

[Myrsloik]

The answer is: nothing. The only thing vdub does differently is to use the normal windows avi parser and query errors through a special interface.

If all you need is to open a script and get frames you may as well do it through vfw.