FCPX is not fully utilizing CPU. Slow Rendering.

Question

Level 1

10 points

FCPX is not fully utilizing CPU. Slow Rendering.

When rendering in FCPX, I notice in the Activity Monitor that FCPX is only using 38-43% of available CPU and the rest of the CPU muscle is sitting there "idle." Does any one know how to correct this problem? This is nonsense. I should be rendering quickly and right now I am not moving faster than my 3 year old iMac with a 512 MB graphics card.

I've spent a bank roll on a top of the line 2012/13 iMac and external drive setup:

3.4 Ghz i7

32MB RAM

3 TB Fusion internal drive (only running system softward and other applications that are NOT opn when I am runing FCPX)

My FCPX files are on a Pegusus R6 12 TB Thunderbolt drive

NVIDIA GeForce GTX 680MX 2048 MB graphics card

Final Cut Pro X, OS X Mountain Lion (10.8.2)

Posted on Dec 23, 2012 3:14 PM

Reply

Answer 1

Dec 23, 2012 4:53 PM in response to SCS00001

As far as I know, FCPX uses the GPU for rendering in the timeline now...

Not sure, if it’s of any help...?

Check out “Mark Spencer” and “Steve Martin” talking about rendering in FCPX...

http://www.fcp.co/final-cut-pro/news/610-mark-spencer-and-steve-martin-talk-gpu- rendering-in-fcpx-and-the-use-of-multiple-cores-with-compressor

Regards

Nolan

Reply

Answer 2

SCS00001 Author

Level 1

10 points

Dec 23, 2012 5:21 PM in response to nolanscott

Hi Nolan,

Thanks for responding. My understanding from the video noted above is that that the iMac exploits GPU to assist with increased speed for project output related codec (uploading projects to Vimeo). Magic Bullett Looks, however, borrows GPU juicer to help render in the timeline. I'm stuggle with slow renders in the timeline and specifically, watching the absence of signifcant alocation of CPU to crunch the data to render modified clips.

Maybe I am missing something here, but that video seemed to be dicussing employing GPU to assist in output not timeline rendering.

Reply

Answer 3

Dec 24, 2012 4:33 PM in response to nolanscott

Rendering requires that data is both read and writen from/to your hard disk as well as any mathematical manipulation of the data. In your case, I suspect that the data is being read/writen as fast as the hard drive will permit, but the processing required is much less than what the CPU is capable of. Have a look at the disk performance figures in activity monitor. The advantage of the new processor will be realised in real time performance when applying FX and transitions to clips on the time line, it will be able to handle more FX without the need to render.

Reply

Answer 4

SCS00001 Author

Level 1

10 points

Dec 25, 2012 9:25 AM in response to geoffreyfromreading

Hi Nolan,

Thanks for responding. My understanding from the video noted above is that that the iMac exploits GPU to assist with increased speed for project output related codec (uploading projects to Vimeo). Magic Bullett Looks, however, borrows GPU juice to help render in the timeline. I'm stuggle with slow renders in the timeline and specifically, watching the absence of signifcant alocation of CPU to crunch the data to render modified clips.

Maybe I am missing something here, but that video seemed to be dicussing employing GPU to assist in output not timeline rendering.

Reply

Answer 5

Jan 20, 2013 8:33 PM in response to SCS00001

I thought the same thing too, I expected more from the GTX 680MX and FCPX performance. Do you have any issues with render of title effects like, far far away (changing the default font)

Maybe there's a driver update soon for the GTX 680.

Reply

Answer 6

SCS00001 Author

Level 1

10 points

Jan 21, 2013 5:43 PM in response to Supersharki

The GTX 680MX graphics card appears to be a part of the problem. It's not video editing friendly for pro level work. I use a program, Neat Video, for noise reduction and it bogs the whole rendering process down a lot! I have not notice long renders for title, but then, I don't use titles too much. I hope a driver update or beefier graphics card is in the works.

Reply