Avisynth 2.04 crashes

[Radioman]

I have a "beautiful" small (3.8mb) sample which version 2.04 crashes with the "failed to decompress frame" crash (error -372) but not version 2.03.

The source is a captured interlaced PAL tv-koncert, compressed with Picvideo mjpeg and it doesn't matter which script i use. Even just the line:
AVISource("f:\lennox.avi") fails.

I first had the error-frame in one of several segmented avi-files and tracked it down and did a direct streamcopy with VD of the critical part. so also the small *.avi file with the simple line above fails.

Is there any interrest from the coders ? Where to upload in that case ?

Almost forgot: I'm on win98se with a PIII 500.

[dividee]

@radioman
If you can send such sized emails, I think I can receive them (my_nick@skynet DOT be, replace my_nick by my nick). Thank you for trying to help us.

[sh0dan]

@radioman: Have you tried the latest CVS binary? (See this thread (http://forum.doom9.org/showthread.php?s=&threadid=31924))

[dividee]

Maybe we should turn off all error reporting in AVISource, and just return the previous frame in case anything goes wrong. My previous fix was only for dropped frames, not for defective ones, and I think error -100 is about defective frames.

[Radioman]

@Sh0dan

I havent tried that late 2.05 version. I will, when I come home from work. I'll test and let you all know in about 5 hours.

[sh0dan]

Originally posted by dividee
Maybe we should turn off all error reporting in AVISource, and just return the previous frame in case anything goes wrong. My previous fix was only for dropped frames, not for defective ones, and I think error -100 is about defective frames.

Seems like a reasonable thing to do - or simply adding it as an optional parameter to AviSource(). Of course you have to throw an error, if it's the first frame, but otherwise it would be a nice thing! Would you take that one? I'll then investigate hakko's exit crash, when I get his test-clip.

[WarpEnterprises]

Pls remember that the "exit crash" (if it is really the same as mine and I quite think so) seems directly coupled to the matrox codec (e.g. the codec setup cannot be opened after the crash).
So if that's true you won't get a crash on your system or (more likely) you won't be able to open hakkos mjpg as it seems to use some semi-proprietary structure (the VD "use VD routines to open" don't work!) and a fourcc "DMB1".

Of course there can be a second independent error when encountering D-frames.

Hope really you get the error !!

[sh0dan]

Originally posted by WarpEnterprises

Hope really you get the error !!

See the other (hopefully fixed) thread.

[Radioman]

@Sh0dan and Dividee

Yes, that preliminary 2.05 version Sh0dan linked me to managed to get trough the -372 passage. Very well done :) I don't have to send any of you the avi -file to struggle with.
Oh, and don't forget to change the version number before that version will be released. It shows 2.04 now.

There is really something happening with avisynth v.2 and I wonder if someone could tell me or link me to some info on what the major highlights is compared with f.ex. version 1.06 ?

[sh0dan]

Look at the changelist. You can always browse the newest one from here. (http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/avisynth2/avisynth/docs/index.html)

Other major changes (before 2.02)

- Layer added.
- MergeChroma / MergeLuma added.
- Tweak added.

Argh - can't remember anymore. RICHARD! ;)