Batch Capture Problem

Paradox wrote on 12/9/2001, 5:25 PM
When trying to batch capture, the deck seeks and finds; plays ok; however it doesn't record onto the disk. It also just continues to play beyond the clip end point until the process is cancelled.

All controls (play/pause/forward/reverse) work fine for the decks (Sony DHR-1000 or GVD-900)and single clip manual capture works fine.

Indications are the problem is within Vegas.

Any thoughts?

Comments

deef wrote on 12/10/2001, 2:17 AM
Can you successfully Capture In to Out on the Advanced Capture tab?
Paradox wrote on 12/10/2001, 12:31 PM
I get the same result: seeks, plays, does not record to disk, continues beyond out point until cancelled.
deef wrote on 12/11/2001, 10:07 AM
Does the Capture Tape function work ok?

Is this mini-DV?
MUCutter wrote on 12/14/2001, 12:08 AM
Same problem with batch capture here.
Manual capture works fine.
GL1 via Firewire.
deef wrote on 12/14/2001, 12:21 PM
I'd like to track this problem down...

What are your systems specs? OS and hw
deef wrote on 12/14/2001, 12:42 PM
In addition to your OS and hw specs...

On clips you manually captured, do the start, length, and recorded on fields have valid data in the Clip Explorer?

Does the seek to in/out points work?

Does Play in to out work?

Does DV Scene Detection work?

Does Capture Tape work?
GaryAshorn wrote on 12/14/2001, 12:58 PM
I have been reading this forum and about this capture problem on previous threads without an answer from Tech. Again asking the same questions as listed a week ago. It appears there is a problem. Can Sonic please comment at least to the status of solving this problem. This is preventing me from upgrading to VV3 until you at least acknowledge this. I think this is only fair to those having the problem and being asked the same questions already posted. This is a serious stumbling block for this upgrade. Thank you.
SonyEPM wrote on 12/14/2001, 1:43 PM
Here's something to try:

Open Vegas

go to ":\Program Files\Sonic Foundry\Shared Plug-Ins\File Formats" and drag "aviplug.dll" onto the open copy of Vegas.

You will be asked whether or not you want to register the plug-in, and you should select "Yes"

Close and restart Vegas (and Vidcap)- this could fix the problem (which sounds like the avi plug-in somehow became unregistered). The above process will re-register the avi plug-in, and hopefully this will fix your problem.

Please let us know either way-
MUCutter wrote on 12/14/2001, 10:28 PM
Tried the aviplug.dll re-register. No Change.

Per previous post...
>In addition to your OS and hw specs...
Dell 8000 Laptop Win2000Pro SV Pack 2
Canon GL1 via Firewire
Upgraded to Vegas 3 two days ago. Capture 3.0 build 63

>On clips you manually captured, do the start, length, and recorded on fields have valid data in the Clip Explorer?
Yes, Manually captured clips play and are editable.

>Does the seek to in/out points work?
?? Not sure how to do that.
Nothing in the help file about how to.

>Does Play in to out work?
YES! Cues, plays the selected clip, stops the tape.

>Does DV Scene Detection work?
No, 10 sec of black followed by 10 sec of a scene ended up as one single clip.

>Does Capture Tape work?
YES!

When in Batch Capture of a clip, tape cues and plays,
another pop up window appears to show two progress bars but nothing ever appears in the bars. Tape just rolls past the out and on forever.

Thanks for your help. Batch is the one big reason I upgraded... Hope we can get the bugs out.
MUCutter wrote on 12/14/2001, 10:46 PM
Under the TRANSPORT / Advanced Capture pull down...
Cue to IN and CUE to OUT do not work.
GOTO TIMECODE DOES work.

deef wrote on 12/19/2001, 8:40 PM
We're currently working on testing fixes for the following batch capture problems (for the next update 3.0a):

-When seeking to In/Out points or performing the seek for a Batch Capture the device doesn't stop at the target timecode. Seems to happen on Win2k/XP with certain devices.
-Huge number of dropped frames are reported when none are actually dropped, causes the out point and clip length to be wrong and unable to batch capture properly. Again seems to happen on Win2k with certain devices.

