wierd lines with hauppage wintv?!?!!?!

[bigleen]

I have a hauppage pci wintv card...My pc is Duron 850 , 256mb ram , 30 gb 5600rpm hd, 32mb geforce mx 2 tv-out, on board sound...When i capture at vcd resolutions "352x288 (pal)" it works great...oh yeah im using mjpeg codec at 19 for quality and im using 24bit rgb....but as soon as i want to capture at higher resolutions ( e.g 640 x 480 +) which are interlaced i get this wierd flickerin thing going on...its like strange coloured lined which show through every 1 second or so...does any body know what i could do...btw i an using virtualDub....

[MITSUI_1]

What you're seeing is parts of the capture display that are not getting erased /replaced by the next field/frame because your I/O subsystem is overloaded. If you have the same problem I did, the bursts will occur each time your OS sends a chunk of data to the hard drive. As far as I can tell, the problem has something to do with saturation of the IO bus. That is to say, your system is taking up a certain amount of internal bandwidth sending data from the capture card to the video card and to the main memory if you've got "preview mode" on. When it then sends chunks 'o data to the hard disk, it's saturating the system but not quite to the point where a bunch of frames start dropping. Instead, what you get is a failure by the capture card to flush the old frames properly.

I'd venture a guess you're capturing to your primary hard disk or a slave to that primary device. That's a no go.

Your capture drive should be on the second IDE channel, as the master device.

That change worked for me. Also, be sure you have DMA turned on with your hard drive and that you haven't FSCKD with the disk i/o settings of virtualdub.

As a last ditch effort, switch to YUY2 as the capture format instead of 24bit RGB if that's what you're using, since YUY2 requires less data per second to be zapped across your system bus.

[bigleen]

uve just explained to me the exact problem that i have...wow!!! but i only have one hd which in the master ide.I sometimes use yuy2 but i wasnt please with the quality plus it does the same thing.also dma is definitely one.Is there any other way to stop the i/o subsystem overload. I am also using preview mode because overlay wont capture 640 x 480 plus.Are u suggesting that i put my hd on a different ide slot on my motherboard?

[ptit-cubi]

hey..
im having the same problem.. i just read that topic and i didnt really solved anything YET.. but just one question..
what do u mean with: "Also, be sure you have DMA turned on with your hard drive and that you haven't FSCKD with the disk i/o settings of virtualdub."

I know where to fix the DMA thing.. and im sure its already turned on.. but what is FSCKD? :/

bye & thx

[nick1977]

I'm pretty sure that YUY2 is the native format for the WinTV cards, so using RGB24 is basically a waste of time.

Someone correct me if I'm wrong!

Oh, and I would suggest switching off overlay and preview during capture and see if that helps. If you only have one hard disk, partition it, and then set the swap file for virtual memory to a fixed size (about 1 1/2 times the amount of RAM you have).

Nick

[SHS]

No but it YVU12

[ptit-cubi]

me again..

i recognized something while capping.. ( or trying to do so )
while i capture i see my HDD Led working every 9-10 seconds.. and if i check the captured avi file i see what that working is.. coz in the video are these strange lines.. every 9-10 secs..
im on win2000pro, i have 384mb sdram, a hauppauge WinTVgo pci series, a 30GB hdd ( 2 partitions )... what the hell could be the problem.. friend of mine keeps telling me to install WinXP but that cant be true.. its ridiculous that there is no solution for win2000pro with my hardware!?
or is there someone who would like to help? :/