fbpx
3 Post Moderation Rule for New Boarders (25 Jan 2021)

New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.

Big problems crashes FCP-X and GoPro files.

More
02 Apr 2012 01:40 #6415 by jagge
Hey

I 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

Please Log in to join the conversation.

More
02 Apr 2012 05:05 #6420 by fcpguru
Hrmm, sounds odd. Take a look in the console for odd messages when playing the GoPro media files. I've had some weird framerate stuff happen to me that's caused the program to go ballistic. Not the best solution, but maybe try converting the GoPro footage in compressor and force it to transcode to the exact settings you want (don't leave it set to whatever the source is).

Make sure your frame rate is 29.97fps!

Please Log in to join the conversation.

More
02 Apr 2012 20:05 #6459 by jagge

fcpguru wrote: Hrmm, sounds odd. Take a look in the console for odd messages when playing the GoPro media files. I've had some weird framerate stuff happen to me that's caused the program to go ballistic. Not the best solution, but maybe try converting the GoPro footage in compressor and force it to transcode to the exact settings you want (don't leave it set to whatever the source is).

Make sure your frame rate is 29.97fps!


Hey

Thx for the suggestions.

I have tried to reencode the gopro files using mpegstreamclip, that did not help. I converted it to a quicktime file which I thought was the closest to FCP.

I am not sure what I did about framerate. My project is in 25p so I guess thats the framerate to choose. Not sure about the 29.97 is that when doing 30P ? Is that a canon specific issue that 30p on those babies is actually 29.97 or is that a general thing ?

Best wishes

Jakob

Please Log in to join the conversation.

More
02 Apr 2012 20:35 #6463 by fcpguru
The framerate may or may not be the issue, but I am curious as to what the native settings of the gopro footage is. Can you use something like MediaInfo and post up what it says on the native Go Pro footage?

Please Log in to join the conversation.

More
02 Apr 2012 20:56 #6465 by tpayton
Hi jagge,

So just how old is that old MacBook Pro? What graphic card does it have?

Please Log in to join the conversation.

More
03 Apr 2012 11:49 #6496 by jagge

tpayton wrote: Hi jagge,

So just how old is that old MacBook Pro? What graphic card does it have?


Its a Macbook, white version, propably 4,5 years 2.4 gHz intel Core 2 Duo, 4GB ram, grafics Intel GMA X3100, 144 mb.

Kind regards

Jakob

Please Log in to join the conversation.

More
03 Apr 2012 11:56 #6497 by jagge
General
Format : MPEG-4
Format profile : JVT
Codec ID : avc1
File size : 1.41 GiB
Duration : 13mn 21s
Overall bit rate mode : Variable
Overall bit rate : 15.1 Mbps
Encoded date : UTC 2011-04-08 04:42:37
Tagged date : UTC 2011-04-08 04:42:37
AMBA :
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Main@L4.2
Format settings, CABAC : Yes
Format settings, ReFrames : 4 frames
Format settings, GOP : M=1, N=15
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 13mn 21s
Bit rate mode : Constant
Bit rate : 15.0 Mbps
Nominal bit rate : 5 120 bps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 25.000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.289
Stream size : 1.40 GiB (99%)
Title : GoPro AVC
Language : English
Encoded date : UTC 2011-04-08 04:42:37
Tagged date : UTC 2011-04-08 04:42:37
Audio
ID : 2
Format : AAC
Format/Info : Advanced Audio Codec
Format profile : LC
Codec ID : 40
Duration : 13mn 21s
Bit rate mode : Variable
Bit rate : 128 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 KHz
Compression mode : Lossy
Stream size : 12.2 MiB (1%)
Title : GoPro AAC
Language : English
Encoded date : UTC 2011-04-08 04:42:37
Tagged date : UTC 2011-04-08 04:42:37

Please Log in to join the conversation.

More
03 Apr 2012 12:17 #6498 by Seanus
Wow I'm amazed FCP X is running at all on that machine!
Doesn't even have a proper graphics card.
Isn't it when FCP exports that it uses the Open CL? Could that be the issue?

Is everything in your timeline rendered before you try and output?

Sean Lander - Editing since 1982 - AVID 1991 - FCP 1999 - FCPX 2011

Please Log in to join the conversation.

More
03 Apr 2012 14:42 - 03 Apr 2012 15:54 #6500 by cgbier
I got FCP X installed on an iMac of the same vintage (same CPU, just a better GPU). It runs, but slowly (molasses runs faster), and whatever has to do with OpenCL doesn't work.

Seeing that your Intel GMA is even worse than my Radeon 2400, I'd assume you have found your culprit there. Shot into the dark: It seems that FCP tries to do something to your footage that it needs the GPU for. It doesn't find a useful GPU, and quits without comment.
Last edit: 03 Apr 2012 15:54 by cgbier.

Please Log in to join the conversation.

More
03 Apr 2012 15:19 - 03 Apr 2012 15:21 #6501 by FvH
I recently produced some pilot footage for a local German tourist board, with mixed 5D and GoPro material. No problem at all. Just imported the files and did some editing. Therefore, I am pretty sure that your problems are due to the vintage hardware.

Here's one of the clips:

Last edit: 03 Apr 2012 15:21 by FvH.

Please Log in to join the conversation.

More
03 Apr 2012 16:20 #6504 by cgbier
Sorry for the OT, but is that in the Ruhrpott area? Nice there. A lot of fun for the Mopped.

Please Log in to join the conversation.

More
03 Apr 2012 17:11 #6506 by FvH
OT reply: It's approx. 40 miles east of Cologne. And indeed: lots of fun with the bike.

Please Log in to join the conversation.

More
03 Apr 2012 17:17 #6507 by cgbier
Ah, I see. Thanks. Been in that area only twice (once with R75/5, once with with XJ900S).

But back to the studio now....

Please Log in to join the conversation.

More
03 Apr 2012 17:55 #6510 by tpayton
Try this as a fix. Render your complete timeline, that is turn on background rendering, or choose Modify > Render All. Then do an export with the codec set to "Current Settings". That should bypass the GPU and should enable you to export.

Also I wonder if there might be an effect on that footage, or perhaps it is transformed that is triggering the failure.

One more question, do you get the "Your graphic card is unsupported" message upon launch of FCP X? GPU isn't an afterthought like it was in legacy FCP, it is vital to it's operation. Sorry you're MacBook is underpowered, that is a bummer :(

Please Log in to join the conversation.