-
FCP crashing
Playing around with Looksuite and Magic Bullet. I want to apply identical gate weave effects to multiple clips in my timeline. If I click and drag or copy/paste from one clip to another, FCP “unexpectedly quits” on me. Using FCP 5.0.4.
is this user error? Am I using too much CPU? Is it a compatibility issue?Also wanting to export the largest file size possible. Exporting a nested sequence (tried with no in/out points, with in/out points, with markers) using quicktime conversion. Choosing AVI, no compression as to yeild the largest file posisible. Thousands of colors worked and rendered a 3.7GB file. Millions of colors rendered a 5.6GB file, but it only exported 1:04 into the video. As far as I could tell the CPU thought it did the whole thing. Any Ideas?
On a similar note. Frustraited with the AVI at millions of colors not working, I turned to exporting via compressor. Used similar settings to the uncompressed AVI. Chose the QT format, no compression, 24fps (as my timeline, origional capture files, and footage were shot at and set to), millions of colors. Compressor went about 70% of the way and then FCP crashed on me again. Any help?
Here’s the gear I’m working with;
Machine Name: Power Mac G5
Machine Model: PowerMac7,2
CPU Type: PowerPC 970 (2.2)
Number Of CPUs: 2
CPU Speed: 2 GHz
L2 Cache (per CPU): 512 KB
Memory: 2.5 GB
Bus Speed: 1 GHz
Boot ROM Version: 5.1.5f0Erik Scholibo
-
4 Replies
-
What is the source of the footage? DV? or?
Jerry
-
yes DV. I’m using a DVX100B shot at 24P.
Erik Scholibo
-
I don’t use those plugins here, but are the versions you are using compatible with the version of FCP you are using? i.e. have you looked at their websites for updates?
What you are attempting to do should work OK as far as the copy of the filters goes.
The AVI export is a different matter I think. Why do you need the largest AVI? you won’t gain any quality for what it’s worth… maybe there’s a better work around to get your job done… if your crashing in compressor about 70% of the way in, it’s common that the render file that’s around that area of the sequence is corrupt, and a simple re render will fix it.
Problems like this arise from software installs that are flaking out too. But in both cases, it’s not a bug per se.. it’s more likely a corrupt install, incompatible filters, and/or a bad render file in the AVI export.
Jerry
-
thanks for the words. I don’t know why I haven’t checked for updates yet. I guess I was too busy pulling my hair out.
thanks again.Erik Scholibo
Reply to this Discussion! Login or Sign Up