[Ryan Poirier]

I’ve had this exact same problem. A project I was no longer working on was previously loaded via a networked HDD. When I wasn’t connected to that drive I’d get a similar message saying FCP 7.0.2 was searing for a render file for a project I haven’t worked on in weeks, and was not loaded in FCP’s project bins. From a user standpoint there was absolutely no reason FCP should be looking for these files and I couldn’t figure out why it still wanted them.

Eventually I decided to clean house, Found all my autosave, waveform cache, & thumbnail files and trashed nearly everything save for some recent autosaves. It all added up to a few gigs worth of space just from those files.

Relaunch FCP. Everything back to normal.

My guess is one of the waveform or thumbnail files were referencing to the networked drive. Why FCP was still trying to load these cache files I’m not sure. Perhaps it’s default action is to load all files located in these folders. Similar to loading a plugins folder. If it’s there, it’ll try to read it.

A little spring cleaning can go a long way to keep an efficiently running ship! I’ve noticed FCP launches more snappy now, even compared to before that error message ;~)

All the more reason to clean out old files. As cruft builds up, you start to loose performance. But it’s usually so slow you don’t even notice it happening. Until FCP has heart attack.

-®yan P.