I'm just doing some very basic testing with AviSynth and VirtualDub lately and came across an issue in the x64 version of VirtualDub2 that seems like it should have a ticket up by now.
Basically I have a simple script just to test my AviSynth environment:
LWLibavVideoSource("C:\test\video.mkv")
It works fine and snappy in the x86 version of VirtualDub2. Seeking frame-by-frame in the x86 and x64 version of VirtualDub2 is also fine. I found the following issues in the x64 version:
1) it takes about 30-60 seconds (sometimes more) to load this simple avs file
2) jumping ahead by clicking on the timeline causes it to hang again for about the same amount of time
The first file i tried was a straight rip from a bluray, uncompressed (12.85 GB), the 2nd file I tried was already encoded down to about 1.5 GB. Both behaved the same.
Here's my system specs:
Windows 10 Pro 1909
Processor: Intel Core i7-4810MQ @ 2.8GHz
Cache: Level 3 6MB
Motherboard: MS-1763
Chipset: Intel Haswell Rev 06
Southbridge: Intel HM87 Rev C2
RAM: 16GB DDR3 PC3-12800
Is this a known issue or expected behavior? Does this happen on anyone elses' machine?
Anonymous
Hi, I think this behavior is caused by lwlibav AviSynth plugin alone. In any case vd here is just a shell which literally just displays picture.
Some ideas:
ask AviSynth devs (on doom9 forums?)
try ffms2 plugin instead
check if your installation of AviSynth is correct (both using same version of core and plugins)