Out of memories

[John Fishback]

Trash preferences and repair permissions. You can search the forum to find out how. Is your media on an external drive? Has this happened before? Alsp, it helps if you describe your system: what computer, what OS, which version of QT, which version of FCP, capture card or box, etc.

John

MacPro 8-core 2.8GHz 8 GB RAM OS 10.5.5 QT7.5.5 Kona 3 Dual Cinema 23 ATI Radeon HD 3870
ATTO ExpressSAS R380 RAID Adapter, PDE Enclosure with 8-drive 6TB RAID 5
24″ TV-Logic Monitor
Final Cut Studio 2 (up to date)

Pro Tools HD w SYNC IO, Yamaha DM1000, Millennia Media HV-3C, Neumann U87, Schoeps Mk41 mics, Genelec Monitors, PrimaLT ISDN

[Michael Nease]

Hi Eric,

Try deleting old render files that you don’t need any more. Have you changed any of FCP’s default settings?

Do you keep your media & render files on a separate scratch disc?

Michael Nease
Firebare Productions
https://www.firebare.com
Los Angeles, CA

[Craig Thomas quinlan]

I second trashing old render files – our clients see this message most often when render files become corrupt. You may even need to trash the render files in the sequence giving you this message and re-render. No one wants to hear this, but it works a good percentage of the time. Narrow down the crash to a particular sequence and give it a shot.

Another possibility that we’ve seen is a piece of corrupt media tripping up this error. Best way to narrow that down is to drag the offending sequence into a new project, new sequence, break it in half. If you render and you don’t get an error message, the bad media is in the other half. If you do, divide it in half again, render, and so on, until you find the piece of media causing the error.

This is one of those FCP messages that is caused by a lot of different problems, and it isn’t usually the RAM or disk space that’s the actual culprit.