How old is "AVISource()" of avisynth?

[shh]

When loading some of my DV-AVIs the number of frames sometimes isn't detected correctly. (0 frames are returned)
VirtualDub loads that file fine, so it seems to be an avisynth-problem.
Also the bugfix from the new VirtualDub 1.4.11 (http://forum.doom9.org/showthread.php?s=&threadid=37095) makes me think the AVISource part of avisynth could be quite old and buggy...
Loading the DV-AVI via DirectShowSource throws an exception, btw.

Is the problem with frame-count detection a known problem?
Is AVISource really quite old and buggy?

Regards,
shh

[Richard Berg]

AviSource used the VDub 1.4.10 codebase + patches, which was certainly not "old" until this week.

[shh]

Hmmm,
so I wonder how VDub 1.4.10 can count the frames correctly.
And, how this can be fixed for future versions of avisynth.

I think this is a "segmented AVI" with frames=0 in the header.
Am I the only having this kind of problems? :confused:

Regards,
shh

[ronnylov]

I have also noticed problems with AviSource in avisynth. I can read the same file with virtualdub without problems. See this thread: http://forum.doom9.org/showthread.php?s=&threadid=36538

But I was using huffyuv segments.

[LigH]

I think some programs rely on the header information, others instead scan the file for its content. VirtualDub, for example, is able to read broken AVI files where the keyframe table was lost (e.g. cancelled downloads). I'm not sure if AviSynth can do that.

I would be interested in the information which e.g. GSpot or abcAVI show you about your "0-frame" AVIs, regarding the frame count.