Ad

Thursday, January 23, 2014

Preliminary Late 2013 Mac Pro 8 core/dual 700 feedback

Reader Paul Antico of Anticipate Media passed along his initial thoughts on the new Mac Pro:




So.... my very preliminary testing with our new Mac Pro using the plugin I use most (filmconvert -FC), shows that Premiere CC needs more optimization for the dual GPUs. In fact, I'd say the CPU utilization is not up to snuff either.

I know FC only uses one GPU presently from the developer. That will change. In the meantime, using a couple of typical projects with that plugin as an example, I'm only seeing 25-45% speed up in exports over our maxed out late 2012 27" iMac exporting the same project. That's significant of course but not the 100%+ one would think we would be seeing at the least given the MacPro config of 8 cores and dual D700s. Premiere Pro CC seems in fact to never maximize CPU (never mind GPUs). I have yet, in my very limited testing, see it "pin the meters" like I did on the iMac.

Of course that's just testing now two short (under 5 min) projects, and it depends on what one is doing. Some stuff is much, much faster like Red Giant's Denoiser II or Warp Stabilizer VFX. The improvement there can be 3-4x faster anecdotally. I used to avoid them for speed reasons unless absolutely needed a lot of the time but now they are fast enough to rely on quickly. Other stuff unrelated top PPro CC like DxO PRIME noise removal on RAW stills is much faster too, as is Photoshop CC. Some effects like blur, sharpening, resize there are nearly instant now even on giga pixel files in Photoshop CC.

And of course FCPX is much faster on it but I hate the whole editing paradigm. The timeline is just horrid on it; simple things like replacing a word in someone's dialogue is a multi click, multistep process that is nearly instant in Premiere and most every other NLE. Just to try to see your whole timeline is a chore, to see what your edits and sound are in detail are problematic, trying to keep things in sync is a chore, and you can't even zoom your timeline window to full screen! It's just not for me until the fundamentals of the program change. The amount of time gained by using it for exports would be lost in counteracting some of Apple's "magnetic" timeline issues.

I'm sure Adobe will improve over time. They have to to stay competitive. In the meantime I'll take the 45%... but I wish I saw much more improvement given the cost and hardware differential.

Unfortunately, for now, the mainstream reviews I have seen regarding PPro performance on this machine were right. More to come as I continue to test.




2 comments:

Doug Fisher said...

@chrisfenwick: Love it or Hate it. You should hear @editblog criticism of #FCPX 10.1 http://t.co/SYUN9cvGOQ Scott has valuable insight.

Anticipate Media said...

I listened to that show and agree with what was said. However I also took a different approach after hearing the pluses. So many editors I talk to seem to love FCPX now that it's baked a few years. And it's tailor made to run on the new a Mac Pro.

As Philip Hodgetts angrily said to me, I need to keep an open mind. And while. His approach was suspect, he's right. I haven't used FCPX since it's first release. I'm willing to relearn it and see if the years of improvements make it worth reconsidering (I'd still use AE and premiere too)