DV-AVI related Vdub/Vdubmod crashes

[kaitsuburi]

I recently rebuilt my laptop from scratch to use it for analog captures and I've run into a problem following my usual capture routine.

I only get this problem with Avisynth 2.5x (2.0x works fine) so I assumed it would be relevant to post here. I also believe this post relates to falcon_b's recent problem:

http://forum.doom9.org/showthread.php?s=&postid=320799

(@Mods: please move thread elsewhere if necessary :confused: )

My problem has to do with Vdub/Vdubmod crashing (silently, i.e. no error message) when I try to 1) close an avs (2.5) script or 2) start a job (avs 2.5) queued in Vdub/Vdubmod joblist (F4). Encoding works fine otherwise (1-pass, unqueued).

My capture was done through a Canopus ADVC-100 (NTSC, full resolution) in ScenalyzerLive (v.2.0) into "Canopus compatible DV" format. The resulting AVI files (1GB each) have a "CDVC" FOURCC and 1-pass test encodes to XviD using VirtualDubMod were beautiful, no chroma upsampling bug even though I use the Canopus DV codec. I tried changing the FOURCC, using a different DV codec, or loading the AVI through DirectShowSource(), but the problem presisted.

Here's the exact script I used:

AviSource("...\scene0001.avi",false)
telecide(guide=1).decimate(5)
crop(4,0,-8,-8)
cnr2().fluxsmooth()
simpleresize(640,464)
unfilter(-3,-3)
limiter()

When the .avs file is opened in Vdub/Vdubmod "File Information" reports "FourCC: [YUV2] unknown"; "Decompressor: YUV 4:2:2 (YUV2)". With info() at the end of the script I get

Frame: 0
ColorSpace: YUV2
Width: 640 pixels, Height: 464 pixels.
Frames per second: 23.9760
FieldBased Video: NO
Parity: Parity unknown
Video Pitch: 1280 bytes.
Has Audio: NO
Audio Channels: 0
Sample Type: NONE
Samples Per Second: 0

If I put info() right after AVISource(...) the only thing that changes is the resolution (720x480), fps (29.9700) and video pitch (1440 bytes). I also tried with a script containing only AviSource(), but same problem. Leaving the sound in does not help, either.

My OS is Win2k-SP3 with all pre-SP4 hotfixes installed. My hardware is a Toshiba Laptop, P3-1.2 with 256MB RAM and 27GB HDD. DirectX 8.1 is installed. I have only installed the latest versions of Xvid (Koepi's build) and DivX codecs as well as the Canopus DV codec I've always been using. I tried all avaiable versions of VirtualDub and VirtualDubMod, all builds of Avisynth 2.5 I could get my hands on, including 2.5.2 that was just released, as well as all possible combinations thereof, but I had the exact same problem (I've been frustrating myself for over 2 hours now). I only have the filters I use in my script in Avisynth's plugin directory (I read the Avisynth FAQ -- I haven't touched the Warpsharp/LoadPluginEx package). I also tried emptying the plugin directory and loading through LoadPlugin(..).

With the **exact** same setup above, only installing the latest Avisynth 2.08 in place of Avisynth 2.5x the problem disappears. Also, there is no problem if I load an AVI file with a different FOURCC (I tried "DIV3" and "XVID").

Could this problem be Avisynth 2.5x-related? I searched for similar posts but, like falcon_b's post, others' problems seemed to be connected to LoadPluginEx.dll which I don't even have on my HDD. Maybe I've blatantly missed something; please nudge me in the right direction :confused:

-kaitsuburi


PS. I wonder if this is what Defiler was referring to in this post:
Originally posted by Defiler
Can I change my vote to "Fix the silent crash when refreshing or closing an AVS file in VirtualDubMod"? :D
It's done that to me like 60 times today. Heh.
in the first sticky in this forum:

http://forum.doom9.org/showthread.php?s=&threadid=53427

[sh0dan]

Could you post a small fraction of the file, that reproduces this error?

The vdubmod crash seems to be a vdubmod issue, since AviSynth doesn't appear to be involved in the crash. I have not yet had the time to do a debug vdubmod compile to actually see where the crash happends.

[kaitsuburi]

My web hosting situation is rather pathetic right now :o I apologize.

I have just uploaded a 4800K avi file (a mere 40 frames) to a small space at Yahoo Groups located here:

http://groups.yahoo.com/group/kaitsuburi/

Please let me know if this works; if not, I will try to find alternative hosting.

On a separate note, I tried rebooting and curiously enough, the first time I start vdub or vdubmod (the problem persists with both, btw) closing the .avs file or starting from the joblist works fine. All subsequent attempts (without rebooting again), however, I get the same silent crash described above, no exceptions. Again, avisynth 2.0x seems to be working fine.

Thanks for your help! :)

-kaitsuburi

ps. I will be away from Monday until Thursday this week and thus my follow-up posts may be delayed.

[kaitsuburi]

Just one more piece of information: opening the raw DV AVI (the little excerpt I uploaded) directly in Vdub/Vdubmod gives the following under File Information:
Video Stream
Frame size, fps: 720x480, 29.970fps
#of frames: 39
FOURCC code: CDVC
Decompressor: Canopus Software DV Codec
Number of key frames: 39
Min/avg/max/total key frame size: 120000/120000/120000 (4571K)
Min/avg/max/total delta frame size: (no delta frames)

Audio Stream
Sampling rate: 48000Hz
Channels: 2
Sample precision: 16-bit
Audio tag: Tag:0x0001, Not decodable PCM
Compression: PCM (Uncompressed)
Preload skew: 24000 blocks/1630 samples (0.50s)
# of frames: 26
Min/avg/max/total frame size: 96/9609/96000 (244K)

Thanks,

-kaitsuburi

[Wilbert]

I assume that you don't have loadexplugin.dll or warpsharp.dll in your autoloading plugin dir of AviSynth?

[kaitsuburi]

Originally posted by Wilbert
I assume that you don't have loadexplugin.dll or warpsharp.dll in your autoloading plugin dir of AviSynth?

Nope, I don't even have those two on my hard drive. I read about that problem on avisynth.org so I don't think it's loadpluginex.dll-related.

I am back home, so I will do some more testing to try and isolate where this problem is coming from. Luckily I've gotten into a habit of taking a "clean" Ghost image right after a fresh OS/hotfix/driver install...

Cheers,

-kaitsuburi