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 11 Dec 2013 07:23 #35633

  • zaz0n
  • zaz0n's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 2
  • Karma: 0
mid 2010 27 inch iMac

2.8 GHz Intel Core i5
16 GB 1333 MHz DDR3 RAM
1TB WDC WD1001FALS-40Y6A0 Hard Drive
ATI Radeon HD 5750 1024 MB Graphics Card

exported to internal 7200 rpm drive

119 seconds
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 11 Dec 2013 12:40 #35652

In anticipation of the new MacPro... :)

FCP X 10.0.8 (trial)
MacBookAir 13" late 2011; 1,7 GHz Intel Core i5; 4 GB 1333 MHz DDR3; Intel HD Graphics 3000 384 MB; OS X 10.9 (13A603)

Export to LaCie 1TB Rugged Thunderbolt

26min 3sek or 1563 seconds :(
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 19 Dec 2013 11:33 #36441

B)
Great benchmark just tried running it under the latest FCPX 10.1 and it did work, claimed to have a problem sharing the file?

Anyone else?
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 19 Dec 2013 13:08 #36463

  • NocoDave
  • NocoDave's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 828
  • Thank you received: 122
  • Karma: 12
I just tried it on 10.1 and it failed to export the file, I've not got time to look further into why at the moment.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 19 Dec 2013 13:21 #36466

  • alex4D
  • alex4D's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 465
  • Thank you received: 250
  • Karma: 36
Same here...



I'll try and find a workaround



@Alex4D
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 19 Dec 2013 13:57 #36475

  • Soundwise
  • Soundwise's Avatar
  • OFFLINE
  • Gold Boarder
  • Posts: 184
  • Thank you received: 39
  • Karma: 7
136 sec on 10.0.9 and 80 sec on 10.1!

MBP late 2011 16 GB Ram, export to int. SSD

Export was fine and also played on QT player.


EDIT: Forgot to change the codec, so this result was with ProRes. H.264 gave the Share error.
Last Edit: 19 Dec 2013 19:05 by Soundwise.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 19 Dec 2013 16:13 #36490

The mystery deepens - I might try the obvious an dreboot just for giggles.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 19 Dec 2013 18:18 #36510

Quick update.

Rebooted, re-imported project, still no luck. Will try on my MBPR...
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 19 Dec 2013 19:01 #36520

  • alex4D
  • alex4D's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 465
  • Thank you received: 250
  • Karma: 36
The choice of H.264 export seems to be the problem. ProRes is OK.

A repeatable bug to report to Apple...

Which I'll do right now.



@Alex4D
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 19 Dec 2013 19:18 #36529

  • freeform
  • freeform's Avatar
  • OFFLINE
  • Senior Boarder
  • Posts: 66
  • Thank you received: 2
  • Karma: 1
You guys all seem like aces..
do you think the Radeon 7950 is still the way to go to get a 4 core PM to jam faster with fcpx?

(I'm just trying to get another year out of this pm before I get the new guy...
I've been dragging my feet since I had hoped the 7950 price would drop but they haven't, they're still 450+. )

THX!
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 20 Dec 2013 01:03 #36614

Not an ace, most of my work is simply CK work and more recently basic colour correction and compositing.

But, I do run some pretty large 1080p jobs 2-3 times a year for my kids productions which run about 2 hours of footage from 2-3 cameras and multiple audio sources, lots of transitions etc and it's here that having the grunt is sanity saving.

Regarding your 7950 vs 5780 question, I have both and will run Bruce's benchmark on both over the weekend and we'll see what the result is. I am pretty confident that the 5K benchmark doesn't really hit CPU OR disk that hard (it writes less than 20MB/sec, more than easily managed by a HDD), so this should be a great test.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 20 Dec 2013 03:46 #36633

  • freeform
  • freeform's Avatar
  • OFFLINE
  • Senior Boarder
  • Posts: 66
  • Thank you received: 2
  • Karma: 1
thanks.. any info on how well the 7950 really helps out fcpx is welcome.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 20 Dec 2013 16:40 #36716

  • MiniEditor
  • MiniEditor's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 7
  • Thank you received: 2
  • Karma: 0
I tried this on my MacMini 2012 with 16Gigs of ram, an SSD and TB attached hd and the integrated AMD 6630 graphics card, a BTO option and FCPx just sat there, nothing happened - spinning beach ball! On re reading the first post I see the words large amount of GPU Ram and the kicker is that I only have 256Mb! You may ask who the hell edits with just 256Mb of Graphics Ram on a $800 machine but I have been for the past 1.5 years!

Now here is the interesting thing, fired up my MBA, mid 2012 and it worked just fine:

Mac Book Air - Mid 2012
2 Ghz i7 - 8 gigs of Ram
Graphics Intel HD Graphics 4000 - 1024 MB
4mins and 30sec = 270sec


The secret here is to max out your ram on a the Air and this then assigns more ram to graphics card. My buddy got a newer Mini with the 4000HD card and he is seeing 1.5Gb or so GPU ram I think.

But looking at the limited RAM you may think it's time to dump the mini but the Mini, even with it's limited GPU WAS FASTER on some tests I did (std HD 1080p - looking at my buddies machine with HD4000 and 1.5 Gb or GPU RAM ) when I wasn't maxing out the GPU ram so I'm not sure what we can say from this test ???? Like I said, my mini has been able to open and edit a big projects with 1200 clips and I run a second monitor! Poor little machine! I also make sure FCPx is the only program running but sometime have a few others open.

I think we need a series of tests, this one is great but also a test to convert to proxy and other stuff. 4k is great but I wonder if it won't perhaps be like Super Audio - you know, the standard that superseded the CD ....
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 21 Dec 2013 02:31 #36800

  • wdevn
  • wdevn's Avatar
  • OFFLINE
  • Gold Boarder
  • Posts: 245
  • Thank you received: 15
  • Karma: 1
Old speed test with 10.1. 69.42 sec. New speed test with 10.1 37.37 sec!


Late 2012 iMac 27 "
3.4 Ghz Intel i7
Memory: 24 GB 1600 Mhz DDR3
Graphics NVIDIA GeForce GTX 680MX 2048 MB
Software: OS X Mavericks 10.9.0
Output to: USB3 exteral drive


CUDA Driver Version: 5.5.28
LLAP,
James
Taipei, Taiwan
Last Edit: 21 Dec 2013 02:31 by wdevn.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 21 Dec 2013 02:34 #36801

  • freeform
  • freeform's Avatar
  • OFFLINE
  • Senior Boarder
  • Posts: 66
  • Thank you received: 2
  • Karma: 1
Woo hoo!
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 21 Dec 2013 03:24 #36805

  • daviddelreal
  • daviddelreal's Avatar
  • OFFLINE
  • Gold Boarder
  • Posts: 238
  • Thank you received: 10
  • Karma: 4
wdevn wrote:
Old speed test with 10.1. 69.42 sec. New speed test with 10.1 37.37 sec!


Late 2012 iMac 27 "
3.4 Ghz Intel i7
Memory: 24 GB 1600 Mhz DDR3
Graphics NVIDIA GeForce GTX 680MX 2048 MB
Software: OS X Mavericks 10.9.0
Output to: USB3 exteral drive


CUDA Driver Version: 5.5.28

How did you get it to work? I still get this error message:

brucex-share-operation-failed.png
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 21 Dec 2013 04:18 #36810

  • Colin McQ
  • Colin McQ's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 1
  • Karma: 0
OSX 10.9.1
FCPX 10.0.9

Early '08 3.2 GHz Octo-Core Intel Xeon
AMD Radeon HD 7970 3GB

~45 seconds exporting to 8 bay G-Speed es (2x4bay G-Speed aS' stripped to RAID 5)
~44 seconds exporting to desktop

Both hit 50% (finished rendering) on the render wheel @~38 seconds then took about 8 more for the QT window to pop up.
Last Edit: 21 Dec 2013 04:21 by Colin McQ. Reason: Added software versions for precision
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 21 Dec 2013 06:40 #36822

  • wdevn
  • wdevn's Avatar
  • OFFLINE
  • Gold Boarder
  • Posts: 245
  • Thank you received: 15
  • Karma: 1
Not at all because I sent the output file to ProRes not H.264.
LLAP,
James
Taipei, Taiwan
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 21 Dec 2013 06:42 #36823

  • daviddelreal
  • daviddelreal's Avatar
  • OFFLINE
  • Gold Boarder
  • Posts: 238
  • Thank you received: 10
  • Karma: 4
wdevn wrote:
Not at all because I sent the output file to ProRes not H.264.

Ah, gotcha. Thanks.
The administrator has disabled public write access.

BruceX: Try this new Final Cut Pro X benchmark 21 Dec 2013 07:31 #36828

  • NocoDave
  • NocoDave's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 828
  • Thank you received: 122
  • Karma: 12
Not at all because I sent the output file to ProRes not H.264.

Did you output the original test to ProRes too? If it was H.264 they won't compare.
The administrator has disabled public write access.