-
FCP7.03 hangs/freezes while loading project
I have a Final Cut project file for this feature film I’ve been working on forever. The project has stopped opening. FCP freezes immediately after the ‘offline files’ dialogue box. (doesn’t matter whether I reconnect media or not.) It thinks for a second, then spinning wheel of death for 5 minutes, then it crashes. I get a KGCore error, which FCS Maintenance interprets as ‘out of memory.’ Obviously this error isn’t the cause, but a symptom.
I just got my computer back from the shop, with leopard 10.5.x. After I had installed all my applications / plugins, something happened, where from that point on I’d get the crash I just described. I troubleshot all the applications, plugins, etc. Uninstalled everything and reinstalled it one at a time. I was able to open the project once after a fresh FCP install, then when I tried to open the same project again seconds later, it froze again with the same problem. Then the same crash every time. I updated FCS, and the first time I tried to open the project it worked fine. Seconds later when I tried to replicate the result, I got the exact same crash. From that point on, the project crashed every time. I ran MemTest and it came out good. Also, last week I had my harddrive, superdrive, battery and screen replaced, and everything else passed the Apple Tech’s inspection, so I am confident this is not a hardware issue.
So I reformatted the computer -> 10.6.4. I reinstalled FCS3 and CS4 and Magic Bullet looks for FCP & AE. Everything worked perfectly for 3 days. Then last night I installed Automatic Duck Free XML Exporter [FCP] and this afternoon I installed Automatic Duck Pro Import AE [AE]. Now I suddenly I can’t open the FCP project again. Exact same error. Freezes immediately after the offline files dialogue box every time. I am able to open other FCP projects though.
Today I tried uninstalling the Free XML exporter, uninstalling Pro Import AE, trashing my preferences, repairing disc permissions, setting my scratch discs to external drives, and I uninstalled and reinstalled CS4 and FCS3 without any plugins. After the fresh install, Final Cut opened the project perfectly the first time, and then gave me exact same crash every subsequent time I opened the project.
I talked to tech support at automatic duck and the guy said the only file that could possibly affect FCP is the xml exporter bundle in final cut pro plugins. It made sense to me that that was the problem, but at this point I’ve not only uninstalled that plugin to no avail, but I’ve uninstalled and reinstalled CS4 and FCS3 too, so I’m thinking its something bigger than that.
I can’t wrap my head around whats going on. I’d be more than happy to reformat the machine again as long as I know it will work afterwards. I just can’t spend days working on this only to have it implode right afterwards.
-
12 Replies
-
Search here for KGCore
-
In the Creative Cow threads on KGCore plug-in crashes, the solution is to delete your thumbnail cache files and restart Final Cut, having it rebuild the the thumbnail cache on restart.
I tried it. It still crashes the exact same way every time.
-
This evening I reformatted again (to 10.6.4) and I installed Quicktime 7 off the OSX install disc optional installs. Then I installed Final Cut. Testing the project, I got the same crash immediately and on every subsequent attempt. So I’m starting to think that installing quicktime 7 in snow leopard might have something to do with it. (I also installed quicktime 7 before this last reformat yesterday evening (the night before these crashes started happening again.)
Tomorrow I will reformat to 10.5 so I won’t have to install quicktime 7, and we’ll see what happens.
-
I don’t think that’s it otherwise you’d see a lot more problems. There’s several threads about it. Make sure you read them all.
-
Well Jeremy I’m not sure what it is you’re telling me to do here. I’ve read every thread I can find about KGCore and Final Cut freezing while opening projects.
Solutions from these threads that haven’t worked:
– Deleting thumbnail cache
– Deleting render files, audio render files, waveform cache
– Disk warrior checked both my media drives and they came out clean
– Ran FCS Maintenance corrupt clip finder. Found 1 clip (which I don’t think was ever referenced in the project) and deleted it.
– I’ve looked for obscure render files inside the package contents of my FCP (there weren’t any, imagine that.) -
Update on the problem: I have found a way to open the project without crashing. I have to open Final Cut first and then open the project using file->open. Then as it loads, I can’t touch any other program. If I click on finder (or firefox or whatever) while its loading, Final Cut crashes as it finishes loading. This goes while I’m working on it too; as soon as I click anything outside of Final Cut, it crashes.
But this means I am able salvage whats inside. Unfortunately though, not via the xml route (generates empty projects). Tomorrow I will create a new project and copy everything over into new sequences, and try to rebuild my master sequence with its 70 nested sequences.
-
[Gerrit Van Woudenberg] “Unfortunately though, not via the xml route (generates empty projects).”
Can you explain your process here a little bit?
[Gerrit Van Woudenberg] “Tomorrow I will create a new project and copy everything over into new sequences, and try to rebuild my master sequence with its 70 nested sequences.”
Why not just copy and paste your whole project in to a new one?
When you reinstalled FCP, you ran the uninstaller first form Digital Rebellion, right? FCS remover?
Jeremy
-
70 nested sequences??!! No wonder it’s unstable. What is the file size of your project?
My software:
FCS Maintenance Pack – Tools to keep Final Cut Studio running smoothly and fix problems when they arise
FCP Versioner – Backs up Final Cut Pro projects to XML and creates changelists for each revision
More tools… -
When I was able to get in, I tried exporting an xml of the entire project. Final Cut would crash at 64% every time. So I slowly deleted every thing I didn’t need from the project (old placeholder assets, old sequences, etc.) Eventually I got the project down to what was totally necessary and I exported an xml. I got an error with regards to a duplicate entry during the export, and when I tried importing the xml (which was only 12kb), I got an empty project. In subsequent attempts it finished exporting the xml without error but the file was still 12kb and the project it created was empty.
When I uninstalled it was always with FCS remover (or a full reformat.)
However your last suggestion seems to be working right now. I opened the project, copied everything into a new project, and booted that up. It started the same way, seemed fine until I clicked on finder, then it gave me the stopwatch for ~10 minutes, then the spinning wheel of death. I thought it was crashing but I left it anyways. About 20 minutes later, the spinning wheel stopped and the project was working. This just happened, but as of right now, it seems to be working fine.
The only thing that concerns me is that my thumbnail cache file still reads as “zero KB”. (I had deleted all my thumbnail files earlier as per a suggestion on COW.) But I assume this means the thumbnails have still not been properly rebuilt.
-
It’s a feature film. For the sake of audio post workflow, I’ve been giving each scene its own sequence (so I can export individual omfs and reference videos for each scene for the sound guys). So yeah, 70 scenes, each one its own sequence, and then the film is one big sequence with 70 nested sequences.
The project was 160MB when I started having these problems. I have since taken out everything that was wasn’t absolutely necessary. Now the project is 90MB. There’s nothing I can really do at this point to make it smaller.
I take it the nested sequences are a bad idea. Any advice you have on Final Cut workflow for feature length would be appreciated. Thanks.
Reply to this Discussion! Login or Sign Up