-
Another “Out Of Memory” thread, but this time it’s different….
Hi,
I know this has been asked and dealt with 10 000 times, this time it’s different, really.
I have a sequence that was going along swimmingly, NO oversized jpegs, CMYK images or H.264 files or anything like that.
Everything has been transcoded to the same flavor of Proress 422 and for ages I’ve had no problems.
But the last few days I’ve been getting the dreaded ‘Out Of Memory’ message.
The project file is only 65MB.
One change I have made, though, is change my scratch folder as the original drive was starting to get fuller than I like. Could the project have problems dealing with render files on different drives?
I’ve trashed my prefs and repaired my permissions.
One additional note: FCP renders fine for a while directly from the launch of FCP. Then, after I’ve been editing for a while, I get the messages. Could it have something to do with the RAM buffer getting filled, or something like that? Would flashing my PRAM or similar maybe help?
I’ve got an 8-Core Mac Pro with 6GB of RAM. FCP 7.0.3 OS X 10.6.4
Any ideas? Any workarounds? Pleeeeeeze?
Thanks,
Wayne
-
9 Replies
-
Another thing I could add, which may be helpful in diagnosing the problem…
After launch everything plays smoothly, including ‘green’ and ‘orange’ un-rendered clips.
However, after a short while, the unrendered clips start jerking and jumping and FCP plays all sorts of random video frames.
Any ideas?
Thanks,
Wayne
-
Do you use external output?
Aja, decklink or matrox?
Set view-) external video OFF
See of problem persist.
Check still cache. Shouldnt be higher than 30%
Also make sure you dont have high undo levels.
Try Copy paste edit in new sequence.
Try to create new admin test user -
Hi Paul,
Thanks for taking the time to write and help.
I’m afraid I need to answer negative to all of the above, ie, I’m not running a Matrox card or anything like that, and I don’t have my stills cache set to higher than 30%, etc.
I’ve also tried copying to another timeline and project – as well as logging in as another user.
I’m starting to think there may be a problem with the RAM [?!]
Any other ideas?
Thanks again,
Wayne
-
How many sequences do you have open Wayne?
David Roth Weiss
Director/Editor/Colorist
David Weiss Productions, Inc.
Los Angeles
https://www.drwfilms.comPOST-PRODUCTION WITHOUT THE USUAL INSANITY ™
Creative COW contributing editor and a forum host of the Business & Marketing and Apple Final Cut Pro forums.
-
Hi David,
Thanks for asking.
I get this problem, even if there is only one sequence open.
W
-
If I were you I would use Media Manager to copy the entire project to one hard drive, and then test to see if the new project created runs better. If so, you can lose the old one. MM does copy all the media in the bins and sequences you select to a single directory on the hard drive you target, but that’s not that big a deal, and may even help in this case.
David Roth Weiss
Director/Editor/Colorist
David Weiss Productions, Inc.
Los Angeles
https://www.drwfilms.comPOST-PRODUCTION WITHOUT THE USUAL INSANITY ™
Creative COW contributing editor and a forum host of the Business & Marketing and Apple Final Cut Pro forums.
-
I can give that a try – just so I understand, what is your thinking behind this suggestion?
W
-
[Wayne Marx] “just so I understand, what is your thinking behind this suggestion?”
1) It will open a brand new project file and will get all your media onto a single hard drive while keeping track of everything in the database, without the need to relink anything.
2) Whether it works or not, it will help to eliminate many variables from the mix of variables, thus helping to refine the search for a cure.
David Roth Weiss
Director/Editor/Colorist
David Weiss Productions, Inc.
Los Angeles
https://www.drwfilms.comPOST-PRODUCTION WITHOUT THE USUAL INSANITY ™
Creative COW contributing editor and a forum host of the Business & Marketing and Apple Final Cut Pro forums.
-
Hi all,
I’m pleased to report that, after a long night of endless crashing & Googling I think I’ve TG solved the issue.
I bought https://www.digitalrebellion.com/fcsmaintenance/ which has a tool that searches projects for corrupted files – turns out there was a photograph I downloaded a few days ago that, even though it was a small file size it must have had incompatible attributes that drove FCP nuts.
If it weren’t for that software I never, in a million years, would have found that photo.
Thanks again to all of y’all that pitched in to help out.
I hope this experience helps some other people.
Wayne
Reply to this Discussion! Login or Sign Up