-
Problem batch capturing with FCP 5
Hello. So here is the problem I am encountering. I am logging and capturing (using batch capture) from a Sony BetaSP deck through an AJA IO digitizer. I have logged and captured my clips properly and have launched batch capture throug the browser. The batch begins at the right time code and the footage seems to be going in find, except for two problems:
1. The computer says it finds time code breaks in the middle of the tape, where there are none. I’ve checked the tape for TC integrity and ther are no problems. Further, FCP has done this same thing on different tapes, so it seems like a hardware/software problem of some sort.
2. When the batch capture has ended, rather than offering me a “Finish” button, the batch capture screen only gives “Cancel” and “Continue”. Clicking on continue restarts the capture, and clicking on cancel closing log and capture saves the clip to the browser (as it is supposed to). I’m concerned though that there is something buggy going on here.Any help would be greatly appreciated.
-
6 Replies
-
Might try cleaning the betacam machine to see if it fixes the phantom TC… The other behavior is normal I think if the batch thinks there’s a TC break. If it doesn’t find a TC break instead of Continue, it says OK as I recall.
Jerry
-
I’m having the same issues with our Blackmagic HD Pro 4:4:4 card capturing SD over SDI from a DVW-A510. It’s taken me twice as long to capture these clips. I’m getting phantom timecode breaks as well. I just updated to 5.0.2 and the problem still exists… I’m going to try trashing prefs and repairing permission, but I’ve learned not to hit
. Matt Small
Pair of Hands
Sherman Oaks, CA“If it was easy, everyone would do it.”
-
Hi,
I am running a KONA LS card and am having the same problem. We have 2 identical Kona, G5 dual 2.3, SCSI raid systems and both have the same problem.
Also, the capture window crashes when you open it most of the time. Very scary.
We have replaced drives, updated drivers and software, wiped the machine, replaced the computer (from a dual 2 to a 2.3), replaced cables, etc. The only constant is the card as far as I can see. Maybe the Kona doesn’t agree with either Tiger or FCP 5.
I wish I knew.
-
I have this problem ONLY when capturing at high res HD. I have a 6-way stripe set & a 4-way set in the same dock (ul4d 2 channel SCSI) . I think I’ve isolated the prob to capturing to the slower set. I get the error “detected TC break” where there isn’t one. The dreaded PHANTOM. This is my thought- it means TC break on the media saved on the capture drives, not the source tape. Any arguments? The MediaManager is still a bust as far as I see. It creates a dup clip for every speed effect & tries to capture big chunk of media when it’s not needed. I’ve tried all the posted methods and I refuse to do the lame workarounds. I just re-log, recapture & re-edit the bad clip if FCP balks. My own lame workaround.I also own an Mac Avid Adrenaline but am back to FCP to serve the HD clients. I’ve used FCP since its inception & find it a workable but frustrated Avid wannabe.I might think different if every solution wasn’t a sketchy workaround. All the hopeful FCP editors who flood the job market better look before they leap. This is not the app that will accomodate work flow, not for a while anyway. In an Avid, uprezzing is fun. In FCP it makes my stomach hurt. A low price doesn’t excuse poor performance. TS
-
Finally fixed the problem.
We found that the most recent version of the Kona driver 1.1.3 is the problem. It is incompatible with FCP 5. With 4.5 it’s fine. Go back to version 1.1.2 and the problem should disappear.
If you are using the Blackmagic card it might be the same added programing in the latest driver that is causing the problem. Try going back a version.
Good luck everybody.
-
David- Which problem did you figure out? i have had my recent troubles with FCP 4.5 & 5 with Kona drivers from 1.0 up to 1.1.2. Never have installed 1.1.3 yet. I don’t get phantom TC breaks with uncompressed SD, nor HD to DV D-con thru the Kona2. Just HDCam uncompressed 8 or 10 bit. I think it is drive speed related. I dunno tho. TS
Reply to this Discussion! Login or Sign Up