-
A (semi) dubious render speed example
Previous 2 projects were rendered on a Macbook Pro Retina (late 2012 i7, 8GB, 256SSD). Media stored on Lacie Thunderbolt 8tb RAID. Cache held on SSD and files being rendered to same RAID.
AE – semi complex multi layered 3minute composition with layers of colour correction, LUT loads and time remapping on BMCC ProRes footage, blurs, text and image layers, cameras and nested comps with some expressions. 1080 25p comp, Same format ProRes footage, outputting to ProRes HQ at 1080 25p.
Pr – 4 minute comp from BMCC ProRes film footage. Had LUT loaded, colour correction and some time remapping. Footage held on RAID. Shot at 1920×1080 25p in ProRes Film format. Outputting to ProRes HQ.
MBPR – Ae – 1hr 39m, Pr – 18m 14s
New Mac Pro – 6 core, 32GB RAM, D700, 512 SSD. Same thunderbolt RAID.
New Mac Pro – Ae – 10m 10s, Pr 3m50s
I make no assurances of my competency to give a totally fair test – I’ve not really done this too often before, but felt compelled to post the results after clicking render last night in Ae, going to make a coffee and coming back to 95% completion.
I’ve got some FCPX projects to render out later this week so I’ll try and post some times.
-
10 Replies
-
And yes, I see the contradictory nature of posting render time results from Adobe software in an FCPX forum. It seems that this is now one of the most active ones on the Cow, and a good place to look at apple hardware as any.
-
[Tom Sefton] “And yes, I see the contradictory nature of posting render time results from Adobe software in an FCPX forum. It seems that this is now one of the most active ones on the Cow, and a good place to look at apple hardware as any.”
Thanks for posting and feel free to post more results!
Steve Connor
There’s nothing we can’t argue about on the FCPX COW Forum
-
What were your multiprocessor settings in AE?
-
The FCP X users here are pretty open-minded about Premiere. I wish the converse were also true. 🙁
-
Render multiple frames simultaneously is enabled with 4GB per CPU.
-
[Brett Sherman] ” The FCP X users here are pretty open-minded about Premiere. I wish the converse were also true. :(“
I routinely switch back and forth between both, so it is.
-
[Tom Sefton] ” Render multiple frames simultaneously is enabled with 4GB per CPU.”
That’s really damn impressive. Interested to know how my nMBPr would hold up with it’s 2GB in tota.
-
Okay, I admit… the title had me. Any post that honest is worth reading.
Those results look promising, and I don’t think it matters what you used, as long as it’s consistent in the testing…
Mitch Ives
Insight Productions Corp.“Criticism may not be agreeable, but it is necessary. It fulfills the same function as pain in the human body. It calls attention to an unhealthy state of things.” – Winston Churchill
-
We are all professionals here and welcome any tips that help our daily lives easier in this field.
Anyone test the Nightflight AE file on a nMP?
I have to find mine (lost in server land) but not sure if it makes sense in this case.
What are people using to benchmark FCPX?
My tests are all Black Magic Disk Speed Utility driven.
I live in R3D world so Im always trying to play catch up to our ROCKET. -
Good to see some AE/PP results. My colleague Ben Balser and I did some FCP X speed tests recently on all the Macs we had handy:
https://www.macprovideo.com/hub/final-cut/final-cut-pro-x-performance-test
He has a new Thunderbolt RAID and I have a slower homemade USB3 software RAID, which explains a lot of the differences, but some of the results are very interesting. But even the complex effects export was much faster than realtime on a modern Mac. A two minute 1080p24 sequence (ProRes HQ, output to ProRes, with Directional Blur, Rain, and Underwater effects applied) took just 21 seconds to export on the Mac Pro, and 41 seconds on a new iMac with a slower drive.
Also note: most of the time, it’s much faster if you don’t render before exporting.
Reply to this Discussion! Login or Sign Up