-
I Inherited a Feature Documentary that keeps crashing! HELP!!!
I’m editing a feature doc. I’ve only been working on it for 2 weeks. It’s all DV footage, and FCP runs fine when I’m editing HD projects and using large projects in After Effects. The old editor tried to make it sound like I didn’t have enough ram. I have 5gigs of Ram on an quad core system. Here’s the situations where it has crashed.
It has crashed after a good deal of functioning fine, while editing a large 40+ minute timeline.
It has crashed when I opened up the file on an external firewire 800 drive and on an internal drive. Both with lots of spare memory.
It has crashed upon opening the project with all files disconnected.
It has crashed with all the files connected to the files external hard drives.
It has told me that the project was made by a newer version (of course I have the newest FCP),
I’m assuming the project file is corrupted, because different drives, or disconnected footage doesn’t make a difference. I’ve tried saving as a new file. I’m trying to create a new project file at the moment. FCP runs smoothly with all other projects too.
I’ve repaired disk permissions, and trashed the preferences multiple times. Deleted the renders, changed the scratch disks, ect?
I may media manage the used footage into a new project if that works.
Any other suggestions or ideas? I need this fixed ASAP.
Crash report:
System Configuration:
Model: MacPro2,1, BootROM MP21.007F.B06, 8 processors, Quad-Core Intel Xeon, 3 GHz, 5 GB
Graphics: kHW_ATIr580Item, ATY,RadeonX1900, spdisplays_pcie_device, 512 MB
Memory Module: DIMM Riser A/DIMM 1, 2 GB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser A/DIMM 2, 2 GB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser B/DIMM 1, 512 MB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser B/DIMM 2, 512 MB, DDR2 FB-DIMM, 667 MHz
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x87), Broadcom BCM43xx 1.0 (5.10.38.24)
Bluetooth: Version 2.1.3f8, 2 service, 1 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en2
PCI Card: ATY,RadeonX1900, display, Slot-2
Serial ATA Device: WDC WD2500AAJS-41RYA0, 232.89 GB
Serial ATA Device: SAMSUNG HD753LJ, 698.64 GB
Serial ATA Device: SAMSUNG HD753LJ, 698.64 GB
Parallel ATA Device: OPTIARC DVD RW AD-7170A
USB Device: hub_device, (null) mA
USB Device: iLok, (null) mA
USB Device: CTE-630-UV3.1-4, (null) mA
USB Device: USB Uno MIDI Interface, (null) mA
USB Device: Bluetooth USB Host Controller, (null) mA
FireWire Device: built-in_hub, unknown_value, unknown_speed
FireWire Device: Iomega eGo HDD, Iomega, 400mbit_speed
FireWire Device: OneTouch, Maxtor, 400mbit_speed
FireWire Device: Mbox 2 Pro, DIGIDESIGN, 400mbit_speedProblem Details:
Process: Final Cut Pro [3040]
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier: com.apple.FinalCutPro
Version: 6.0.5 (6.0.5)
Build Info: FCPApp-810171515~24
Code Type: X86 (Native)
Parent Process: launchd [159]Date/Time: 2009-02-11 13:18:54.087 -0800
OS Version: Mac OS X 10.5.6 (9G55)
Report Version: 6Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0Thread 0 Crashed:
0 …pple.ATIRadeonX1000GLDriver 0x09863f94 gldGetString + 110740
1 …pple.ATIRadeonX1000GLDriver 0x098b7a82 gldGetString + 453506
2 …pple.ATIRadeonX1000GLDriver 0x09830f84 gldInitDispatch + 12308
3 …pple.ATIRadeonX1000GLDriver 0x09832485 gldInitDispatch + 17685
4 …pple.ATIRadeonX1000GLDriver 0x09832bac gldInitDispatch + 19516
5 …pple.ATIRadeonX1000GLDriver 0x09811056 gldGetPipelineProgramInfo + 38
6 GLEngine 0x09668ad5 glGetProgramivARB_Exec + 1445
7 libGL.dylib 0x94ad500d glGetProgramivARB + 45
8 com.apple.motion.filters 0x30fb6830 Effect_CanUseFragmentProgram(char const*) + 166
9 com.apple.motion.filters 0x30fab3ec -[Vignette initWithAPIManager:] + 76
10 …uartzComposer.FxPlugWrapper 0x2ee94c12 0x2ee92000 + 11282
11 com.apple.QuartzComposer 0x95c6b115 +[GFNode(Private) newWithIdentifier:] + 99
12 com.apple.ProFX 0x00e1f1a6 -[PFXNodeManager nodeInstanceWithName:] + 74
13 com.apple.FinalCutPro 0x004f4fd5 PatchForEffectDict + 281
14 com.apple.FinalCutPro 0x004f5fe4 EffectGetQCPatch(KGDictInt*) + 180
15 com.apple.FinalCutPro 0x004f6013 EffectGetFrameSequenceChangedProc(KGDictInt*) + 17
16 com.apple.FinalCutPro 0x000916af KGClipItemSyncEffects_((anonymous namespace)::ClipItem const&) + 243
17 com.apple.FinalCutPro 0x00091a03 pKGClipItemSyncEffects(KGDictInt*, KGDictInt*) + 39
18 com.apple.FinalCutPro 0x000bfb10 SetupMaintenanceCore(KGDictInt*, KGMessageableRec**) + 1988
19 com.apple.FinalCutPro 0x000bfe22 ClipMaintenancePropagater(long, long, KGDictInt*, void*) + 350 -
3 Replies
-
I’d maybe suggest trashing the render files if you can – it could be an issue with those. Generally, projects that go bad stay bad – they’re not unstable, their unusable. This suggests you have an issue with the media connections to the project – which could be render files.
Whatever the issue is, if you cannot revert to a stable and previously saved version, I’d get a new project up and running with the timeline copied across – assuming you can keep the project open to do this.
I would be tempted to split the timeline into sections, just copy and pasting them into a fresh project with (say) 4 timelines. At the very least, this may help to isolate the problem.
I’d also recommend 8Gb RAM in an 8-Core (2xQuad Core) machine, or at least symmetrical RAM on each riser as per Apple’s recommendation – but I doubt that is the specific problem here.
Ben
Ben
Edit Out Ltd
—————————-
FCP Editor/Trainer/System Consultant
EVS/VT Supervisor for live broadcast
RED camera transfer/post
Independent Director/Producer -
Here is something that has saved me in the past. Especially when I receive a new project from another editor and my system runs fine, but then…..
For some reason I have noticed render files appearing inside my FCP Applications folder. Where are your renders going? I am sure Apple would not recommend everyone just checking out what is in there so be careful checking it as such.
go to.
your Applications folder
right click on the FCP icon and click on Show Package Contents
double click on MacOS
If there is a Render Files folder in there open it to see of there are some stray render files from your current project in there. If so, move them to the trash but don’t delete yet. Re-open FCP and see if your timeline works. If so Delete the Render Files from the trash.I currently edit around 2 30 minute effects heavy projects a month and numerous short form ones. When my system is misbehaving I delete prefs, repair permissions and check that folder in Applications>FCP. this makes my mac happy.
good luck
Victor
-
Did you empty the trash after you deleted the render files?? I’ve been hosed like this. Trashed Prefs, change scratch disk etc…and it turned out to be bad render files that were still in my trash can. Just a thought.
Andre
Reply to this Discussion! Login or Sign Up