![]() You'll see it whenever you capture with a height more than 240 lines (NTSC) or 288 lines (PAL). That's interlacing - what you're seeing is two fields, taken at slightly different times, and combined together to form a single frame. I see a lot of thin lines in my image, like a comb. If it's only a few lines at the bottom, it's likely VHS head switching noise. It looks sort of like the picture, but distorted. I see a greyish, wavering line at the bottom of my capture. If you are using RGB24 for your raw capture format, switch to YUY2 to drop your raw datarate by 33% (see below), which may be enough to lower PCI bus load to workable levels. For instance, Pinnacle has a PCI adjustment utility for some of their cards. (The result is similar that of making the red lights appear every ten seconds at a four-way intersection.) In that case, try installing the Microsoft drivers instead.Īlso, check the websites for the hardware manufacturers to see if they have utilities which may help. As for the Live!, the Creative driver is known to cause problems by lowering the latency timer of the PCI bus. In the former case, try upgrading your VIA 4-in-1 drivers first, and if that is not sufficient, check for a motherboard BIOS update that specifically addresses your problem. This problem is reported more frequently on motherboards that have a VIA chipset, or in systems that have a SoundBlaster Live! sound card. No one has a rock-solid answer for why these problems occur, but it appears to be caused by contention on the PCI bus, which then prevents the sound card and video capture devices from emptying their buffers in time. Occasionally, I see thin horizontal strips in the captured video that looks like they came from the last frame? (Note: If you are using an external source with I get sound, but it has cracks and pops in it. It can be used to force the audio pass-through on for those cards. Voice chat programs are notorious for automatically switching inputs for you, and some video capture drivers are known to reset volume levels as well.įinally, if you have a Hauppauge WinTV, check for an AUDIOSEL.EXE application on your hard disk or driver CD. Make sure Line-in, Aux, or whatever input you are using is selected. Next, bring up Volume Control ( sndvol32.exe), go up to the menu and choose Properties, then switch to Recording controls. Most video capture cards don't have on-board sound capture and instead use your sound card, so if you don't connect the cable from the capture board to the sound input, you won't get any sound. I get no sound.įirst, check that you aren't missing the pass-through. I don't have any DV specs, so I can't make VirtualDub extract the audio. Video for Windows only captures audio through a sound device with DV, the audio is interleaved with the video itself. I can capture DV through VirtualDub, but I get the audio out of my sound card instead. The wrapper will show up as "Microsoft WDM Image Capture (Win32)." If it works for you, great. Also, ATI appears to be shipping their current devices with a WDM (Windows Driver Model) driver only this can be used indirectly by VirtualDub through a Microsoft wrapper, but it is crippled in functionality and it also appears that the wrapper is buggy. Most Firewire (DV) devices do not provide a VFW driver, and thus cannot be used by VirtualDub at all. VirtualDub needs a Video for Windows capture driver to capture. VirtualDub says I don't have a capture device, but I know I have one. ![]() You will take a sizeable hit with a 24-bit or 32-bit desktop if you have Preview on. ![]() Note that these are with a 16-bit desktop.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |