Welcome, Guest
Username: Password: Remember me

TOPIC: BruceX: Try this new Final Cut Pro X benchmark

BruceX: Try this new Final Cut Pro X benchmark 29 Oct 2013 21:35 #33437

  • alex4D
  • alex4D's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 462
  • Thank you received: 248
  • Karma: 36
To help people work out which Macs work best with Final Cut Pro X, it is useful to refer to a standard speed test.

In the past we've had the 'Far Far Away' test, in which you time how long it takes to render the 10 second long standard 'Far Far Away' title. This was useful to test to see if Mac's memory or GPU configuration was good enough to run Final Cut Pro X well.

The 'Far Far Away' test showed that my 2009 MacBook Pro was severely limited by only having 4GB of RAM installed. Due to a bug in 10.0.9, it took 79 minutes. After I upgraded the memory to 8GB, the same test took 65 seconds.

With more recent Macs, the test is proving less useful. In another topic 'qbe' asked me to do the same test on my new Late 2013 MacBook Pro using first the internal Iris Pro graphics system, then using the discrete GeForce GT 750M 2GB GPU. The results seemed counterintuitive:

MacBook Pro late-2013 Discrete GeForce GT 750M 2GB 18.8 seconds
MacBook Pro late-2013 Intel Iris Pro 1GB 19.2 seconds

Could there be such a small advantage in using a specialised GPU? In this case there is.

On the one hand, early testing shows that Iris Pro graphics are better than many expected. Take a look at a new post at Bare Feats:
In the past we sneered at the integrated GPUs and their puny performance. Not any more. The Intel Iris and Iris Pro are every bit the match or master of discrete NVIDIA Mobile GPUs -- at least when it comes to OpenCL acceleration.
from www.barefeats.com/rmbpc.html

Although it is great news that integrated GPUs are getting better, many are worried that the MacBook Pros should be avoided until Iris Pro has improved a little more.

In practice, the 'Far Far Away' test didn't stress the integrated GPU in the MacBook Pro 15" enough.


I've come up with a test that shows the differences between these GPUs and other Macs...

The BruceX benchmark

BruceX is a small Final Cut Pro X XML file that you import into Final Cut Pro. It creates a very short timeline at the highest possible standard resolution that Final Cut can handle: 5120 by 2700 (at 23.975 fps). It uses standard Final Cut generators, titles and transitions. As it uses many layers of complex content, it requires lots of GPU RAM.

The benchmark is based on timing how long a Mac configuration takes to export the project to disk.

To use this import the XML file at

Alex4D.com/BruceX_Test.zip

...and time the export of a 5K master file from the timeline.

1. Have both QuickTime player and Final Cut Pro X open at the same time.

3. In Final Cut Pro X, go to 'Final Cut Pro:Preferences…' – in the Playback tab make sure 'Background Render' is off.

3. Use the 'File:Import:XML...' command to import 'BruceX Test - 5K.fcpxml' to create a very short but complex 5K project.

4. Click the new 'BruceX Test - 5K ' timeline (this makes the Share command selectable)

5. Export the QuickTime movie by choosing "File:Share:Master File...'

6. In the dialogue box that appears, click the 'Settings' Tab

