PDA

View Full Version : Problems opening DV-captured AVI in AviSynth


adrenochrome
23rd October 2002, 10:51
Hi,

In an attempt to transfer the content from my mini-dv cassete to a CD, I got stuck when I tried to perform some additional processing of a captured avi file in my AviSynth script. When I try to open .avs file from VirtualDub, I get the 'unhandled exception' error message on the following (the only one) line in my script:

DirectShowSource("c:\mydir\myfile.avi")

The file opens correctly in MS Media Player.

The avi file itself is captured using MS MovieMaker (I guess it means using MS DV codec). I also tried capture in Pinnacle Studio 8.1 (using both default and Mainconcept DV codecs), but with the same result.

The environment: WinXP SP1, AviSynth 2.06, VirtualDub 1.4.10 (the camera is Sony DCR-PC8). The captured avi file is rather small (cca 100 MB).

Does anyone have an idea what could be wrong? I thought that 'DirectShowSource' would open any file that MS Media Player can open, since it relies upon the same functionality. Or, perhaps I need to use specific DV codec in a specific way, and not just 'no-brain' MS MovieMaker capture?

Thanks in advance!

Wilbert
23rd October 2002, 11:51
Welcome to the forum,

1) Is it a type-1 or a type-2 dv avi? In the latter case you can try to open it with AviSOurce.

2) Try using an older version (say v2.04 or v1.07) of AviSynth.

adrenochrome
23rd October 2002, 14:28
Originally posted by Wilbert
Welcome to the forum,

1) Is it a type-1 or a type-2 dv avi? In the latter case you can try to open it with AviSOurce.

2) Try using an older version (say v2.04 or v1.07) of AviSynth.


Thanks,

I guess (can't try at the moment, unfortunately) it must be type-1 then, since I'm unable to open avi file directly from VirtualDub which uses VFW interface. For the same reasons AviSource() will probably fail (?).

I'll try to use an older version, thanks for help.

Wilbert
23rd October 2002, 15:16
Maybe a stupid question. Did you install a DV codec (like panasonic)? Information can be found on the faq in the DV forum.

adrenochrome
23rd October 2002, 15:34
Originally posted by Wilbert
Maybe a stupid question. Did you install a DV codec (like panasonic)? Information can be found on the faq in the DV forum.

Not that I'm aware of, though it might have been installed as a part of some other package (Nimo codec pack or similar).

Could it interfere with something if installed, or it is just the opposite -- I might need it? Installing/removing it is not a problem.

Wilbert
23rd October 2002, 16:01
You will need it. If you open VirtualDub and select video compression you will find a DV codec if you installed one (I guess you will find MainConcept codec in that list). Maybe you can try the panasonic DV encoder (see link in the DV faq).

Suzahara
24th October 2002, 01:11
For directshowsource() you need to include the framerate of the video since otherwise it won't know and it'll just get mad and error.

adrenochrome
24th October 2002, 19:47
Originally posted by Wilbert
Is it a type-1 or a type-2 dv avi? In the latter case you can try to open it with AviSOurce.

I have finally found the time to check this, and it works! I still don't get it (how & why), but who cares :D

Thanks once again!

bb
25th October 2002, 08:14
Because with AviSource your VfW codec will be used, whereas DirectShowSource (as the name implies) needs a DirectShow filter (.ax filename extension).

bb

adrenochrome
25th October 2002, 09:27
Because with AviSource your VfW codec will be used, whereas DirectShowSource (as the name implies) needs a DirectShow filter (.ax filename extension).

OK, in that case it must be Mainconcept DV codec that actually made this possible. It was not possible to open captured avi file directly in VirtualDub until I installed that codec.

That could explain why AviSource works, but still leaves the question why DirectShowSource doesn't.

I'll probably try to use a debug build of AviSynth, hoping that I'll be able to trace back to the place where the exception is thrown. Perhaps that would tell me more about what kind of exception that is and what is the problem actually.