OK .. at the moment I've got 21 minDV tapes I've shot. Not ALL full - mostly 80 > 100% filled. This is a project taken me 4 months to video.
So, much time being spent in capture PLUS realtime "auditioning" of the clips. I'm staying with VidCap .. I'll get more use with Scenalyzer presently. However Iw as wanting to get a handle on the feasibility - not wanting to waste time PLUS wanting to get "post-captrue" clips worked up wihile the 9th ot 10 th tape is being captured.
I'm experimenting t-with the following w/f:
#1 - capture in VidCap by scene
#2 - Auditioning as I go .. it's ok, somebody is removing a wall here . .it will take about 20 minutes .. lol .. .
#3 I'm making Works database notes to help me "garner" a narrative from these shots .. that is going well.
#4 - My idea . . when this tape has been captured .. is to then employ scenalyzer to print off the 9 image sheets of the clips. This'll give me a nice visual "buffet" of all the stuff.
.. oops hold on nice shot this .. . shadows of blokes working . ..
#5 - THEN I've got Media Manager to further audition and pile stuff into tags ..
Typical scenario for me:
- Capture from MiniDV ... while simultaneously ...
- Editing in one Vegas session
- Rendering simultaneously in 2, 3, 4, 5, or more other Vegas sessions
- Several browser windows open
- Word processor open
- Photo editor open with dozens of images loaded
- Animation software running
- FTP transferring files
- Media Player playing
- Probably a dozen or more other miscellaneous tasks running
Number of dropped frames or other glitches while doing all this ... approximately zero in the last year.
I forgot to mention that the reason this works so well (and like Kelly, I don't remember the last time I had a dropped frame when capturing DV) is that the capture is nothing more than a file copy operation, and this is done entirely using DMA. Thus, the processor is not involved at all. The only thing I would try to avoid is doing a DVD burn at 16x from the same disk to which you are capturing. I haven't tried that, but I would bet that either the DVD or the capture would "blink" and one of them would have to back off.
I'm running all on one box, using Window XP Pro, practically no tweaks whatsoever.
When rendering i'll set Vegas' dymanic preview ram to 0 since it's not needed. This makes Vegas much less of a memory hog. I also reduce it's priority to below normal. As i've stated elsewhere i've had over a dozen renders all going at once on a 256K 866MHz computer without the UI getting sluggish. I'm now running on a 2.6GHz box with 768MB RAM, but the extra memory doesn't seem to make any difference to Vegas. I installed it so that i could switch between other programs faster.
To make sure VidCap gets all the processor cycles it needs i set it's priority to above normal.