capture with vdub doesnt work proper

[NoIdea]

hello, i capture with a gainward gf4 tv-in and somehow the picture in vdub is pretty bad. i get interlace lines and the picture is pixeled and not fluent. of course when i start capturing i get lotsa framedrops.
with the card came an app named wincoder and with that the picture is good without any visible interlacing or distortions. i can even capture with it and it looks ok. it just doesnt allow to capture uncompressed or wit huffyuv and also misses vdubs filters.
i use nvidia wdm driver 1.11, det 28.32, vdub1.4.10 and my system is an 1,3 ghz athlon c with 384mb ram so should be enough for capture.
tx,
noidea

[avih]

if u use wdm drivers (especially if it's btwincap) then the oeverlay resolution is not correct. it just takes something like 320x200 picture and streches it to the required size. note however that it DOES NOT affect the capture, which is in your selected resolution.

to see the real image you're gonna record use 'preview' instead of overlay.

interlaced artifacts are natural. read more stuff from the capture forum if u don't understand why u get interlacing artifacts

avi.

[NoIdea]

hi, yea when chosing preview i cant see any interlacing in the file when i view it ;)
but now the picture is positioned wrong, i only get the upper 2/3rd of the picture and a big black bar above. its the same on all resolutions.
theres also still a flickering bar in all colors above the picture and its also in the video file.
i noticed that the framedrops are exact half of all recorded frames and the recorded file doesnt look that bad.
noidea

[Ookami]

Like avih just said... Just take a read on the Capture forum.

Cheers,

Ookie.

[avih]

another suggestion for the framedrops (half of them).

you should set the framerate for capture as 25 (for pal) or 30 (ntsc) (could be also 29.97 for ntsc, but i don't have any experience with that).

when u capture, the capture card gives you 2 fields in the same frame. so there actually 2 pictures 'interleaved' (=interlaced) in each captured frame. that's why u capture @25 frames a sec, but u actually get 50 fields/sec.