FCP X incredibly slow rendering!

I have FCP 10.3.4 on two computers. The first is a 3.2 GHz Quad-core Xeon desktop with 32gb RAM running OS 10.12.5. The second is a brand new MacBook Pro 2Ghz Intel Core i5 with 8 GB RAM running OS 10.12.6.


FCP X rendering is slow on both, but especially the laptop. To give you an idea of how slow, I have a 10 minute timeline consisting of nothing more than jpegs, text, and one png graphic. No filters, no motion, nothing. It takes at least 90 minutes to render, usually more.


I have discovered that eliminating the text speeds things up substantially. Why would that be?


I've trashed preferences. I have created a new user, which worked for a while then it got slow again. I have disconnected the external drive and used only the internal drive. Nothing is working.


Help me, Obi Wan Kenobi! You're my only hope!

Mac Pro, macOS Sierra (10.12.5)

Posted on Aug 10, 2017 10:58 AM

Reply
7 replies

Aug 11, 2017 12:31 PM in response to vv3vv3

This topic has been covered extensively. There are a number of reasons why FCPX rendering can be slow.


You've stated some of the specs of your computers: cores, RAM, OS, none of which really has that much effect on rendering (except maybe the extra RAM on the desktop — which helps). FCPX has undergone several changes since it's initial offering, in particular, the changeover to directing most of it's processing power to the GPU(s) (with the introduction of "Metal" — a core library for handling graphics). Also, there is a HUGE difference between using the Basic Title and some elaborately animated title perhaps involving 3D text. Without knowing the type(s) of Title...


JPEG and PNG images are not really designed for video editing, they're not a video codec. Every frame must be converted to video. Which codec you have set up for your project could also cause FCPX to move more slowly (usually ProRes 422 or one of its variants are the swiftest). If you're trying to use Uncompressed... ... ... why? (ProRes 4444 is better).


Any spinning platter disk is going to be slower than an SSD (or RAID) particularly if that disk is an external drive. It won't matter much if you have USB3 or Thunderbolt if the drive hardware is the bottleneck for speed.


Those are a few reasons why FCPX can move slowly.


One way for your type of project to get "up to speed" is to layout the images as you want them for the entire project and export just the visual media, then bring it back into FCPX as a video (recommend at least ProRes 422LT project for export). It's called "baking". You'll have to wait out the initial rendering, but you'll save a lot of time afterwards.

Aug 15, 2017 8:03 AM in response to fox_m

Hi fox_m,

The titles I am using are basic, non 3D titles, without any filters, keyframes, motion, or transitions. I'm using ProRes 422LT. The hard drive is SSD. There is no audio. When importing the jpegs, I'm making optimized versions.


Here's the vexing thing: rendering hasn't always been this slow. When I first began, it was lightning fast.

Aug 15, 2017 10:20 AM in response to vv3vv3

Then it's probably that you're running out of room on your hard drive (the one on which the library exists.) OSX needs 10% of the memory available on a hard drive in order to function efficiently. If this is the problem, then deleting all your (unnecessary) render files might (should, actually) make enough room, or consider moving your library to another drive with room.


If... you have plenty of room on your SSD (and it's an external), it might need some maintenance (Why Solid-State Drives Slow Down As You Fill Them Up). How you handle this situation may be dependent on the brand of the SSD. You should also investigate turning no TRIM on your Mac (How to Enable TRIM for Third-Party SSDs on Mac OS X). Some SSDs have firmware embedded that does this sort of operation as well, but if you read the fine print, you'll see you need to leave them on overnight, or something like that, every so often.


HTH

Aug 29, 2017 7:01 AM in response to fox_m

Hi fox,

I have discovered the problem lies with creating titles. Everything else runs smoothly as long as there are no titles on the timeline. I deleted FCP X and every associated file, event, project, et al before reinstalling. Still no luck. Rendering a 20 second title takes at least 20 minutes. Again, no effects applied. I will look up enabling TRIM as you suggested. I have tried both the internal SSD and an external hard drive with plenty of drive space, but still no improvement.

Aug 29, 2017 8:42 AM in response to vv3vv3

There might be a problem with fonts (though these usually result in crashes rather than slowness).

You say you already deleted preferences, which would be the first thing to try.

Did you try testing with a new library?


There also may be a conflict with other software that you may have installed.

You may want to run the diagnostic tool Etrecheck and post its report here.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

FCP X incredibly slow rendering!

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