-
FCP 4.5 Crash after capture
Dual G4 500
1.75 gb memory
10.3.8
qt6.5.2
FCP HD
Various ext FW 400 drivesCapturing DVCam
After capture, it crashes everytime! After restart the qt file is there.
Clean reinstall, fix pemissions, etc. Still crashes. No matter which ext drive I use.However, will capture fine in imovie.
The rest of FCP is working just fine also.Here is part of the crash log. Anyone understand what this is telling me?
Jun 25 19:19:20 localhost kernel: AppleFWOHCI_DCLProgram.cpp 1195: ERROR: interrupt chain ran off end of DCL program 0x262cf00
Jun 25 19:19:20 localhost /Applications/Final Cut Pro HD.app/Contents/MacOS/Final Cut Pro: DVHandleOutputUnderrun: 0x0xe006c00At the end of the log it says this:
Jun 25 19:20:31 localhost kernel: FWOHCI Bad selfIDs, issuing bus reset (retry 1)
Jun 25 19:20:31 localhost kernel: FWOHCI Bad selfIDs, issuing bus reset (retry 2)
Jun 25 19:25:03 localhost kernel: FWOHCI Bad selfIDs, issuing bus reset (retry 1)Hardware or software problem?
Your thoughts? Thanks. -
3 Replies
-
Hi Richard,
Your setup is similar to my own. I’ve found that the most stable version of OSX for us G4 users is 10.3.4. I have a seperate firewire PCI card (LaCie) for my external FW drives, and this is to keep my camera/deck on it’s own FW bus. Sometimes communication problems surface with having your capture source and firewire drives on the same FW bus.
I also know that iMovie and FCP capture video differently, although I’m not sure of the differences at the moment, so this may be why the iMovie capture works for you and FCP doesn’t.
Anyway, albeit slow compared to the G5’s, my current system is rock solid and never crashes. Sometimes FCP will start running more slowly during heavy use or act a little wierd, then I run ‘Final CUt Pro Rescue’ to trash the FCP pref files and it always gets right back to normal afterwards.
Hope this helps.
– Don
-
Problem solved by resetting pram and resetting the nvram! Thanks.
-
Hi,
How do you reset pram and nvram?
eric
Reply to this Discussion! Login or Sign Up