Capture Glitches

[Brian Sinks]

Okay, I’m assuming you mean you formatted an additional hard drive (internal or external) from your primary C drive.

So, in that case, you might want to look at your “Preferences/Disc Management” setup in the capture window and make sure it is capturing to the correct hard drive. Vegas (for me) always defaults to my C drive. The Disc Management tap will show you a list. Make sure it shows (if not then add) the second hard drive (ex. I/Vegas Capture – you’ll need to add the “Vegas Capture” file to the second hard drive) in the list and has it checked. If it shows the C drive on the list I’d click on it and delete it from the list.

Brian Sinks
IN1ACCORD Productions
Tulsa, Oklahoma

[Gary Kleiner]

[Brian Sinks] “Vegas (for me) always defaults to my C drive”

Set it up how you like, then resave the default.

Gary Kleiner

Learn Vegas and DVD Architect

http://www.VegasTrainingAndTools.com

[Gary Kleiner]

Are you saying that DURING capture glitches and sync problems happen(normal), or that there is a problem with the captured files afterwards as well?

Gary Kleiner

Learn Vegas and DVD Architect

http://www.VegasTrainingAndTools.com

[Laszlo Kovacs]

Hi,

Make sure, your drive is defragged well…

[gksmiler] “Though I understood capture not to be CPU intensive, I see that Task Manager is reporting that Vegas is using 97-98% of the CPU resources.”

Accidentally, is the directory compressed you capture to?
It’s an NTFS option, windows compresses/decompresses files on the fly when writing/reading thus achieveing more disk space: that’s
not what you could whish to do with dv-avi files.

Another cause of the high cpu load can be the DMA status of that drive, if it is disabled.

By(t)e

K.L.

[Mark Moss]

How do you know if the directory you are capturing to is compressed or not?

Thanks,

Mossman

[Laszlo Kovacs]

In windows explorer right click that folder, choose “properties”.
Look for a button something like “special”, then click it.

On the panel you get, there will be options, including something like
“compress contents for save disk space”.
If that option is checked, your folder is compressed: uncheck it.

Sorry about those “something like”, but I’m using hungarian version of windows, so I can’t tell you the exact captions.

Hope I could help.

By(t)e

K.L.

[Guy Kingston]

Thanks for all the suggestions.

I am capturing to an internal additional hard drive (D drive). I have checked that

[Laszlo Kovacs]

Hi,

[gksmiler] “I tried capturing again this afternoon on the faster system. I got 45 minutes into it without a glitch ( a record) and kept Task manager open throughout. Most of the time Vegas was using around 20% of the CPU”

To compare:
Years ago when I started with DV it was on a PentiumIII with 1000MHz,
512MB of RAM, and had only one drive…

On that machine capturing DV through firewire took about 20..30% CPU with Vegas4 (under Windows 2000), and I never had any glitch nor a dropped frame (except that one case when I accidentally wanted to capture to a compressed folder).
I guess your machine is just in lack of power.
Or may it as fast (or faster than) a PIII-1000, then a bus conflict could cause problems – should this be the case, try to place your firewire card into an other slot.
(I’ve seen conflict with one of my motherboards, where everything seemed fine, but I got dropped frames, randomly, approx 1 per minute no matter which slot I used for the firewire card – I returned that MoBo more times, thinking that it’s defect, but the problem went away only when I replaced it with an other brand).

I Also heard that some VIA VT6307 chipset based capture cards are not the best.

Again in short:

Assuming your machine is powerful at least as a PIII-1GHz

-is your capture card VIA based?
-try to place your capture card into another slot
-at last try another MoBo (time to upgrade?)

Please let me know how your problem is solved.

Hope I could help.

By(t)e

K.L.

[Guy Kingston]

Hi,

These are the specs of the better of the two systems (capture glitches are happening on both!):

[Laszlo Kovacs]

Ehhhmmm….

In general, overclocking is not a good idea.
It can cause strange problems, however your system
may appear stable…

For example, PCI bus runs at 33.3MHz by design.
If you overclock it (let’s say 40MHz), a device attached to
it may miss every second clock, however it looks running OK,
actually it is running at 20MHz – thus you lost about 30%
of it’s speed.

SATA devices are very sensitive too, be careful!

So, if you have ANY problem, don’t overclock.

After that:

https://hu.asus.com/products.aspx?l1=3&l2=11&l3=397&l4=0&model=1459&modelmenu=2

tells that

IEEE 1394a VIA6308P controller supports 2 x 1394a ports

Try to buy a capture card, I can recommend you pyro basic dv.
That does it really well.
You should get it for about $30.

Another thing you gould give a try: capture to a single drive, not to the RAID. (I had strange problems with asus p4p800 integrated raid controller).

Also you could try to disable any hardware you don’t use, to minize the risk of bus conflicts (including onboard 1394 if you put a capture card in).

By(t)e

K.L.