Video Capture Picture Breakup

Blackout wrote on 5/28/2002, 4:24 AM
Hi,

I am using Win XP and trying to capture from a Canopus ADVC-100 via firewire. Using an AMD XP1700 and Asus A7v266-e MB, 512 Meg. When i go into capture preview mode on 3.0a i see the sound and picture ok for about 15-20 seconds or so. Then slowly the picture and sound starts to break up, the picture starts to "stick" and the sound has small breaks. A Capture has dropped frames.

If i want to induce this problem even faster all i have to do is load something else, say even windows explorer, and swap to it and back to Vegas, then the capture preview mode starts to break up.

Im not running any antivirus, or any firewall etc software, all thats on the pc is XP fresh and Vegas. Is this an XP problem or a bug?

Many thanks,
darren.



Comments

JumboTech wrote on 5/28/2002, 8:55 AM
Do you have DMA enabled for your HD?

Al
stepfour wrote on 5/28/2002, 9:29 AM
Did you shut down the macrovision in your Canopus ADVC-100? I'm not sure if it's as much a problem with firewire in on that unit but a lot of users reported that that unit was detecting macrovision when they tried to use it to convert VHS tapes to digital. It couldn't hurt to shut it off.

You also also might have some system or IRQ conflicts. The way your problem presents itself sounds like IRQ issues but depending on your setup could be something else. I don't know anything about XP, though.

What's the source of your video? Where does your ADVC-100 fit in? Since you're using it, I assume you're using an analog source to to into the ADVC-100 and then coming out on the firewire and into a IEEE-1394 interface card. In that setup the Canopus box could very well be detecting macrovision.
Blackout wrote on 5/28/2002, 9:45 PM
Hi,

thanks for posting, this issue occurs for even a straight picture from free-to-air TV thru the ADVC-100. Turning macrovision off (the 15 second thing) does not stop this problem, indeed it was the first thing i tried.

Its not an irq problem, changing the board slots around which forces them to use new irqs makes no difference.

Is it possible that something is polling my cpu in XP that is clashing with Vegas Capture?
jetdv wrote on 5/29/2002, 1:14 PM
I have test captured using Scenalyzer on a PIII 750MHz with Win2K and the audio and video preview both work fine and in real time. Using the same program on a PIV 2.4GHz with WinXP, the display is frozen more than it is moving and the audio also comes in spurts. However, the captured video on both machines is fine. I believe this is probably a symptom of WinXP. Were the captured files OK?
bakerja wrote on 5/29/2002, 2:47 PM
I read on another post that unplugging your network connection during captures stops some problems. I was getting dropped frames and now get no dropped frames with the network cable unplugged. Windows must be polling for network connections when it is connected and when it has no network, it quits. It worked for me.

JAB
seeker wrote on 5/29/2002, 11:53 PM
Blackout,

> Is it possible that something is polling my cpu in XP that is clashing with Vegas Capture? <

Yes. I still use Win98SE, so am not familiar with XP, but does Ctrl-Alt-Delete still bring up a Close Program dialog? If so, you can get an idea of how many tasks are competing with Vegas during the capture. You may be surprised. In Win98SE it is good practice to close nearly all tasks, except of course Explorer and Systray, before starting Vegas. Frequently that can be tedious because there are so many tasks that need to be closed. There is a special utility to help automate task pruning called "EndItAll version 2", which came out before WinXP was released, but apparently it will work under WinXP. You can verify that at (incidentally, Neil J. Rubenking is the author of EndItAll):

http://discuss.pcmag.com/n/main.asp?webtag=pcmag&nav=messages&msg=4605.2

http://discuss.pcmag.com/pcmag/messages/?msg=1938.2

http://discuss.pcmag.com/pcmag/messages/?msg=1938.3

You can download EndItAll2 at:

http://www.pcmag.com/article/0,2997,s%253D1478%2526a%253D10165,00.asp

Your first goal should be to eliminate dropped frames, and eliminating competition with Vegas is a good strategy. If you have two hard drives, it is a good idea to capture to the hard drive that does not have your OS on it, provided it is fast enough. The capture drive should have a speed of 7200 RPM, and check to see if DMA is enabled for it. If you are having dropped frame trouble, change the DMA setting as an experiment. But first try the pruned task list thing. For a first try, just manually trim the list.

-- Burton --
Blackout wrote on 5/30/2002, 3:31 PM
Hi,

thanks for your posts....jetdv, that sounds exactly like my problem, i had no problems with win2k and capturing. As soon as i hit "capture" in XP, the stuttering and breakup of sound becomes smooth ...the capture seems ok sound and picture-wise which sounds like the same thing that you experience also. I do get 4-7 dropped frames depending, but now im guessing that these are a side-reaction from going from "stuttering" to "smooth" when i hit capture and probably only at the very start of the file.

Yanking the network usb lead didnt seem to help preview. Sounded like a good theory tho JAB, thanks. Also thanks seeker for your comments, im already doing all those things, like most ppl should by default. Good tips.

So it looks like we have found a fairly big bug in Vegas Capture with XP here....Sofo?

blackout.
briand wrote on 5/30/2002, 3:46 PM
Somebody on the Sound Forge forum pointed out the site

http://www.musicxp.net/

for a few tweaks to get XP performing better in multimedia environments. It's intended for sound/music editing, but pretty much every tweak there applies to video capture as well. It's mostly just a checklist of how to turn off XP's "fluff" and get as much real power out of your machine as possible. Probably worth a look for your situation, although I think your real issue will end up being something else, considering how severe the problem is.

I would re-iterate the previous poster's question concerning DMA. Do you know it's turned on, and have you run a benchmark (HDtach is quite functional) to make sure of it?