First article of the New Year and it's one that a lot of people have asked for, real statistics on the Apple Pro Video Apps running on a new iMac Pro. Ben Balser had a new machine arrive just in time for the holiday break. He gave it a good test, it's fast, but it's not all great news.


It’s December 2017 and the new iMac Pro has been released. But how powerful is it really?

The specs on paper are impressive, at least. So how does it stand up to the late 2013 Mac Pro? In this article I will explore the differences, specifically pertaining to the Apple Pro Video Apps.

Let me begin as all good performance comparisons should be done, with the specs of the two Macs I’ll be testing.

My old late 2013 Mac Pro, purchased December 2013, is an 8 core, 3.0GHz Intel Xeon E5 CPU with 3.9GHz turbo boost.

With 32 GB RAM it has the dual AMD FirePro D700 CPUs with 6 GB of 1866MHz GDDR5 VRAM each. I had a 1 TB system drive and a 27” Apple 2560x1440 max, Thunderbolt Display. With the display this rig cost me $9,626.78 at that time.

IMP 2013MP

My new 2017 iMac Pro, purchase December 2017, is a 10 core, 3.0GHz Intel Xeon W CPU with 4.5GHz turbo boost.

Loaded with 64 GB of 2666MHz RAM it sports a Radeon Pro Vega 64 GPU with 16 GB HBM2 VRAM. It has a 2 TB SSD system drive and its own built-in 27” 5120x2880 max, 5K monitor.

With the included Magic Keyboard and Magic Trackpad, the list price of this Mac is $9,050.89, making it $545.89 less than my Mac Pro, and with much more power.

IMP back

Thus, I do not consider this the most expensive Mac model ever sold. I claim the late 2013 Mac Pro was the most expensive Mac ever sold.

Folks seem to forget what we paid for those 4 years ago. And if you could spec a top end late 2013 MP to match the cores, RAM, etc of a top end 2017 iMP, the MP would still be more expensive based on Apple’s pricing scheme for it, and considering you have to purchase a monitor or it’s simply not usable.

All my media and Libraries are on a Promise Pegasus 16 TB RAID 5, with Thunderbolt 2 connections. I will simply disconnect it from the old Mac Pro and reconnect it to the new iMac Pro. All of the following test were run strictly off of this RAID for a more real world performance test.

I am keeping my Thunderbolt Display as a secondary for the new iMac Pro, but won’t connect it up while these tests are run. I want the two systems to be as evenly matched as is reasonable.

Both Macs are running macOS 10.13.2 High Sierra with the current versions of FCPX 10.4.0, Motion 5.4.0 and Compressor 4.4.0.

Every test uses the same 4 R3D clips from various RED cameras, downloaded from the RED web site. None of these has any audio. I feel this will give a good idea of the performance differences, and can easily be extrapolated out to other codecs by experienced users.

A final note, I did a cold boot of each Mac to do these tests, so that there was no other tasks running from other apps from my regular work day. I also ran each test three times and used the average of those times. Times are shown as minutes:seconds.fraction of second.

IMP Desk1

Final Cut Pro X 10.4.0

Import Clips

My first test was for ingesting media. I copied in 4 clips of .R3D Red cinema files, copied to the Library, consisting of 4K, 5K and 8K clips. The image below shows more detail. All together they totaled 5.08GB in size.

Late 2013 Mac Pro = 0:36.53 seconds
2017 iMac Pro = 0:34.91seconds

IMP Files In Browser

Browser playback and skimming were both a pretty choppy on the MP. Definitely some lag, I’d need to make a proxy if I were really editing this stuff. On the iMP only the 8K clip had choppy playback and skimming, but not nearly as bad as the MP.

Proxy Media

I timed how long it took to convert all of that into to proxies, in the Browser after import. Again, the iMP is proving to be a huge time saver with these sorts of tasks.

Late 2013 Mac Pro = 1:50.86
2017 iMac Pro = 0:53.09

Optimized Media

