[Thomas A. johnson]

I spoke too soon. It’s still doing it.

-TAJ

[Thomas A. johnson]

I have been dealing with this problem, like the rest of you. The whole 9 yards of multiple rounds of Apple support, replaced logic boards, and general finger pointing regarding whose fault this issue was. After today’s Premiere update,I just pulled three CUDA renders without glitches occurring. I’m hoping this is a good sign.

-TAJ

[Thomas A. johnson]

Thanks everyone for the advice.

Just for the sake of leaving my troubleshooting path-
I ran disk warrior, I reinstalled FCP- both with no change.
It seems I saved the most obvious solution until last…

So far, it looks like the ‘bloated database’ is what happened. I never was able to ascertain exactly what caused the issue, but my work-around was to pull my sequences to a new project that did not include my original media bins. It seems to be rendering fine now. However, I don’t know what I did to bloat the database. Any thoughts on this point / things to avoid?

DB structure for reference: I had appx 30 hours of 4:3 NTSC DV25 footage all sub-clipped out with description/detials filled in and divided into various bins. I had a separate bin for audio clips (wav and SoundtrackPro), a separate bin for graphics (.png from AE, livetype,logo graphics), , a separate bin for clips prepped for FX (slow-mo, etc)

-TAJ

[Thomas A. johnson]

Okay. I analyzed a couple of older versions of the project, and I came up with the following:

I had a version sitting at 87MB, which had all of my stills in place (appx 500 or so used in a couple of animation sequences).
The next version I had was 160MB- the primary difference that I see on this is that I linked to a soundtrack pro project file (.stap)

Also, if I have had one of these projects open, close the project (without exiting final cut) and try to open another version of the project, FCP will shut down.

thoughts?

-TAJ

[Thomas A. johnson]

Okay… I’ll answer several questions at once here:

RAM: 6.5GB
Number of timelines open: I have had is crash with as little as one and as many as 5.
DiskWarrior: No, I don’t have it, but I have seen that mentioned in various threads before.
Project size: (I had not considered looking at this before.) 221.7MB
I notice that several revisions back the project file was considerably smaller.
Duration of project: there are a few timelines within, but the one primarily in question right now is just under 10 minutes
Files referenced: I am referencing quite a bit of footage on a firewire drive (just shy of 30 hours)

Notes: No other software seems affected. I have tried systematically taking our RAM modules to see if this helped (it didn’t). It seems as if it is filling up all available ram and not letting it go for some reason. (No, I haven’t benchmarked this- just a theory.)
the FCP disappearing routine began just after doing a small edit which included cutting out part of the beginning of a soundtrack project file.
I did try deleting the prefs files (but not the whole folder) at one point, which did not help.

-TAJ