FCP quitting unexpectly during rendering

[Latch Everest]

Hey Mike, thanks so much for your response. It means a lot to hear from someone else who is experiencing this, although I don’t wish it on you. It’s almost a sense of confusion loves company at this point. Granted I’ve always edited in SD so HD is a new animal for me, but an error like this just doesn’t compute as an operator error to me either.

I’m taking all your suggestions to heart. Yesterday, I contacted the tech support for the dealer I got the turnkey system from and asked him to ask everyone in tech support there for any possible solutions. Like everyone else they were completely confused and the only solution they came up with was what you said above about removing 2gb of memory because of possible corruption. I haven’t tried this, nor your suggestion about removing the AJA card since I’m currently in the middle of a project and don’t want to jeapordize anything any further, but tommorrow or Friday I will definitely be doing some testing. In addition I’m currently trying to contact AJA but can’t get through on the phone so I sent an email. Hopefully they’ll call me soon.

I edit for a half-hour show (23:30 without commercials) so my timelines aren’t that intense: aside from color correction– lower thirds, pop-ups, billboards, opening and closing graphics is really all I’m working with. The total size of my project file is under 5mb. And I’m only working with 6 tracks of audio.

To top it off, in addition to render crashes, sometimes just clicking on an unrendered clip in the FCP timeline causes it to crash with no warning or explanation (aside from the error log which appears after the screen is blank). Does that sound familiar to you?

Thanks again.

[Mike Parfit]

Yes, it does sound familiar to me. Exactly the same. Sometimes I’ll just be scrolling the playhead across the timeline looking for something and it kind of catches on a non-rendered chunk and boom, it’s gone. In my case the report option sometimes doesn’t even come up.

Also, about the removal of the 2gb of memory. In my case it is unrelated to there being an actual memory problem. It has been explained to me as a problem that Final Cut sometimes has in actually dealing with memory larger than 2GB. The reason I know it’s not the memory is that 1. Exactly the same stuff happened on two different machines whose memory had been tested, and 2. It didn’t matter WHICH 2GB of memory I removed, I still had the improvement.

It’s interesting that you have so much trouble with a small project file size, but this is such a strange and hard-to-duplicate problem that I’m not surprised.

Good luck,

Mike

[Chris T]

i was browsing though to see if anyone had an answer for this problem. same story for me.

the machine is 2 x 3 GHz quad-core intel xeon with 9gb of ram. our 2tb raid is filling up but we have about 200gb free.
the project file is roughly 130mb in size at the moment.
there is a kona lh card in the machine.

so yes, final cut will disappear (crash – with no report) on a regular basis: scrubbing over the timeline, especially over un-rendered segments, or every time when trying to render more than 90seconds of the timeline in one go.
fairly frustrating stuff.
has there been any progress on solution that doesn’t involve removing components from the computer?

[Chris T]

i was browsing though to see if anyone had an answer for this problem. same story for me.

the machine is 2 x 3 GHz quad-core intel xeon with 9gb of ram. our 2tb raid is filling up but we have about 200gb free.
the project file is roughly 130mb in size at the moment.
there is a kona lh card in the machine.

so yes, final cut will disappear (crash – with no report) on a regular basis: scrubbing over the timeline, especially over un-rendered segments, or every time when trying to render more than 90seconds of the timeline in one go.
fairly frustrating stuff.
has there been any progress on solution that doesn’t involve removing components from the computer?

– oh another note – I’ve been watching the activity monitor lately and when i grab a chunk of 30 seconds or so to render i’ll notice final cut jumps up to using 16.7TB of real memorywhile it render! pretty whacky stuff eh?

[Chris T]

sorry for the double post, but i reckon such a situation is worthy of it.
I’m working in a hdv timeline 🙁
which runs at about 75 minutes long…

[Bill Wade]

K,

I noticed your FCP challenges similar to what I’m running into with an editor. Did you get your Doc with Ford and the Dalai Lama finished?

Bill Wade
Secrets of Love Productions LLP
https://www.secretsoflove.tv