Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Ken Burns Crashes FCP X

I am currently on 10.0.7 of FCP X. I have noticed this bug since the last release, but not prior to that. This occurs on my MacBook Pro (2.2 GHz Intel Core i7 running MacOS 10.6.8) and also on my 11" MacBook Air.


Basically, a third of the time that I add in a Ken Burns effect, the program crashes as soon as I go to adjust the START/END boxes. The effect will still run as long as I don't touch the default positions of the boxes. Once this occurs, I can not edit KB on that image, no matter how many times I restart FCP or the computer.


This is a relatively new issue to me that hasn't gone away. I have seen a prior thread from a year ago on this topic (https://discussions.apple.com/thread/3707812) but the suggestions all point to a user file size issue which I don't think is the case here. It is clearly a FCP bug that perhaps the Mac application development folks don't see on the combination of hardware/OS that they are using.


Any thoughts on this? Does anyone else see this bug?


Thanks in advance for any tips,


-Todd

Posted on Jan 8, 2013 10:11 AM

Reply
34 replies

Jan 8, 2013 5:58 PM in response to Tom Wolsky

Tom,


This happens on most movies I edit, but it may have something to do with size as it is usually after I'm 90 seconds or so into the flick. All my movies are 720P or 1080P and the content is either from a GoPro HD camera (any of the 3 generations) or my Nikon Coolpix S8100 (video and stills).


Today I was reminded that this problem happens with Ken Burns cropping video in addition to stills, so it is not limited to the file type. Seems tied to the KB effect and perhaps (?) the size of my project. I just don't see it on video as often as I rarely use this effect.


Would it be useful to post or email the crash information that FCP provides when it restarts? I always submit it to Apple, FWIW.


I do have my media on an external drive when running FCP. I use a USB slim drive for the Air and a FW GDrive on the Pro. It is possible that I only see this problem when running the USB slim drive, but I can't confirm that (I usually see it on the Air, but currently am using the slim drive on the Pro and see the problem.)

Jan 9, 2013 6:08 AM in response to Tom Wolsky

I have exactly the same problem as toddjb.

FCPX 10.0.6

OS 10.7.5

FCPX libraries reside on USB 3.0 drive (less than 50% full) running through USB 2 hub

Pictures are either D800 or Sony Nex 5N processed in Aperture and drug over to FCPX to where I want them. Files are JPEG in the range of 4300x3500 pixels.


Almost 100% of the time, whenever I click on the start/end of the Ken Burns, FCPX crashes.

Jan 9, 2013 6:28 AM in response to Tom Wolsky

Files are 8-bit RGB. Project needs to remain mobile until complete so it needs to sit on an external mobile drive. Picture file size is pretty standard in the photography industry so I would consider this to be a serious weakness in FCPX.


I believe the same phenomena has happened on projects run off my Thunderbolt drive (but I don't have a direct quantitative comparison).


I am curious as to the evidence or data which supports your suggestion?

Jan 9, 2013 7:24 AM in response to e2photo

I don't think the USB is a cause of the problem. I'm just pointing out that it's a poor idea to run a fast USB3 drive through a slow hub.


The image size can be a problem. It's much larger than standard video formats. If you have a great many files loaded in a project like this they have to all be held in RAM while the application processes them. The Ken Burns effect and its preview is processed entirely in the graphics card and held in RAM.


You should also look at how the image is procssed in Aperture. You might want to check what settings you have in Aperture for the image previews.


Would it be possible to post a few of these large images somewhere so I could try to reproduce the problem? Currently the effect doesn't produce the result you're getting with my media.

Jan 9, 2013 7:29 AM in response to e2photo

You have some sleuthing to do. Edit the pic down in size and see if that cures it. Buy or borrow another drive if possible or put the file on your local HD and see if that helps. Do one at a time. It is a pretty large file for use in FCPx but I also would agree that FCPx -should- handle it, but there's still a lot that FCPx doesn't do so I treat it like it's late beta. If you take the position that it -should- work you may never GET it to work so I'd start doing some investigation and see if you can bring an answer of your own back to the forum.

Ken Burns Crashes FCP X

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.