Then I converted it all into Optimized media, in the Browser after import. The iMP was about 5:18 faster!

Late 2013 Mac Pro = 7:18.24
2017 iMac Pro = 2:00.20

I then deleted all Optimized and Proxy media for the rest of the tests.

Timeline Render

Next I placed all of the clips into a Project timeline to manually render. The 4 clips I used created a timeline 1:07:07 in duration.

Late 2013 Mac Pro = 5:30.32
2017 iMac Pro = 1:14.46

On the iMP in the Project Timeilne, the 8K clip had some jitter during playback, but all the other clips played smooth as silk. On the MP the 5K also stuttered just sightly, but it was not so bad you couldn’t edit with it. The 8K on the MP was so jittery it was impossible to deal with. Rendering made it play smoothly on the iMP and with slight jitter on the MP.

Multicam Playback and Render

I tested general playback performance and timeline rendering on a 4 angled Multicam clip in a Timeline using the 4 RED clips natively, 36:08 duration. Yes, I had to fake the multicam, but performance will be reflected honestly even so. I duplicated the shorter clips to make each angle as close to the same length as the longest as was reasonable.

Late 2013 Mac Pro = 2:53.40

On the MP playback was so jittery both during the edit and simply playing back after the edit, it was impossible to work with the native files. Proxy files would be the only way to realistically edit this multicam.

2017 iMac Pro = 0:39.20

Playback was quit a bit better on the iMP, but still choppy. Borderline enough to edit, with patience. Out of curiosity, I removed the 8K clip from the multicam, and playback for editing was much smoother. Still a slight jitter, but smooth enough to actually edit on. Either way, rendering on the iMP was amazingly faster.

IMP Multicam

File Export

I timed how long it took this multicam in its Project timeline (36:08 duration) to export to ProRes 422, H.264 (Web Hosting, faster encoding) at its original 4K frame size/rate (3840x2160, 23.98fps), from the original Recode RAW.

The MXF exported file was encoded to a 1080 HD 59.96fps file using a preset I created for my weekly broadcast deliveries. Note that I deleted all render files before exporting. And yes, the iMP is so much faster it ain’t funny.

Late 2013 Mac Pro:

ProRes HQ - 4:30.81
H.264 - 5:02.15
MXF - 4:33.74

2017 iMac Pro:

ProRes HQ - 0:50.26
H.264 - 0:45.06
MXF - 0:49.99

BruceX XML Test

Finally I ran the BruceX test, which you can find here on the forums. And as expected the iMP pretty much smoked the 2013 MP by 9.91 seconds.

Late 2013 Mac Pro - 35.55
2017 iMac Pro - 25.64

My Real World Test

I export a specific TV show (amongst others) weekly. It takes 1 full hour and change to export an H.264 preview copy and upload it to a GoogleDrive. I can set my watch by it. Doing the same on the iMac Pro took only 28 minutes.


Motion 5.4.0

I ran two Motion tests. One is just an emitter, the other is an actual 1:30 graphic heavy commercial spot. This gives me a good test, as I have to update seminar location & dates in one text panel, then export this once or twice every week for actual broadcast delivery.

The first test is possible with the help of our forum moderator Karsten Schuter, who’s pretty good with Motion. I used his 10 seconds long Motion project which contains a particle emitter with no external media at all, and LOTS of particles. This is pretty basic, but it make the point.

Late 2013 Mac Pro

H.264 - 16:19.60
ProRes 4444 XQ - 15:02.62

2017 iMac Pro

H.264 - 13:04.27
ProRes 4444 XQ - 13:07.78

The second test as I said before is from my actual weekly television broadcast work. A full minute and a half TV spot, graphics intensive, no particle emitters, lots of text. I was a bit disappointed in this test’s H.264 export, not sure what to say here.

Late 2013 Mac Pro

H.264 - 5:45.90
ProRes 4444 XQ - 9:44.55

2017 iMac Pro

H.264 - 7:32.29
ProRes 4444 XQ - 7:48.88

