-
Major Capture Problem in 5.0.3!!!
I have encountered a major problem in FCP 5.0.3.
Whenever I try to batch capture I get either dropped frames or a timecode break error. Neither error should be occurring. I have found that if I create a new project file and try to capture the clip then, it works, but only 90% of the time.
I thought that I was alone with this problem, and have not seen any posts related to it here. But today I found another system in my office with the exact same issue. I am using the Kona 2 for capture and the other system is using the Io. Both systems are on FCP 5.0.3 and QT 7.0.3. The Io is on OS X 10.4.3 while the Kona is on 10.4.2. The only other commonality is that both systems are using the Xserve RAID. We have tried to capture in DV, DVCPRO 50 UC 10bit & UC 8bit all with the same issue.
I have done the usual steps to try and solve this problem, trash prefs, restart, repair permissions, and so on. A reinstall is next, but I wanted to see if anyone else is having these problems or if anyone may have found another solution.
Jared
Idea Spring Editing, Inc.
Denver Final Cut Pro UG -
8 Replies
-
I know this may sound incorrect, but since there really is no dropped frames happening
and no time code breaks (assuming you are sure there are none) then just go to the
user prefs and turn off abort capture on dropped frames and on time code break,
warn after capture. I’ve done this when capturing from our DVCPRO deck and
I have zero editing issues or recapturing issues since doing this, since FCP 5.0.
There is some kind of problem with FCP and Panasonic decks it seems.
I have not seen this problem with our Sony decks, digibeta and betasp.Dan
-
Thanks for the input but that does not work. When I do that it just keeps trying to capture the same clip over and over and over. I let it go for an hour and it still had not captured anything.
And and update, reinstalled FCP back to 5.0 on another system and the problem is still there. So now I have now idea what the issue is. I am starting to think that it might me stemming for the Xserve RAID.
Jared
Idea Spring Editing, Inc.
Denver Final Cut Pro UG -
What deck are you using?
dan
-
Several, a beta uvw 1800, pan AJ93, JVC d-9 and a sony dv. All with the same issues.
Jared
Idea Spring Editing, Inc.
Denver Final Cut Pro UG -
What happens if you try capturing to an internal drive, just as a test?
Do you have two internal drives., with one that isn’t your system drive?
Even if you capture to your system drive, it would still tell us if it is
indeed a problem with your RAID. Of course the capture would
need to be DV level or DV50.dan
-
Not that this is of any help but I have a similar problem with an internal 4 drive(maxtor 300g 16mb cache) software raid, seritek 1v4 card,
a uvw 1800 beta deck and a aurora pipe studio capture card. No time code break errors but I get a random dropped frame error
usually at the very start of the capture. I’ll press try again a couple of times and then it suddenly will deside to capture, even a
long piece, then a short 2 sec capture comes up next and it errors dropped frames again. I have to baby sit the process and keep
hitting return on error. Batch capture use to be a coffee break for me! Now its the biggest hassle.
I’m Running G5 2.3, 2g mem. FCP 4.5 quicktime 7.0.3 and all updated aurora.Did you do a computer to computer upgrade? I upgraded from a G4 moving all my programs and files from there to the G5. I was under the
impression this is as good as a clean install but not sure now.When I try to compress a FCP file using compressor it gives an “unable to connect to background process” error.
-
Mark,
The interesting thing about what you just said is you are using FCP 4.5.
I had no trouble with any decks when using that, plus my Pipe Studio.
And even since upgrading to 5, the only trouble is with our DVCPRO
deck. The DigiBeta and BetaSP decks are fine. And right now,
except for batches from that DVCPRO 455 deck, my setup with
FCP 5.0.3, OS 10.4.3, QT 7.0.3, Aurora Driver 5.0, Firmware 2.0
is very solid. No crashes for weeks. Using a dual 2.5 gig G5
and a 4 drive external SATA RAID with the Sonnet 4+4 PCI card.As for your install, I would have serious reservations about doing it
that way. If I were you, I’d start with a fresh hard drive and install
the OS and FCP or FCS. You can migrate your other apps and
documents. But I would not transfer one OS from one computer
to another or FCP that way either. And FCP5 is nice, now that the
bugs are out of it at .03 version. I’d recommend upgrading.Dan
-
Thanks for the feed back Dan. I have been wanting to here about someones system similar to mine working fine just so
I could have piece of mind plugging forward to a bug free capture and edit day. I’m in the middle of a waterfall landscaping
“how to” project with 10 hrs of raw and approaching a 2 hr dvd so I am going to wait till this raps up before I try any new
configs. As you suggested to Jared I have turned off the “abort on dropped frames during capture” so that it will batch without stopping. I haven’t
noticed a real dropped frame yet on any captures but figure I’ll just go and recapture if I see an issue. Though I would
not recomend turning off the “abort on dropped frames on capture” permanently since dropped frames are not always
easly spotted. It just would be nice to know it’s all there without having to find the glitch later and digging up the tape again.
I’m looking forward to FCP 5.0.. Regards, MarkI fixed the compressor issue from an earlier Cow link.
The Cow is quickly becoming like my cell phone… what on earth did I do before it!
Reply to this Discussion! Login or Sign Up