-
FCPx crashes on export, GoPro file issues ???
just started with FCP-X and are a relatively newbie. I did work a bit with FCP7 but I am no pro for sure.
Anyhow, I have made 1 project based on Gopro files and that worked fine. Now I have been working on a project based on Nex5 N files and Gopro files. The Gopro used 1080p mv4 files. On import i made FCP make optimized media.
I am editting on a old macbook that is not actually supported but I has been working ok.
Now on this project I am being driven absolutely crazy. Everything worked fine, no problems in the edit, BUT when i started to export the final media hell started. FCP crashes on every single export attemt no matter what version i choose. I started pulling out clips one by one, and after a while I realized that its the gopro files. When i pull them out of the sequence I can make a export.
Now what the heck can be wrong. The files playback ok in the editor I have even tried to convert them using mpeg streamclip to a quicktime file before using them in FCP x but that did not solve the problem.
I would really like to understand how to solve it and what goes wrong so if anyone can help i would be very gratefull.
Best wishes
Jakob
-
7 Replies
-
I do a ton of GoPro, Drift and Contour work and have never ran into any problem clips for final export.
Double-check if the GoPro clips are already converted to ProRes.
Over the last year, this seems to be the culprit with most problems concerning final export with FCPX.
Also if you have access to a different Mac, can you try and export from there?
What export option are you using? -
Uh,
You’ve kinda acknowledged that you’re running the program on hardware that’s not officially supported.
Sounds to me like it was fine when the hardware didn’t have to do much work. Now you’re asking it to do more and it can’t.
The manufacturer told us the hardware profile for good results. You’re not following that – and you’re not getting good results.
I understand. For a while I didn’t have a supported card in my Tower, so I ran X mostly on my laptop. Then I got a new supported card for the tower. Now I run it on both but my 2011 laptop runs it SO much BETTER than my 2009 tower. (fewer glitches and screw ups by a huge margin.)
X likes new hardware, lots of RAM, and the most modern OS you feed it. If you can’t give it what it’s designed to run on – then you’re going to need lots of patience, IMO.
“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor
-
Hey Man
I see where you are coming from :0). You are kind of right, I need to get my boss to upgrade my hardware for sure :0).
BUT its a very small sequence and for me the way the system behaves points to something else than ” crippled hardware”. I have made a small project before with Gopro files AND a longer sequence without the gopro files outputs fine. As soon as I add the smallest section of the Gopro files the issue appears.
For that reason I think the problem resides somewhere else, but you absolutely have a point.
Best wishes
Jakob
-
Hey Eric
Thx for your suggestions. Good to hear that you have succesfully worked with Gopro files. The odd thing is that I actually have also just made a small project based on only gopro files, that worked…
Now for this mixed project it did not. I am relatively new to this, what is your general workflow when you are embarking on a project containing Gopro files ?
I am sure that when importing the gopro files i asked FCP X to make optimized media, I assume that means “convert the files I am importing to Proress” ? How do I check the what the files are, the “info” window ?
I actually have a different mac but I dont quite understand the file structure in FCP X. When I can not export the file, how can I open it using another mac ? Can I export the complete project of how does it work ?
Best wishes
Jakob
-
Ill try and answer some (due to workload here).
I take all GoPro files and Optimize using FCPX.
I wouldnt say its fool-proof cause Ive heard others having issues here and there.
If you really have to, use Compressor and output to ProRes HQ.
Now to move the project, its best to be on an external drive drive this way your Final Cut Pro Events and Final Cut Pro Projects are intact.
Once you open FCPX with that external attached, the projects will populate in the Projects list within FCPX.
If you’re not using an external, I wouldnt suggest any other option to moving your files.
Burning on a DVD or BD-ROM is the other options but dependent on your project/events size.
Splitting it up on multiple DVDs is a pain 😛
You will find both folders in your Documents folder if you’re not using an external drive. -
First, watch this: https://library.creativecow.net/ross_shane/tapeless-workflow_fcp-7/1
You’re asking the processor to do a lot of work it can’t do. The problem is the mixed media.
When X starts a project, then it selects the settings of the first footage you import.
Your footage is of two kinds:
The GoPro is 1080p with a particular frame rate that you haven’t mentioned.
The Nex5 is 1080i with a frame rate you haven’t mentioned. I just looked it up on line your could be different. You’ll have to check.
When you export/share, X will create one file that has transcoded all of the media to a single specification, which was set when you started your project. Transcoding footage especially frame rate is very processor heavy.
The fixit technique is apparently old school is linked above. Use the app called Compressor to transcode all of you media BEFORE you start your project. All of your media should be the same exact specs. Then open X and import the newly transcoded footage.
-
thx for the suggestions i will try them out
Jakob
Reply to this Discussion! Login or Sign Up