I’m finding some Motion projects are faster and some are slower to export H.264 on the new iMac Pro. Playback performance seems the same on both Macs, I did not find any differences there at all, but expected some improvement.

Motion obviously has not been optimized to take full advantage of the new iMac Pro hardware, which is a shame, as it has such great potential. AE on any hardware is slow as molasses. Motion is becoming a viable alternative for the work it can do. Why isn’t it taking full advantage of our hardware and being more consistent?

I would hope the next bug patch update (5.4.1) will give us some extremely vital improvements in playback and export for Motion. One would hope Apple is paying attention AND takes action in this direction

IMP MotionScreengrab showing Motion not using all cores

 IMP CPU Timeline Render FCPXComparison screen grab showing FCPX using all cores

Compressor 4.4.0

To test Compressor I took a 30 minute infomercial that I edit weekly in 1080HD, exported as ProRes 422, brought it to Compressor and encoded it as MXF for broadcast and as H.264 for the web, in the same batch.

Again, this is a real workflow for a real show I edit weekly, so this specific result tells me a lot about how much better my life will be after upgrading to the iMac Pro. I actually spend as much, if not more time waiting on exports as I do editing. This test result just made my day.

Late 2013 Mac Pro - 1:35:17.87
2017 iMac Pro - 31:01.67


CPU & GPU Differences

There are some significant differences between the CPUs and GPUs on these two Macs. The Mac Pro had an Intel Xeon E5 processor, while the iMac Pro has the newer Intel Xeon W processor. The “W” at the same clock speed and core numbers has huge advantages. It runs much faster RAM (2666MHz vs MP’s 1866MHz RAM), has faster and larger internal buffers, faster i/o and has a ton of technology in it, including processing tweaked for VR media development. Not to mention it over clocks quite a bit faster.

The Mac Pro had dual D700 GPUs which were nice at the time. But the newer Vega 64 GPU has huge advantages, also. The D700 had 6 GB of “GDDR5” VRAM. The GDDR5 is now out of date because it can’t be supported on the GPU chip very well, is larger and runs hotter, with only 3.5 teraflops performance. Not to mention its max resolution is lower than that of the Vega 64.

The Vega 64 uses HBM2 VRAM which is smaller, cooler, much faster, and easily integrated onto the GPU chip design. Direct connections make it much faster and more efficient. Smaller, faster, lower heat generation, the HBM2 VRAM goes a long way to helping the VEGA 64 be a very nice GPU. Not to mention the Vega 64 does 11 teraflops in single precision, and 22 in half precision. That’s a bit beyond the D700’s 3.5 (7 teraflops between the two D700’s installed).

From what we’ve seen on the OWC tear-down video, the SSDs are installed in pairs using a RAID configuration, which increases possible data throughput. Plus the sophisticated cooling system shows how Apple has achieved near total silence with the iMac Pro.



Well, the iMac Pro is a beastie, and a beautiful one at that. I love the elegant look of the late 2013 Mac Pro very much. But the space grey of the iMac Pro is really nice on my very nice desk. As you can see from the above numbers, the iMac Pro is Apple’s new king of media production for us in the industry.

A quick note about the 2017 iMac Pro, it is a beautiful machine visually. The screen is really bright and sharp, about the best image I’ve seen on a computer. The keyboard is fantastic. I have read a lot of reviews saying it lays too flat, but I don’t find that at all. I am a very proficient typist, and I am now typing faster and more accurately on this new wireless keyboard than ever. During the most intensive exports, the vent on the back had a good bit of heat pouring out of it, but it was dead quiet.

Most importantly for me, personally, if my render and export times are cut this much, 2018 is going to be a very nice year for my editing work.


Ben BalserBen Balser is a freelance producer and post-production specialist in the broadcast field, as well as an Apple Certified Master Trainer. He has used Final Cut Pro since its initial release over a decade ago. He also runs the web site offering free resources for Apple pro app users.