DV Capture issue in FCP

I'm having trouble capturing some DV footage in FC Studio 2. I'm a long time editor, and I'm fairly proficient in the basic functions, but when the program starts to do something strange, I get lost.

I shot footage on DV, with a Panasonic GS10, consumer camera, and when I go to log & capture, it works fine for a while, then his a point in the tape where the capture freezes up. The tape continues to play, however as if nothing is wrong.

I get the "dropped frames occurred during capture, capture was aborted message", so unchecked the abort capture on dropped frames option. I still have the same issue.

Also, the footage that I am able to capture, will also suddenly freeze up on playback, and even go to black at certain points.

I assume there's just something wrong with the physical tape, because I don't get this issue with other tapes, so problem identified, bad tape. It is strange though, because the tape plays just fine, FCP just doesn't like something about it.

Ok, so bad tape, fine, I can live with that. As a solution however, I tried recording the footage to a DVD to create an entire new piece of video, in an attempt to "smooth over" any weird timecode breaks or glitches on the tape or whatever. I then re-recorded that DVD back to a DV tape, creating yet another new piece of video, with a whole new timecode. In my experience, this usually works.

However, even with the new version of the footage, I get the same problem capturing. Doesn't it seem that this brand new piece of video, on this brand new tape should work? If there was an issue with the original tape physically, it should be a non-factor. If there was some weird timecode issue, it should also be a non-factor, right?

I did go firewire from the original DV to the DVD, so I can see how that might cause the issue to transfer possibly, but it seems unlikely. Additionally, I copied the DVD to the second DVD via S-video, so I can't imagine any of the original digital information could possibly have transferred over. It just seems unlikely.

If anyone has any insight, I'd greatly appreciate it. Thanks!

 

Thanks, yeah I have been trying to capture just the short clips I need, but I keep running into the problem. I can wrap my brain around time code breaks, that makes sense, but I cannot for the life of me, figure out why there would be any issues with the new signal, which should have a totally new, uninterrupted timecode. I did also try different cables, same result. It's just so weird...

The problem if definitely with the original tape, I just can't figure out why it persists with the new tape.

 

^

It's not that crazy. I was recording with a battery. It was outside in very hot weather, at a zoo. It was dusty as well. I definitely thought of the heat issue causing problems with the tape. There's no mystery there, but I was confused as to why the new tape did it as well. You are probably right about the difference between battery & AC. I'm sure that's a factor.

I should try striping a new DV tape with TC. I only have one playback DV device though (the camera) which is why I made a DVD dub then went back to DV. I can try to re-dub the DVD to a new DV tape after laying down black. Who knows, it might work.

Also, I wonder if the fact that the first dub was via firewire had something to do with it. Maybe if I go composite video from the start it will make a difference. Less chance of transferring bad digital info maybe?

Thanks for the advice everyone, I'll keep trying!

*Update:

I just transferred a bunch of old Hi8 footage to DV, and hen I went to capture it, it seemed to working fine for the first 20 min or so, then began displaying the same problems. So now I think it must just be the camera, or maybe capturing longer than a certain amount of time causes the problem, as someone suggested. I wonder if there's a problem with autosaving during capturing. Maybe it tries to autosave and then things get bogged down or something. Does anyone know if autosave is disabled during capture? Maybe I'll try capturing shorter segments, and set the autosave to longer than my capture time. I haven't had that issue before though. Maybe my system is just getting bogged down.