I was able to get a repro on these problems with Win2k/XP using a Canon XL1.

Strangely, I used the exact same striped tape and footage with a Sony TRV11 and Canon Elura and couldn't get a repro.
MUCutter wrote on 12/19/2001, 10:18 PM
Thanks for looking into this!
Will be looking for the upgrade.
deef wrote on 12/19/2001, 11:14 PM
Also make sure you have valid disks setup in Disk Management Preferences.
KSaville wrote on 1/10/2002, 1:43 PM
I am also experiencing the same problems. Win XP, P4 based machine Sony GDV-300 PAL Mini DV deck.

I hope SF can find a solution to this as the batch, or rather recapture feature was the main reason for my upgrade.

Incidentally to SF, the first couple of time I tried to recapture missing media, VV3 crashed, can’t get it to happen again. Also and more importantly, if one manually captures footage the reported timecode for that clip is incorrect. It will always report that the timecode in is 00:00:00:00 and the out is the clip duration…

I have also noticed that the audio randomly comes in at 32 or 48Khz even when capturing the same bit of tape repeatedly.
nusfbee wrote on 1/10/2002, 9:58 PM

When trying to batch capture, the deck seeks and finds; plays ok; however it doesn't record onto the disk. It also just continues to play beyond the clip end point until the process is cancelled.

All controls (play/pause/forward/reverse) work fine for the decks (Sony VX1000)and single clip manual capture works fine.
Also my Panasonic works perfectly...
Tried 98se2,win2k,winxp same same same
Only Sony products have been an issue for me.
My Brother is waiting to upgrade until he can properly use his Sony gear.
Any guesses until the patch will be issued?

Holding my breath,
nusfbee
deef wrote on 1/11/2002, 1:11 AM
When this happens, do you actually get a clip, albeit longer than wanted?
nusfbee wrote on 1/11/2002, 8:10 AM
No Clip gets recorded at all.
Problem first noted on p3 900.
Same on my AMD 1200
Only happens with VX1000 or Sony "Clamshell"
Not reproducable with other cameras.
Thank You
dvetter wrote on 2/7/2002, 3:11 PM
I have exactly the same symptoms as BigTSonic and KSaville. SF, if you want any further detailed system information to help resolve this problem, please ask. I am looking forward to the 3.0a update for a fix.

System Summary:
Win2K, Dual PIII
Adaptec Firewire Card
Sony DSR-250 Camera
glentx wrote on 2/20/2002, 9:57 AM
We're encountering the same problems. Does anyone know if this problem occurs mainly with Sony cameras? We're using Sony DSR-250s. Could this be part of a driver conflict? I really hope this problem gets fixed soon. All other capture methods work great. Vegas Video is a great product, but without a working batch capture mode, it really hinders productivity.

Recap: Batch Capture problem - VV3 cues tape, starts playing, and playing and playing, no footage is recorded. Basic Capture works fine.

Other than this Batch Capture issue, VegasVideo rocks!
;-)
Glen
db wrote on 2/20/2002, 2:17 PM
"Recap: Batch Capture problem - VV3 cues tape, starts playing, and playing and playing, no footage is recorded. Basic Capture works fine. "

i was having the same problems and few others .. i recently tested a beta VV3 capture and i had no problems to report ( using my panasonic dv deck , GL , elura ) ...and it was FRAME accurate !! and i do mean FRAME accurate ... i always use a film slate at heads and tails of tape ..therfore i have a visual/audio of a SYNC point that happens at a EXACT time code ! using the beta batch capture the captured clip source time code matched the time code on the DV tape EXACTLY !!! everytime !!
glentx wrote on 2/21/2002, 7:56 AM
beta of VV3? What are you talking about?
glentx wrote on 2/22/2002, 8:39 AM
I understand the concept of beta testing I've done it for other companies. What threw me was that you refered to it as VV3 beta when VV3 has already been released. Maybe they should have called it VV3.1 beta to avoid confusion. Instead, I think Sonicfoundy uses letters instead of adding ".#" to the end of each upgrade (VV3f).

I can't wait for them to release this fix. I'm still amazed what can be done with this program. It offers a lot of bang for the buck.