avs+VIDEOINFOHEADER2

[^^-+I4004+-^^]

http://www.microsoft.com/Developer/PRODINFO/directx/dxm/help/ds/ref/structs/structs.htm
(scroll down to VIH2)

so,avi should have all this info in it;
what i want ot know:
if capturing software had written down this into avi header
(i don't know did he or not.... ie. if VDub does this or not..)
then why all the mess with "assume"/field,frame/tff/bff
in avs if that info exists already.......
if it doesn't exist in original captured avi file,forget it,
i'll ask in VD forums as this ain't avs problem....
(this came to me reading the recent thread
>http://forum.doom9.org/showthread.php?s=&threadid=46007
and how more of assuming is included..........avs assumed progressive
in one of shodan's posts.....and it shouldn't.......also some troubles for me to troubleshoot why capturing with "swapped fields" in VD yields problems on plb for some matrox folks....)

so if a definitive way to solve this is possible,let's see
if it can be worked out.....
there's too much assuming if you ask me.....

cheers

Ivo

[Si]

I think the problem is that although the avi file contains field information, the VFW interface can't convey the information to VirtuaDub or Avisynth.

regards
Simon

[^^-+I4004+-^^]

seems to me you're right:
in mentioned thread shodan speaks:
" Since VFW was not designed to handle interlaced material from design, there is no way that we can communicate that a source is interlaced. So DivX (as the converter) cannot know that the YV12 material it's decoding is interlaced. "

so now at least i know what's the problem.....