Leopard…Now what??!

[Ernie Santella]

For what it’s worth. I had a render crash issue. My problem was a bad memory chip. Kinda’ a pain to track as you have to pull each one and try the render.

[Peter Wiggins]

Have you got some duff media in the timeline?

Try a completely new sequence with some new media in it
(or even a few generators)

Peter

[Sean Harris]

I’ll try some new media. Currently, it is rendering short pieces. I will try the new media when I get to the short piece that crashes it. As I have hours of captured media for the show.

Thanks you for the reply.

Sean

[Kevin Hamm]

Have you had any kernel panics with this machine? Even, actually most especially just a few and only when you really loaded up the system? If so, I’m seconding the advice about the memory sticks. Here’s an easy test: Open the computer and remove the outermost 2 sticks, one from each side. They have to be placed in tandem on each side, so you need to do 2 out, but once they are out, restart and try the render. It will be slower, but shouldn’t be so bad it’s unworkable. And if it crashes, swap the sticks, so that again you have just one set in there, one set out. Try once more.

If after that you’re still having problems, get your logs and get on with Apple about it. They can tell you if the memory of the Graphics card is bad, or if something else, like a firewire bus connection, is causing this problem.

kev~!

Kevin Hamm
Video, Web, Print and coloring books.

[David Roth weiss]

Sean,

Are you absolutely certain that you have the latest updates for the OS and for FCS? If you click on teh Apple Software Updater does it come back with a message that all of your software is up to date? If not, this is most likely your problem.

David

David Roth Weiss
Director/Editor
David Weiss Productions, Inc.
Los Angeles

POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

A forum host of Creative COW’s Business & Marketing, and Indie Film & Documentary forums.

[Sean Harris]

Thanks David & thanks Kevin. I will try all your try’s.

Sincerely

Sean Harris

[Toobit]

I had this happen with a brand new Mac Pro also in December. It turned out to be exactly what Peter mentioned, a corrupt graphic file. The project was pretty visually intense, involving a bunch of PSD’s that were being keyframed. When playing back it would hit a spot and crash, but it wasn’t the SAME SPOT each time, but always happened during the graphic. Then, I forced a render on it and it would crash the render.

So, I opened the project and saved it with a new name. I thought it would be fixed, but it turns out, each time I opened THAT new project it would give me an error and wouldn’t even let me OPEN it anymore. So, I figured it was one of these weird PSD’s and I opened the PSD, saved IT with a new name and then trashed the original.

When I opened the project again that media was missing, so I just reconnected it and it was all good. Worked ever since and never had an issue.

I will admit that for a good 10-15 minutes I was ready to throw my brand new 8-core through the window. But, I then remembered a message I read on here about when the media in a project gets “corrupt”, I was ableto fix it and I was able to save a windows life (and a new Mac Pro’s)!

Honestly, this board is amazing…this collection of experience is the best tech support I’ve ever had.