7. In the 'Video Codec' section choose 'H.264' (edited to add - many people have got errors with H.264, so use ProRes422 instead you you have a problem - some times are given with different flavours of ProRes, but each person usually mentions which they've used when reporting their results)

8. In the 'Open With' section, choose 'QuickTime Player'

9. Click the 'Next' button in the bottom-right of the dialogue box

10. In the Save sheet, choose a name and location for the export - export to your fastest drive connected using your fastest connection.

11. Get your stopwatch ready and time from when you click 'Save' until you see the movie open up in QuickTime Player.

12. Quit and restart Final Cut to clear some cached renders and time the export again. Quit and restart Final Cut again, export a third time. The BruceX value is the average of the three export times.



My results


iMac mid-2011 27" 16GB RAM / Radeon HD 6970M 2 GB 73 seconds

MacBook Pro late-2013 Discrete GeForce GT 750M 2GB 88 seconds
MacBook Pro late-2013 Intel Iris Pro 1GB 163 seconds

( To choose which GPU to use for the test on my MacBook Pro with more than one, I used gfxCardStatus by Cody Krieger - a Shareware app downloaded from gfx.io )




Here's a summary of the results so far (including those sent to me directly by Rob-ART of Bare Feats):



Hope people find this a useful way to compare Mac configurations,



@Alex4D
Last Edit: 09 Nov 2014 18:36 by alex4D.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 29 Oct 2013 22:18 #33444

  • fcpguru
  • fcpguru's Avatar
  • OFFLINE
  • Gold Boarder
  • Posts: 268
  • Thank you received: 24
  • Karma: 5
iMac 27" with 2GB Radeon Card 32GB RAM exporting to a Promise R4 RAID - 58sec

One note, I made sure to have background rendering off, so the timeline didn't begin to render - not sure that matters since the export is to H.264, but wanted to double check.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 29 Oct 2013 23:31 #33453

  • alex4D
  • alex4D's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 462
  • Thank you received: 248
  • Karma: 36
Matthew,

I don't think frames rendered as part of background rendering get used for export, but I'll add that stage to the instructions. Thanks.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 30 Oct 2013 01:38 #33459

  • Darren Roark
  • Darren Roark's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 481
  • Thank you received: 61
  • Karma: 13
I'm on a "custom built mac" with an ivy bridge 3770k 3.5ghz, 32GB memory to a 128gb ssd running mavericks. The GPU is an XFX AMD HD 7950 with 3GB. My Geekbench score averages about 14,900.

It did it three times in a row in 37-38 seconds. One very odd thing, I had QT open and bg rendering off just like you said, but when it opened in QT, it was just a black clip. In VLC it plays great. I also to be safe tossed all render files.

Is the whole thing only 2 seconds? If it's longer that could explain my suspicious score.

Also Alex as always you are a genius, great idea.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 30 Oct 2013 01:47 #33460

  • Julian
  • Julian's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 377
  • Thank you received: 32
  • Karma: 5
Darren Roark wrote:
I'm on a "custom built mac" with an ivy bridge 3770k 3.5ghz, 32GB memory to a 128gb ssd running mavericks. The GPU is an XFX AMD HD 7950 with 3GB. My Geekbench score averages about 14,900.

It did it three times in a row in 37-38 seconds. One very odd thing, I had QT open and bg rendering off just like you said, but when it opened in QT, it was just a black clip. In VLC it plays great. I also to be safe tossed all render files.

Is the whole thing only 2 seconds? If it's longer that could explain my suspicious score.

Also Alex as always you are a genius, great idea.


Yeah, in QT it just showed a black video as well, about 55 seconds to export on:

2011 i7 iMac 3.4Ghz
SSD
Mavericks
FCPX 10.0.9
16GB RAM
2GB AMD 6970M (recalled)
external Thunderbolt drive that typically reads/writes between 160 and 180MBps.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 30 Oct 2013 02:19 #33462

  • Darren Roark
  • Darren Roark's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 481
  • Thank you received: 61
  • Karma: 13
Wow, then this 7950 is really something. Or it's the RAM, which I could do a test with 16GB.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 30 Oct 2013 04:03 #33463

  • Bobbyco
  • Bobbyco's Avatar
  • OFFLINE
  • Expert Boarder
  • Posts: 139
  • Thank you received: 21
  • Karma: 4
I have a mid-2010 15" MB Pro 2.8G i7, top of the line for that year, 8GB RAM, FCPX.app & OS on a 128GB SSD, FCPX Event/Project folders on an internal Seagate Momentous hybrid 750GB SSD.
Sad, I quit the test when I got to 10% in 1:27 seconds. Fans whirring away. Now that's why I'm looking to upgrade :woohoo:
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 30 Oct 2013 08:46 #33467

  • paurray
  • paurray's Avatar
  • OFFLINE
  • Platinum Boarder
  • Absence of Quality is the essence of squareness.
  • Posts: 390
  • Thank you received: 14
  • Karma: 3
Hi alex4D

Love the idea also great name for the test.

Brings my 2011 Power book to its knees

2GHz Intel Core i7+4GB 133 Hhz DDR3
internal 256gb SD Drive

Am 5 minuets in into test and at 2%

I think at the current rate it is going to be something like 5% every 20 minutes! 7 hours maybe!?!

I need to put another 4GB RAM in the computer anyway but can not imagine it being a deal breaker!

Now I wonder if the Blackmagic 4K Ultra Studio that I just happen to have sitting on my desk would help?

:ohmy:

Paul
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 30 Oct 2013 10:18 #33469

  • Dave_EP
  • Dave_EP's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 388
  • Thank you received: 37
  • Karma: 6
Post removed for clarity - see next post.
Last Edit: 30 Oct 2013 10:54 by Dave_EP.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 30 Oct 2013 10:29 #33470

  • alex4D
  • alex4D's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 462
  • Thank you received: 248
  • Karma: 36
I'm not sure why QuickTime player can't play the output video, but the timings still apply.

Are you using QuickTime Player 7?

It still works in Mavericks - you can download it from support.apple.com/kb/DL923

Have you tried using VLC or another player?

It is common for Final Cut to render anything but ProRes by going from 0 to 50% and suddenly finishing - so don't worry about that. The first 50% is for the render, Final Cut allows the other 50% for the encoding to non-ProRes files.


@Alex4D
Last Edit: 30 Oct 2013 10:30 by alex4D.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 30 Oct 2013 10:52 #33471

  • Dave_EP
  • Dave_EP's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 388
  • Thank you received: 37
  • Karma: 6
ok I don't feel so bad it only going to 50% ;) I guess I never noticed before.

So,

MacPro 3,1 8 core 2.8Ghz (early 2008) 16GB 5770 (1GB) - 133 seconds

MacBookPro 17" 2.5Ghz i7 16GB HD6770M (1GB) - 136 seconds

Mac Mini 2.3Ghz i7 16GB HD4000 - 223 seconds

Now, this is still kinda odd. On this test the MacPro out performs the MBP, yet in every single test I've done on HD footage, colour board in FCPX etc the MBP has been much faster than the MacPro, by up to double the speed and never less than 1/3 faster. Any reason for this ?
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 30 Oct 2013 11:11 #33472

  • kzi2006
  • kzi2006's Avatar
  • OFFLINE
  • Junior Boarder
  • Posts: 20
  • Thank you received: 2
  • Karma: -5
hackintosh 3.6 Intel Core i7
16 Gb, GTX660TI 2 GB
Mountain Lion, FCPX 10.0.9

110 sek
Last Edit: 30 Oct 2013 11:14 by kzi2006.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 30 Oct 2013 11:40 #33474

  • alex4D
  • alex4D's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 462
  • Thank you received: 248
  • Karma: 36
Dave_EP,

I don't know why your Mac Pro seemed to do so much better than on other tests.

Perhaps this test works better on multiple core machines? I'm looking forward to seeing it on the new Mac Pros!


@Alex4D
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 30 Oct 2013 12:41 #33477

  • anickt
  • anickt's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 388
  • Thank you received: 57
  • Karma: 12
I get 78 seconds

MId-2011 iMac 27"
3.4 Ghz I7
32 GB RAM
AMD Radeon HD 6970M 1 GB
OS 10.8.5
Promise R4

I'll try again once I update to Mavericks
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 30 Oct 2013 13:54 #33478

  • Tom Wolsky
  • Tom Wolsky's Avatar
  • OFFLINE
  • Moderator
  • Posts: 3629
  • Thank you received: 589
  • Karma: 97
Getting black video as well. Didn't run a time trial, but the result was black in both in both QT players, though movie inspector shows the correct information.

P.S. Works correctly in ProRes.
Last Edit: 30 Oct 2013 14:17 by Tom Wolsky.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 30 Oct 2013 14:17 #33480

  • jefharris
  • jefharris's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 8
  • Karma: 0
Except for the RAM this machine is as is out of box.

IMac 27inch, Late 2012
Processor 3.4 GHz Intel Core i7
Memory 32 GB 1600 MHz DDR3
Graphics NVIDIA GeForce GTX 680MX 2048 MB
Software OS X 10.8.5

78 seconds
Last Edit: 30 Oct 2013 17:39 by jefharris.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 30 Oct 2013 14:25 #33481

  • tpayton
  • tpayton's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 949
  • Thank you received: 135
  • Karma: 25
iMac 27" 3.4 i7
24GB Ram
Nvidia 680MX 2GB
OWC Raid 5 - thunderbolt esata adapater
10.9

First run: 94
Second run: 88
Last Edit: 30 Oct 2013 14:26 by tpayton.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 30 Oct 2013 14:26 #33482

"Save operation could not be completed" when clicking Import.

??????

rick
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 30 Oct 2013 14:45 #33483

  • tpayton
  • tpayton's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 949
  • Thank you received: 135
  • Karma: 25
My system (above) Reran with ProRes:

First run (with Preparing media to share): 89 seconds.
Second Run: 85 seconds

This plays just fine in QT Player. Perhaps 5K h264 isn't supported yet.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 30 Oct 2013 15:55 #33493

  • rickytin
  • rickytin's Avatar
  • OFFLINE
  • Gold Boarder
  • Posts: 165
  • Thank you received: 9
  • Karma: 3
MacPro4,1 early 2009 2 x 2.93 GHz Quad-Core Intel Xeon
20GB RAM
ATI Radeon HD 5870 1024 MB
OS X 10.8.5
G-SPEED eS Pro 8TB
In Quicktime 7 black clip in VLC OK

Test: 103 sec
The administrator has disabled public write access.