Help! Weird FCP HD problem!
 

For some unknown reason, when I try to open a short film's sequence (22 minute film) in the latest version of FCP HD (and no problems prior to this), I get two pop-up windows, as it says it's "preparing video for display:"

"General Error (34)"

and

"Error: Out of Memory."

What's up and how can fix it?

I'm running the latest Panther and FCP HD, I have 1.25 gb of Ram and plenty of hard drive space (about 50 gb). The footage is DV. Never had this problem before, even when I was re-mastering my feature (110 minutes).

THANKS!

heath

In FCP3 on a DP500 G4 with *256MB* I encountered the error message

"Error: Out of Memory."

Before that preparing video for display would take forever. What fixed it:
A- Installing more RAM.
B- Not using lots of nesting. Nesting will slow your project down a lot. 7 is ok, 100 is not.
C- Not putting ten gazillion markers into the clips and then cutting them.
D- Splitting the project up into various sequences, and then using nests to join all of them. In the sequences, you can set in and out points so the nests can have cross dissolves applied to them.

It seems that B and C correlate with FCP project file size. That might mean something. I'm not sure if that helps as you have 1.25GB of RAM. But if your project is really complicated then it might happen. Do the splitting into sequences thing in that case.

No nesting, only 3 or 4 sequences but none are joined together. I'm at a loss.

heath

Hi Heath
I have no answer, sorry But have you had a look around the FCP user groups.

http://www.lafcpug.org/

Is a very good one with many helpful people and lots of useful links, Hope all goes well for you soon tho' as it sounds very stressful

here's 3 pages worth of posts on General Error 34
http://discussions.info.apple.com/webx?127@680.69fTaA9DHam.0@.ee6bcd7
Here's some on out of memory
http://discussions.info.apple.com/webx?127@680.69fTaA9DHam.3@.ee6bcd7

This should help (the Apple site stuff), thanks!

I tried opening it with my firewire drives off, and it finally opened, so I think a file was corrupted. I'll probably just re-capture, since I still have the in's and out's on the clips.

heath