[Christian Gainsley]

So I tried what I’d proposed earlier; I captured the whole clips from the P2 card (in this case a dump to a hard drive done during production), click on the media in the browser that’s disconnected -in the browser it also lists the mother clip it came from in the shot/take column i.e. 8202HX- and did a reconnect media. Unclicked ‘Matched Clip an Reel name only’ and then selected the 8202HX clip in the capture scratch and it referenced the correct TC. The only problem is that I have to do each clip individually since I’m manually selecting the mother clip. But it’s getting around the log and transfer/capture problem.
Christian

[Christian Gainsley]

Since I haven’t seen a clear fix to this problem I should also note this is happening to me. A P2-only project is being batch captured and a few of the cards referenced seem to be flagged as tapes, and so log and capture opens and then fails because of lack of drive/media.
I’m using FCP7.0.2 on snow leopard. I’m rebuilding a project for a client who’s drive holding the capture scratch died, but had another drive with all their P2 dumps on it. There’s approximately (20) 16 or 32GB tape dumps and probably 2 or 3 are being flagged by FCP as tapes. All the clips have custom in’s and out’s and were logged with custom clip names so unfortunately just capturing all the original media in bulk form won’t work for a reconnect media. Maybe I could deselect ‘match name and reel’ and see if it picks up on the TC? Guess I’ll try that.
Christian