-
Out of Memory blues continued
I came to this excellent forum for help with an Out of Memory error that I’m getting in FCP 6 (error has occured in previous versions on same computer).
I’ve read the other posts on this forum that suggest a number of fixes, and have tried these but the error persists.
It occurs in a sequence of 27mins duration, it’s DVCPRO HD, has extensive color correction/filtering applied, uses Boris 3d text. Basically, I get an Out of Memory error when attempting to render the sequence. It happens after only a minute or two of rendering. I used to work around this problem by exporting a reference movie and then a self contained movie from that. At the moment I can’t even create a ref movie (I get the same error).
It was suggested elsewhere on the Cow that this problem could be caused by fx script plugins, or preference errors. I have repeatedly re-installed all software on the machine in question (I even zeroed all drives), which usually gets rid of the problem for a week or two, but then it returns.
As an experiment I opened the same sequence up on another machine, and have been rendering it for 45 mins with no crash, which makes me think it is an error in my machine, rather than in the project. But then again, after a clean install it takes a few weeks for the eroor to return, so maybe a few renders down the track the alternate machine will go down too. It’s odd that the problem keeps re-creating itself after re-installs and preference trashings. Obviously, it would be great to work out what process is repeatedly corrupting my projects/system.
I’m running a fully updated version of FCP 6 on a MacPro Dual 2.66 with 4 GB of RAM which is installed symetrically as per Apple’s guidelines.
Any suggestions much appreciated.
-
8 Replies
-
I have had similar issues and I found it was just a small still file that was causing the whole system to crash.
I could render everything before and after the file no problem .
Identifying the file enabled me to work around it.regards
patrick -
Hi,
“Out of memory errors are often related to corrupted clips, renders, and/or CYMK colorspace still images”
1)Delete all your renders files and rerender.
if that does not help:
2)If you have any stills – try to change the name of their location and open your project.if that does not help you probably have a corrupt mediafile:
3)Change the name of your projects capture Scratch folder to “___new”
open your project and now you can reconnect bin after bin/sequence after sequence – untill you find the corrupt file and recapture it.Another workaround is to devide your sequense in smal parts and export them out one bit at the time…
Hope this helps you out,
Andreas -
I get the same problem, and I too have 4 gig ram. However, I have checked Apples web page and it looks like the intel mac is quite picky about ram config. Check out the correct setup (how much of different kind of ram on each “side”..etc)
Anders
-
[Anders Haavie] “the intel mac is quite picky about ram config”
I just spoke with the tech who setup our system
seems the RAM pickiness is about maximum performance as opposed to negative performance issues. If there is equal RAM on the 2nd set of risers it can write across the 2
which is great for uncompressed HDPatrick
-
I spent hours on the phone with Apple Care including Final Cut specialists and I can assure you that rendering to your existing hard drive (or adding a new INTERNAL HARD DRIVE) is your best solution. If you are having these problems do not continue to render to external third party drives (particularly via USB or other slow connections). By using the hard drive for render files the computer’s memory or RAM does not get used up and result in an Out of Memory error message.
I was having tremendous problems rendering certain HD sequences until I followed Apple’s advice and switched my scratch disk choice in System Settings Menu to my hard drive (a new third party drive configured with Mac OS Extended will function just as well as your internal hard drive that the computer shipped with). Now my HD sequences render perfectly. This is the way to go if you are having Out of Memory nightmares. I’m off to buy a new 1.5TB internal drive.
-
A couple more additional comments to add to my post above:
(1) Quick & dirty solution to out of memory error is to select a few clips at a time and render those only (not all the clips in the sequence). This does work from time to time
(2) Apparently gremlins do get introduced to sequences as they get more complex over time and certain aspects of the sequence may get corrupted. To fix this:
(a) start a new project;
(b) create a new sequence:
(c) select all clips in your existing sequence and copy the clips from your problem sequence into the new sequence in your new project;
(d) set your scratch disk to your existing hard drive or additional internal hard drive (dirt cheap now for 1+ TB); and
(d) render without any trouble.
If this still does not fix the issues, google a document called Final Cut Basic Troubleshooting
Hope this helps.
-
I have had the same problem in a SD project. Seems the jpegs the client gave me were too huge… just resized them in GiMP (use Photoshop if you have to) down to a size closer to 720px wide.
Beware the Sounds of Silence.
-
Although I still had a couple hundred GB of space, I received this error in Final Cut. The solution was to delete the render files associated with the sequence in question. Thanks!
Ogden Studios – Salt Lake Video Production
Cordell Wolking
Ogden Studios – Utah Audio / Video Production
Reply to this Discussion! Login or Sign Up